[Desktop-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

[Dieter Maurer]

Calling "apport-collect 1649566" reproducible causes the crash reported in this 
ticket.
Is there a different way to provide the information you need?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: 

[Desktop-packages] [Bug 1746874] Dependencies.txt

[Daniel van Vugt]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047323/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746874] ProcEnviron.txt

[Daniel van Vugt]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047326/+files/ProcEnviron.txt

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746874] JournalErrors.txt

[Daniel van Vugt]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047324/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746874] ProcCpuinfoMinimal.txt

[Daniel van Vugt]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047325/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Daniel van Vugt]

apport information

** Tags added: apport-collected

** Description changed:

  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).
  
  This is despite:
  
  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0
  
  So really there are two problems:
  
  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:
  
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.8-0ubuntu7
+ Architecture: amd64
+ CrashReports:
+  640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
+  640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
+  640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
+  640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
+  640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-12-12 (52 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
+ Package: mutter
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
+ Tags:  bionic
+ Uname: Linux 4.13.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "ApportLog.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047322/+files/ApportLog.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic 

[Desktop-packages] [Bug 1746882] Re: gvfsd-mtp crashed with SIGSEGV

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047311/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047313/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047317/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047318/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047319/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047320/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1746882/+attachment/5047321/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1746882

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Issue in the background, doesn't seem related to a device
  connection/disconnection. Maybe on resume from standby..

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.34.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Mon Jan 29 08:00:55 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2018-01-24 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180123)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/16
  SegvAnalysis:
   Segfault happened at: 0x7fdf2959e5a9:mov0x18(%rax),%rax
   PC (0x7fdf2959e5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave ~/core files (not crash files)

[Daniel van Vugt]

I wonder - is this the default kernel behaviour if the pipe command
fails?

/proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P

** Summary changed:

- gnome-shell and Xwayland sometimes leave ~/core files (not crash files)
+ gnome-shell and Xwayland sometimes leave $HOME/core files (should be crash 
files)

** Description changed:

- gnome-shell and Xwayland sometimes leave ~/core files (not crash files)
+ gnome-shell and Xwayland sometimes leave $HOME/core files (should be
+ /var/crash files).
  
  This is despite:
  
  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0
  
  So really there are two problems:
  
  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:
-  
+ 
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- gnome-shell and Xwayland sometimes leave $HOME/core files (should be crash 
files)
+ gnome-shell and Xwayland sometimes leave $HOME/core files (should be 
/var/crash files)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1746874] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1746874

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave ~/core files (not crash files)

[Daniel van Vugt]

This issue was first mentioned in bug 1746653. But then I noticed my
machine doing it too.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1746874] [NEW] gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Daniel van Vugt]

Public bug reported:

gnome-shell and Xwayland sometimes leave $HOME/core files (should be
/var/crash files).

This is despite:

$ grep . /proc/sys/kernel/core_*
/proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
/proc/sys/kernel/core_pipe_limit:0
/proc/sys/kernel/core_uses_pid:0

So really there are two problems:

1. ~/core files are created but no /var/crash/ files
2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
Date: Fri Feb  2 15:13:52 2018
DisplayManager:

InstallationDate: Installed on 2017-12-12 (52 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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


** Tags: amd64 apport-bug bionic

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1746865] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1746865

Title:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I was updating the packages provided by the software updater.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Thu Feb  1 15:31:53 2018
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1746865/+subscriptions

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

[Desktop-packages] [Bug 1746865] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Ravindra Gullapalli]

Public bug reported:

I was updating the packages provided by the software updater.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
Date: Thu Feb  1 15:31:53 2018
ErrorMessage: installed tex-common package post-installation script subprocess 
returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: tex-common
Title: package tex-common 6.09 failed to install/upgrade: installed tex-common 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1746865

Title:
  package tex-common 6.09 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I was updating the packages provided by the software updater.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Thu Feb  1 15:31:53 2018
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1746865/+subscriptions

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

[Desktop-packages] [Bug 1746819] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[dino99]

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1746819

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Trying to run an upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Feb  1 15:58:41 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bNaUCt/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-12-27 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-11-11 (82 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1746819/+subscriptions

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

[Desktop-packages] [Bug 1746859] Re: gnome-shell wayland is spamming syslog with wl_ messages

[Daniel van Vugt]

Rocko, what does your /etc/environment look like?

I wonder if you have verbose or debug modes enabled.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746859

Title:
  gnome-shell wayland is spamming syslog with wl_ messages

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Whenever I run gnome-shell under wayland now in Ubuntu 18.04, I get
  thousands of messages in syslog like this:

  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769569.758] 
wl_callb...@48.done(9760355)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.845]  -> 
wl_surface@31.attach(wl_buffer@50, 0, 0)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.888]  -> 
wl_surface@31.set_buffer_scale(2)
  wl_surface@31.set_input_region(wl_region@48)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.235]  -> 
wl_surface@31.frame(new id wl_callback@44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.252]  -> 
wl_surface@31.commit()
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.277] 
wl_surface@31.set_input_region(wl_region@48)
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.286] 
wl_region@48.destroy()
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.293]  -> 
wl_display@1.delete_id(48)
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.342] 
wl_surface@31.frame(new id wl_display@1.delete_id(44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.628] 
wl_display@1.delete_id(44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.669] 
wl_keybo...@28.key(344, 9760410, 46, 1)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.727] 
wl_callb...@44.done(9760414)

  This didn't used to happen and it doesn't happen running under X.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 11:53:30 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (169 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (76 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1746859/+subscriptions

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

[Desktop-packages] [Bug 1746771] Re: black background drop-down menu

[Kai-Heng Feng]

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1746771

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1746859] [NEW] gnome-shell wayland is spamming syslog with wl_ messages

[Rocko]

Public bug reported:

Whenever I run gnome-shell under wayland now in Ubuntu 18.04, I get
thousands of messages in syslog like this:

Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769569.758] 
wl_callb...@48.done(9760355)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.845]  -> 
wl_surface@31.attach(wl_buffer@50, 0, 0)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.888]  -> 
wl_surface@31.set_buffer_scale(2)
wl_surface@31.set_input_region(wl_region@48)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.235]  -> 
wl_surface@31.frame(new id wl_callback@44)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.252]  -> 
wl_surface@31.commit()
Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.277] 
wl_surface@31.set_input_region(wl_region@48)
Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.286] 
wl_region@48.destroy()
Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.293]  -> 
wl_display@1.delete_id(48)
Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.342] 
wl_surface@31.frame(new id wl_display@1.delete_id(44)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.628] 
wl_display@1.delete_id(44)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.669] 
wl_keybo...@28.key(344, 9760410, 46, 1)
Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.727] 
wl_callb...@44.done(9760414)

This didn't used to happen and it doesn't happen running under X.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu2
Uname: Linux 4.15.0-041500-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  2 11:53:30 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-08-16 (169 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2017-11-17 (76 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1746859

Title:
  gnome-shell wayland is spamming syslog with wl_ messages

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I run gnome-shell under wayland now in Ubuntu 18.04, I get
  thousands of messages in syslog like this:

  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769569.758] 
wl_callb...@48.done(9760355)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.845]  -> 
wl_surface@31.attach(wl_buffer@50, 0, 0)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769618.888]  -> 
wl_surface@31.set_buffer_scale(2)
  wl_surface@31.set_input_region(wl_region@48)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.235]  -> 
wl_surface@31.frame(new id wl_callback@44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769619.252]  -> 
wl_surface@31.commit()
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.277] 
wl_surface@31.set_input_region(wl_region@48)
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.286] 
wl_region@48.destroy()
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.293]  -> 
wl_display@1.delete_id(48)
  Feb  2 11:52:44 xps15-9560 org.gnome.Shell.desktop[31805]: [2769619.342] 
wl_surface@31.frame(new id wl_display@1.delete_id(44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.628] 
wl_display@1.delete_id(44)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.669] 
wl_keybo...@28.key(344, 9760410, 46, 1)
  Feb  2 11:52:44 xps15-9560 gnome-terminal-server[32220]: [2769629.727] 
wl_callb...@44.done(9760414)

  This didn't used to happen and it doesn't happen running under X.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 11:53:30 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (169 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (76 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1746859/+subscriptions

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

[Desktop-packages] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Alex Tu]

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1728547/+attachment/5047201/+files/Xorg.0.log

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

** Changed in: oem-priority
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions

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

[Desktop-packages] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Alex Tu]

verified on BRM4-DVT1-C2H (201710-25874)

ubuntu-drivers-common: 1:0.4.17.6


** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1728547/+attachment/5047200/+files/gpu-manager.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions

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

[Desktop-packages] [Bug 1746856] [NEW] usb printer does not print (canon d530)

[Alex Yasbek]

Public bug reported:

Bus 002 Device 005: ID 04a9:2775 Canon, Inc. 
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 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated 
Camera (0.3MP)
Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 Mouse
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

