[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-02-09 Thread Tidhar Klein Orbach
I have the same issue with my Lenovo Thinkpad. The internal mic doesn't
work, but when using a headset the mic works.

Details:

❯ uname -a
Linux my-laptop 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

❯ arecord -l
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 2: ALC285 Alt Analog [ALC285 Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

System Information
Manufacturer: LENOVO
Product Name: 20QES0H400
Version: ThinkPad X1 Carbon 7th

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1840725

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862566] Re: Corrupt sound played

2020-02-09 Thread Daniel van Vugt
Can you please test a newer kernel? Either from:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.2/

or just live boot Ubuntu 19.10:

  https://ubuntu.com/download/desktop

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1862566

Title:
  Corrupt sound played

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every once in a while, I get sort of static-y sound with a degree of
  echo.  This affects all sounds - within browser, using `play` from the
  terminal, etc.  I can solve it by restarting pulseaudio. However, when
  I do that, I no longer get the terminal beep.

  Ubuntu 18.04

  It's not common, and I can't find anything wrong in the system log.

  To restart, I killed the process:
/usr/bin/pulseaudio --start --log-target=syslog

  It restarts itself, and audio generally seems to be working now.
  However, I now see in the system log things like:

  
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: 
". Reason: Missing track ID in msid attribute.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed 
to create native session description. Type: "offer" SDP: "v=0\r\no=- 
4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 
0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 
0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 
0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256
 
23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid:
 \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 
cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 
mslabel:-\r\na=ssrc:4203958806 label:\r\n"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.5
  ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
  Uname: Linux 4.15.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 22:02:47 2020
  InstallationDate: Installed on 2016-05-30 (1350 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago)
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10DAI
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: SMC X10
  dmi.product.name: X10DAi
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862566/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862566] Re: Corrupt sound played

2020-02-09 Thread Daniel van Vugt
I think we should ignore the log messages after restarting and focus on
the original problem of corrupt sound. Bugs should only cover a single
issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1862566

Title:
  Corrupt sound played

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every once in a while, I get sort of static-y sound with a degree of
  echo.  This affects all sounds - within browser, using `play` from the
  terminal, etc.  I can solve it by restarting pulseaudio. However, when
  I do that, I no longer get the terminal beep.

  Ubuntu 18.04

  It's not common, and I can't find anything wrong in the system log.

  To restart, I killed the process:
/usr/bin/pulseaudio --start --log-target=syslog

  It restarts itself, and audio generally seems to be working now.
  However, I now see in the system log things like:

  
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: 
". Reason: Missing track ID in msid attribute.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed 
to create native session description. Type: "offer" SDP: "v=0\r\no=- 
4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 
0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 
0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 
0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256
 
23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid:
 \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 
cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 
mslabel:-\r\na=ssrc:4203958806 label:\r\n"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.5
  ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
  Uname: Linux 4.15.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 22:02:47 2020
  InstallationDate: Installed on 2016-05-30 (1350 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago)
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10DAI
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: SMC X10
  dmi.product.name: X10DAi
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862566/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-02-09 Thread Nivedita Singhvi
Hello Edwin,

Here is more information on the issue we are seeing wrt dropped 
packets and other connectivity issues with this NIC.

The problem is *only* seen when the second port on the NIC is 
chosen as the active interface of a active-backup configuration. 

So on the "bad" system with the interfaces:

enp94s0f0 -> when chosen as active, all OK
enp94s0f1d1 -> when chosen as active, not OK

I'll see if the reporters can confirm that on the "good" systems,
there was no problem when the second interface is active.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1853638

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this particular case description, the nodes are USRP x310s. However, we 
have the same issue with N210 nodes dropping samples connected to the BCM57416 
NetXtreme-E Dual-Media 10G RDMA Ethernet device.

  There is no problem with the USRPs 

[Touch-packages] [Bug 1862566] [NEW] Corrupt sound played

2020-02-09 Thread Jerry Quinn
Public bug reported:

Every once in a while, I get sort of static-y sound with a degree of
echo.  This affects all sounds - within browser, using `play` from the
terminal, etc.  I can solve it by restarting pulseaudio. However, when I
do that, I no longer get the terminal beep.

Ubuntu 18.04

It's not common, and I can't find anything wrong in the system log.

To restart, I killed the process:
  /usr/bin/pulseaudio --start --log-target=syslog

It restarts itself, and audio generally seems to be working now.
However, I now see in the system log things like:


Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: 
". Reason: Missing track ID in msid attribute.
Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed 
to create native session description. Type: "offer" SDP: "v=0\r\no=- 
4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 
0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 
0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 
0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256
 
