[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

regression submitted upstream see 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 
for further details

** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/issues 
#119
   https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

[Matthew Ruffell]

** Description changed:

  [Impact]
  
-  * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.
+  * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.
  
-  * update-rc.d incorrectly modifies symlinks when enabling or disabling 
services
-which are started on the "S" runlevel.
+  * update-rc.d incorrectly modifies symlinks when enabling or disabling  
+services which are started on the "S" runlevel.
  
-  * This can lead to services being changed from S runlevel from where they 
would
-be started on boot, to "0" runlevel, and are run on halt, which is 
incorrect.
+  * This can lead to services being changed from S runlevel from where they 
+would be started on boot, to "0" runlevel, and are run on halt, which is 
+incorrect.
  
-  * The bug is caused by trying to use the runlevel to index into an integer
-array of runlevels. When the runlevel in question is "S", an error is 
printed
-
-Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 
232.
+  * The bug is caused by trying to use the runlevel to index into an integer
+    array of runlevels. When the runlevel in question is "S", an error is 
+printed
  
-Perl then sets the index to default to 0, which changes the runlevel.
+Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 
+232.
  
-  * The fix is to check if the runlevel is "S", and if it is, set the index to 
99
-which conforms with other expected usages for the "S" runlevel in the 
script.
-See the "startstop" and "makelinks" subroutines.
+    Perl then sets the index to default to 0, which changes the runlevel.
+ 
+  * The fix is to check if the runlevel is "S", and if it is, set the index to 
 
+99 which conforms with other expected usages for the "S" runlevel in the 
+script. See the "startstop" and "makelinks" subroutines.
  
  [Test Case]
  
- * You can reproduce this with any service that is started on the "S" runlevel.
-   We will use open-iscsi for an example.
+ * You can reproduce this with any service that is started on the "S" 
+   runlevel. We will use open-iscsi for an example.
  
  1) Install open-iscsi
  
  $ sudo apt install open-iscsi
  
  2) Check to see symlinks for init.d scripts are set to defaults:
  
  root@trusty-openiscsi:/etc# ls -l /etc/rc[0123456S].d/*iscsi*
- lrwxrwxrwx 1 root root 24 Apr 29 20:56 /etc/rc0.d/K80umountiscsi.sh -> 
../init.d/umountiscsi.sh
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rc0.d/K81open-iscsi -> 
../init.d/open-iscsi
- lrwxrwxrwx 1 root root 24 Apr 29 20:56 /etc/rc1.d/K80umountiscsi.sh -> 
../init.d/umountiscsi.sh
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rc1.d/K81open-iscsi -> 
../init.d/open-iscsi
- lrwxrwxrwx 1 root root 24 Apr 29 20:56 /etc/rc6.d/K80umountiscsi.sh -> 
../init.d/umountiscsi.sh
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rc6.d/K81open-iscsi -> 
../init.d/open-iscsi
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rcS.d/S45open-iscsi -> 
../init.d/open-iscsi
+ /etc/rc0.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
+ /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
+ /etc/rc1.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
+ /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
+ /etc/rc6.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
+ /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
+ /etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi
  
  3) Use update-rc.d to enable open-iscsi service
  
  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
  Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 232.
  Enabling system startup links for /etc/init.d/open-iscsi ...
  Removing any system startup links for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi
  /etc/rc1.d/K81open-iscsi
  /etc/rc6.d/K81open-iscsi
  /etc/rcS.d/S45open-iscsi
  Adding system startup for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc0.d/S45open-iscsi -> ../init.d/open-iscsi
  
- * The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly 
changed to
-   "/etc/rc0.d/S45open-iscsi".
+ * The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly 
+   changed to "/etc/rc0.d/S45open-iscsi".
  
- * Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/
- intact:
+ * Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/ 
+   intact:
  
  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

[Daniel van Vugt]

Great!

By the way, one possible reason why you were unable to follow comment #2
is that gdm is designed to catch mutter/gnome-shell crashes in the
Wayland backend (which it tries first). If such a crash occurs then it
is meant to automatically fall back to Xorg.

Regardless of whether the automatic fallback was working for you, that
crash handling done by gdm would possibly prevent any crash in mutter
/gnome-shell Wayland start-up from being saved and sent to Ubuntu :(

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutt

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

[Gregory Stewart]

I didn't know how to log into "Ubuntu" instead of "Ubuntu on Wayland"
since I only got a blinking cursor and no logon prompt. I edited
/etc/gdm3/custom.conf and rebooted.

Successfully got a GUI logon prompt and was able to log in to the
desktop.

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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.ne

[Touch-packages] [Bug 1827172] [NEW] update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

[Matthew Ruffell]

Public bug reported:

[Impact]

 * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.

 * update-rc.d incorrectly modifies symlinks when enabling or disabling  
   services which are started on the "S" runlevel.

 * This can lead to services being changed from S runlevel from where they 
   would be started on boot, to "0" runlevel, and are run on halt, which is 
   incorrect.

 * The bug is caused by trying to use the runlevel to index into an integer
   array of runlevels. When the runlevel in question is "S", an error is 
   printed

   Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 
   232.

   Perl then sets the index to default to 0, which changes the runlevel.

 * The fix is to check if the runlevel is "S", and if it is, set the index to  
   99 which conforms with other expected usages for the "S" runlevel in the 
   script. See the "startstop" and "makelinks" subroutines.

[Test Case]

* You can reproduce this with any service that is started on the "S" 
  runlevel. We will use open-iscsi for an example.

1) Install open-iscsi

$ sudo apt install open-iscsi

2) Check to see symlinks for init.d scripts are set to defaults:

root@trusty-openiscsi:/etc# ls -l /etc/rc[0123456S].d/*iscsi*
/etc/rc0.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
/etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc1.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
/etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc6.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
/etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

3) Use update-rc.d to enable open-iscsi service

root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 232.
Enabling system startup links for /etc/init.d/open-iscsi ...
Removing any system startup links for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi
/etc/rc1.d/K81open-iscsi
/etc/rc6.d/K81open-iscsi
/etc/rcS.d/S45open-iscsi
Adding system startup for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc0.d/S45open-iscsi -> ../init.d/open-iscsi

* The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly 
  changed to "/etc/rc0.d/S45open-iscsi".

* Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/ 
  intact:

root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
Enabling system startup links for /etc/init.d/open-iscsi ...
Removing any system startup links for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi
/etc/rc1.d/K81open-iscsi
/etc/rc6.d/K81open-iscsi
/etc/rcS.d/S45open-iscsi
Adding system startup for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

[Regression Potential]

 * There is only one file modified, which is the update-rc.d perl script. 
   Worst case scenario is that users cannot enable or disable their services, 
   or a symlink is changed such that a service is started / stopped on an 
   incorrect runlevel.

 * If a regression happens, any damage should be easily spotted by a 
   sysadmin and can be manually repaired by making manual symlinks with 
   "ln -s".

[Other Info]

 * trusty is the last Ubuntu release to use sysvinit, and this bug is not 
   present in newer versions since they use systemd, and the code in question 
   is removed from update-rc.d.

 * The bug exists in debian squeeze, which is now unsupported, and the code 
   in question is not in any newer versions.

 * The bug was introduced in 2009-06-29 and somehow evaded anyone noticing 
   it.

** Affects: sysvinit (Ubuntu)
 Importance: Medium
 Assignee: Matthew Ruffell (mruffell)
 Status: New

** Affects: sysvinit (Ubuntu Trusty)
 Importance: Medium
 Assignee: Matthew Ruffell (mruffell)
 Status: New


** Tags: sts