Description:Ubuntu 17.10
Release:17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cups 2.2.4-7ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  1 19:14:46 2018
InstallationDate: Installed on 2018-01-22 (10 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Lpstat: device for Canon_D530_D560: cnusb:/dev/usb/lp0
MachineType: LENOVO 4239CTO
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon_D530_D560.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon_D530_D560.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=1aa4feb1-4b49-43d5-bcce-25b90425a69e ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET58WW (1.38 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4239CTO
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:bvr8AET58WW(1.38):bd07/05/2012:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T520
dmi.product.name: 4239CTO
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1746856

Title:
  usb printer does not print (canon d530)

Status in cups package in Ubuntu:
  New

Bug description:
  Bus 002 Device 005: ID 04a9:2775 Canon, Inc. 
  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 04f2:b217 Chicony Electronics Co., Ltd Lenovo 
Integrated Camera (0.3MP)
  Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 Mouse
  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

  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cups 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 19:14:46 2018
  InstallationDate: Installed on 2018-01-22 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lpstat: device for Canon_D530_D560: cnusb:/dev/usb/lp0
  MachineType: LENOVO 4239CTO
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon_D530_D560.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon_D530_D560.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=1aa4feb1-4b49-43d5-bcce-25b90425a69e ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET58WW (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  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:bvr8AET58WW(1.38):bd07/05/2012:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1740507] Re: error: Python gobject/dbus may be not installed

[Afshan F]

** Changed in: hplip
   Status: New => In Progress

** Changed in: hplip
 Assignee: (unassigned) => Afshan F (afshan)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1740507

Title:
  error: Python gobject/dbus may be not installed

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  New

Bug description:
  Done.
  root@fanta-Lenovo:~# hp-plugin

  HP Linux Imaging and Printing System (ver. 3.17.11)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  warning: It is not recommended to run 'hp-plugin' in a root mode.

  HP Linux Imaging and Printing System (ver. 3.17.11)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  (Note: Defaults for each question are maked with a '*'. Press 
  to accept the default.)

  
  --
  | PLUG-IN INSTALLATION FOR HPLIP 3.17.11 |
  --

Option  Description   
--  --
d   Download plug-in from HP (recommended)
p   Specify a path to the plug-in (advanced)  
q   Quit hp-plugin (skip installation)

  Enter option (d=download*, p=specify path, q=quit) ? d

  ---
  | DOWNLOAD PLUGIN |
  ---

  Checking for network connection...
  Downloading plug-in from: 
  Downloading plug-in: [\   

] 0% Receiving digital keys: /usr/bin/gpg --homedir 
/home/fanta/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu 
--recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
   

  --
  | INSTALLING PLUG-IN |
  --

  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.17.11 Plugin Self Extracting 
Archive..
  Traceback (most recent call last):
File "./plugin_install.py", line 107, in 
  (UI_TOOLKIT_QT3, UI_TOOLKIT_QT4, UI_TOOLKIT_QT5), True)
  NameError: name 'UI_TOOLKIT_QT5' is not defined
  error: Python gobject/dbus may be not installed

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Sorry for the confusion. Comment #49 appeared at a time when
1:11.1-1ubuntu4 had _vanished_ from the archive. So for a while it was
not "released".

Then minutes later, vorlon uploaded a new proposed version
1:11.1-1ubuntu5, and 1:11.1-1ubuntu4 reappeared too:

https://launchpad.net/ubuntu/+source/pulseaudio

Now released.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Description changed:

  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty
  
  affected to pacemaker 1.1.10.
+ affected to glib2.0 2.40.2-0ubuntu1
+ 
+ Please note that patch for pacemaker is created myself.
  
  [Test Case]
  
  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage
  
  [Regression]
- Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[2] changed file structure ( e.g 
attrd created from tools/attrd.c ), This might affect to system. however, both 
of patches are landed to 1.11, so risk is not that high.
+ Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
+ For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.
  
  [Others]
  
  Related commits.
  
- [1] commit a1a6922e43dfe80b23887a88401cbb93fe3645c0
- Author: David Vossel 
- Date:   Tue Jan 7 14:02:18 2014 -0600
- 
- Fix: ipc: fix memory leak for failed ipc client connections.
- 
- When pacemaker ipc servers accept client connections, client
- state data is allocated when the libqb 'accept' callback function is
- invoked.  It is possible however that even after the client
- accepts the connection in the libqb 'accept' callback, the connection
- could still fail to initialize fully if the client side hangs up.
- 
- Currently this results in the client state data never being
- destroyed because the libqb "close" callback for client connection
- is never invoked on the server side. Instead, libqb jumps directly to
- the "destroy" callback because the connection never actually got created.
- 
- To account for this memory leak, pacemaker needs to verify client
- state data is destroyed in the destroy callback.
- [2] commit a7b61e276120184c7586a3217ed3571a982f5017
+ [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000
  
  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng
  
  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3
  
  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168
  
  $ rmadison pacemaker
-  pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty 
-  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
-  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates
+  pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
+  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
+  pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates
  
-  pacemaker | 1.1.14-2ubuntu1   | xenial
-  pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
-  pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
-  pacemaker | 1.1.16-1ubuntu1   | zesty
-  pacemaker | 1.1.16-1ubuntu1   | artful
-  pacemaker | 1.1.18~rc3-1ubuntu1   | bionic 
+  pacemaker | 1.1.14-2ubuntu1   | xenial
+  pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
+  pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
+  pacemaker | 1.1.16-1ubuntu1   | zesty
+  pacemaker | 1.1.16-1ubuntu1   | artful
+  pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --
+ 
+ For glib
+ [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
+ [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
+ [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
+ [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a
  
  [Original Description]
  
  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.
  
  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused by
  the g_dbus API, the use of which was removed in Pacemaker 1.11.
  
  I've also attached the Valgrind output from the run that exposed the
  issue.
  
  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).
  
  If not, can you 

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[Daniel van Vugt]

If you experience "similar" crashes please start by logging your own
bug.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1729028

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions

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

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[Daniel van Vugt]

Please leave the status as Incomplete while we wait for feedback (crash
files, core files, stack traces) from the original reporter.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1729028

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions

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

[Desktop-packages] [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

[Daniel van Vugt]

It looks like the upstream fix(es) have landed ready for mutter 3.26.3.
Although there are a couple so I'm not sure.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724439

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Patch added: "lp1316970_trusty_glib2.0.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047147/+files/lp1316970_trusty_glib2.0.debdiff

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Attachment added: "valgrind-afterpatch"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047145/+files/valgrind-afterpatch

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Attachment added: "valgrind-beforepatch"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047144/+files/valgrind-beforepatch

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Patch added: "lp1316970_trusty_pacemaker.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047146/+files/lp1316970_trusty_pacemaker.debdiff

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1723831] Re: Alt+Tab doesn't work for same application with multiple windows

[Daniel van Vugt]

Since this is a Gnome design feature, but understandably annoying for
users coming from other environments, I think the right resolution is
"Won't Fix".

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723831

Title:
  Alt+Tab doesn't work for same application with multiple windows

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  I open 2 File manager windows and also have other windows open. From
  the side dock, I can switch between the 2 File manager windows. But
  Alt+Tab doesn't swap back and forth like expected, it picks some other
  open application and brings that to the front.

  Tested this with Gnome Terminal and get the same result. Have open 2
  terminals and a Firefox browser. I'd think Alt+Tab would switch
  between them if they were both the current and last used window, but
  no, Firefox comes to the front.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 19:46:16 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-29 (717 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723831/+subscriptions

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

[Desktop-packages] [Bug 1725078] Re: Can't set Ctrl+Shift as a shortcut

[Daniel van Vugt]

Alright. I understand why software wouldn't support such combos by
default. Because both keys are modifiers and not normal keys.

That said, with more work it is usually possible to make software
respond to modifier taps, as we have done in Unity before.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725078

Title:
  Can't set Ctrl+Shift as a shortcut

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Can't set Ctrl+Shift (and many other key combinations) as a shortcut
  in new and shiny Ubuntu 17.10. Nothing happens when I press these
  keys. For example, when setting "Switch to next input source"
  shortcut, a window pops up waiting for a key combination, but nothing
  happens at all when I press Ctrl+Shift. I can still set some
  combinations like Super+Space, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-shortcuts (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 04:03:29 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell-extension-shortcuts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725078/+subscriptions

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

[Desktop-packages] [Bug 1723831] Re: Alt+Tab doesn't work for same application with multiple windows

[Daniel van Vugt]

"Windows in the window switcher are grouped by application. Previews of
applications with multiple windows pop down as you click through. Hold
down Super and press ` (or the key above Tab) to step through the list."

[https://help.gnome.org/users/gnome-help/stable/shell-windows-
switching.html]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723831

Title:
  Alt+Tab doesn't work for same application with multiple windows

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  I open 2 File manager windows and also have other windows open. From
  the side dock, I can switch between the 2 File manager windows. But
  Alt+Tab doesn't swap back and forth like expected, it picks some other
  open application and brings that to the front.

  Tested this with Gnome Terminal and get the same result. Have open 2
  terminals and a Firefox browser. I'd think Alt+Tab would switch
  between them if they were both the current and last used window, but
  no, Firefox comes to the front.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 19:46:16 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-29 (717 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723831/+subscriptions

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

[Desktop-packages] [Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[Daniel van Vugt]

Launchpad bug 1724439 already covers that.

It would be a bonus if this bug was resolved by the same fix so we'll
wait and see.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726352

Title:
  gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

  ---

  Ordinary bug report in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 13:08:15 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi
   PC (0x7f8d82fc8c5c) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_x11_configure_request () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Please un-reject 1:11.1-1ubuntu4 -- it is good, and only blocked by
gsequencer bug 1743511.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Patch removed: "lp1316970_trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5031302/+files/lp1316970_trusty.debdiff

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[2] changed file structure ( e.g 
attrd created from tools/attrd.c ), This might affect to system. however, both 
of patches are landed to 1.11, so risk is not that high.

  [Others]

  Related commits.

  [1] commit a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Author: David Vossel 
  Date:   Tue Jan 7 14:02:18 2014 -0600

  Fix: ipc: fix memory leak for failed ipc client connections.

  When pacemaker ipc servers accept client connections, client
  state data is allocated when the libqb 'accept' callback function is
  invoked.  It is possible however that even after the client
  accepts the connection in the libqb 'accept' callback, the connection
  could still fail to initialize fully if the client side hangs up.

  Currently this results in the client state data never being
  destroyed because the libqb "close" callback for client connection
  is never invoked on the server side. Instead, libqb jumps directly to
  the "destroy" callback because the connection never actually got created.

  To account for this memory leak, pacemaker needs to verify client
  state data is destroyed in the destroy callback.
  [2] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty 
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic 
  --

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu4

---
pulseaudio (1:11.1-1ubuntu4) bionic; urgency=high

  * 0030-load-module-switch-on-connect.patch: Correct typo in default.pa
causing pulseaudio startup failure. (LP: #1742750, LP: #1732629)
  * Refresh patches to apply more cleanly:
- 0802-alsa-mixer-Add-support-for-usb-audio-in-the-Dell-doc.patch
- 0803-build-sys-add-the-Dell-dock-TB16-configuration.patch

 -- Daniel van Vugt   Fri, 12 Jan 2018
10:23:11 +0800

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1732629] Re: Selecting USB Amp/Dac audio output in gnome sound does nothing

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu4

---
pulseaudio (1:11.1-1ubuntu4) bionic; urgency=high

  * 0030-load-module-switch-on-connect.patch: Correct typo in default.pa
causing pulseaudio startup failure. (LP: #1742750, LP: #1732629)
  * Refresh patches to apply more cleanly:
- 0802-alsa-mixer-Add-support-for-usb-audio-in-the-Dell-doc.patch
- 0803-build-sys-add-the-Dell-dock-TB16-configuration.patch

 -- Daniel van Vugt   Fri, 12 Jan 2018
10:23:11 +0800

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1732629

Title:
  Selecting USB Amp/Dac audio output in gnome sound does nothing

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
  correctly recognized and I can play audio through it via aplay, but
  when I select it as my output sink from gnome sound, nothing happens:
  apps still output sound via the speakers.

  In order to fix it I have to restart pulseaudio.
  I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
   /dev/snd/controlC1:  sergio 1374 F pulseaudio
   /dev/snd/controlC0:  sergio 1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:03:19 2017
  InstallationDate: Installed on 2017-10-24 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

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

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

[Desktop-packages] [Bug 1745383] Re: setup.py crashed with TypeError in readwriteFaxInformation(): critical(QWidget, str, str, buttons: Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] =

[Badal]

** Changed in: hplip (Ubuntu)
   Status: Opinion => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1745383

Title:
  setup.py crashed with TypeError in readwriteFaxInformation():
  critical(QWidget, str, str, buttons:
  Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] =
  QMessageBox.Ok, defaultButton: QMessageBox.StandardButton =
  QMessageBox.NoButton): argument 5 has unexpected type
  'StandardButtons'

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  In Progress

Bug description:
  Happened while creating print/fax queues for the HP OfficeJet Pro 8730
  with "hp-setup". Queues got created, seems that the crash happened
  afterwards. Main window did not crash, only some sub process.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: hplip-data 3.17.10+repack0-2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 25 10:52:09 2018
  Dependencies:
   gcc-7-base 7.2.0-18ubuntu2
   libc6 2.26-0ubuntu2.1 [origin: unknown]
   libgcc1 1:7.2.0-18ubuntu2
   liblzma5 5.2.2-1.3
   xz-utils 5.2.2-1.3
  ExecutablePath: /usr/share/hplip/setup.py
  InstallationDate: Installed on 2015-04-30 (1001 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.6
  MachineType: LENOVO 20A8X50300
  PackageArchitecture: all
  Papersize: letter
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-setup
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=ff9fee12-fd92-4cfd-88bf-c8f57ffba318 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/bin/hp-setup']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: hplip
  Title: setup.py crashed with TypeError in readwriteFaxInformation(): 
critical(QWidget, str, str, buttons: Union[QMessageBox.StandardButtons, 
QMessageBox.StandardButton] = QMessageBox.Ok, defaultButton: 
QMessageBox.StandardButton = QMessageBox.NoButton): argument 5 has unexpected 
type 'StandardButtons'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo wireshark
  dmi.bios.date: 09/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET40WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8X50300
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET40WW(1.17):bd09/02/2014:svnLENOVO:pn20A8X50300:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8X50300:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X1 Carbon 2nd
  dmi.product.name: 20A8X50300
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1725078] Re: Can't set Ctrl+Shift as a shortcut

[shankao]

@Daniel, I can confirm that many keyboard shortcuts can't be set under
Xorg either in Bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725078

Title:
  Can't set Ctrl+Shift as a shortcut

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Can't set Ctrl+Shift (and many other key combinations) as a shortcut
  in new and shiny Ubuntu 17.10. Nothing happens when I press these
  keys. For example, when setting "Switch to next input source"
  shortcut, a window pops up waiting for a key combination, but nothing
  happens at all when I press Ctrl+Shift. I can still set some
  combinations like Super+Space, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-shortcuts (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 04:03:29 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell-extension-shortcuts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725078/+subscriptions

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

[Desktop-packages] [Bug 1715213] Re: Adopt openSUSE patch that adds high-res icons for Firefox, so the Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox icon

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1715213

Title:
  Adopt openSUSE patch that adds high-res icons for Firefox, so the
  Large Icons task switcher in KDE Plasma doesn't have an ugly Firefox
  icon

Status in One Hundred Papercuts:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Right now, Firefox in Ubuntu is packaged with a set of low-res icons.
  Because of this, if you use KDE Plasma with the Large Icons alt-tab
  task switcher, the Firefox icons look ugly:
  https://i.imgur.com/LdL7wlM.png

  openSUSE packagers patch in larger icons, and so in openSUSE, they
  look sharp and crisp: https://i.imgur.com/Le8ZhWg.png

  I have opened a ticket with Mozilla, but it has been ignored:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1371932

  So until they fix it upstream, we may want to consider adopting the
  openSUSE patch in Ubuntu:
  https://build.opensuse.org/package/view_file/openSUSE:Factory/MozillaFirefox
  /firefox-branded-icons.patch?expand=1

  (I have also asked the openSUSE folks to upstream their patch, though
  I don't have high hopes that Mozilla will take it:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1057115)

  This way, KDE Plasma users will get nice Firefox icons in their Large
  Icons alt-tab task switchers.

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

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

[Desktop-packages] [Bug 1723831] Re: Alt+Tab doesn't work for same application with multiple windows

[Launchpad Bug Tracker]

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723831

Title:
  Alt+Tab doesn't work for same application with multiple windows

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I open 2 File manager windows and also have other windows open. From
  the side dock, I can switch between the 2 File manager windows. But
  Alt+Tab doesn't swap back and forth like expected, it picks some other
  open application and brings that to the front.

  Tested this with Gnome Terminal and get the same result. Have open 2
  terminals and a Firefox browser. I'd think Alt+Tab would switch
  between them if they were both the current and last used window, but
  no, Firefox comes to the front.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 19:46:16 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-29 (717 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723831/+subscriptions

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

[Desktop-packages] [Bug 1746652] Re: Document property profiles

[Esther]

I attempted to create a new document to save as a template with my
preferred settings. I cannot overwrite the default.svg file without
changing permissions on the /usr/share/inkscape/templates/ folder. This
means that I cannot create and save any template and have it stored in
the templates folder without changing permissions of that folder.

Current work around is to create a file and store it in my documents
folder and open that instead.

So from a usability perspective these things needs to be considered:

1. Create a document profiles system that a user can click on preferred
settings in the document properties box.

2. Allow the user to create and save templates in an accessible area. Of
course a user can do that now, but it is not all that clear on how that
should be done especially with the New from Template option. It is a bit
confusing. At a minimum an average user should not need root access or
have to change folder permissions to create, edit, or save templates.
Perhaps create a template SVG file format?

3. Include default document property option settings for program launch
in the Global Inkscape Preferences menu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1746652

Title:
  Document property profiles

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  This is less a bug and more a usability suggestion. I noticed with
  Inkscape 0.92, display and measurement units default to mm instead of
  pixels. Previous versions defaulted to pixels, if I remember right. I
  rarely use mm in my work, so I have to change this every time. There
  is no way that I know to change the default document properties.

  Each time a new Inkscape document is opened, I have to select the
  properties required for the project. If I create multiple documents
  that require the same properties, I still have to go through the same
  selection process each time. It would save time if I could create a
  document property profile to save for future use. If this were
  implemented, I could then open the document properties box, select the
  profile and click apply. This would improve workflow by saving extra
  clicks to setup a document.

  Ubuntu 16.04.3 LTS
  Inkscape 0.92.2+68~ubuntu16.04.1

  I expected the default units to be pixels. Instead they were mm. This
  caused unexpected dimensions in my drawing until I realized the
  default units were different in Inkscape 0.92 from previous versions.
  There is currently no way that I know to change the default document
  properties.

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

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

[Desktop-packages] [Bug 1739469] Re: FTBFS in bionic

[Steve Langasek]

Removing packages from bionic-proposed:
trust-store 2.0.0+16.04.20160119-0ubuntu7 in bionic
Comment: FTBFS against current boost; unmaintained, obsoleted product; LP: 
#1739469
1 package successfully removed.
Removing packages from bionic:
trust-store 2.0.0+16.04.20160119-0ubuntu6 in bionic
libtrust-store-dev 2.0.0+16.04.20160119-0ubuntu6 in bionic amd64
libtrust-store-dev 2.0.0+16.04.20160119-0ubuntu6 in bionic arm64
libtrust-store-dev 2.0.0+16.04.20160119-0ubuntu6 in bionic armhf
libtrust-store-dev 2.0.0+16.04.20160119-0ubuntu6 in bionic i386
libtrust-store-dev 2.0.0+16.04.20160119-0ubuntu6 in bionic 
ppc64el
libtrust-store-dev 2.0.0+16.04.20160119-0ubuntu6 in bionic s390x
libtrust-store-doc 2.0.0+16.04.20160119-0ubuntu6 in bionic amd64
libtrust-store-doc 2.0.0+16.04.20160119-0ubuntu6 in bionic arm64
libtrust-store-doc 2.0.0+16.04.20160119-0ubuntu6 in bionic armhf
libtrust-store-doc 2.0.0+16.04.20160119-0ubuntu6 in bionic i386
libtrust-store-doc 2.0.0+16.04.20160119-0ubuntu6 in bionic 
ppc64el
libtrust-store-doc 2.0.0+16.04.20160119-0ubuntu6 in bionic s390x
libtrust-store2 2.0.0+16.04.20160119-0ubuntu6 in bionic amd64
libtrust-store2 2.0.0+16.04.20160119-0ubuntu6 in bionic arm64
libtrust-store2 2.0.0+16.04.20160119-0ubuntu6 in bionic armhf
libtrust-store2 2.0.0+16.04.20160119-0ubuntu6 in bionic i386
libtrust-store2 2.0.0+16.04.20160119-0ubuntu6 in bionic ppc64el
libtrust-store2 2.0.0+16.04.20160119-0ubuntu6 in bionic s390x
trust-store-bin 2.0.0+16.04.20160119-0ubuntu6 in bionic amd64
trust-store-bin 2.0.0+16.04.20160119-0ubuntu6 in bionic arm64
trust-store-bin 2.0.0+16.04.20160119-0ubuntu6 in bionic armhf
trust-store-bin 2.0.0+16.04.20160119-0ubuntu6 in bionic i386
trust-store-bin 2.0.0+16.04.20160119-0ubuntu6 in bionic ppc64el
trust-store-bin 2.0.0+16.04.20160119-0ubuntu6 in bionic s390x
trust-store-tests 2.0.0+16.04.20160119-0ubuntu6 in bionic amd64
trust-store-tests 2.0.0+16.04.20160119-0ubuntu6 in bionic arm64
trust-store-tests 2.0.0+16.04.20160119-0ubuntu6 in bionic armhf
trust-store-tests 2.0.0+16.04.20160119-0ubuntu6 in bionic i386
trust-store-tests 2.0.0+16.04.20160119-0ubuntu6 in bionic 
ppc64el
trust-store-tests 2.0.0+16.04.20160119-0ubuntu6 in bionic s390x
Comment: FTBFS against current boost; unmaintained, obsoleted product; LP: 
#1739469
1 package successfully removed.


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

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: trust-store (Ubuntu)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1739469

Title:
  FTBFS in bionic

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in trust-store package in Ubuntu:
  Fix Released

Bug description:
  A rebuild of trust-store for the new boost ABI fails in bionic:

  /usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/trust-store-2.0.0+16.04.20160119=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wall -pedantic -Wextra -fPIC -fvisibility=hidden 
-pthread -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-Bsymbolic-functions 
-Wl,-z,relro  -rdynamic CMakeFiles/cmTC_75174.dir/CheckFunctionExists.c.o  -o 
cmTC_75174 -lpthreads 
  /usr/bin/ld: cannot find -lpthreads
  collect2: error: ld returned 1 exit status

  If anyone cares about this package for bionic, they will need to
  resolve this.  Otherwise, the build-dependency from pulseaudio to
  trust-store should be dropped and trust-store should be removed from
  the archive.

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

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

[Desktop-packages] [Bug 1739469] Re: FTBFS in bionic

[Steve Langasek]

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1739469

Title:
  FTBFS in bionic

Status in pulseaudio package in Ubuntu:
  New
Status in trust-store package in Ubuntu:
  New

Bug description:
  A rebuild of trust-store for the new boost ABI fails in bionic:

  /usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/trust-store-2.0.0+16.04.20160119=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wall -pedantic -Wextra -fPIC -fvisibility=hidden 
-pthread -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-Bsymbolic-functions 
-Wl,-z,relro  -rdynamic CMakeFiles/cmTC_75174.dir/CheckFunctionExists.c.o  -o 
cmTC_75174 -lpthreads 
  /usr/bin/ld: cannot find -lpthreads
  collect2: error: ld returned 1 exit status

  If anyone cares about this package for bionic, they will need to
  resolve this.  Otherwise, the build-dependency from pulseaudio to
  trust-store should be dropped and trust-store should be removed from
  the archive.

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

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

[Desktop-packages] [Bug 1746773] Re: Search for Skype in GNOME Software doesn't list Skype as the first match

[Robert Ancell]

Confirmed that snapd is returning skype before spreedme so must be some
re-ordering going on in GNOME Software...

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1746773

Title:
  Search for Skype in GNOME Software doesn't list Skype as the first
  match

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  When searching for Skype in GNOME Software on Ubuntu 18.04 daily,
  Skype is not the first match that is listed. See the attached
  screenshot.

  ## Expected behaviour

  When searching for Skype, Skype should be the first match.

  ## Actual behaviour

  I search for Skype and the first match is not Skype.

  ## Steps to reproduce the behaviour

* Open Ubuntu Software
* Click the search icon and enter 'skype'

  ## Ubuntu version

* Ubuntu 18.04 daily

  ## ubuntu-software version

  Package: ubuntu-software
  Version: 3.26.5-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1746773/+subscriptions

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

[Desktop-packages] [Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)

[Egmont Koblinger]

FYI: Forthcoming gnome-terminal 3.27.90 will no longer have an --enable-
distro-packaging config option. Just drop it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1744711

Title:
  Update gnome-terminal to 3.28 (vte 0.52)

Status in gnome-terminal package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Triaged

Bug description:
  Followup of lp:1721412

  18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming
  that it ships GNOME 3.28).

  This requires updating the PCRE2 patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+subscriptions

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

[Desktop-packages] [Bug 1746819] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1746819

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Trying to run an upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Feb  1 15:58:41 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bNaUCt/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-12-27 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-11-11 (82 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1746819/+subscriptions

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

[Desktop-packages] [Bug 1746819] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[Michael Messano]

Public bug reported:

Trying to run an upgrade.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Feb  1 15:58:41 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-bNaUCt/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2016-12-27 (400 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: Upgraded to artful on 2017-11-11 (82 days ago)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1746819

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Trying to run an upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Feb  1 15:58:41 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bNaUCt/4-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-12-27 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-11-11 (82 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1746819/+subscriptions

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

[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

[Kenneth Loafman]

** Changed in: duplicity
   Status: In Progress => Fix Committed

** Changed in: duplicity
 Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1730451

Title:
  MemoryError while verifying backup

Status in Duplicity:
  Fix Committed
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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

[Desktop-packages] [Bug 1722256] Re: Wifi connection status icon shows a "?" when connected

[Casey]

Confirming that adding dns=default to
/etc/NetworkManager/NetworkManager.conf solved the problem for me as
well - thank you Scorpius!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1722256

Title:
  Wifi connection status icon shows a "?" when connected

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Wifi connection status icon on the top bar shows a "?" even when connected to 
a wifi network.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Christopher M. Penalver]

Diogo Gomes:
>"Al information is complete for the 16.04 LTS"

Once its been completed for the latest release, then it can be
upstreamed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1718824] Proposed package upload rejected

[Brian Murray]

An upload of pulseaudio to xenial-proposed has been rejected from the
upload queue for the following reason: ""Based off comment #42 it seems
the fix in bionic doesn't match the SRU i.e. the SRUs are still missing
whatever change went into 1:11.1-1ubuntu4 so I'm rejecting this
upload."".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1718824] Proposed package upload rejected

[Brian Murray]

An upload of pulseaudio to artful-proposed has been rejected from the
upload queue for the following reason: ""Based off comment #42 it seems
the fix in bionic doesn't match the SRU i.e. the SRUs are still missing
whatever change went into 1:11.1-1ubuntu4 so I'm rejecting this
upload."".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Christopher M. Penalver]

Diogo Gomes:
>"I add the last 10min of kern.log before crash happen. Please tell me if is 
>useful."

Please attach xorg and dmesg in full. In the future, always attach logs
in their entirety (no snips).

>"I take a picture too, should I upload it?"

Yes please.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1746809] [NEW] Ubuntu 17.10 Network manager doesn't allow creating VLAN Interfaces

[Cher81]

Public bug reported:

In 17.4 there was an option to create VLAN interface and after upgrading
to 17.10 it has disappeared and VLAN interfaces have been moved under
Bluetooth connections. I've noticed that vlan-xxx.deb has been
uninstalled as well and i had to reinstall it. Can we get GUI fixed to
work properly?

In the screenshot attached I can manage VLAN interfaces but they have
been there since 17.04.

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "ubuntu17.10.PNG"
   
https://bugs.launchpad.net/bugs/1746809/+attachment/5047067/+files/ubuntu17.10.PNG

** Description changed:

  In 17.4 there was an option to create VLAN interface and after upgrading
  to 17.10 it has disappeared and VLAN interfaces have been moved under
  Bluetooth connections. I've noticed that vlan-xxx.deb has been
  uninstalled as well and i had to reinstall it. Can we get GUI fixed to
  work properly?
  
- In the screenshot applied I can manage VLAN interfaces but they have
+ In the screenshot attached I can manage VLAN interfaces but they have
  been there since 17.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1746809

Title:
  Ubuntu 17.10 Network manager doesn't allow creating VLAN Interfaces

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  In 17.4 there was an option to create VLAN interface and after
  upgrading to 17.10 it has disappeared and VLAN interfaces have been
  moved under Bluetooth connections. I've noticed that vlan-xxx.deb has
  been uninstalled as well and i had to reinstall it. Can we get GUI
  fixed to work properly?

  In the screenshot attached I can manage VLAN interfaces but they have
  been there since 17.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1746809/+subscriptions

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Diogo Gomes]

I upload a possible "screenshot" of the crash.

Al information is complete for the 16.04 LTS.

** Attachment added: "P2010090.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5047059/+files/P2010090.JPG

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1746757] Re: [SRU] libreoffice 5.4.4 for artful

[Olivier Tilloy]

I have prepared source packages, ready for an upload to artful-proposed,
at https://people.canonical.com/~osomon/libreoffice-5.4.4/artful-sru/.

** Also affects: libreoffice-l10n (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1746757

Title:
  [SRU] libreoffice 5.4.4 for artful

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New

Bug description:
  [Impact]

   * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
     For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
   https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
  been available for users to test since 2017-12-24 in the official
  "LibreOffice Fresh" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages),
  and it is in bionic-proposed since 2018-01-26.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * Two new minor releases with a total of 134 bug fixes always carry
  the potential for introducing regressions, even though they are
  bugfix-only releases, meaning that no new features were added, and no
  existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Diogo Gomes]

I add the last 10min of kern.log before crash happen.

Please tell me if is useful.

I take a picture too, should I upload it?

** Attachment added: "kern.log (10 last min before crash)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5047048/+files/kern%20%2810m%20before%20crash%29.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1746776] Re: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: gnome-menus (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-menus (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1746776

Title:
  package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Invalid

Bug description:
  klkhl lhlhl

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gnome-menus 3.13.3-6ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98
  Uname: Linux 4.4.0-112-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Jan 30 15:03:56 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-23 (373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20170123)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.25
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to artful on 2018-01-29 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1746776/+subscriptions

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

[Desktop-packages] [Bug 1735362] Re: Replace ibus-sunpinyin with ibus-libpinyin

[Bug Watch Updater]

** Changed in: ibus-libpinyin (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1735362

Title:
  Replace ibus-sunpinyin with ibus-libpinyin

Status in fcitx-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libzhuyin package in Ubuntu:
  Fix Released
Status in ibus-sunpinyin package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Debian:
  Fix Released
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fcitx-libpinyin/+bug/1735362/+subscriptions

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

[Desktop-packages] [Bug 1746757] Re: [SRU] libreoffice 5.4.4 for artful

[Olivier Tilloy]

** Description changed:

  [Impact]
  
-  * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
-For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
-  https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
-  https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
-  https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
-  https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs
+  * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
+    For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
+  https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs
  
-  * Given the nature of the project, the complexity of the codebase and
+  * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU a
  minor release rather than cherry-pick selected bug fixes.
  
-  * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
- been available for users to test since 2017-12-13 in the official
- "LibreOffice Pre-Releases" PPA
- (https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
- prereleases/+packages), and it is in bionic-proposed since 2018-01-26.
+  * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
+ been available for users to test since 2017-12-24 in the official
+ "LibreOffice Fresh" PPA
+ (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages), and
+ it is in bionic-proposed since 2018-01-26.
  
  [Test Case]
  
-  * No specific test case, bugs fixed upstream hopefully come with
+  * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 release candidates.
  
-  * The libreoffice packages include autopkgtests, those should be run
+  * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.
  
-  * General smoke testing of all the applications in the office suite
+  * General smoke testing of all the applications in the office suite
  should be carried out.
  
  [Regression Potential]
  
-  * Two new minor releases with a total of 134 bug fixes always carry the
+  * Two new minor releases with a total of 134 bug fixes always carry the
  potential for introducing regressions, even though they are bugfix-only
  releases, meaning that no new features were added, and no existing
  features were removed.
  
-  * A combination of autopkgtests and careful smoke testing as described
+  * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1746757

Title:
  [SRU] libreoffice 5.4.4 for artful

Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Impact]

   * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
     For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
   https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
  been available for users to test since 2017-12-24 in the official
  "LibreOffice Fresh" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages),
  and it is in bionic-proposed since 2018-01-26.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 

[Desktop-packages] [Bug 1746789] [NEW] gnome-online-accounts crashes when icon is clicked

[ventrical]

Public bug reported:

This bug from experimental ppa:

https://code.launchpad.net/~khurshid-alam/+archive/ubuntu/experimental-
ppa

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-online-accounts 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Feb  1 14:15:09 2018
InstallationDate: Installed on 2017-12-27 (36 days ago)
InstallationMedia: Ubuntu 18.04.0 2017.12.27 amd64 "ubuntu-unity Bionic Beaver"
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1746789

Title:
  gnome-online-accounts crashes when icon is clicked

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  This bug from experimental ppa:

  https://code.launchpad.net/~khurshid-alam/+archive/ubuntu
  /experimental-ppa

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-online-accounts 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Feb  1 14:15:09 2018
  InstallationDate: Installed on 2017-12-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.12.27 amd64 "ubuntu-unity Bionic 
Beaver"
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1746789/+subscriptions

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

[Desktop-packages] [Bug 1739372] Re: Merge xdg-utils 1.1.2-1 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package xdg-utils - 1.1.2-1ubuntu1

---
xdg-utils (1.1.2-1ubuntu1) bionic; urgency=medium

  * Sync with Debian (LP: #1739372). Remaining changes:
- Add debian/xdg-utils.links:
  + Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)
- Add lp779156-lubuntu.diff
  + Adds open_lxde shell function, used when LXDE detected.
  + Adds run_sylpheed function, used to call sylpheed (LP: #779156)
  * Drop patches applied in new release:
- mimeappslist-file-location
- prefer-gio.patch
- xdg-screensaver-restore-timeout.diff
  * Drop xdg-email-mutt-detect.diff:
- Debian dropped their patch in 1.1.0~rc3+git20150907-2

xdg-utils (1.1.2-1) unstable; urgency=low

  [ Nicholas Guriev ]
  * New maintainer, Debian freedesktop.org group. Closes: #876401.
  * New upstream release. Closes: #865210.
  * Bump Standards Version, no modifications for this.
  * Remove gvfs-bin package from dependencies. Closes: #877747.

  [ Per Olofsson ]
  * Update Description.
- Correctly indent the list of commands.
- Remove mention of the Portland project. (xdg-utils is the only
  surviving product from Portland.)
- gvfs-bin is also needed in MATE and Cinnamon.
  * Add bug-script that reports the value of $XDG_CURRENT_DESKTOP.
  * Add bug-presubj asking for 'sh -x' output.

  [ Emilio Pozuelo Monfort ]
  * Remove Fathi from Uploaders. Thanks for your previous work!

 -- Jeremy Bicha   Wed, 31 Jan 2018 21:00:04 -0500

** Changed in: xdg-utils (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1739372

Title:
  Merge xdg-utils 1.1.2-1 (main) from Debian unstable (main)

Status in xdg-utils package in Ubuntu:
  Fix Released

Bug description:
  Please merge xdg-utils 1.1.2-1 (main) from Debian unstable (main)

  I cannot work on this merge myself. This is only a reference.

  Explanation of the Ubuntu delta:
* debian/patches/prefer-gio.patch: switch to preferring gio commands over
  gvfs ones. (LP: #1721948)
* debian/xdg-utils.links:
  - Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)
* Merge from Debian unstable. Remaining changes:
  - debian/patches/xdg-email-mutt-detect.diff
  - debian/patches/xdg-screensaver-restore-timeout.diff
  - debian/patches/lp779156-lubuntu.diff
  Removed patches because upstream implements:
  - xdg-email-envvar.diff
  - xdg-open-browser-multiword.diff
  - xdg-open-printf.diff
  - xdg-screensaver-new-gnome.diff
  - no-X.diff
  - fix-bashism-use-of-echo.patch
  - gnome-3.0.diff
  - filenames-with-spaces.patch
* debian/patches/mimeappslist-file-location: "xdg-mime default"
  only set old deprecated mimeapps location. "xdg-mime query default"
  retrieved, but nothing could set.  (LP: #1518053)
  ---

  Changelog entries since current bionic version 1.1.1-1ubuntu3:

  xdg-utils (1.1.2-1) unstable; urgency=low

[ Nicholas Guriev ]
* New maintainer, Debian freedesktop.org group. Closes: #876401.
* New upstream release. Closes: #865210.
* Bump Standards Version, no modifications for this.
* Remove gvfs-bin package from dependencies. Closes: #877747.

[ Per Olofsson ]
* Update Description.
  - Correctly indent the list of commands.
  - Remove mention of the Portland project. (xdg-utils is the only
surviving product from Portland.)
  - gvfs-bin is also needed in MATE and Cinnamon.
* Add bug-script that reports the value of $XDG_CURRENT_DESKTOP.
* Add bug-presubj asking for 'sh -x' output.

[ Emilio Pozuelo Monfort ]
* Remove Fathi from Uploaders. Thanks for your previous work!

   -- Nicholas Guriev   Sun, 08 Oct 2017 21:16:51 +0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1739372/+subscriptions

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

[Desktop-packages] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.26

---
ubuntu-drivers-common (1:0.4.26) bionic; urgency=medium

  * tests/gpu-manager.py:
- It is ok that quirks are still be detected, even though bbswitch
  won't use them, as it's not being loaded. Fixes FTFS.
- Skip test_system_modaliases_system on s390x.

 -- Alberto Milone   Thu, 01 Feb 2018
16:22:00 +0100

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions

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

[Desktop-packages] [Bug 1746544] Re: Upgrade to xkeyboard-config 2.23

[Gunnar Hjalmarsson]

After having talked with Timo Aaltonen on #ubuntu-devel, Timo uploaded
xkeyboard-config to Debian including the fix of the Polish issue, and
the proposed upload in the PPA now merges with Debian.

** Summary changed:

- Upgrade to xkeyboard-config 2.23
+ Please merge xkeyboard-config 2.23.1-1 (main) from Debian unstable (main)

** Changed in: xkeyboard-config (Ubuntu)
   Importance: High => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1746544

Title:
  Please merge xkeyboard-config 2.23.1-1 (main) from Debian unstable
  (main)

Status in xkeyboard-config package in Ubuntu:
  In Progress

Bug description:
  Version 2.23 of xkeyboard-config has been released upstream:

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=963db158

  It's highly desirable that this makes it in Ubuntu 18.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1746544/+subscriptions

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

[Desktop-packages] [Bug 1746776] [NEW] package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned

[Jawahir Junaith]

Public bug reported:

klkhl lhlhl

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: gnome-menus 3.13.3-6ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98
Uname: Linux 4.4.0-112-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Jan 30 15:03:56 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-01-23 (373 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20170123)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.2.25
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to artful on 2018-01-29 (2 days ago)

** Affects: gnome-menus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1746776

Title:
  package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  klkhl lhlhl

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gnome-menus 3.13.3-6ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98
  Uname: Linux 4.4.0-112-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Jan 30 15:03:56 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-23 (373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20170123)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.25
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to artful on 2018-01-29 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1746776/+subscriptions

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

[Desktop-packages] [Bug 1746773] Re: Search for Skype in GNOME Software doesn't list Skype as the first match

[Will Cooke]

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1746773

Title:
  Search for Skype in GNOME Software doesn't list Skype as the first
  match

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  When searching for Skype in GNOME Software on Ubuntu 18.04 daily,
  Skype is not the first match that is listed. See the attached
  screenshot.

  ## Expected behaviour

  When searching for Skype, Skype should be the first match.

  ## Actual behaviour

  I search for Skype and the first match is not Skype.

  ## Steps to reproduce the behaviour

* Open Ubuntu Software
* Click the search icon and enter 'skype'

  ## Ubuntu version

* Ubuntu 18.04 daily

  ## ubuntu-software version

  Package: ubuntu-software
  Version: 3.26.5-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1746773/+subscriptions

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

[Desktop-packages] [Bug 1746752] Re: switch-screen key has stopped working

[teo1978]

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

Oh, I'm afraid this is just a duplicate of the annoying #1731294

** This bug has been marked a duplicate of bug 1731294
   Keyboard shortcuts stop working; restarting unity-settings-daemon  fixes them

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746752

Title:
  switch-screen key has stopped working

Status in xorg package in Ubuntu:
  New

Bug description:
  I often connect an external monitor to my laptop and, when I do, I use it as 
the only screen, with the built-in display turned off.
  This is the configuration I manually set a long time ago, and there was a 
time when, by plugging in the screen, or bootin with the screen already 
connected, it would automatically switch to this configuration, as one would 
expect.
  Then Ubuntu fucked things up as it usually do at every update, so the 
behavior when plugging in the screen or booting became utterly random, but 
until now, I would always be able to switch screen configurations with the 
hardware keyboard shortcut (on my laptop it's fn+F6) until I get the desired 
one (built-in screen turned off, external screen as the only one). Actually 
there's usually an interval of time while the system is finishing the boot 
process (which takes several minutes because, you know, Ubuntu) during which 
the hardware switch-screen key wouldn't work properly, just switching the 
built-in screen on and off (immediately) without properly switching 
configurations. But then, when everything is up and running, it would start 
working as expected properly switching among different screen configurations 
(only built-in; builtin+external in extended desktop; mirrored; external 
only)... except that it would frantically switch several times for all the 
times you had been trying while finishing booting. That makes me think that the 
keyboard shortcut is handled by hardware and is just a hard on-off switch for 
the builtin display until something in the OS is up and running and starts 
handling it.

  Now, this was the usual behavior until now. It's pathetic in may ways,
  but that's not the bug I'm reporting.

  Now instead, after completing the boot, the screens came up as mirrored, and 
the hardware switch-screens key wouldn't work (it would just turn the builtin 
screen on and off while leaving the external screen at the same shitty 
resolution as a mirror of the builtin one), just like it usually happens for 
the first few minutes, except this time it kept (not)working this way.
  I had to manually go to Display settings, turn off mirror mode, switch the 
builtin screen off, AND adjust the external screen resolution to a non-idiotic 
value.
  And the hardware key still does nothing (not even turn on and off the builtin 
screen which remains off).

  
  I don't know if this issue will disappear at the next boot. I'm quite 
confident that it will, but that doesn't make the issue any less of a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb  1 16:18:03 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (1573 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present 

[Desktop-packages] [Bug 1746773] [NEW] Search for Skype in GNOME Software doesn't list Skype as the first match

[Martin Wimpress]

Public bug reported:

When searching for Skype in GNOME Software on Ubuntu 18.04 daily, Skype
is not the first match that is listed. See the attached screenshot.

## Expected behaviour

When searching for Skype, Skype should be the first match.

## Actual behaviour

I search for Skype and the first match is not Skype.

## Steps to reproduce the behaviour

  * Open Ubuntu Software
  * Click the search icon and enter 'skype'

## Ubuntu version

  * Ubuntu 18.04 daily

## ubuntu-software version

Package: ubuntu-software
Version: 3.26.5-1ubuntu1

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Skype-Search-GNOME-Software.png"
   
https://bugs.launchpad.net/bugs/1746773/+attachment/5046985/+files/Skype-Search-GNOME-Software.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1746773

Title:
  Search for Skype in GNOME Software doesn't list Skype as the first
  match

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When searching for Skype in GNOME Software on Ubuntu 18.04 daily,
  Skype is not the first match that is listed. See the attached
  screenshot.

  ## Expected behaviour

  When searching for Skype, Skype should be the first match.

  ## Actual behaviour

  I search for Skype and the first match is not Skype.

  ## Steps to reproduce the behaviour

* Open Ubuntu Software
* Click the search icon and enter 'skype'

  ## Ubuntu version

* Ubuntu 18.04 daily

  ## ubuntu-software version

  Package: ubuntu-software
  Version: 3.26.5-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1746773/+subscriptions

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Christopher M. Penalver]

Diogo Gomes:
>"I tested in live and crashes and do not stored any logs, it's the reason why 
>I didn't upload."

Using the following in a live environment may yield something useful
https://wiki.ubuntu.com/DebuggingKernelBoot .

>"I can't do it in a production machine."

If the above doesn't providing anything, then you will have to either
dual boot Bionic, or backup your production install and replace with
Bionic temporarily to gather something useful for upstream.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1746728] Re: Uninstalling VLC using Ubuntu Software does not uninstall the actual application

[Sebastian Ramacher]

No, really not a vlc bug.

** Package changed: vlc (Ubuntu) => gnome-software (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1746728

Title:
  Uninstalling VLC using Ubuntu Software does not uninstall the actual
  application

Status in gnome-software package in Ubuntu:
  New

Bug description:
  If you try to uninstall VLC using Ubuntu Software (GNOME Software),
  only the desktop/icon files are removed, not the actual binaries in
  /usr/bin. This is because VLC has them in a separate vlc-bin package
  and GNOME Software does not support uninstalling dependencies. Please,
  try to workaround this somehow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1746728/+subscriptions

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

[Desktop-packages] [Bug 1746728] [NEW] Uninstalling VLC using Ubuntu Software does not uninstall the actual application

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

If you try to uninstall VLC using Ubuntu Software (GNOME Software), only
the desktop/icon files are removed, not the actual binaries in /usr/bin.
This is because VLC has them in a separate vlc-bin package and GNOME
Software does not support uninstalling dependencies. Please, try to
workaround this somehow.

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic xenial zesty
-- 
Uninstalling VLC using Ubuntu Software does not uninstall the actual application
https://bugs.launchpad.net/bugs/1746728
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Diogo Gomes]

Once again, it's impossible capture before reboot. The system crashes
tottally.

> In addition, because you haven't tested latest packages and then provide 
> useful logs, upstream developers aren't going to be focusing on your issue. 
> Some log you grabbed years ago from an old distro isn't useful.
I tested in live and crashes and do not stored any logs, it's the reason why I 
didn't upload. I can't do it in a production machine.

> Some log you grabbed years ago from an old distro isn't useful.
I can upload the new if you want, it's same information.

> you may be holding your breath for a fix that never happens
It's disappointing and unprofessional because I already said that I can't use 
the system when it crashes

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock

[Andi]

Hi!

I've got the same problem on a debian unstable.

I solved it by resetting the desktop environment.
You may want to save your configuration first (i forgot it ;))
dconf dump
This is the command for the hard reset - use it with caution:
dconf reset -f /

Bug description:
I'm not sure what caused the bug. But one thing i did was creating a second 
user via gnome and deleting it a few days later.

The same problem also appeared always when i used the gnome shell search
or application menu.

After a  few seconds, the window decorators disappeared and then the
session stopped. I got back to the gdm.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730540

Title:
  gnome-shell freezes after resume then unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Often after resuming and then entering my password to unlock gnome-
  shell, when I press the enter key gnome-shell immediately freezes. The
  lock screen is still displayed, the mouse no longer responds, and the
  keys no longer respond (I can't even get a tty console with CTRL-ALT-
  Fn key). I have to perform a hard reset at this point because gnome-
  shell remains frozen even after leaving the PC alone for 15 minutes.

  I haven't been able to find any crash files or error logs.

  It seems that this freeze is much more likely to occur if I have
  changed location between suspending and resuming and am therefore
  connecting to a different wifi router. Once, however, it happened at
  home on the same router and I was able to log in via ssh from another
  machine (so only gnome-shell was frozen, not the kernel). However, I
  couldn't see any messages or reason that gnome-shell had crashed, so
  all I could do was reboot (any hints as to what I should try at this
  stage are welcome).

  Bug #1709994 looks similar but in that case a) the user is using Xorg,
  not Wayland, b) he also gets past the lock screen, and c) gnome-shell
  eventually restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:46:43 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540/+subscriptions

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

[Desktop-packages] [Bug 1746585] Re: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all

[Ryan]

** Description changed:

  Speakers and HDMI sound work fine, only headphones not working. I went
  through all of the steps on
  
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure
  https://help.ubuntu.com/community/SoundTroubleshooting
  and
  https://wiki.ubuntu.com/DebuggingSoundProblems
  
  and submitted this report with ubuntu-bug -s audio
+ 
+ Some possibly relevant information: This installation of Ubuntu was
+ originally installed on a Dell Inspiron 15, but I cloned the partition
+ onto an SSD that I installed on the Latitude 6420. It is the Latitude
+ that is affected, the headphones work fine on the Inspiron.
  
  Let me know if any more information is required.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
-  /dev/snd/controlC0:  rviertel   2881 F pulseaudio
-   rviertel   4589 F alsamixer
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
+  /dev/snd/controlC0:  rviertel   2881 F pulseaudio
+   rviertel   4589 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Jan 31 12:22:17 2018
  InstallationDate: Installed on 2015-04-27 (1009 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
-  /dev/snd/controlC0:  rviertel   2881 F pulseaudio
-   rviertel   4589 F alsamixer
-  /dev/snd/seq:timidity   1191 F timidity
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
+  /dev/snd/controlC0:  rviertel   2881 F pulseaudio
+   rviertel   4589 F alsamixer
+  /dev/snd/seq:timidity   1191 F timidity
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0K0DNP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Speakers and HDMI sound work fine, only headphones not working. I went
  through all of the steps on

  https://help.ubuntu.com/community/SoundTroubleshootingProcedure
  https://help.ubuntu.com/community/SoundTroubleshooting
  and
  https://wiki.ubuntu.com/DebuggingSoundProblems

  and submitted this report with ubuntu-bug -s audio

  Some possibly relevant information: This installation of Ubuntu was
  originally installed on a Dell Inspiron 15, but I cloned the partition
  onto an SSD that I installed on the Latitude 6420. It is the Latitude
  that is affected, the headphones work fine on the Inspiron.

  Let me know if any more information is required.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
   /dev/snd/controlC0:  rviertel   2881 F pulseaudio
    rviertel   4589 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Jan 31 12:22:17 2018
  InstallationDate: Installed on 2015-04-27 (1009 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
   /dev/snd/controlC0:  

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Christopher M. Penalver]

Diogo Gomes, to advise, nobody has enough information to debug or root
cause any of the reports at this point because all the logs on all
reports don't include useful information. However, developers who know
what is a duplicate of what submit patches to fix the issue.

Also, here on Launchpad, each person with their hardware and issue has a
separate report, versus everyone piles onto one report with similar
symptom(s), wastes time claiming what is a duplicate without root
causing in code, etc.

In addition, because you haven't tested latest packages and then provide
useful logs, upstream developers aren't going to be focusing on your
issue. Some log you grabbed years ago from an old distro isn't useful.

Hence, until you provide the requested information from
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/comments/9
you may be holding your breath for a fix that never happens.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Diogo Gomes]

Sorry but I change and add because is the same bug that I have since
2016. Maybe I need to wait 2 more years or change distro...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Christopher M. Penalver]

Diogo Gomes, please stop changing the Description, adding packages to
this report, subscribing me to bugs when I didn't ask, etc.

** No longer affects: xorg-hwe-16.04 (Ubuntu)

** Description changed:

- Maybe this is a duplicate from #1649566
- 
  When using the nouveau graphics driver my pc freezes and crashes.
  
  WORKAROUND: Use the proprietary nvidia driver.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  

[Desktop-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

[Christopher M. Penalver]

Dieter Maurer, thank you for reporting this and helping make Ubuntu
better.

After confirming the package xdiagnose is installed, click the Yes button for 
attaching additional debugging information after running the following from a 
terminal:
ubuntu-bug xorg

** Attachment removed: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1649566/+attachment/4836158/+files/kern.log

** Package changed: xserver-xorg-video-nouveau (Ubuntu) => xorg (Ubuntu)

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

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Incomplete

** Tags added: regression-potential

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev 

[Desktop-packages] [Bug 1746757] [NEW] [SRU] libreoffice 5.4.4 for artful

[Olivier Tilloy]

Public bug reported:

[Impact]

 * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
   For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in the 
RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
 https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

 * Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU a
minor release rather than cherry-pick selected bug fixes.

 * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
been available for users to test since 2017-12-13 in the official
"LibreOffice Pre-Releases" PPA
(https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
prereleases/+packages), and it is in bionic-proposed since 2018-01-26.

[Test Case]

 * No specific test case, bugs fixed upstream hopefully come with
unit/regression tests, and the release itself is extensively exercised
upstream (both in an automated manner and manually) by a community of
testers. Each minor release went through 2 release candidates.

 * The libreoffice packages include autopkgtests, those should be run
and verified to pass.

 * General smoke testing of all the applications in the office suite
should be carried out.

[Regression Potential]

 * Two new minor releases with a total of 134 bug fixes always carry the
potential for introducing regressions, even though they are bugfix-only
releases, meaning that no new features were added, and no existing
features were removed.

 * A combination of autopkgtests and careful smoke testing as described
above should provide reasonable confidence that no regressions sneaked
in.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1746757

Title:
  [SRU] libreoffice 5.4.4 for artful

Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Impact]

   * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
 For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
   https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
  been available for users to test since 2017-12-13 in the official
  "LibreOffice Pre-Releases" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
  prereleases/+packages), and it is in bionic-proposed since 2018-01-26.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * Two new minor releases with a total of 134 bug fixes always carry
  the potential for introducing regressions, even though they are
  bugfix-only releases, meaning that no new features were added, and no
  existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Łukasz Zemczak]

Looking at the autopkgtest failures - the network-manager s390x seems to
be failing for every package since over a month. It shouldn't be related
to the modemmanager changes. I might hint it in later.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Committed
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 Xenial:
  Fix Committed
Status in libqmi source package in Xenial:
  Fix Committed
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * 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 Zesty 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]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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

[Desktop-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

[Christopher M. Penalver]

Dieter Maurer, thank you for reporting this and helping make Ubuntu
better.

After confirming the package xdiagnose is installed, click the Yes button for 
attaching additional debugging information after running the following from a 
terminal:
apport-collect 1649566

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA 

[Desktop-packages] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Alberto Milone]

I have pushed a fix for the test suite in Bionic.

The release in xenial-proposed built without problems, and my last upload only 
disabled one test on s390x:
https://github.com/tseliot/ubuntu-drivers-common/commit/de5e65cb9c20215fee0f3c13383690469864ff97

Nothing is really blocking this SRU, as the only issue was a FTBFS
(caused by a test on s390x), which is gone now. The actual code is
exactly the same, and that was verified.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions

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

[Desktop-packages] [Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[wdoekes]

By the way, upstream appears to have a fix for this too:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726352

Title:
  gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

  ---

  Ordinary bug report in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 13:08:15 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi
   PC (0x7f8d82fc8c5c) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_x11_configure_request () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1746752] [NEW] switch-screen key has stopped working

[teo1978]

Public bug reported:

I often connect an external monitor to my laptop and, when I do, I use it as 
the only screen, with the built-in display turned off.
This is the configuration I manually set a long time ago, and there was a time 
when, by plugging in the screen, or bootin with the screen already connected, 
it would automatically switch to this configuration, as one would expect.
Then Ubuntu fucked things up as it usually do at every update, so the behavior 
when plugging in the screen or booting became utterly random, but until now, I 
would always be able to switch screen configurations with the hardware keyboard 
shortcut (on my laptop it's fn+F6) until I get the desired one (built-in screen 
turned off, external screen as the only one). Actually there's usually an 
interval of time while the system is finishing the boot process (which takes 
several minutes because, you know, Ubuntu) during which the hardware 
switch-screen key wouldn't work properly, just switching the built-in screen on 
and off (immediately) without properly switching configurations. But then, when 
everything is up and running, it would start working as expected properly 
switching among different screen configurations (only built-in; 
builtin+external in extended desktop; mirrored; external only)... except that 
it would frantically switch several times for all the times you had been trying 
while finishing booting. That makes me think that the keyboard shortcut is 
handled by hardware and is just a hard on-off switch for the builtin display 
until something in the OS is up and running and starts handling it.

Now, this was the usual behavior until now. It's pathetic in may ways,
but that's not the bug I'm reporting.

Now instead, after completing the boot, the screens came up as mirrored, and 
the hardware switch-screens key wouldn't work (it would just turn the builtin 
screen on and off while leaving the external screen at the same shitty 
resolution as a mirror of the builtin one), just like it usually happens for 
the first few minutes, except this time it kept (not)working this way.
I had to manually go to Display settings, turn off mirror mode, switch the 
builtin screen off, AND adjust the external screen resolution to a non-idiotic 
value.
And the hardware key still does nothing (not even turn on and off the builtin 
screen which remains off).


I don't know if this issue will disappear at the next boot. I'm quite confident 
that it will, but that doesn't make the issue any less of a bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
NonfreeKernelModules: nvidia_uvm 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  340.102  Mon Jan 16 13:06:29 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb  1 16:18:03 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (1573 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: 

[Desktop-packages] [Bug 1746638] Re: Nouveau graphics driver freezes and crashes

[Diogo Gomes]

** Description changed:

+ Maybe this is a duplicate from #1649566
+ 
  When using the nouveau graphics driver my pc freezes and crashes.
  
  WORKAROUND: Use the proprietary nvidia driver.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746638

Title:
  Nouveau graphics driver freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg-hwe-16.04 package in Ubuntu:
  New

Bug description:
  Maybe this is a duplicate from #1649566

  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   

[Desktop-packages] [Bug 1612226] Re: Calc EDITING - Selecting a Range pressing enter and dragging Closes App

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1612226

Title:
  Calc EDITING - Selecting a Range pressing enter and dragging Closes
  App

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Using the 5.2 Snap Release under Ubuntu OS when selecting a range of Cells By 
Highlighting and Pressing Enter Then trying to move then by dragging closes the 
app. This does not happen in my 5.1 install. Have attached the stdout when 
starting the app from the command line (not sure this is of any use?)
  (from https://bugs.documentfoundation.org/show_bug.cgi?id=101377)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1612226/+subscriptions

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

[Desktop-packages] [Bug 1746652] Re: Document property profiles

[Esther]

Thank you for the response. I think that blog entry is out of date.

I created a default.svg and saved it to home/.config/inkscape/templates.
There was no existing default.svg file existing to overwrite. Upon
relaunching Inkscape, the modified default template was not launched. I
noticed in the home/.config/inkscape folder a preferences.xml file. I
suspect that is where some default settings are stored, though I do not
think that as a regular user that is something I should edit nor would I
have known to edit it. If a document profile system is not created, then
options need to be available through the global Inkscape settings menu.
(As an aside, I tried to save a default.svg to the above folder from
within Inkscape, but Thunar would not show me hidden files/folders from
within the Save As window in Inkscape. Not sure if that is an Inkscape
or Thunar problem. My work around was to save to the desktop and
manually move it over).

Creating a document New from Template pulls the templates from
/usr/share/inkscape/templates. The pre-installed templates do not give
any details other than a title, so they may or may not be suitable for
my task.

I see that I can create a document and save it to
/usr/share/inkscape/templates/ and even overwrite the default.svg. But
as a regular user this option is not obvious. When I go to save a file
there is no option to save as a template and have the save option
default to the appropriate folder.

Now that I know I am looking for a custom template, I found the correct
reference in the Inkscape manual. As a user I searched the manual for
document properties, default settings, etc., and could not find how to
change this. From a usability perspective, this could use some
rethinking as it has driven me crazy for a long time. As I am a Linux
user, I'm not sure how all this works on other platforms.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1746652

Title:
  Document property profiles

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  This is less a bug and more a usability suggestion. I noticed with
  Inkscape 0.92, display and measurement units default to mm instead of
  pixels. Previous versions defaulted to pixels, if I remember right. I
  rarely use mm in my work, so I have to change this every time. There
  is no way that I know to change the default document properties.

  Each time a new Inkscape document is opened, I have to select the
  properties required for the project. If I create multiple documents
  that require the same properties, I still have to go through the same
  selection process each time. It would save time if I could create a
  document property profile to save for future use. If this were
  implemented, I could then open the document properties box, select the
  profile and click apply. This would improve workflow by saving extra
  clicks to setup a document.

  Ubuntu 16.04.3 LTS
  Inkscape 0.92.2+68~ubuntu16.04.1

  I expected the default units to be pixels. Instead they were mm. This
  caused unexpected dimensions in my drawing until I realized the
  default units were different in Inkscape 0.92 from previous versions.
  There is currently no way that I know to change the default document
  properties.

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

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

[Desktop-packages] [Bug 1746544] Re: Upgrade to xkeyboard-config 2.23

[Gunnar Hjalmarsson]

Issue with Polish layout reported:

https://bugs.freedesktop.org/show_bug.cgi?id=104904

** Bug watch added: freedesktop.org Bugzilla #104904
   https://bugs.freedesktop.org/show_bug.cgi?id=104904

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1746544

Title:
  Upgrade to xkeyboard-config 2.23

Status in xkeyboard-config package in Ubuntu:
  In Progress

Bug description:
  Version 2.23 of xkeyboard-config has been released upstream:

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=963db158

  It's highly desirable that this makes it in Ubuntu 18.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1746544/+subscriptions

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

[Desktop-packages] [Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[wdoekes]

Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/

Cheers,
Walter Doekes
OSSO B.V.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726352

Title:
  gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

  ---

  Ordinary bug report in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 13:08:15 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi
   PC (0x7f8d82fc8c5c) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_x11_configure_request () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[wdoekes]

In my case, applying just [3] wasn't enough.
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557
[2] https://bugzilla.gnome.org/show_bug.cgi?id=788764
[3] https://bug788764.bugzilla-attachments.gnome.org/attachment.cgi?id=361654

I also had to apply [6] to fix [5]:
[4] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726352
[5] https://bugzilla.gnome.org/show_bug.cgi?id=790207 (possibly?)
[6]
--- a/src/x11/window-x11.c
+++ b/src/x11/window-x11.c
@@ -1973,6 +1973,9 @@ meta_window_move_resize_request (MetaWindow *window,
   gboolean in_grab_op;
   MetaMoveResizeFlags flags;
 
+  if (!window->monitor)
+return;
+
   /* We ignore configure requests while the user is moving/resizing
* the window, since these represent the app sucking and fighting
* the user, most likely due to a bug in the app (e.g. pfaedit


I created builds for Artful here, which appear to work:
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/

The only added patch is:
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/handle_resizing_when_headless.patch

Cheers,
Walter Doekes
OSSO B.V.


** Bug watch added: GNOME Bug Tracker #790207
   https://bugzilla.gnome.org/show_bug.cgi?id=790207

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724557

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1746745] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1746745

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Thu Feb  1 01:28:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2010-12-07 (2612 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-11-21 (436 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1746745/+subscriptions

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

[Desktop-packages] [Bug 1746745] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Ruben Cuesta]

Public bug reported:

package tex-common 6.04 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Thu Feb  1 01:28:42 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2010-12-07 (2612 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-11-21 (436 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1746745

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Thu Feb  1 01:28:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2010-12-07 (2612 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-11-21 (436 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1746745/+subscriptions

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

[Desktop-packages] [Bug 1746741] [NEW] cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

Public bug reported:

Hello!

After the update manager popped up and I've done the update, it seems
that the ctrl alt arrows are no longer working to switch between the
workspaces?

I can still switch by using the mouse andthe icon on the launcher, it
just takes more time and Idislike that.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb  1 14:18:35 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2015-08-06 (910 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
MachineType: LENOVO 20B7S0JC01
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20B7S0JC01
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.asset.tag: AH509827
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20B7S0JC01
dmi.product.version: ThinkPad T440
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Feb  1 14:11:17 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12350 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746741

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no 

[Desktop-packages] [Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

[demiurg_spb]

Ubuntu 17.10 (duplicity 0.7.12)

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1546, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1510, in do_backup
full_backup(col_stats)
  File "/usr/bin/duplicity", line 575, in full_backup
globals.backend)
  File "/usr/bin/duplicity", line 434, in write_multivol
at_end = gpg.GzipWriteFile(tarblock_iter, tdp.name, globals.volsize)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 421, in 
GzipWriteFile
new_block = block_iter.next()
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 520, in 
next
result = self.process_continued()
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 700, in 
process_continued
data, last_block = self.get_data_block(self.process_fp)
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 686, in 
get_data_block
if fp.close():
  File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 440, in 
close
self.callback(self.sig_gen.getsig(), *self.extra_args)
  File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py", line 218, in 
getsig
return ''.join(self.sigstring_list)
MemoryError

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1729695

Title:
  ASCII decode error, but not due to filenames in backup target

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10, I have deja-dup 36.2-0ubuntu1 installed. When I run
  "DEJA_DUP_DEBUG=1 deja-dup", it starts a backup as soon as it opens,
  as expected. But the backup fails. I get the following at the end of
  the output. I tried uninstalling Dropbox and deleting its .dropbox-
  dist directory, and then deja-dup crashed when trying to back up a
  completely different file (but the same byte in the same position). So
  I don't think this is due to any of the filenames I have in my backup
  target. I also tried a few commands to find non-ASCII filenames, with
  no luck. I'm not sure what else I can do to troubleshoot.

  
  DUPLICITY: INFO 4 
'home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so'
  DUPLICITY: . A 
home/paul/.dropbox-dist/dropbox-lnx.x86_64-38.4.27/PyQt5.QtGui.so

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-S72EWc-tempdir/mktemp-hYd54u-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/duplicity-VyBN42-tempdir/mktemp-BO1DKJ-1

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing duplicity-full.20171102T205615Z.vol1.difftar.gz

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
/home/paul/.cache/deja-dup/1499b6292f58faddd30853ffbbfefcf6/lockfile.lock

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-c9BMvB-tempdir/mktemp-RtijDc-270

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-c9BMvB-tempdir/mkstemp-3cxG5G-1

  DUPLICITY: ERROR 30 UnicodeDecodeError
  DUPLICITY: . Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1546, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1540, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1391, in main
  DUPLICITY: . do_backup(action)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1510, in do_backup
  DUPLICITY: . full_backup(col_stats)
  DUPLICITY: .   File "/usr/bin/duplicity", line 575, in full_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity", line 456, in write_multivol
  DUPLICITY: . (tdp, dest_filename, vol_num)))
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 146, in 
schedule_task
  DUPLICITY: . return self.__run_synchronously(fn, params)
  DUPLICITY: .   File 
"/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 172, in 
__run_synchronously
  DUPLICITY: . ret = fn(*params)
  DUPLICITY: .   File "/usr/bin/duplicity", line 455, in 
  DUPLICITY: . vol_num: put(tdp, dest_filename, vol_num),
  DUPLICITY: .   File "/usr/bin/duplicity", line 344, in put
  DUPLICITY: . backend.put(tdp, dest_filename)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", 
line 376, in inner_retry
  DUPLICITY: . % exception_traceback())
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/util.py", 
line 52, in exception_traceback
  

[Desktop-packages] [Bug 1746544] Re: Upgrade to xkeyboard-config 2.23

[Gunnar Hjalmarsson]

There is some issue with the Polish layout in 2.23:

$ setxkbmap pl
Error loading new keyboard description

Uploaded 2.23.1 to the PPA to see if that makes a difference.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1746544

Title:
  Upgrade to xkeyboard-config 2.23

Status in xkeyboard-config package in Ubuntu:
  In Progress

Bug description:
  Version 2.23 of xkeyboard-config has been released upstream:

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=963db158

  It's highly desirable that this makes it in Ubuntu 18.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1746544/+subscriptions

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

[Desktop-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

[AsciiWolf]

** Changed in: ubuntu-translations
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1491787

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  Fix Released
Status in gettext package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gettext source package in Artful:
  Invalid
Status in gnome-control-center source package in Artful:
  Fix Released
Status in gnome-shell source package in Artful:
  Invalid

Bug description:
  [ Description ]

  In GNOME's activities overview, search entries from gnome-control-
  center aren't translated.

  [ Fix ]

  setlocale() wasn't being called until after the model that supplies
  search results was constructed. We fix the initialisation code to run
  slightly later, after setlocale() has been called.

  [ QA ]

  1. Open a session in a non-English locale which has gnome-control-center 
translations (French works).
  2. Hit super and type an "a"
  3. There should be some results from "Settings". They should be in French (or 
whatever language you're using).

  [ Regression potential ]

  If we misunderstood when the initialisation phases in GtkApplication
  ran then there could be a race condition. You'd see that manifesting
  as either a crash in the search provider or no results being returned.
  Make sure there aren't crahes reported in errors.u.c.

  [ Original description ]

  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1491787/+subscriptions

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

[Desktop-packages] [Bug 1709164] Re: [MIR] bubblewrap

[Didier Roche]

ok, my deb-src were still on artful for some reason… I woudl split them in a 
separate package as they don't need to be installed by default, but it's up to 
you.
Thanks for filing the bpf big and explaining the changes that happened in 
bionic!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bubblewrap in Ubuntu.
https://bugs.launchpad.net/bugs/1709164

Title:
  [MIR] bubblewrap

Status in bubblewrap package in Ubuntu:
  Confirmed

Bug description:
  Availability
  
  Built for all supported architectures.

  In sync with Debian.

  Rationale
  =
  The gnome-desktop3 library 3.25.90+ requires bubblewrap. bubblewrap is most 
commonly used as part of Flatpak's security isolation feature. Here it's being 
used to sandbox the thumbnailers.

  See https://git.gnome.org/browse/gnome-desktop/log (changes from
  3.25.4 to 3.25.90)

  The bubblewrap feature was disabled in Ubuntu 17.10's gnome-desktop3
  package because this MIR was not processed.

  Security
  
  No known open security vulnerabilities in any Ubuntu releases.

  https://security-tracker.debian.org/tracker/source-package/bubblewrap

  I helped prepare a security update (LP: #1657357) (CVE-2017-5226) for
  bubblewrap/flatpak several months ago.

  Security-sensitive package.

  Quality assurance
  =
  Bug subscriber: should be Ubuntu Desktop Bugs

  https://bugs.launchpad.net/ubuntu/+source/bubblewrap
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=bubblewrap
  https://github.com/projectatomic/bubblewrap/issues

  dh_auto_test runs the build tests but they appear to be set as SKIP
  upstream. (See comment #4)

  Multiple autopkgtests passing on all Ubuntu architectures. Because the
  tests require machine isolation, the autopkgtests don't run on
  Debian's infrastructure currently.

  Dependencies
  
  check-mir reports all other binary dependencies are in main

  Standards compliance
  
  4.0.0

  Maintenance
  ===
  - Actively developed upstream
  https://github.com/projectatomic/bubblewrap

  - Maintained in Debian by the pkg-utopia team but more specifically,
  it is maintained by Simon McVittie (smcv) who also maintains Flatpak
  and ostree in Debian and Ubuntu.

  short dh7 style rules, dh compat 10

  Background information
  ==
  William Hua (attente) had been working last year on a snapcraft plugin that 
used bubblewrap.

  So maybe more stuff will use bubblewrap in the future.

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

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

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

[wdoekes]

Stack trace looks like https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1724557 here too. Guessing this is a duplicate.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1729028

Title:
  gnome-shell crashes when monitor sleeps or is turned off

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions

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