23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid:
 \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 
cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 
mslabel:-\r\na=ssrc:4203958806 label:\r\n"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.5
ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
Uname: Linux 4.15.0-87-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb  9 22:02:47 2020
InstallationDate: Installed on 2016-05-30 (1350 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago)
dmi.bios.date: 01/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X10DAI
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: SMC X10
dmi.product.name: X10DAi
dmi.product.version: 123456789
dmi.sys.vendor: Supermicro

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic package-from-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1862566

Title:
  Corrupt sound played

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every once in a while, I get sort of static-y sound with a degree of
  echo.  This affects all sounds - within browser, using `play` from the
  terminal, etc.  I can solve it by restarting pulseaudio. However, when
  I do that, I no longer get the terminal beep.

  Ubuntu 18.04

  It's not common, and I can't find anything wrong in the system log.

  To restart, I killed the process:
/usr/bin/pulseaudio --start --log-target=syslog

  It restarts itself, and audio generally seems to be working now.
  However, I now see in the system log things like:

  
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: 
". Reason: Missing track ID in msid attribute.
  Feb  9 22:05:38 cerberus update-notifier.desktop[4802]: 
[8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed 
to create native session description. Type: "offer" SDP: "v=0\r\no=- 
4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 
0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 

[Touch-packages] [Bug 1655189] Re: Cannot record videos into Theora

2020-02-09 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues 
#134
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/134

** Changed in: xorg-server
   Importance: Medium => Unknown

** Changed in: xorg-server
 Remote watch: freedesktop.org Bugzilla #99342 => 
gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #134

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libtheora in Ubuntu.
https://bugs.launchpad.net/bugs/1655189

Title:
  Cannot record videos into Theora

Status in guvcview:
  Confirmed
Status in recordmydesktop:
  Confirmed
Status in theora:
  Unknown
Status in X.Org X server:
  Unknown
Status in libtheora package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Record a video using the Theora codec.

  RESULT:
  - In the recording the image is frozen or broken.

  RELEVANT DETAILS:
  - Doesn't matter which application you use to record or play the video.
  - I'm attaching samples from various programs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libtheora0 1.1.1+dfsg.1-8
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 01:17:54 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   libogg0 1.3.2-1
   multiarch-support 2.23-0ubuntu5
  InstallationDate: Installed on 2013-01-25 (1445 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: libtheora
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (157 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/guvcview/+bug/1655189/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862341] Re: Errors thrown at boot: Security

2020-02-09 Thread Daniel van Vugt
I can't see that error message in any of the attached logs. Can you
please collect a full system log:

  journalctl -b0 > journal.txt

and attach it here?

** Tags added: vmware vmwgfx

** Package changed: xorg (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862341

Title:
  Errors thrown at boot: Security

Status in Ubuntu:
  Incomplete

Bug description:
  DETAILS:

  Version:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  xorg:
Installed: 1:7.7+19ubuntu13
Candidate: 1:7.7+19ubuntu13
Version table:
   *** 1:7.7+19ubuntu13 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Xorg, at boot, through a couple of errors:

  [ error ] display server started at tty -1

  For 20 seconds, the xorg server went on complaining the same issue. I
  tried to ssh into the virtual machine in VirtualBox, and it simply
  logged in without a password.

  Note:
Automatic Login was disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.438
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 11:41:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1862341/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors

2020-02-09 Thread Daniel van Vugt
Good news of sorts: nautilus-desktop which is what provides the desktop
icons in 18.04 is no longer supported and has been replaced in later
Ubuntu versions.

** Package changed: xorg (Ubuntu) => nautilus (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862500

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
  InstallationDate: Installed on 2019-12-20 (50 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 3212AP3
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT63AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3212AP3
  dmi.product.sku: LENOVO_MT_3212
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862500/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862377] Re: WXtoimg

2020-02-09 Thread Daniel van Vugt
Please explain what kind of problem you are experiencing.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862377

Title:
  WXtoimg

Status in Ubuntu:
  Incomplete

Bug description:
  No information

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  Uname: Linux 4.16.8-xanmod9 x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb  7 16:11:25 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2019-08-19 (171 days ago)
  InstallationMedia: Skywave Linux 3.1.1 - Release amd64 (20180606)
  MachineType: ASUSTeK Computer Inc. K54L
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.8-xanmod9 
root=UUID=4fd4c874-6312-499d-b5b8-a0d6f67182bc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54L.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54L
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54L.208:bd09/26/2011:svnASUSTeKComputerInc.:pnK54L:pvr1.0:rvnASUSTeKComputerInc.:rnK54L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K54L
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.92+git1805251830.c1f2d9~oibaf~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1806011930.f00fcf~oibaf~x
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1806011930.f00fcf~oibaf~x
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.1+git1805221933.65c9df~oibaf~x
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1805201934.ac8f7b~oibaf~x
  xserver.bootTime: Fri Feb  7 16:04:35 2020
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1862377/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1856045] Re: capabilities set with setcap are not honoured

2020-02-09 Thread Michael Hudson-Doyle
Well this is a consequence of this upstream change in iproute2:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?h=v4.16.0=ba2fc55b99f8363c80ce36681bc1ec97690b66f5.
Upstream discussion, such as it is, of the patch appears to be here:
https://lore.kernel.org/netdev/20180327162419.8962-1-bl...@debian.org/

Probably the next step is to email the netdev list about this. Is that
something you would be interested in doing? You are probably better able
to explain your use case than I am!

** Changed in: iproute2 (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1856045

Title:
  capabilities set with setcap are not honoured

Status in iproute2 package in Ubuntu:
  Triaged
Status in iproute2 source package in Eoan:
  Confirmed

Bug description:
  Hi,

  In Ubuntu 19.10 I set capabilities as;

  setcap cap_net_admin,cap_sys_admin+ep /bin/ip
  getcap /bin/ip
  /bin/ip = cap_net_admin,cap_sys_admin+ep

  but;

  > ip addr add 20.20.20.20/32 dev lo
  RTNETLINK answers: Operation not permitted

  *exactly* the same works perfect on 18.04.3 LTS.

  BTW the set of a silly address on "lo" is just an example.
  Nothing works on Ubuntu 19.10

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libcap2-bin 1:2.25-2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Dec 11 15:27:00 2019
  InstallationDate: Installed on 2019-12-09 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: libcap2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1856045] Re: capabilities set with setcap are not honoured

2020-02-09 Thread Michael Hudson-Doyle
** Package changed: libcap2 (Ubuntu) => iproute2 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1856045

Title:
  capabilities set with setcap are not honoured

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Eoan:
  Confirmed

Bug description:
  Hi,

  In Ubuntu 19.10 I set capabilities as;

  setcap cap_net_admin,cap_sys_admin+ep /bin/ip
  getcap /bin/ip
  /bin/ip = cap_net_admin,cap_sys_admin+ep

  but;

  > ip addr add 20.20.20.20/32 dev lo
  RTNETLINK answers: Operation not permitted

  *exactly* the same works perfect on 18.04.3 LTS.

  BTW the set of a silly address on "lo" is just an example.
  Nothing works on Ubuntu 19.10

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libcap2-bin 1:2.25-2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Dec 11 15:27:00 2019
  InstallationDate: Installed on 2019-12-09 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: libcap2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1856045] Re: capabilities set with setcap are not honoured

2020-02-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: iproute2 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1856045

Title:
  capabilities set with setcap are not honoured

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Eoan:
  Confirmed

Bug description:
  Hi,

  In Ubuntu 19.10 I set capabilities as;

  setcap cap_net_admin,cap_sys_admin+ep /bin/ip
  getcap /bin/ip
  /bin/ip = cap_net_admin,cap_sys_admin+ep

  but;

  > ip addr add 20.20.20.20/32 dev lo
  RTNETLINK answers: Operation not permitted

  *exactly* the same works perfect on 18.04.3 LTS.

  BTW the set of a silly address on "lo" is just an example.
  Nothing works on Ubuntu 19.10

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libcap2-bin 1:2.25-2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Dec 11 15:27:00 2019
  InstallationDate: Installed on 2019-12-09 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: libcap2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1410495] Re: Battery indicator goes Critical Red with more than 1 hour battery left

2020-02-09 Thread koyakun
Same issue on Ubuntu 19.10. A red indicator with 4 hours (45%) of
battery left is counterintuitive. I find myself repeatedly clicking the
indicator when it turns red only to find out that I have several hours
left.

** Attachment added: "4+ hours of battery left and red indicator"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+attachment/5326826/+files/Screenshot%20from%202020-02-10%2011-14-54.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1410495

Title:
  Battery indicator goes Critical Red with more than 1 hour battery left

Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  indicator-power 12.10.6+14.10.20141015-0ubuntu1, Ubuntu 14.10

  On my current laptop, the battery indicator shows a red-with-a-little-
  left icon when there is more than an hour left in the battery, which
  is not really appropriate for a "critical battery warning".

  This bug is probably a regression of #743823, and I was asked to create a new 
bug by @mpt:
  > Christoph, yes, please report a new bug including a screenshot. On phones 
we may have to color by percentage, but on PCs we can and should color by time 
remaining to avoid false alarms.

  A screenshot is attached. Unfortunately I didn't realize at the time
  that the screenshotter does not record open menus, so you'll have to
  take my word that the time remaining in the indicator menu was at > 1
  hour. I can redo the screenshot, if necessary.

  : "If it is discharging, the icon
  interior should be filled from left to right approximately as much as
  the remaining charge. If it has less than 30 minutes left on a PC, or
  less than 20% left on a phone or tablet, the fill should be red rather
  than monochrome."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862556] Re: Promore and Colourlovers

2020-02-09 Thread Daniel van Vugt
Could you please explain in more detail what kind of problem you are
experiencing?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862556

Title:
  Promore and Colourlovers

Status in Ubuntu:
  Incomplete

Bug description:
  Just appeared and no explanation as to function

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
  Uname: Linux 4.4.0-173-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: COMODO cmgdaemon service.
   [  OK  ] Started Network Manager Script Dispatcher Service.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb  9 17:19:28 2020
  DistUpgraded: 2017-01-13 10:58:43,955 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:3047]
  InstallationDate: Installed on 2017-01-10 (1125 days ago)
  InstallationMedia: It
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic 
root=UUID=f91ffe70-345b-4ad3-8970-945377f127c5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-01-13 (1122 days ago)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.17
  dmi.board.asset.tag: 2UA1422FS7
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA1422FS7
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.17:bd04/18/2012:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Feb  9 16:21:48 2020
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1862556/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862557] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 2