** Also affects: sysvinit (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: sysvinit (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: sysvinit (Ubuntu Trusty)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

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

Title:
  update-rc.d: e

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => New

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1817998] Re: KVM Guest - DHCP lease lost (Ubuntu 18.04)

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1817998

Title:
  KVM Guest - DHCP lease lost (Ubuntu 18.04)

Status in systemd package in Ubuntu:
  Expired

Bug description:
  On Nvidia DGX2 system, we configured linux bridge (br0) using host
  physical NIC interface and it is using static IP (see below netplan
  file). BTW, we are using 18.04.2 based BaseOS and Guest images.

  - All KVM guests are being launched using virtual network interface based 
on br0. All VMs are getting DHCP based IP address and network interface works 
fine for few hours (may be upto 24hours).  
  - After that we are noticing these VMs are losing IP address and noticed 
the message in VM’s syslog
  "Feb 26 17:16:41 test-1g0 systemd-networkd[3479]: enp6s0: DHCP lease lost".
  - At this point, we tried to create new VMs using br0 and none of them 
are getting any IP address.
  - Then, we checked KVM host, and status of bridge but we didn’t see any 
error. Tried to unconfigure br0 by removing bridge configuration from host 
netplan and did “sudo netplan apply” but br0 is still there. It seems like 
bridge has in weird state and cannot unload this driver. 

  Guest
  lab@dgx-server-vm:~$ ssh nvidia@192.168.123.138
  The authenticity of host '192.168.123.138 (192.168.123.138)' can't be 
established.
  ECDSA key fingerprint is SHA256:k8XpnGH7yle76z46CX16pflYVeYcKoG6kWCymIkv0kk.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added '192.168.123.138' (ECDSA) to the list of known 
hosts.
  nvidia@192.168.123.138's password: 
   _   _   _ _ _ ______  
  | \ | |_   _(_) __| (_) __ _  | |_ ___  ___| |_ / | __ _ / _ \ 
  |  \| \ \ / / |/ _` | |/ _` | | __/ _ \/ __| __|| |/ _` | | | |
  | |\  |\ V /| | (_| | | (_| | | ||  __/\__ \ ||_| | (_| | |_| |
  |_| \_| \_/ |_|\__,_|_|\__,_|  \__\___||___/\__||_|\__, |\___/ 
 |___/   

  Welcome to Ubuntu 18.04.2 LTS (4.15.0-45-generic)

  Welcome to NVIDIA DGX KVM VM Server Version 4.0.5 (GNU/Linux
  4.15.0-45-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage
  System information as of: Wed Feb 27 12:20:21 PST 2019

  System load:  0.00IP Address: 
  Memory usage: 0.0% (59.36G avail) System uptime:  21:04 hours
  Usage on /:   8% (44G free)   Swap usage: 0.0%
  Local Users:  1   Processes:  158

  
System information as of Wed Feb 27 12:20:22 PST 2019

System load:  0.0   Processes:  155
Usage of /:   6.7% of 48.96GB   Users logged in:1
Memory usage: 0%IP address for enp1s0:  192.168.123.138
Swap usage:   0%IP address for docker0: 172.17.0.1

   * Canonical Livepatch is available for installation.
 - Reduce system reboots and improve kernel security. Activate at:
   https://ubuntu.com/livepatch

  15 packages can be updated.
  9 updates are security updates.

  Last login: Wed Feb 27 12:05:09 2019
  nvidia@test-1g0:~$ ifconfig
  docker0: flags=4099  mtu 1500
  inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
  ether 02:42:5c:b9:6f:94  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp1s0: flags=4163  mtu 1500
  inet 192.168.123.138  netmask 255.255.255.0  broadcast 192.168.123.255
  inet6 fe80::5054:ff:feb9:b8a1  prefixlen 64  scopeid 0x20
  ether 52:54:00:b9:b8:a1  txqueuelen 1000  (Ethernet)
  RX packets 38879  bytes 2449778 (2.4 MB)
  RX errors 0  dropped 1  overruns 0  frame 0
  TX packets 977  bytes 132770 (132.7 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp6s0: flags=4163  mtu 1500
  inet6 fe80::5055:ff:fe78:faa9  prefixlen 64  scopeid 0x20
  ether 52:55:00:78:fa:a9  txqueuelen 1000  (Ethernet)
  RX packets 93842  bytes 7637062 (7.6 MB)
  RX errors 0  dropped 27  overruns 0  frame 0
  TX packets 1874  bytes 442869 (442.8 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 562  bytes 52271 (52.2 KB)
  RX errors 0  dropped 0  overruns 0  frame 0

[Touch-packages] [Bug 1818271] Re: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by sig

[Launchpad Bug Tracker]

[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package unattended-upgrades 1.5ubuntu3.18.10.2 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess was killed by signal (Broken pipe)

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  ??

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: unattended-upgrades 1.5ubuntu3.18.10.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Fri Mar  1 10:23:17 2019
  DuplicateSignature:
   package:unattended-upgrades:1.5ubuntu3.18.10.2
   Setting up sddm (0.18.0-1ubuntu2) ...
   dpkg: error processing package sddm (--configure):
installed sddm package post-installation script subprocess was killed by 
signal (Broken pipe)
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess was killed by signal (Broken pipe)
  InstallationDate: Installed on 2019-03-01 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess was killed by signal (Broken pipe)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1818271/+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 1818059] Re: packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()

[Launchpad Bug Tracker]

[Expired for packagekit (Ubuntu) because there has been no activity for
60 days.]

** Changed in: packagekit (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()

Status in packagekit package in Ubuntu:
  Expired

Bug description:
  Kept happening since yesterday 27-02-2019 every time the system
  starts.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: packagekit 1.1.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Feb 28 16:48:30 2019
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2019-02-26 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   __strncasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:260
   std::__cxx11::basic_string, 
std::allocator >::_M_replace(unsigned long, unsigned long, char const*, 
unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
   show_errors(PkBackendJob*, PkErrorEnum, bool) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1818059/+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 1827118] Re: Boot black screen

[Daniel van Vugt]

I can't see any problem in the files attached so far. We need a log file
covering the period of time when the problem actually happened. To get
that please:

1. Reproduce the problem.

2. Reboot and then immediately run:

   journalctl -b-1 > prevboot.txt

   and then attach the file 'prevboot.txt' to this bug.


** 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/1827118

Title:
  Boot black screen

Status in Ubuntu:
  Incomplete

Bug description:
  At several times boot stops and each time no boot menu (Grub)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 20:53:28 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2019-04-29 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 7829A71
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=4f77cbd0-dae8-4ab6-a7bb-2af4093855de ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET38WW (1.15 )
  dmi.board.name: 7829A71
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn7829A71:pvrThinkPadL420:rvnLENOVO:rn7829A71:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 7829A71
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1827118/+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 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly

[widon1104]

This bug appear a few time today after I upgrade my system to ubuntu19.04.
This is definitely a bug.

widon@widon-X555YI:~$ uname -a
Linux widon-X555YI 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

-- 
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/1805077

Title:
  [ASUS X555YI] the audio pause and repeat for a very short of time
  randomly

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  the audio pause and repeat for a very short of time randomly
  when I use web browser to play music and use smplayer play video this bug 
happens randomly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon 13716 F pulseaudio
   /dev/snd/controlC0:  widon 13716 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  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.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1805077/+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 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

[Daniel van Vugt]

Also, to avoid Wayland fully, please edit /etc/gdm3/custom.conf and
uncomment:

  #WaylandEnable=false

then reboot.

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Daniel van Vugt]

** No longer affects: linux (Ubuntu)

** Summary changed:

- gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: 
Function not implemented" on Matrox graphics card)

** Changed in: mesa (Ubuntu)
   Importance: High => Low

** Changed in: mutter (Ubuntu)
   Importance: High => Low

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

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

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifi

[Touch-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot

[Theron Muller]

Dear Sebastian,
Thanks for your response. I've raised the bug upstream here: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166

I'll try to keep this bug stream and that one coordinated.

** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues 
#166
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166

-- 
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/1826403

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Daniel van Vugt]

Tracking upstream (I think) in
https://gitlab.gnome.org/GNOME/mutter/issues/57

** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)

** Summary changed:

- gnome-shell trap int3 no desktop (MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #57
   https://gitlab.gnome.org/GNOME/mutter/issues/57

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/57
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.out

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Daniel van Vugt]

** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Daniel van Vugt]

** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1826025] Re: gnome-shell trap int3 no desktop

[Daniel van Vugt]

It appears this message keeps happening with the gnome-shell crash:

  "Impossible to lock surface front buffer: Function not implemented"

that's from mutter's "native" (Wayland) backend:

  next_bo = gbm_surface_lock_front_buffer (gbm_surface);

  if (!next_bo)
{
  g_error ("Impossible to lock surface front buffer: %m");
  return FALSE;
}

so it means your kernel graphics driver (mgag200) does not fully support
Wayland sessions.

Please just use Xorg sessions instead (log into "Ubuntu" instead of
"Ubuntu on Wayland").

** Summary changed:

- gnome-shell trap int3 no desktop
+ gnome-shell trap int3 no desktop (MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfi

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1826025/+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 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  gnome-control-center crashed with SIGSEGV in
  _gdk_event_queue_handle_motion_compression()

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503

  ---

  [Impact]
  When I try to set the pen on my touch screen. gnome-control-center crashes.

  [Fix]
  That you can configure the pencil to later occupy it with my touch screen.

  [Test Case]
  1. Open gnome-control-center
  2. Click on Wacom tablet
  3. Press the buttons of the pencil, touching the screen
  4. gnome-control-center crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.32.1-1ubuntu5
  Uname: Linux 5.1.0-050100rc7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 19:28:42 2019
  InstallationDate: Installed on 2018-12-02 (149 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()

[El jinete sin cabeza]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gnome-control-center crashed with SIGSEGV in
  _gdk_event_queue_handle_motion_compression()

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503

  ---

  [Impact]
  When I try to set the pen on my touch screen. gnome-control-center crashes.

  [Fix]
  That you can configure the pencil to later occupy it with my touch screen.

  [Test Case]
  1. Open gnome-control-center
  2. Click on Wacom tablet
  3. Press the buttons of the pencil, touching the screen
  4. gnome-control-center crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.32.1-1ubuntu5
  Uname: Linux 5.1.0-050100rc7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 19:28:42 2019
  InstallationDate: Installed on 2018-12-02 (149 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Chris Halse Rogers]

Marking as verification-failed as per the last couple of comments.

It looks like that might want to be split out into a new bug,
particularly as it also affects cosmic (and disco?)

** Tags removed: verification-done
** Tags added: regression-proposed verification-failed

** Tags removed: verification-done-bionic
** Tags added: verification-failed-bionic

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1826025] Re: gnome-shell trap int3 no desktop

[Gregory Stewart]

Uninstalled xorgxrdp, no change:

/var/log/apport.log:
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: called for pid 2790, signal 
5, core limit 0, dump mode 1
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: debug: session gdbus call: 
(false,)

ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: happens for shutting
down session, ignoring

syslog:

Apr 30 16:47:43 mizuno kernel: [  101.347616] traps: gnome-shell[2790] trap 
int3 ip:7efffdf69955 sp:7ffc6beecca0 error:0 in 
libglib-2.0.so.0.6000.0[7efffdf3+8]
Apr 30 16:47:43 mizuno gnome-shell[2790]: Impossible to lock surface front 
buffer: Function not implemented

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

Title:
  gnome-shell trap int3 no desktop

Status in gdm3 package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.c

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop

[Gregory Stewart]

apport is enabled.

>From /var/log/apport.log.1:

ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: called for pid 2699, signal 
5, core limit 0, dump mode 1
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: debug: session gdbus call: 
(false,)

ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: happens for shutting
down session, ignoring

>From dpkg -l | grep rdp:

ii  libfreerdp-client2-2:amd64   
2.0.0~git20190204.1.2693389a+dfsg1-1amd64Free Remote Desktop 
Protocol library (client library)
ii  libfreerdp-common1.1.0:amd64 
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 amd64Free Remote Desktop 
Protocol library (common library)
ii  libfreerdp-plugins-standard:amd64
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 amd64RDP client for Windows 
Terminal Services (plugins)
ii  libfreerdp-utils1.1:amd64
1.1.0~git20140921.1.440916e+dfsg1-15ubuntu1 amd64Free Remote Desktop 
Protocol library (freerdp-utils library)
rc  libfreerdp1:amd641.0.2-2ubuntu1 
 amd64RDP client for Windows Terminal Services 
(library)
ii  libfreerdp2-2:amd64  
2.0.0~git20190204.1.2693389a+dfsg1-1amd64Free Remote Desktop 
Protocol library (core library)
ii  remmina-plugin-rdp:amd64 1.3.3+dfsg-2ubuntu1
 amd64RDP plugin for Remmina
ii  xorgxrdp 1:0.2.9-1  
 amd64Remote Desktop Protocol (RDP) modules for 
X.org
ii  xrdp 0.9.9-1
 amd64Remote Desktop Protocol (RDP) server

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

Title:
  gnome-shell trap int3 no desktop

Status in gdm3 package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.ch

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

[Brian Murray]

Hello Alan, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.4 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1770082] Re: systemd-networkd not renaming devices on boot

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.4 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

-- 
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/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  lin

[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

1.8.2-1 from cosmic also has this regression

 [1556659895.024512] Starting detailed registration state check
 [1556659895.024533]   Skipping detailed registration state check
 [1556659895.024543] All CDMA registration state checks done
 [1556659895.024636] Will start keeping track of state for subsystem 
'cdma1x'
  [1556659895.024671] Modem /org/freedesktop/ModemManager1/Modem/0: state 
changed (enabled -> registered)
 [1556659895.024907] Periodic signal checks enabled
 [1556659895.024921] Periodic signal check refresh requested
 [1556659895.024931] loading signal quality...
 [1556659895.024956] (rfcomm0) device open count is 4 (open)
 [1556659895.025046] Will start keeping track of state for subsystem 
'evdo'
 [1556659895.025076] Modem is currently registered in a CDMA network 
(CDMA1x: 'yes', EV-DO: 'no')
  [1556659895.025092] Simple connect state (6/8): Bearer
 [1556659895.025104] Creating new bearer...
 [1556659895.025120] Creating Broadband bearer in broadband modem
 [1556659895.025620] (rfcomm0) device open count is 5 (open)
 [1556659895.025679] (rfcomm0) device open count is 4 (close)
  [1556659895.026094] Simple connect state (7/8): Connect
 [1556659895.026129] Connecting bearer 
'/org/freedesktop/ModemManager1/Bearer/0'
  [1556659895.026155] Modem /org/freedesktop/ModemManager1/Modem/0: state 
changed (registered -> connecting)
 [1556659895.026456] Launching 3GPP2 connection attempt
 [1556659895.026485] (rfcomm0) device open count is 5 (open)
 [1556659895.026495] Connection through a plain serial AT port (rfcomm0)
 [1556659895.026515] (rfcomm0) device open count is 6 (open)
 [1556659895.026554] (rfcomm0) device open count is 5 (close)
 [1556659895.026584] (rfcomm0): --> 'AT+CSS?'
 [1556659895.049351] (rfcomm0): <-- '?, 
26OK'
 [1556659895.049510] Starting detailed registration state check
 [1556659895.049527]   Skipping detailed registration state check
 [1556659895.049537] All CDMA registration state checks done
 [1556659895.049702] Initial CDMA registration checks finished
 [1556659895.049727] (rfcomm0) device open count is 4 (close)
 [1556659895.049766] (rfcomm0): --> 'AT+CSQ'
 [1556659895.070553] (rfcomm0): <-- '22, 
99OK'
 [1556659895.070772] Modem /org/freedesktop/ModemManager1/Modem/0: 
signal quality updated (70)
 [1556659895.070809] EVDO registration: 0
 [1556659895.070818] CDMA1x registration: 1
 [1556659895.070825] Fallback access tech: 0x0400
 [1556659895.070836] Fallback access technology: 0x0400
 [1556659895.070867] (rfcomm0) device open count is 3 (close)
 [1556659895.071116] Modem /org/freedesktop/ModemManager1/Modem/0: 
access technology changed (unknown -> 1xrtt)
 [1556659895.071149] Periodic signal quality checks scheduled in 30s
 [1556659895.071290] (rfcomm0): --> 'ATDT#777'
 [1556659896.924337] (rfcomm0): <-- 'CONNECT 240'
 [1556659896.924406] [rfcomm0] Setting flow control: rts-cts
 [1556659896.924414] (rfcomm0): enabling RTS/CTS flow control
 [1556659896.924431] (rfcomm0): port now connected
 [1556659896.924450] Connected bearer 
'/org/freedesktop/ModemManager1/Bearer/0'
  [1556659896.924532] Modem /org/freedesktop/ModemManager1/Modem/0: state 
changed (connecting -> connected)
  [1556659896.924655] Simple connect state (8/8): All done
 [1556659896.924705] (rfcomm0) device open count is 2 (close)
 [1556659896.952641] (net/ppp0): adding device at sysfs path: 
/sys/devices/virtual/net/ppp0
 [1556659896.952743] [filter] (net/ppp0) port filtered: virtual device
 [1556659925.033012] Running registration checks (CDMA1x: 'yes', EV-DO: 
'yes')
 [1556659925.033073] Will skip all QCDM-based registration checks
 [1556659925.033086] Will skip generic detailed registration check, we 
don't have Sprint commands
 [1556659925.033111] loading signal quality...
 [1556659925.033158] Starting QCDM-based registration checks
 [1556659925.033169]   Skipping all QCDM-based checks and falling back 
to AT-based checks
 [1556659925.033210] Starting AT-based registration checks
 [1556659925.033260] Couldn't refresh signal quality: 'No AT port 
available to run command'
 [1556659925.033324] EVDO registration: 0
 [1556659925.033346] CDMA1x registration: 1
 [1556659925.033375] Fallback access tech: 0x0400
 [1556659925.033389] Fallback access technology: 0x0400
 [1556659925.033448] No CDMA service found
 [1556659925.033470] All CDMA registration state checks done
 [1556659925.033565] Connected bearer not registered in CDMA network
 [1556659925.033686] Periodic signal quality checks scheduled in 30

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status i

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.3 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic

-- 
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/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

[Brian Murray]

Hello Alan, or anyone else affected,

Accepted netplan.io into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.3 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-cosmic
** Tags added: verification-needed-cosmic

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

i downgraded ModemManager back to 1.6.8-2ubuntu1 and the problem went
away, so it is caused by ModemManager.

attached are the logs for ModemManager 1.6.8-2ubuntu1

** Attachment added: "mm.log"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5260385/+files/mm.log

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

[Balint Reczey]

@me-b7 This does not seem to be related. Please open a new bug and
attach relevant logs to see what causes the hang.

-- 
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/1803391

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  
  [Impact] 

   * Installation of latest systemd update in -security hangs with
  current versions of unattended-upgrades in supported releases. The
  u-u-side fix is tracked in LP: #1778219.

  
  [Regression Potential] 

   * The daemons, shipped in deb:systemd, are not attempted to be
  restarted because despite package installation the system is in the
  middle of shutting down. This means that currently running daemons may
  be helding up open files on the filesystem, however all process are
  being stopped and killed as part of shutdown. Hence the worst possible
  regression from this, is an unclean shutdown, but even that shouldn't
  happen with this update.

  [Test Case]

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' f

[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Balint Reczey]

@paelzer: From LP: #1820291 it looks like there is a ready test package for 
Cosmic and that could be used to test Disco as well. ;-)
I'll set one up for Xenial using equivs.

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * If an update has a new conffile at a path that in a former version was
     a directory like
  old: /a/b/c
  new: a/b
     Here b is the new file name and was a directory in the old version.
     Then unattended upgrades breaks on installing such a package.

   * a recent qemu update has such a case and due to that triggered the
     issue in >=Bionic

   * The fix is to harden unattended upgrades to be able to handle the case
     without aborting.

  [Test Case]

  Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12
  That can be done with:
    $ time uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic
    $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic 
label=daily

  Log in and apt update & upgrade all packages, then Install the release level 
qemu in there.
    $ uvt-kvm ssh bionic-testuu
    $ sudo apt update
    $ sudo apt dist-upgrade
    $ sudo apt install unattended-upgrades
    $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7

  All before was preparation, now force the unattended upgrade to trigger the 
bug.
    $ sudo unattended-upgrade -d

  With the bug you'll find some error like:
  found pkg: qemu-guest-agent
  conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191
  current md5: f61a64ac1e48993023018fd1cff85191
  conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 
15f6ff42cbc5550a07ee21c2a471d905
  /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles 
/etc/init.d/qemu-guest-agent
  /etc/qemu/fsfreeze-hook
  found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 2057, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1773, in main
  if conffile_prompt(item.destfile):
    File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  [Regression Potential]

   * The fix is trying to detect moved conffiles by looking for /etc/foo/foo 
when the new package ships /etc/foo and /etc/foo is not a known conffile and 
also checking the renames in the opposite direction.
  The potential regression is breaking the logic for detecting changed 
conffiles and either holding back a package for no reason or trying to install 
a package with a modified conffile on the system and aborting the upgrade in 
the middle due to the appearing conffile prompt. To avoid such regressions the 
test_conffile.py tests are extended to cover rename scenarios.

  [Other Info]

   * n/a

  ---

  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
    File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents 

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Launchpad Bug Tracker]

This bug was fixed in the package ureadahead - 0.100.0-19.1

---
ureadahead (0.100.0-19.1) xenial; urgency=medium

  * add -q parameter to stop ureadahead from logging thousands of
lines of noise (LP: #1579580)

 -- Dan Streetman   Wed, 10 Apr 2019 13:59:25
-0400

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

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Won't Fix
Status in ureadahead source package in Xenial:
  Fix Released
Status in ureadahead source package in Bionic:
  Fix Released

Bug description:
  [impact]

  ureadahead logs thousands of lines of useless noise on each boot.

  [test case]

  install bionic on physical hardware (ureadhead doesn't run under virt)
  and check the boot logs:

  #journalctl -b | grep ureadahead | wc -l
  30244

  ureadahead stores its data in /var/lib/ureadahead/pack so on future
  boots, it doesn't print as many noise messages (if any), until the
  pack file is a month or more old, at which time it recreates it (at
  the next boot) and prints all the noise out again.

  to reproduce this test case without waiting a month, just remove the
  pack file and reboot.

  [regression potential]

  very little, adding the -q param only causes libnih to switch to quiet
  mode.  any regression would likely be around ureadahead not starting
  at all, which really wouldn't be that bad anyway, as ureadahead has
  been removed entirely from Ubuntu starting in cosmic.

  [other info]

  original description:

  --

  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

yparitcher, as this SRU consists of three packages, ModemManager itself
and the two libraries, try at first to downgrade only modemmanager to
the original. If this solves the problem, it is caused by modemmanager,
if not, downgrade one of the libraries, then try to downgrade the other,
... until you could spot one of the three packages having caused your
problem.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1164016] Re: restore type-ahead find

[teo1978]

> The Gnome team is extremely resistant to bring back the old intuitive 
> functionality.
> I tried to explain the problems at 
> https://gitlab.gnome.org/GNOME/nautilus/issues/244 
> , as did many others.

Trying to reason with the Gnome team is a complete waste of time.

That's why Ubuntu should either patch it, or drop Nautilus completely.


Why the f*** is this bug still in the "fix released" status? It should either 
be reopened or a new one created.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1827130] Re: /usr/bin/unattended-upgrade:UnicodeEncodeError:/usr/bin/unattended-upgrade@1976:parse_args:_process_args:_process_long_opt:process:take_action:print_help

[Balint Reczey]

*** This bug is a duplicate of bug 1806076 ***
https://bugs.launchpad.net/bugs/1806076

** This bug has been marked a duplicate of bug 1806076
   unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is 
ascii

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

Title:
  /usr/bin/unattended-upgrade:UnicodeEncodeError:/usr/bin/unattended-
  
upgrade@1976:parse_args:_process_args:_process_long_opt:process:take_action:print_help

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.10, the problem page at 
https://errors.ubuntu.com/problem/4726865ac9cd2c209f0c5dccf92755e981255090 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827130/+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 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii

[Balint Reczey]

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  unattended-upgrade --help raises UnicodeEncodeError when stdout
  encoding is ascii

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  New
Status in apt source package in Xenial:
  New
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  New

Bug description:
  [Test Case]

  rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076
  Creating bb-lp-1806076
  Starting bb-lp-1806076
  rbalint@yogi:~$ lxc shell bb-lp-1806076
  mesg: ttyname failed: No such device
  root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base
  The following package was automatically installed and is no longer required:
    libfreetype6
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
    language-pack-ru
  The following NEW packages will be installed:
    language-pack-ru language-pack-ru-base
  0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded.
  Need to get 2310 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Selecting previously unselected package language-pack-ru-base.
  (Reading database ... 28536 files and directories currently installed.)
  Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru-base (1:18.04+20180712) ...
  Selecting previously unselected package language-pack-ru.
  Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ...
  Unpacking language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru (1:18.04+20180712) ...
  Setting up language-pack-ru-base (1:18.04+20180712) ...
  Generating locales (this might take a while)...
    ru_RU.UTF-8... done
    ru_UA.UTF-8... done
  Generation complete.
  root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1983, in 
  (options, args) = parser.parse_args()  # type: ignore
    File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args
  stop = self._process_args(largs, rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args
  self._process_long_opt(rargs, values)
    File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt
  option.process(opt, value, values, self)
    File "/usr/lib/python3.6/optparse.py", line 785, in process
  self.action, self.dest, opt, value, values, parser)
    File "/usr/lib/python3.6/optparse.py", line 807, in take_action
  parser.print_help()
    File "/usr/lib/python3.6/optparse.py", line 1647, in print_help
  file.write(self.format_help())
  UnicodeEncodeError: 'ascii' codec can't encode characters in position 
126-133: ordinal not in range(128)

  root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat
  Usage: unattended-upgrade [options]

  Options:
    -h, --helpshow this help message and exit
    -d, --debug   print debug messages
    --apt-debug   make apt/libapt print verbose debug messages
    -v, --verbose print info messages
    --dry-run Simulation, download but do not install
    --download-only   Only download, do not even try to install.
    --minimal-upgrade-steps
  Upgrade in minimal steps (and allow interrupting with
  SIGTERM

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.6, the problem page at 
https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Also seen in:
   * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a

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

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

[Touch-packages] [Bug 1827130] [NEW] /usr/bin/unattended-upgrade:UnicodeEncodeError:/usr/bin/unattended-upgrade@1976:parse_args:_process_args:_process_long_opt:process:take_action:print_help

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1806076 ***
https://bugs.launchpad.net/bugs/1806076

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.10, the problem page at 
https://errors.ubuntu.com/problem/4726865ac9cd2c209f0c5dccf92755e981255090 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic xenial

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

Title:
  /usr/bin/unattended-upgrade:UnicodeEncodeError:/usr/bin/unattended-
  
upgrade@1976:parse_args:_process_args:_process_long_opt:process:take_action:print_help

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.10, the problem page at 
https://errors.ubuntu.com/problem/4726865ac9cd2c209f0c5dccf92755e981255090 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827130/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

i am very happy to try any fixes helping to try different versions to see where 
the regression was introduced.
thanks.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[yparitcher]

I would like to report a regression.
i have a verizon samsung phone using as a bluetooth CDMA/3G modem.
after the upgrade modemmanager disconnects ~30sec after connecting.

attached find modem manager --debug logs

 [1556654159.032559] Running registration checks (CDMA1x: 'yes', EV-DO: 
'yes')
 [1556654159.032629] Will skip all QCDM-based registration checks
 [1556654159.032649] Will skip generic detailed registration check, we 
don't have Sprint commands
 [1556654159.032684] loading signal quality...
 [1556654159.032748] Starting QCDM-based registration checks
 [1556654159.032766]   Skipping all QCDM-based checks and falling back 
to AT-based checks
 [1556654159.032782] Starting AT-based registration checks
 [1556654159.032841] Couldn't refresh signal quality: 'No AT port 
available to run command'
 [1556654159.032887] EVDO registration: 0
 [1556654159.032899] CDMA1x registration: 1
 [1556654159.032911] Fallback access tech: 0x0400
 [1556654159.032927] Fallback access technology: 0x0400
 [1556654159.032977] No CDMA service found
 [1556654159.032991] All CDMA registration state checks done
 [1556654159.033076] Connected bearer not registered in CDMA network
 [1556654159.033172] Periodic signal quality checks scheduled in 30s
 [1556654161.006911] Connection monitoring is unsupported by the device
 [1556654174.016444] Forcing bearer disconnection, not registered in 
CDMA network
 [1556654174.016472] Forcing disconnection of bearer 
'/org/freedesktop/ModemManager1/Bearer/0'
  [1556654174.016551] Modem /org/freedesktop/ModemManager1/Modem/0: state 
changed (connected -> disconnecting)


** Attachment added: "mm.log"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5260379/+files/mm.log

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.2

---
glib2.0 (2.56.4-0ubuntu0.18.04.2) bionic; urgency=medium

  * Backport upstream patches to fix GVariant alignment tests
d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch,
d/p/tests-Allocate-gvariant-data-from-the-heap-to-guarantee-a.patch:
Cherry-pick.

glib2.0 (2.56.4-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1816547)
+ Various buffer overflow fixes in GMarkup/GVariant/GDBus
+ Fix "Moving a bookmark item to the same URI causes a crash" (LP:
  #1760569)
  * debian/libglib2.0-0.symbols: New symbols

 -- Iain Lane   Fri, 22 Mar 2019 12:17:34 +

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1760569] Update Released

[Brian Murray]

The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1816547] Update Released

[Brian Murray]

The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1816547] Re: SRU 2.56.4 to bionic

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.2

---
glib2.0 (2.56.4-0ubuntu0.18.04.2) bionic; urgency=medium

  * Backport upstream patches to fix GVariant alignment tests
d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch,
d/p/tests-Allocate-gvariant-data-from-the-heap-to-guarantee-a.patch:
Cherry-pick.

glib2.0 (2.56.4-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1816547)
+ Various buffer overflow fixes in GMarkup/GVariant/GDBus
+ Fix "Moving a bookmark item to the same URI causes a crash" (LP:
  #1760569)
  * debian/libglib2.0-0.symbols: New symbols

 -- Iain Lane   Fri, 22 Mar 2019 12:17:34 +

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

Brian, do you have some link (bug report, ...) to this failure?

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Brian Murray]

What's going on with the network-manager arm64 autopkgtest failure with
the new modem-manager?

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu3

---
gtk+3.0 (3.22.30-1ubuntu3) bionic; urgency=medium

  [ Sebastien Bacher ]
  * d/p/Check-for-NULL-priv-popup_window-in-gtk_combo_box_popdown.patch:
- Check for NULL priv->popup_window in gtk_combo_box_popdown()
(lp: #1816032)

  [ Andrea Azzarone ]
  * d/p/restore_filechooser_typeaheadfind.patch:
- Disable typeahead if in search mode (LP: #1592177)

 -- Sebastien Bacher   Tue, 02 Apr 2019 17:30:09
+0200

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1816032] Update Released

[Brian Murray]

The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gtk_widget_destroy reports error

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released

Bug description:
  * Impact
  Buggy warnings are displayed in some cases, which can confuses users/coders

  *  Test case
  Build and use the small program attached in the comments, it should display 
no warning

  * Regression potential
  The change is a simple null check in the combo widget code, the regression 
potential is low but make sure combos work in a few softwares just in case

  --

  
  I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 
program that reports an error:-

  Gtk-CRITICAL  gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET
  (widget)' failed

  The same program runs without error on another computer with 16.04.

  The problem occurs when a ComboBoxText widget in a container (grid) is 
destroyed using gtk_widget_destroy.
  Other widgets may be affected but the problem does not occur for GtkScale 
widgets. The widget does actually get destroyed, but the message is produced in 
the process.
  I have also found that using gtk_container_remove avoids the error, but the 
docs indicate that this is
  inefficient and not preferred.

  I have attached a test program to reproduce the error. It also
  includes a few other things that I tried to see if they made any
  difference but to no avail. 'Destroy cbox' is the essential test to
  reproduce.

  System details:
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  libwxgtk3.0-dev:
    Installed: (none)
    Candidate: 3.0.4+dfsg-3
    Version table:
   3.0.4+dfsg-3 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1816032/+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 1816032] Re: gtk_widget_destroy reports error

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu3

---
gtk+3.0 (3.22.30-1ubuntu3) bionic; urgency=medium

  [ Sebastien Bacher ]
  * d/p/Check-for-NULL-priv-popup_window-in-gtk_combo_box_popdown.patch:
- Check for NULL priv->popup_window in gtk_combo_box_popdown()
(lp: #1816032)

  [ Andrea Azzarone ]
  * d/p/restore_filechooser_typeaheadfind.patch:
- Disable typeahead if in search mode (LP: #1592177)

 -- Sebastien Bacher   Tue, 02 Apr 2019 17:30:09
+0200

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  gtk_widget_destroy reports error

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released

Bug description:
  * Impact
  Buggy warnings are displayed in some cases, which can confuses users/coders

  *  Test case
  Build and use the small program attached in the comments, it should display 
no warning

  * Regression potential
  The change is a simple null check in the combo widget code, the regression 
potential is low but make sure combos work in a few softwares just in case

  --

  
  I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 
program that reports an error:-

  Gtk-CRITICAL  gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET
  (widget)' failed

  The same program runs without error on another computer with 16.04.

  The problem occurs when a ComboBoxText widget in a container (grid) is 
destroyed using gtk_widget_destroy.
  Other widgets may be affected but the problem does not occur for GtkScale 
widgets. The widget does actually get destroyed, but the message is produced in 
the process.
  I have also found that using gtk_container_remove avoids the error, but the 
docs indicate that this is
  inefficient and not preferred.

  I have attached a test program to reproduce the error. It also
  includes a few other things that I tried to see if they made any
  difference but to no avail. 'Destroy cbox' is the essential test to
  reproduce.

  System details:
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  libwxgtk3.0-dev:
    Installed: (none)
    Candidate: 3.0.4+dfsg-3
    Version table:
   3.0.4+dfsg-3 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1816032/+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 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem

[Max Samukha]

Same problem on ux501vw, Ubuntu 18.10

-- 
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/1547024

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise
  Problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure what's happening, my sound works great, there's just a
  static noise in the background that can get very annoying.

  Let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.5.0-040500rc4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zkanda 1519 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Feb 18 21:34:15 2016
  InstallationDate: Installed on 2016-02-16 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160216)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.204:bd11/12/2015:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547024/+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 1827118] [NEW] Boot black screen

[Crafsierra]

Public bug reported:

At several times boot stops and each time no boot menu (Grub)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 20:53:28 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
InstallationDate: Installed on 2019-04-29 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 7829A71
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=4f77cbd0-dae8-4ab6-a7bb-2af4093855de ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 7829A71
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn7829A71:pvrThinkPadL420:rvnLENOVO:rn7829A71:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad L420
dmi.product.name: 7829A71
dmi.product.version: ThinkPad L420
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco 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/1827118

Title:
  Boot black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  At several times boot stops and each time no boot menu (Grub)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 20:53:28 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2019-04-29 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 7829A71
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=4f77cbd0-dae8-4ab6-a7bb-2af4093855de ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET38WW (1.15 )
  dmi.board.name: 7829A71
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dm

[Touch-packages] [Bug 1592177] Update Released

[Brian Murray]

The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.24.4-0ubuntu1.1

---
gtk+3.0 (3.24.4-0ubuntu1.1) cosmic; urgency=medium

  [ Andrea Azzarone ]
  * d/p/restore_filechooser_typeaheadfind.patch:
- Disable typeahead if in search mode (LP: #1592177)

 -- Sebastien Bacher   Fri, 15 Mar 2019 21:26:23
+0100

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Released
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04

[Ruud Bos]

Quite annoying that LivePatch does not work with Disco Dingo 19.04.
At work I'm used to work with CentOS, which has reboot-less updates (including 
kernel) for ages - probably somewhere around the time when kernel 4.0 was 
released.

Some of the server VM's used to run a server-version of Ubuntu, but even
those machines were nagging for required reboots after certain updates.
It's like using Microsoft Windows :-/

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

Title:
  Livepatch is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+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 1827099] Re: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.10-1 failed to install/upgrade: triggers
  looping, abandoned

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Crash at the end of upgrade to 19.04

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue Apr 30 21:07:35 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-28 (1280 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.0
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+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 1827099] [NEW] package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned

[danielbu]

Public bug reported:

Crash at the end of upgrade to 19.04

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: shared-mime-info 1.10-1
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Tue Apr 30 21:07:35 2019
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-10-28 (1280 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1
 apt  1.8.0
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package disco third-party-packages

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

Title:
  package shared-mime-info 1.10-1 failed to install/upgrade: triggers
  looping, abandoned

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Crash at the end of upgrade to 19.04

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue Apr 30 21:07:35 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-28 (1280 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.0
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Stephane Some]

I confirm the issue in 19.04. I just upgraded from 16.04. I used to get
in fine on eduroam not anymore.

-- 
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/1748839

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1827085] [NEW] Fn key to blank screen also locks screen (i.e. logs out)

[Adrian Wenke]

Public bug reported:

This was different in Ubuntu 18.04 (and Windows). There it just turns
off the screen and when you move your mouse again, there is no need to
login. I'm using this functionality a lot because I don't use automatic
blank screen - I prefer controlling that manually. Not sure what package
controls that, possibly a udev rule?

(PS: I was thinking about whether this is actually a bug or a feature
change. But I reached the conclusion that it actually *is* a bug because
turning off the screen and locking the OS are two independent actions -
you can also lock the OS without locking the screen and the fn key
clearly refers to the screen.)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: udev 240-6ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.core.rules
Date: Tue Apr 30 18:02:31 2019
InstallationDate: Installed on 2019-04-30 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
 Bus 001 Device 002: ID 1532:005c Razer USA, Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LAB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=4a45d8a1-72c8-47a7-b54b-290b455e1f94 ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LAB.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LAB.210:bd08/25/2015:svnASUSTeKCOMPUTERINC.:pnUX303LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX303LAB
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug disco

** Description changed:

  This was different in Ubuntu 18.04 (and Windows). There it just turns
  off the screen and when you move your mouse again, there is no need to
  login. I'm using this functionality a lot because I don't use automatic
  blank screen - I prefer controlling that manually. Not sure what package
- controls that, possibly a udev rule? (PS: I was thinking about whether
- this is actually a bug or a feature change. But I reached the conclusion
- that it actually *is* a bug because turning off the screen and locking
- the OS are two independent actions (you can also lock the OS without
- locking the screen and the fn key clearly refers to the screen).
+ controls that, possibly a udev rule?
+ 
+ (PS: I was thinking about whether this is actually a bug or a feature
+ change. But I reached the conclusion that it actually *is* a bug because
+ turning off the screen and locking the OS are two independent actions -
+ you can also lock the OS without locking the screen and the fn key
+ clearly refers to the screen.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udev 240-6ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Tue Apr 30 18:02:31 2019
  InstallationDate: Installed on 2019-04-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
-  Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
-  Bus 001 Device 002: ID 1532:005c Razer USA, Ltd 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0a2a Intel Corp.
+  Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
+  Bus 001 Device 002: ID 1532:005c Razer USA, Ltd
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LAB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=4a45d8a1-72c8-47a7-b54b-290b455e1f94 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LAB.210
  dmi.board

[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract

[Sebastien Bacher]

The issue is an upstream one, could someone report it on
https://gitlab.gnome.org/GNOME/tracker/issues ?

** Changed in: tracker (Ubuntu)
   Importance: Low => High

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1826403] Re: Ethernet won't connect when cable is plugged in at boot

[Sebastien Bacher]

Thank you for your bug report, could you report that upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ ?

-- 
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/1826403

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Amr Ibrahim]

When you want to file a bug against a certain package, you type the name
of the source package, which is gtk+3.0 here. You can find the name of a
source package from its Launchpad page at the top under the Ubuntu title
(here for example https://launchpad.net/ubuntu/+source/gtk+3.0).

So you run:
ubuntu-bug gtk+3.0

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1549733] Re: SystemSettings Language&Text view: hitting Space on HW keyboard triggers switch even when it (or its list item) does not show any visual focus frame

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  SystemSettings Language&Text view: hitting Space on HW keyboard
  triggers switch even when it (or its list item) does not show any
  visual focus frame

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  Nexus7, rc-proposed, r373
  Ubuntu UI Toolkit version r1795

  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard

  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen
  This is confusing for the user as he can never be sure about which item will 
be actioned by the keyboard keys

  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame

  : “To avoid errors from unintended focus and
  distraction from irrelevant focus rings, there should be three classes
  of control: … • Non-pointer-focusable: Focusable with Tab … Yes …
  Focusable with pointing device … No”

  : “To avoid distraction from irrelevant
  selection, there should be three classes of list: … • Non-pointer-
  selectable: Selectable with arrow keys … Yes … Selectable with
  pointing device … No … Any list that is non-pointer-selectable should
  be non-pointer-focusable.”

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549733/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Amr Ibrahim]

** Tags removed: verification-needed

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1438162] Re: [osk] Touching "world" icon on the keyboard should cycle through all active keyboard layouts

[Matthew Paul Thomas]

** Description changed:

  I have 3 keyboard layouts active: English, Polish, Emoji. Now let's say
  the current layout is English. When I touch on the "world" icon the
  keyboard, the layout changes to Emoji. When I touch the icon again, the
  layout changes back to English. Then I touch it again, I get Emoji and
  so on. There's no way to change to the third layout without longpressing
  on the "world" icon and selecting the right layout there. I would expect
  the layout change to go through all active layouts, in my example
  English->Polish->Emoji->English and so on.
+ 
+ : “If you
+ tap on the button, it should cycle through layouts in order of how
+ recently you entered a character using each one.”

** No longer affects: ubuntu-ux

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

Title:
  [osk] Touching "world" icon on the keyboard should cycle through all
  active keyboard layouts

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  I have 3 keyboard layouts active: English, Polish, Emoji. Now let's
  say the current layout is English. When I touch on the "world" icon
  the keyboard, the layout changes to Emoji. When I touch the icon
  again, the layout changes back to English. Then I touch it again, I
  get Emoji and so on. There's no way to change to the third layout
  without longpressing on the "world" icon and selecting the right
  layout there. I would expect the layout change to go through all
  active layouts, in my example English->Polish->Emoji->English and so
  on.

  : “If you
  tap on the button, it should cycle through layouts in order of how
  recently you entered a character using each one.”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1438162/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Rainer Rohde]

This is what I get when typing ubuntu-bug gtk3-:

gtk3-engines-breeze  gtk3-engines-xfcegtk3-nocsd   
gtk3-engines-unico   gtk3-im-libthai   

So what do I pick?

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1826735] Re: .uuid files in font directories not removed during purge

[Sebastien Bacher]

** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  .uuid files in font directories not removed during purge

Status in fontconfig package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  On Ubuntu 19.04 (amd64):

  Removing fonts-liberation2 (2.00.5-1) ...
  dpkg: warning: while removing fonts-liberation2, directory 
'/usr/share/fonts/truetype/liberation2' not empty so not removed
  Removing fonts-opensymbol (2:102.10+LibO6.2.2-0ubuntu2) ...
  dpkg: warning: while removing fonts-opensymbol, directory 
'/usr/share/fonts/truetype/openoffice' not empty so not removed

  ls -a against these directories shows there's still .uuid files in
  there which dpkg -S is unaware of.

  Upstream bug report: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=897040

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1826735/+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 1825350] Re: [19.10 FEAT] gzip compression improvements

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [19.10 FEAT] gzip compression improvements

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in gzip package in Ubuntu:
  Fix Released

Bug description:
  Compression improvements for Linux on z using the gzip tool in support
  of better performance.

  The patch has been accepted upstream:
  http://lists.gnu.org/archive/html/bug-gzip/2019-04/msg0.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825350/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Sebastien Bacher]

same as this one, gtk+3.0

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1825350] Re: [19.10 FEAT] gzip compression improvements

[Launchpad Bug Tracker]

This bug was fixed in the package gzip - 1.10-0ubuntu1

---
gzip (1.10-0ubuntu1) eoan; urgency=medium

  * New upstream release
  * Cherrypick upstream patches for optimizied s390x zlib compression and
enable it LP: #1825350

 -- Dimitri John Ledkov   Tue, 30 Apr 2019 14:19:45
+0100

** Changed in: gzip (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 gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1825350

Title:
  [19.10 FEAT] gzip compression improvements

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gzip package in Ubuntu:
  Fix Released

Bug description:
  Compression improvements for Linux on z using the gzip tool in support
  of better performance.

  The patch has been accepted upstream:
  http://lists.gnu.org/archive/html/bug-gzip/2019-04/msg0.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825350/+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 1827031] Re: Desktop wallpaper and lock screen wallpaper corrupted after waking up the system

[Sebastien Bacher]

Thank you for your bug report. Could you add your journalctl log to the
bug after hitting the issue?

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

-- 
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/1827031

Title:
  Desktop wallpaper and lock screen wallpaper corrupted after waking up
  the system

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Desktop wallpaper and lock screen wallpaper corrupted after waking up
  the system

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  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: Tue Apr 30 13:39:10 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell XPS 15 9550 [1028:06e4]
 Subsystem: Dell XPS 15 9550 [1028:06e4]
  InstallationDate: Installed on 2019-04-28 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=/dev/nvme0n1p4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0Y9N5X
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd02/25/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA07:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/+source/gnome-shell/+bug/1827031/+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 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Julian Andres Klode]

APT sets "/usr/sbin:/usr/bin:/sbin:/bin" as its PATH since disco. We
explicitly do not add /snap/bin to the path as discussed internally,
because we do not want deb maintainer scripts to be affected implicitly
by snaps (they can still specify /snap/bin/).

** Changed in: apt (Ubuntu)
   Status: New => Fix Released

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

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  I believe later releases of bash, do too include CWD in the built-in
  PATH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+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 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Julian Andres Klode]

We don't want to change dpkg's default path, the change in apt should be
sufficient, as dpkg should not really be used on its own.

** Changed in: dpkg (Ubuntu)
   Status: New => Won't Fix

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

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  I believe later releases of bash, do too include CWD in the built-in
  PATH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+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 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

[Sebastien Bacher]

** Also affects: iptables (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

Status in iptables package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have detected that iptables does not behave in the same way as with 
previous kernel.
  Old behaviour:
  'timestart' referred to the absolute time (UTC or whatever) to start applying 
the rul
  New behaviour: 
  'timestart' refers to the offset since boot start

  It implies a migration of the old rules, and it is difficult to keep 
compatibility, as the offset is complex to behave as an absolute time.
  Is that expected? Man page suggests that the correct behaviour is the old one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1827040/+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 1287210] Re: [system settings] No indication that Wi-Fi is available ("Prompt when not connected")

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  [system settings] No indication that Wi-Fi is available ("Prompt when
  not connected")

Status in indicator-network package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Trusty r188

  0. If you haven't already, connect to a Wi-Fi network.
  1. In System Settings > Wi-Fi, turn off Wi-Fi.
  2. Turn off "Auto-join previous networks".
  3. Switch from System Settings to anything else.
  4. Turn on Wi-Fi.

  What happens: Nothing.

  What should happen: You're prompted to join the previously used Wi-Fi
  network.

  : "A
  prompt should appear, suggesting that you connect to Wi-Fi, if all of
  these conditions are true..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1287210/+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 1511015] Re: [pocket pc] No option to keep app launcher visible

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  [pocket pc] No option to keep app launcher visible

Status in Canonical System Image:
  Fix Released
Status in Canonical Pocket Desktop:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The app launcher auto-hides and there doesnt seem to be an option to
  keep it visible. no so much a bug but missing feature.

  : “The
  ‘Launcher & Menus’ panel should be present only when any of the
  settings apply…”

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511015/+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 1352784] Re: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled.

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  GPS indicator does not disappear when location services disabled, but
  bluetooth indicator does disappear when disabled.

Status in platform-api:
  Invalid
Status in indicator-location package in Ubuntu:
  Invalid
Status in platform-api package in Ubuntu:
  Invalid

Bug description:
  There is inconsistency between the bluetooth indicator and the
  location indication. Currently (image #171):

  - if location+GPS are disabled, the indicator persists.
  - if bluetooth is disabled, it disappaears.

  Which behaviour is correct?

  Further, even if the location indicator behaviour is correct, surely
  we should consider "greying out" the indicator so that the user can
  see at a glance that that indicator is disabled?

  
  Desired resolution: either implement the new indicators access method (bug 
1368856); or hide the location indicator altogether until it can be implemented 
as specced; or both.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1352784/+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 1396208] Re: Pressing volume key doesn't restore full screen brightness

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  Pressing volume key doesn't restore full screen brightness

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  1. Let device sit idle until the screen dims (not off, just dim)
  2. Press a volume up/down button

  Expected behavior: Screen returns to full brightness
  Actual Behavior: No change in brightness

  Reproduced on Nex4

  : "Any input, including
  volume buttons, should cancel the lock and therefore restore the
  display."

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1396208/+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 1447504] Re: Phone app: Wrong number is shown in call history

[Matthew Paul Thomas]

** No longer affects: ubuntu-ux

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

Title:
  Phone app: Wrong number is shown in call history

Status in dialer-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  arale, r180, ubuntu-touch/vivid-proposed

  Steps
  1. Launch dialer-app
  2. Input number a Chinese phone number, e.g. 18812345678, and dial
  3. End the call
  4. Review in call history
  =>
  The number is displayed as (881) 234-5678

  Expected:
  1) number should be complete whithout missing the leading "1"
  2) format should be like 188-1234-5678, or just 18812345678

  : "An international phone number should be
  presented following the E.123 format, while a domestic phone number
  should be presented following the national format for the country that
  the phone was in at the time."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1447504/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Rainer Rohde]

@Sebastien - so what do I file a new report against then?

When typing: ubuntu-bug GtkFileChooserDialog
I get: dpkg-query: no packages found matching GtkFileChooserDialog

Any pointer?

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * For consistency reasons sbin should be ordered before bin in PATH.
+ 
+ [Test Case]
+ 
+  * $ env -u PATH /bin/bash -c 'echo $PATH'
+ 
+ And check that matching pairs in PATH, have /sbin variant leading /bin
+ variant.
+ 
+ [Regression Potential]
+ 
+  * Ubuntu does not ship duplicate binries, with different behaviour
+ between /sbin and /bin, thus all binaries will continue to be found in
+ all locations. Also PATH is normally already set in the environment, and
+ this change only affects the fallback path when bash is executed without
+ any environment, i.e. booting with 'init=/bin/bash'
+ 
+ [Other Info]
+  
+  * Original bug report detailing inconsistent paths between various shells.
+ 
+ ---
+ 
+ 
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  
  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  
  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  
  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  
  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin
  
  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin
  
  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin
  
  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
  
  apt & dpkg => should probably initiate /usr/local-less PATH
  
  Imho the rest should probably be harmonised to:
  
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
  
  ===
  
  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :
  
  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  
  I believe later releases of bash, do too include CWD in the built-in
  PATH.

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

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  New
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  New
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/

[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * The fallback path built into bash contains '.' which leads to
+ unexpected addition of the current working directory. It should not be
+ there, just like it isnt' in pre-precise and cosmic+.
+ 
+ [Test Case]
+ 
+  * $ env -u PATH /bin/bash -c 'echo $PATH'
+ 
+ Should not have '.' as any component. Nor should there be any empty
+ components, i.e. '::'.
+ 
+ [Regression Potential]
+ 
+  * Normally PATH is always set by either init, systemd, or any other
+ hypervisor. Thus this only affects executions under bash, when it was
+ started without any environment - e.g. booting with 'init=/bin/bash'.
+ 
+ [Other Info]
+  
+  * Original bug report.
+ 
  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:
  
  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  
  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Sebastien Bacher]

@Rainer, that space thing is not what the bug was about nor an issue
with the fix, I would say that you should probably open another report

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1822062] Re: Race condition on boot between cups and sssd

[Sebastien Bacher]

** Changed in: cups (Ubuntu Disco)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: cups (Ubuntu Cosmic)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: cups (Ubuntu Bionic)
 Assignee: (unassigned) => Victor Tapia (vtapia)

** Changed in: cups (Ubuntu Xenial)
 Assignee: (unassigned) => Victor Tapia (vtapia)

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1827044] Re: binutils: debian/changelog formatting issue

[Sebastien Bacher]

** Changed in: binutils (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  binutils: debian/changelog formatting issue

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  The Debian python modules emits warnings when parsing
  the debian/changelog file from binutils 2.32-8ubuntu1:

 $ python3 -c 'from debian import changelog as c; f = 
open("debian/changelog"); c.Changelog(f)'
 /usr/lib/python3/dist-packages/debian/changelog.py:484: UserWarning: 
Unexpected line while looking for next heading of EOF:   * 
   warnings.warn(message)
 /usr/lib/python3/dist-packages/debian/changelog.py:484: UserWarning: 
Unexpected line while looking for next heading of EOF:  -- Matthias Klose 
  Wed, 13 Dec 2017 10:50:43 +
   warnings.warn(message)

  It is caused by this changelog entry:

 binutils (2.29-8ubuntu1) artful; urgency=medium

   * Merge with Debian; remaining changes:
 - Build from upstream sources.

  -- Matthias Klose   Wed, 30 Aug 2017 08:13:33 +0200
   * 

  -- Matthias Klose   Wed, 13 Dec 2017 10:50:43 +

  This doesn't appear to be present in the equivalent Debian version.

   affects ubuntu/binutils

  -- 
  bye,
  pabs

  https://wiki.debian.org/PaulWise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1827044/+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 1825350] Re: [19.10 FEAT] gzip compression improvements

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => Fix Committed

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

Title:
  [19.10 FEAT] gzip compression improvements

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gzip package in Ubuntu:
  Fix Committed

Bug description:
  Compression improvements for Linux on z using the gzip tool in support
  of better performance.

  The patch has been accepted upstream:
  http://lists.gnu.org/archive/html/bug-gzip/2019-04/msg0.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825350/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

[Will Cooke]

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Tags removed: rls-ee-incoming

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1825350] Re: [19.10 FEAT] gzip compression improvements

[Dimitri John Ledkov]

** Information type changed from Private to Public

** Changed in: gzip (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [19.10 FEAT] gzip compression improvements

Status in Ubuntu on IBM z Systems:
  Triaged
Status in gzip package in Ubuntu:
  Fix Committed

Bug description:
  Compression improvements for Linux on z using the gzip tool in support
  of better performance.

  The patch has been accepted upstream:
  http://lists.gnu.org/archive/html/bug-gzip/2019-04/msg0.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825350/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Rainer Rohde]

@Sebastien: This is only partially correct - when searching for
 , hitting space in the search jumps to the fist
occurrence of , but what if you wanted another result? So
entering  breaks the search.

The desired outcome would be that only  would descend into the
directory after the correct search result was found.

If  interrupts the search, the search is rather useless that way.

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Till Kamppeter]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Sebastien Bacher]

Tested on cosmic using 3.24.4-0ubuntu1.1, the focus is correctly saying
in the text widget as described

** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1592177/+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 1816032] Re: gtk_widget_destroy reports error

[Sebastien Bacher]

Using the current bionic-updates version the warning is displayed, after
upgrading to 3.22.30-1ubuntu3 clicking the button works without any
warning display, the fix is verified

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  gtk_widget_destroy reports error

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  Buggy warnings are displayed in some cases, which can confuses users/coders

  *  Test case
  Build and use the small program attached in the comments, it should display 
no warning

  * Regression potential
  The change is a simple null check in the combo widget code, the regression 
potential is low but make sure combos work in a few softwares just in case

  --

  
  I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 
program that reports an error:-

  Gtk-CRITICAL  gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET
  (widget)' failed

  The same program runs without error on another computer with 16.04.

  The problem occurs when a ComboBoxText widget in a container (grid) is 
destroyed using gtk_widget_destroy.
  Other widgets may be affected but the problem does not occur for GtkScale 
widgets. The widget does actually get destroyed, but the message is produced in 
the process.
  I have also found that using gtk_container_remove avoids the error, but the 
docs indicate that this is
  inefficient and not preferred.

  I have attached a test program to reproduce the error. It also
  includes a few other things that I tried to see if they made any
  difference but to no avail. 'Destroy cbox' is the essential test to
  reproduce.

  System details:
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  libwxgtk3.0-dev:
    Installed: (none)
    Candidate: 3.0.4+dfsg-3
    Version table:
   3.0.4+dfsg-3 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1816032/+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 1827044] [NEW] binutils: debian/changelog formatting issue

[Paul Wise (Debian)]

Public bug reported:

The Debian python modules emits warnings when parsing
the debian/changelog file from binutils 2.32-8ubuntu1:

   $ python3 -c 'from debian import changelog as c; f = 
open("debian/changelog"); c.Changelog(f)'
   /usr/lib/python3/dist-packages/debian/changelog.py:484: UserWarning: 
Unexpected line while looking for next heading of EOF:   * 
 warnings.warn(message)
   /usr/lib/python3/dist-packages/debian/changelog.py:484: UserWarning: 
Unexpected line while looking for next heading of EOF:  -- Matthias Klose 
  Wed, 13 Dec 2017 10:50:43 +
 warnings.warn(message)

It is caused by this changelog entry:

   binutils (2.29-8ubuntu1) artful; urgency=medium

 * Merge with Debian; remaining changes:
   - Build from upstream sources.

-- Matthias Klose   Wed, 30 Aug 2017 08:13:33 +0200
 * 

-- Matthias Klose   Wed, 13 Dec 2017 10:50:43 +

This doesn't appear to be present in the equivalent Debian version.

 affects ubuntu/binutils

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

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

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

Title:
  binutils: debian/changelog formatting issue

Status in binutils package in Ubuntu:
  New

Bug description:
  The Debian python modules emits warnings when parsing
  the debian/changelog file from binutils 2.32-8ubuntu1:

 $ python3 -c 'from debian import changelog as c; f = 
open("debian/changelog"); c.Changelog(f)'
 /usr/lib/python3/dist-packages/debian/changelog.py:484: UserWarning: 
Unexpected line while looking for next heading of EOF:   * 
   warnings.warn(message)
 /usr/lib/python3/dist-packages/debian/changelog.py:484: UserWarning: 
Unexpected line while looking for next heading of EOF:  -- Matthias Klose 
  Wed, 13 Dec 2017 10:50:43 +
   warnings.warn(message)

  It is caused by this changelog entry:

 binutils (2.29-8ubuntu1) artful; urgency=medium

   * Merge with Debian; remaining changes:
 - Build from upstream sources.

  -- Matthias Klose   Wed, 30 Aug 2017 08:13:33 +0200
   * 

  -- Matthias Klose   Wed, 13 Dec 2017 10:50:43 +

  This doesn't appear to be present in the equivalent Debian version.

   affects ubuntu/binutils

  -- 
  bye,
  pabs

  https://wiki.debian.org/PaulWise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1827044/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Christian Ehrhardt ]

I only have a testcase for Bionic, I hope rbalint has one for the other
releases.


root@b:~# apt list --upgradable
Listing... Done
qemu-guest-agent/bionic-updates,bionic-security 1:2.11+dfsg-1ubuntu7.12 amd64 
[upgradable from: 1:2.11+dfsg-1ubuntu7]
N: There is 1 additional version. Please use the '-a' switch to see it
root@b:~# 
root@b:~# 
root@b:~# sudo unattended-upgrade -d
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
Using 
(^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*)
 regexp to find kernel packages
Using 
(^linux-image-4\.15\.0\-48\-generic$|^linux-headers-4\.15\.0\-48\-generic$|^linux-image-extra-4\.15\.0\-48\-generic$|^linux-modules-4\.15\.0\-48\-generic$|^linux-modules-extra-4\.15\.0\-48\-generic$|^linux-signed-image-4\.15\.0\-48\-generic$|^kfreebsd-image-4\.15\.0\-48\-generic$|^kfreebsd-headers-4\.15\.0\-48\-generic$|^gnumach-image-4\.15\.0\-48\-generic$|^.*-modules-4\.15\.0\-48\-generic$|^.*-kernel-4\.15\.0\-48\-generic$|^linux-backports-modules-.*-4\.15\.0\-48\-generic$|^linux-modules-.*-4\.15\.0\-48\-generic$|^linux-tools-4\.15\.0\-48\-generic$|^linux-cloud-tools-4\.15\.0\-48\-generic$)
 regexp to find running kernel packages
Checking: qemu-guest-agent ([, ])
pkgs that look like they should be upgraded: qemu-guest-agent
Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
qemu-guest-agent amd64 1:2.11+dfsg-1ubuntu7.12 [232 kB] 

Fetched 232 kB in 0s (0 B/s)

 
fetch.run() result: 0
http://archive.ubuntu.com/ubuntu/pool/universe/q/qemu/qemu-guest-agent_2.11+dfsg-1ubuntu7.12_amd64.deb'
 ID:1 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/qemu-guest-agent_1%3a2.11+dfsg-1ubuntu7.12_amd64.deb)
found pkg: qemu-guest-agent
conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191
current md5: f61a64ac1e48993023018fd1cff85191
conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 
15f6ff42cbc5550a07ee21c2a471d905
/etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles 
/etc/init.d/qemu-guest-agent
/etc/qemu/fsfreeze-hook
found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 2057, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1773, in main
if conffile_prompt(item.destfile):
  File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt
with open(prefix + conf_file, 'rb') as fp:
IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

That is good, it means that the error is affecting this system.
After installing the new unattended upgrades from proposed this works fine now:

root@b:~# apt list --upgradable
Listing... Done
qemu-guest-agent/bionic-updates,bionic-security 1:2.11+dfsg-1ubuntu7.12 amd64 
[upgradable from: 1:2.11+dfsg-1ubuntu7]
N: There is 1 additional version. Please use the '-a' switch to see it
root@b:~# sudo unattended-upgrade -d
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
Using 
(^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*)
 regexp to find kernel packages
Using 
(^linux-image-4\.15\.0\-48\-generic$|^linux-headers-4\.15\.0\-48\-generic$|^linux-image-extra-4\.15\.0\-48\-generic$|^linux-modules-4\.15\.0\-48\-generic$|^linux-modules-extra-4\.15\.0\-48\-generic$|^linux-signed-image-4\.15\.0\-48\-generic$|^kfreebsd-image-4\.15\.0\-48\-generic$|^kfreebsd-headers-4\.15\.0\-48\-generic$|^gnumach-image-4\.15\.0\-48\-generic$|^.*-modules-4\.15\.0\-48\-generic$|^.*-kernel-4\.15\.0\-48\-generic$|^

[Touch-packages] [Bug 1827031] [NEW] Desktop wallpaper and lock screen wallpaper corrupted after waking up the system

[Ievgen Sobko]

Public bug reported:

Desktop wallpaper and lock screen wallpaper corrupted after waking up
the system

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
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: Tue Apr 30 13:39:10 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Dell XPS 15 9550 [1028:06e4]
   Subsystem: Dell XPS 15 9550 [1028:06e4]
InstallationDate: Installed on 2019-04-28 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0025 Intel Corp. 
 Bus 001 Device 003: ID 0c45:6713 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=/dev/nvme0n1p4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.0
dmi.board.name: 0Y9N5X
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd02/25/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA07:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9550
dmi.product.sku: 06E4
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption disco ubuntu

** Attachment added: "2019-04-30__13-37-46.png"
   
https://bugs.launchpad.net/bugs/1827031/+attachment/5260252/+files/2019-04-30__13-37-46.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/1827031

Title:
  Desktop wallpaper and lock screen wallpaper corrupted after waking up
  the system

Status in xorg package in Ubuntu:
  New

Bug description:
  Desktop wallpaper and lock screen wallpaper corrupted after waking up
  the system

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  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: Tue Apr 30 13:39:10 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell XPS 15 9550 [1028:06e4]
 Subsystem: Dell XPS 15 9550 [1028:06e4]
  InstallationDate: Installed on 2019-04-28 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Ding

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop

[Sebastien Bacher]

Without having a backtrace it's a bit tricky to debug.

To figure out why apport isn't working, could you look at the content of
/var/log/apport.log to see if there is anything useful there? Maybe try
enabling apport by editing /etc/default/apport and restarting.

If apport doesn't work for some reason it would be possible to manually
attach gdb from a vt (if you switch to one, gdm respawning might make
that difficult) or from a ssh login.


The logs also have that error which could be part of the issue
'Failed to load /usr/lib/xorg/modules/drivers/xrdpdev_drv.so: 
/usr/lib/xorg/modules/drivers/xrdpdev_drv.so: undefined symbol: 
rdpRRModeDestroy'

Could you give the output of "dpkg -l | grep rdp" and maybe uninstall
xorgxrdp and see if that makes a difference?

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

Title:
  gnome-shell trap int3 no desktop

Status in gdm3 package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/

[Touch-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop

[Sebastien Bacher]

The log also has
'[   601.234] (EE) mga: The PCI device 0x532 at 01@00:03:0 has a kernel module 
claiming it.
[   601.234] (EE) mga: This driver cannot operate until it has been unloaded.
[   601.235] (EE) [drm] Failed to open DRM device for pci::02:00.0: -2'

Unsure that has to do with the issue though

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

Title:
  gnome-shell trap int3 no desktop

Status in gdm3 package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile: /home/greg/xorg.conf.new
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1826025/+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/

[Touch-packages] [Bug 460897] Re: Tracker not returning known results

[Sebastien Bacher]

The bug is 9 years old, is it still an issue?

** Changed in: tracker (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Tracker not returning known results

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: tracker

  Tracker is not giving me results when I query a known-existing string.
  I have a large collection of MP3s that are indexed on a mdadm RAID5
  array that are shared through Samba. I have many ZZ Top albums on this
  share but Tracker will return 0 results when the query "zz top" is
  used. A similar search for "acdc" also returns 0 results even though
  many songs exist in the indexed locations. The total files indexed by
  the Tracker daemon is 337951, 49562 of them being identified as music
  in the "Statistics" dialog. Most queries return correct results, these
  were just two that I tried to verify that the Tracker was working
  correctly, and it isn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/460897/+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