2020-02-09 Thread James
Public bug reported:

upgrading from xenial to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
Uname: Linux 4.4.0-173-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Sun Feb  9 14:43:44 2020
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2017-02-16 (1088 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
UpgradeStatus: Upgraded to bionic on 2020-02-09 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1862557

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  upgrading from xenial to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
  Uname: Linux 4.4.0-173-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Sun Feb  9 14:43:44 2020
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2017-02-16 (1088 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 2
  UpgradeStatus: Upgraded to bionic on 2020-02-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1862557/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862556] [NEW] Promore and Colourlovers

2020-02-09 Thread Ethel Barina
Public bug reported:

Just appeared and no explanation as to function

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
Uname: Linux 4.4.0-173-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: COMODO cmgdaemon service.
 [  OK  ] Started Network Manager Script Dispatcher Service.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Feb  9 17:19:28 2020
DistUpgraded: 2017-01-13 10:58:43,955 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:3047]
InstallationDate: Installed on 2017-01-10 (1125 days ago)
InstallationMedia: It
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic 
root=UUID=f91ffe70-345b-4ad3-8970-945377f127c5 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-01-13 (1122 days ago)
dmi.bios.date: 04/18/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.17
dmi.board.asset.tag: 2UA1422FS7
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA1422FS7
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.17:bd04/18/2012:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Feb  9 16:21:48 2020
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862556

Title:
  Promore and Colourlovers

Status in xorg package in Ubuntu:
  New

Bug description:
  Just appeared and no explanation as to function

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
  Uname: Linux 4.4.0-173-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: COMODO cmgdaemon service.
   [  OK  ] Started Network Manager Script Dispatcher Service.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb  9 17:19:28 2020
  DistUpgraded: 2017-01-13 10:58:43,955 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:3047]
  InstallationDate: Installed on 2017-01-10 (1125 days ago)
  InstallationMedia: It
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic 
root=UUID=f91ffe70-345b-4ad3-8970-945377f127c5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-01-13 (1122 days ago)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.17
  dmi.board.asset.tag: 2UA1422FS7
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA1422FS7
  

[Touch-packages] [Bug 1862537] [NEW] No /usr/bin/python or `python` package is provided on focal

2020-02-09 Thread Oded Arbel
Public bug reported:

After upgrading to focal, there is no `/usr/bin/python` executable and
no `python` package that can installed.

As are result:
- 3rd party packages that require a `python` package fail to install or are 
removed during upgrade or `apt --fix-broken install`
- software installed using `pip install --user` does not function after an 
upgrade to focal

The python runtime packages (`python2.7-minimal` and
`python3.7-minimal`) should provider a `/usr/bin/python` alternative
using the standard `update-alternatives` mechanisms, similar to how
other compilers and interpreters, such as gcc, php or java are doing it.

Workarounds:

1. Create a dummy package to provide the `python` requirement so that
3rd party packages will not be deemed broken and removed (for example,
slack-desktop), by running

equivs-build <(echo "Section: misc
Priority: optional
Standards-Version: 3.9.2

Package: python-dummy
Version: 1.0
Provides: python
Architecture: all
Description: Transitional package to provide the `python` requirement for 3rd 
party packages
") && sudo dpkg -i python-dummy_1.0_all.deb

2. Create a update-alternative configuration for /usr/bin/python that
can be configured by the local admin to use python2 or python3, but
defaults to python3, by running:

update-alternatives --install /usr/bin/python python /usr/bin/python2.7 2070 \
--slave /usr/share/man/man1/python.1.gz python.1.gz 
/usr/share/man/man1/python3.8.1.gz
update-alternatives --install /usr/bin/python python /usr/bin/python3.7 3070 \
--slave /usr/share/man/man1/python.1.gz python.1.gz 
/usr/share/man/man1/python3.7.1.gz
update-alternatives --install /usr/bin/python python /usr/bin/python3.8 3080 \
--slave /usr/share/man/man1/python.1.gz python.1.gz 
/usr/share/man/man1/python3.8.1.gz

(this assumes both python2.7, python3.7 and python3.8 - which was the
setup on my system after upgrading from eoan to focal)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1862537

Title:
  No /usr/bin/python or `python` package is provided on focal

Status in python-defaults package in Ubuntu:
  New

Bug description:
  After upgrading to focal, there is no `/usr/bin/python` executable and
  no `python` package that can installed.

  As are result:
  - 3rd party packages that require a `python` package fail to install or are 
removed during upgrade or `apt --fix-broken install`
  - software installed using `pip install --user` does not function after an 
upgrade to focal

  The python runtime packages (`python2.7-minimal` and
  `python3.7-minimal`) should provider a `/usr/bin/python` alternative
  using the standard `update-alternatives` mechanisms, similar to how
  other compilers and interpreters, such as gcc, php or java are doing
  it.

  Workarounds:

  1. Create a dummy package to provide the `python` requirement so that
  3rd party packages will not be deemed broken and removed (for example,
  slack-desktop), by running

  equivs-build <(echo "Section: misc
  Priority: optional
  Standards-Version: 3.9.2

  Package: python-dummy
  Version: 1.0
  Provides: python
  Architecture: all
  Description: Transitional package to provide the `python` requirement for 3rd 
party packages
  ") && sudo dpkg -i python-dummy_1.0_all.deb

  2. Create a update-alternative configuration for /usr/bin/python that
  can be configured by the local admin to use python2 or python3, but
  defaults to python3, by running:

  update-alternatives --install /usr/bin/python python /usr/bin/python2.7 2070 \
  --slave /usr/share/man/man1/python.1.gz python.1.gz 
/usr/share/man/man1/python3.8.1.gz
  update-alternatives --install /usr/bin/python python /usr/bin/python3.7 3070 \
  --slave /usr/share/man/man1/python.1.gz python.1.gz 
/usr/share/man/man1/python3.7.1.gz
  update-alternatives --install /usr/bin/python python /usr/bin/python3.8 3080 \
  --slave /usr/share/man/man1/python.1.gz python.1.gz 
/usr/share/man/man1/python3.8.1.gz

  (this assumes both python2.7, python3.7 and python3.8 - which was the
  setup on my system after upgrading from eoan to focal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1862537/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862483] Re: Setting PATH with environment.d/*.conf does not work

2020-02-09 Thread Dan Streetman
*** This bug is a duplicate of bug 1861363 ***
https://bugs.launchpad.net/bugs/1861363

** This bug has been marked a duplicate of bug 1861363
   /etc/environment.d cannot be used to add to PATH

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1862483

Title:
  Setting PATH with environment.d/*.conf does not work

Status in systemd package in Ubuntu:
  New

Bug description:
  ~> cat ~/.config/environment.d/10-mongo.conf 
  PATH=$PATH:~/Soft/mongodb42/bin
  TESTENVVAR=foobar

  ~> env
  COLORTERM=truecolor
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
  DESKTOP_SESSION=gnome
  DISPLAY=:0
  GDMSESSION=gnome
  GJS_DEBUG_OUTPUT=stderr
  GJS_DEBUG_TOPICS=JS ERROR;JS LOG
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/8f01f21a_f9a2_44ae_97d3_db8ff212779e
  GNOME_TERMINAL_SERVICE=:1.89
  GTK_MODULES=gail:atk-bridge
  HOME=/home/simon
  INVOCATION_ID=73f5572789da4b98ac504e7dce4269e1
  JOURNAL_STREAM=9:45969
  LANG=en_US.UTF-8
  LC_ADDRESS=en_GB.UTF-8
  LC_IDENTIFICATION=en_GB.UTF-8
  LC_MEASUREMENT=en_GB.UTF-8
  LC_MONETARY=en_GB.UTF-8
  LC_NAME=en_GB.UTF-8
  LC_NUMERIC=en_GB.UTF-8
  LC_PAPER=en_GB.UTF-8
  LC_TELEPHONE=en_GB.UTF-8
  LC_TIME=en_GB.UTF-8
  LOGNAME=simon
  MANAGERPID=2164
  PAPERSIZE=a4
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  PWD=/home/simon
  QT_IM_MODULE=ibus
  SESSION_MANAGER=local/T450:@/tmp/.ICE-unix/2232,unix/T450:/tmp/.ICE-unix/2232
  SHELL=/usr/bin/fish
  SHLVL=2
  SSH_AGENT_LAUNCHER=gnome-keyring
  SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  TERM=xterm-256color
  TESTENVVAR=foobar <- pay attention
  USER=simon
  USERNAME=simon
  VTE_VERSION=5802
  WAYLAND_DISPLAY=wayland-0
  XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.DY6MF0
  XDG_CURRENT_DESKTOP=GNOME
  XDG_DATA_DIRS=/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_MENU_PREFIX=gnome-
  XDG_RUNTIME_DIR=/run/user/1000
  XDG_SESSION_CLASS=user
  XDG_SESSION_DESKTOP=gnome
  XDG_SESSION_TYPE=wayland
  XMODIFIERS=@im=ibus

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.6
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb  9 00:57:13 2020
  InstallationDate: Installed on 2019-10-20 (111 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20BUS04A04
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=7af429cf-e7fe-41af-868c-955fbda6f55f ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to eoan on 2019-12-26 (44 days ago)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BUS04A04
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BUS04A04:pvrThinkPadT450:rvnLENOVO:rn20BUS04A04:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BUS04A04
  dmi.product.sku: LENOVO_MT_20BU_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862483/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1861721] Re: curl imap returns error 78 File not found instead of the email

2020-02-09 Thread Bug Watch Updater
** Changed in: curl
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1861721

Title:
  curl imap returns error 78 File not found instead of the email

Status in Curl:
  Fix Released
Status in curl package in Ubuntu:
  New

Bug description:
  The version of curl included in Ubuntu 18.04 LTS has a bug that causes
  the imap sub-command/scheme to return Error 78 File not found when it
  should return the contents of the email.

  This is documented in the Bug Report on GitHub as:
  https://github.com/curl/curl/issues/4479

  The version supplied in Ubuntu 19.10, and future 20.04 LTS will be the
  fixed version.

  Ubuntu 18.04
  Version:
  $ curl -V
  curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 
libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
  Release-Date: 2018-01-24
  Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 
pop3s rtmp rtsp smb smbs smtp smtps telnet tftp 
  Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB 
SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL 

  Command:
  $ curl --insecure --url "imaps://email.example.co.nz/Spam;UID=33" -n
  curl: (78) Remote file not found

  Ubuntu 19.10
  Version:
  $ curl -V
  curl 7.65.3 (x86_64-pc-linux-gnu) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 
libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.9.0/openssl/zlib 
nghttp2/1.39.2 librtmp/2.3
  Release-Date: 2019-07-19
  Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 
pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
  Features: AsynchDNS GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile 
libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets

  Command:
  $ curl --insecure --url "imaps://email.example.co.nz/Spam;UID=33" -n
  Return-Path: 
  Received: from email.example.co.nz ([unix socket])
 by email (Cyrus x.xx.xx. with LMTPA;
 Tue, 28 Jan 2020 22:05:56 +1300
  X-Sieve: CMU Sieve x.x
  8x  Snip  x8

  Also the version supplied with OSX works correctly.

  % curl -V
  curl 7.64.1 (x86_64-apple-darwin19.0) libcurl/7.64.1 (SecureTransport) 
LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.39.2
  Release-Date: 2019-03-27
  Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 
pop3s rtsp smb smbs smtp smtps telnet tftp 
  Features: AsynchDNS GSS-API HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz 
MultiSSL NTLM NTLM_WB SPNEGO SSL UnixSockets

  
  Running curl with -v returns this for a failed download (after authentication 
and other house keeping):

  > A003 SELECT Spam
  < * 8 EXISTS
  < * 0 RECENT
  < * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
  < * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok
  < * OK [UIDVALIDITY 1573031905] Ok
  < * OK [UIDNEXT 41] Ok
  < * OK [HIGHESTMODSEQ 89] Ok
  < * OK [URLMECH INTERNAL] Ok
  < * OK [ANNOTATIONS 65536] Ok
  < A003 OK [READ-WRITE] Completed
  > A004 FETCH 33 BODY[]
  < A004 NO No matching messages (0.000 sec)
  > A005 LOGOUT
  < * BYE LOGOUT received
  < A005 OK Completed
  * Closing connection 0
  curl: (78) Remote file not found

  
  Cheers
  Jim

To manage notifications about this bug go to:
https://bugs.launchpad.net/curl/+bug/1861721/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862480] Re: dpkg-reconfigure console-setup changes do not apply after reboot.

2020-02-09 Thread Colin Watson
** Project changed: console-setup => console-setup (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1862480

Title:
  dpkg-reconfigure console-setup changes do not apply after reboot.

Status in console-setup package in Ubuntu:
  New

Bug description:
  I boot Ubuntu 18.04.4 in mode 3 (console mode) and run `sudo dpkg-
  reconfigure console-setup` and select UTF-8 -> Latin1 and Latin5 ->
  Terminus -> 10x20. After that the console immediately switches to this
  font and font size. And it also prints the following message:

  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.130ubuntu3.9) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-76-generic

  After that I reboot into mode 3 again but the font and the font size
  don't get applied. I have to manually run `sudo setupcon -v -f` for my
  changes to take effect after a reboot.

  This looks to be a bug in `dpkg-reconfigure console-setup`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1862480/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862480] [NEW] dpkg-reconfigure console-setup changes do not apply after reboot.

2020-02-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I boot Ubuntu 18.04.4 in mode 3 (console mode) and run `sudo dpkg-
reconfigure console-setup` and select UTF-8 -> Latin1 and Latin5 ->
Terminus -> 10x20. After that the console immediately switches to this
font and font size. And it also prints the following message:

update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.9) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-76-generic

After that I reboot into mode 3 again but the font and the font size
don't get applied. I have to manually run `sudo setupcon -v -f` for my
changes to take effect after a reboot.

This looks to be a bug in `dpkg-reconfigure console-setup`.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

-- 
dpkg-reconfigure console-setup changes do not apply after reboot.
https://bugs.launchpad.net/bugs/1862480
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to console-setup in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

2020-02-09 Thread Michael Hudson-Doyle
> Ah, no I think this might be along right lines: udev is calling blkid
> on the _partition_ of course, so it can probe for filesystem etc without
> looking at the partition table. After it's done that, it does look for
> the partition table so it can read the ID_PART_ENTRY_* values from it,
> but if it fails to load the partition table it just gives up and still
> returns success.

Ah so this was in the right direction, but not completely right: the
failure is not in reading the partition table of the disk being probed,
but failing to figure out which entry in that table corresponds to the
partition being probed:

Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: 
LOWPROBE: trying to convert devno 0x811 to partition
Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: 
LOWPROBE: searching by offset/size
Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: 
LOWPROBE: not found partition for device
Feb 06 00:37:42 test-xrdpdnvfctsofyygmzan systemd-udevd[556]: 556: libblkid: 
LOWPROBE: parts: end probing for partition entry [nothing]

The function of interest in libblkid here is
blkid_partlist_devno_to_partition, which (unless some apis have very
misleading names) is reading the offset and size of the partition from
sysfs. What must be happening here is that udev sees the disk being
closed by gdisk and somehow runs the builting blkid command on the
partition before the kernel has been informed of the resize of the
partition. And indeed, we can see when the kernel notices this:

Feb 06 00:37:43 test-xrdpdnvfctsofyygmzan kernel: EXT4-fs (sdb1): resizing 
filesystem from 548091 to 7836155 blocks
Feb 06 00:37:44 test-xrdpdnvfctsofyygmzan kernel: EXT4-fs (sdb1): resized 
filesystem to 7836155

At least a second later. (In passing_journalctl_output.txt, this message
is printed before udev even gets the inotify event about sdb being
closed).

So there's always a race here but I don't know why we only see this on
Azure with newer releases. A proper fix would be to get sgdisk to call
partx_resize_partition before closing the disk but it would also be
interesting to see why it takes so long to get to that part sometimes.
growpart is too much shell for me, but maybe it's possible to get it to
run partx under strace and get the output of that out somehow?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1834875

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  

[Touch-packages] [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default

2020-02-09 Thread Hui Wang
registered sponsor team

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1862505

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-02-09 Thread Hui Wang
I opened a similar bug for focal, we need to put the alsa-ucm-conf and
alsa-topology-conf to the focal image.

This is the bug link: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1862505

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1859754

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862505] [NEW] alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default

2020-02-09 Thread Hui Wang
Public bug reported:

Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
alsa-lib, when we install the alsa-lib/libasound2, they are installed
together with alsa-lib. But from 1.2.1 they are separated from the alsa-
lib, and in the focal, we choose the 1.2.1.2 version, we should install
the ucm and topology too, otherwise those machines need ucm and topology
will not work anymore, users have to install these two packages
manually.

Two packages we need to put into the focal image are:
alsa-ucm-conf 1.2.1.2-2
alsa-topology-conf 1.2.1-2

** Affects: alsa-lib (Ubuntu)
 Importance: High
 Status: New

** Changed in: alsa-lib (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1862505

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors

2020-02-09 Thread André Hoek
Resolution Settings

** Attachment added: "MonitorSettings.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+attachment/5326639/+files/MonitorSettings.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862500

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
  InstallationDate: Installed on 2019-12-20 (50 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 3212AP3
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT63AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3212AP3
  dmi.product.sku: LENOVO_MT_3212
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1858971] Re: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures

2020-02-09 Thread Dimitri John Ledkov
** Changed in: openssl (Ubuntu)
   Status: New => Fix Released

** Changed in: cmake (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: nodejs (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: python2.7 (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1858971

Title:
  SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest
  failures

Status in cmake package in Ubuntu:
  Fix Released
Status in nodejs package in Ubuntu:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Fix Committed
Status in python3.8 package in Ubuntu:
  Fix Committed
Status in ruby-openssl package in Ubuntu:
  Fix Committed
Status in ruby2.5 package in Ubuntu:
  Fix Committed

Bug description:
  SECLEVEL=2 by default is causing ftbfs / autopkgtest failure

  openssl switched to SECLEVEL=2 by default

  Causes:

  SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl

  openssl uses tls1.2-min:

  test_ssl failing in python2.7
  ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests)
  Connecting to an SSLv23 server with various client options
  ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests)
  Connecting to a TLSv1.1 server with various client options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1858971/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862500] Re: Desktop icons are placed off-screen when using multiple monitors

2020-02-09 Thread André Hoek
Image showing the perceived location of missing icons on Desktop

** Attachment added: "FullDesktop.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+attachment/5326638/+files/FullDesktop.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862500

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
  InstallationDate: Installed on 2019-12-20 (50 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 3212AP3
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT63AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3212AP3
  dmi.product.sku: LENOVO_MT_3212
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862500/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1862500] [NEW] Desktop icons are placed off-screen when using multiple monitors

2020-02-09 Thread André Hoek
Public bug reported:

I have 2 monitors connected in "Join Display Mode".
Monitor 1 (secondary) 1366x798, Landscape, 100%
Monitor 2 (primary) 1920x1080, Landscape, 100%

I can see files on the Desktop inside the File Browser, but on the
Desktop icons are either not visible or limited text from one of the
icons can be seen in the top left corner of the secondary monitor.

Screenshots attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb  9 10:16:18 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[17aa:3083]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] 
(prog-if 00 [VGA controller])
   Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Caicos PRO 
[Radeon HD 7450] [1642:3a76]
InstallationDate: Installed on 2019-12-20 (50 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 3212AP3
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=c29a-51cf-4584-b908-5081f9693928 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT63AUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT63AUS:bd03/21/2013:svnLENOVO:pn3212AP3:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3212AP3
dmi.product.sku: LENOVO_MT_3212
dmi.product.version: ThinkCentre M92p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1862500

Title:
  Desktop icons are placed off-screen when using multiple monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors connected in "Join Display Mode".
  Monitor 1 (secondary) 1366x798, Landscape, 100%
  Monitor 2 (primary) 1920x1080, Landscape, 100%

  I can see files on the Desktop inside the File Browser, but on the
  Desktop icons are either not visible or limited text from one of the
  icons can be seen in the top left corner of the secondary monitor.

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 10:16:18 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.60, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] 
[1002:677b] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information