[Desktop-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache
** No longer affects: libnl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache Status in libnl3 package in Ubuntu: In Progress Bug description: Retrieving information about configured neighbors fail my application is running the following procedure: neigh = NULL; cache = rtnl_neigh_alloc_cache(sk); while(NULL == neigh){ nl_cache_refill(sk, chache); neigh = rtnl_neigh_get(cache, ifindex, dst_addr); } with libnl3 3.2.21-1 this loop will never end, even when adding a static arp entry. However, with libnl-3.2.24 the neighbor lookup succeed. additional general info: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ uname -r 3.13.0-24-generic $ apt-cache policy libnl-genl-3-200 libnl-route-3-200 libnl-genl-3-200: Installed: 3.2.21-1 Candidate: 3.2.21-1 Version table: *** 3.2.21-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libnl-route-3-200: Installed: 3.2.21-1 Candidate: 3.2.21-1 Version table: *** 3.2.21-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1312419/+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 1767258] Re: bluetooth cann't open
*** This bug is a duplicate of bug 1532267 *** https://bugs.launchpad.net/bugs/1532267 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1532267, so it 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. Feel free to continue to report any other bugs you may find. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - bluetooth cann't open + Atheros QCA9565 bluetooth hardware not detected ** This bug has been marked a duplicate of bug 1532267 Atheros QCA9565 Bluetooth not recognized -- 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/1767258 Title: Atheros QCA9565 bluetooth hardware not detected Status in bluez package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: I can't open bluetooth in the setting panel,it's gray. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 12:01:53 2018 InstallationDate: Installed on 2018-03-15 (43 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) InterestingModules: bnep btusb bluetooth MachineType: Acer TravelMate P257-MG ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: TravelMate P257-MG dmi.product.version: V3.72 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767258/+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 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache
Hi, Same issue. I am using similar test application to get the neighboring mac addresses on a Centos 7.2.1511 machine. Installed 3.21, 3.28, 3.4 versions and all returned with NULL. Is this going to be fixed? Or Is there any other API within libnl3 that can do the trick? Abhik -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache Status in libnl: New Status in libnl3 package in Ubuntu: In Progress Bug description: Retrieving information about configured neighbors fail my application is running the following procedure: neigh = NULL; cache = rtnl_neigh_alloc_cache(sk); while(NULL == neigh){ nl_cache_refill(sk, chache); neigh = rtnl_neigh_get(cache, ifindex, dst_addr); } with libnl3 3.2.21-1 this loop will never end, even when adding a static arp entry. However, with libnl-3.2.24 the neighbor lookup succeed. additional general info: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ uname -r 3.13.0-24-generic $ apt-cache policy libnl-genl-3-200 libnl-route-3-200 libnl-genl-3-200: Installed: 3.2.21-1 Candidate: 3.2.21-1 Version table: *** 3.2.21-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libnl-route-3-200: Installed: 3.2.21-1 Candidate: 3.2.21-1 Version table: *** 3.2.21-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/libnl/+bug/1312419/+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 1767258] Re: bluetooth cann't open
Please try toggling the switch in the header bar to ON (next to the minimize/maximize/close buttons). If that doesn't work then it appears the problem is that the kernel has not detected your bluetooth hardware (see rfkill.txt above). ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1767258 Title: bluetooth cann't open Status in bluez package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I can't open bluetooth in the setting panel,it's gray. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 12:01:53 2018 InstallationDate: Installed on 2018-03-15 (43 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) InterestingModules: bnep btusb bluetooth MachineType: Acer TravelMate P257-MG ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: TravelMate P257-MG dmi.product.version: V3.72 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767258/+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 1741839] Re: gdm3 lock screen/gnome-shell freeze after opening laptop lid
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- 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/1741839 Title: gdm3 lock screen/gnome-shell freeze after opening laptop lid Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: Sometimes when I open the lid of my laptop to input my password to unlock, everything freezes and I am unable to do anything but to hard reboot. I am talking about the lock screen (logged in already just locked). Ubuntu 17.10 gdm3 version: 3.26.1-3ubuntu3 gnome-shell version: 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-12-19 (384 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gdm3 3.26.1-3ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-21-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (80 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2017-06-17T01:23:09.018818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1741839/+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 1741839] Re: gdm3 lock screen/gnome-shell freeze after opening laptop lid
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1741839 Title: gdm3 lock screen/gnome-shell freeze after opening laptop lid Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: Sometimes when I open the lid of my laptop to input my password to unlock, everything freezes and I am unable to do anything but to hard reboot. I am talking about the lock screen (logged in already just locked). Ubuntu 17.10 gdm3 version: 3.26.1-3ubuntu3 gnome-shell version: 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-12-19 (384 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gdm3 3.26.1-3ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-21-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (80 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2017-06-17T01:23:09.018818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1741839/+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 1750558] Re: gnome-software crashed with SIGSEGV in __strlen_avx2()
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- 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/1750558 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() Status in gnome-software package in Ubuntu: Expired Bug description: from lxqt? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.27.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Date: Tue Feb 20 12:54:36 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.27.90-1ubuntu1 ProcCmdline: /usr/bin/gnome-software --local-filename=/tmp/mozilla_frank0/gdm3setup-20141021-1.deb ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 LANGUAGE= SegvAnalysis: Segfault happened at: 0x7f43bc20c191 <__strlen_avx2+17>: vpcmpeqb (%rdi),%ymm0,%ymm1 PC (0x7f43bc20c191) ok source "(%rdi)" (0x0004) not located in a known VMA region (needed readable region)! destination "%ymm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62 _IO_vfprintf_internal (s=s@entry=0x7ffe9de6e2f0, format=format@entry=0x7f43bfd21211 , ap=ap@entry=0x7ffe9de6e460) at vfprintf.c:1643 __GI___vasprintf_chk (result_ptr=0x7ffe9de6e440, flags=1, format=0x7f43bfd21211 , args=0x7ffe9de6e460) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() UpgradeStatus: Upgraded to bionic on 2017-12-04 (78 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750558/+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 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache
** Also affects: libnl Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache Status in libnl: New Status in libnl3 package in Ubuntu: In Progress Bug description: Retrieving information about configured neighbors fail my application is running the following procedure: neigh = NULL; cache = rtnl_neigh_alloc_cache(sk); while(NULL == neigh){ nl_cache_refill(sk, chache); neigh = rtnl_neigh_get(cache, ifindex, dst_addr); } with libnl3 3.2.21-1 this loop will never end, even when adding a static arp entry. However, with libnl-3.2.24 the neighbor lookup succeed. additional general info: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ uname -r 3.13.0-24-generic $ apt-cache policy libnl-genl-3-200 libnl-route-3-200 libnl-genl-3-200: Installed: 3.2.21-1 Candidate: 3.2.21-1 Version table: *** 3.2.21-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libnl-route-3-200: Installed: 3.2.21-1 Candidate: 3.2.21-1 Version table: *** 3.2.21-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/libnl/+bug/1312419/+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 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
** Tags added: fixed-in-3.28.2 fixed-in-3.29.1 -- 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() Status in gnome-shell package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/130 https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339 --- This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either. What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen. So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two). Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat). Either way is a bug because the session should survive monitor shenanigans... :-) 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 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 14 15:39:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-30 (75 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fae20ab44a0 : mov0x8(%rdi),%eax PC (0x7fae20ab44a0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723615/+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 1758528] Re: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id()
** Tags added: fixed-in-3.28.2 fixed-in-3.29.1 -- 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/1758528 Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id() Status in gnome-shell package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/21 https://errors.ubuntu.com/problem/a3d143e94242ebfe1c753ef1e2809b7128702abc --- Randomly crashes in minutes following a reboot. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 22 21:39:40 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fce03ec7c90 : mov (%rdi),%rax PC (0x7fce03ec7c90) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: gbm_bo_get_plane_count () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758528/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
This crash is now fixed in Ubuntu 18.04. But I'll leave the gnome-shell task open for a while to help people and bots find the bug more easily. ** No longer affects: gdm3 (Ubuntu Artful) ** No longer affects: gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1767246] [NEW] package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 仍未被配置
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxdamage1:i386 1:1.1.4-2 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Apr 23 10:02:26 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ErrorMessage: 依赖关系问题 - 仍未被配置 GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2016-08-02 (632 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 4291N96 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=bd4fd09f-c9c0-45d0-941d-ca61fc81d0ab ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: libxdamage Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET72WW (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291N96 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:bvr8DET72WW(1.42):bd02/18/2016:svnLENOVO:pn4291N96:pvrThinkPadX220:rvnLENOVO:rn4291N96:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291N96 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO 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.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 ** Affects: libxdamage (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxdamage in Ubuntu. https://bugs.launchpad.net/bugs/1767246 Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 Status in libxdamage package in Ubuntu: New Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxdamage1:i386 1:1.1.4-2 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Apr 23 10:02:26 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ErrorMessage: 依赖关系问题 - 仍未被配置 GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2016-08-02 (632 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: LENOVO 4291N96 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=bd4fd09f-c9c0-45d0-941d-ca61fc81d0ab ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: libxdamage Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET72WW (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291N96 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:bvr8DET72WW(1.42):bd02/18/2016:svnLENOVO:pn4291N96:pvrThinkPadX220:rvnLENOVO:rn4291N96:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291N96
[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
** No longer affects: gnome-shell (Ubuntu Artful) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in gdm3 source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Bug description: https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742 --- Occurred during start-up, before I did anything special... 1 Ubuntu Wily Werewolf (development branch) 15.10 2 3.16.3-1ubuntu6 3&4 not applicable ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gnome-shell 3.16.3-1ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 12 19:22:07 2015 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-08 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/libmutter.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 274647] Re: Thunderbird fails to perform undo operations correctly
** Changed in: thunderbird Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/274647 Title: Thunderbird fails to perform undo operations correctly Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Triaged Bug description: I have noticed Thunderbird doesn't remember all actions one performs and therefore fails to perform undo properly. Try to move a few emails between folders and delete a couple and see what undo would do. I am using Thunderbird 2.0.0.16 under the most recent Intrepid. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/274647/+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
Re: [Desktop-packages] [Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
On Fri, 2018-04-27 at 02:15 +, Daniel van Vugt wrote: > I'm guessing the reason why we don't see many reports of this crash > is > because it's possibly triggered by shell extensions that Ubuntu > doesn't > normally ship with. > > Yours are: > b'org.gnome.shell' b'enabled-extensions' b"['freon@UshakovVasilii_Git > hub.yahoo.com', 'netsp...@hedayaty.gmail.com', 'uptime-indicator@gnio > urfgniourf.gmail.com', 'screenshot-window-sizer@gnome-shell-extension > s.gcampax.github.com', 'openweather-extens...@jenslody.de', 'launch-n > ew-insta...@gnome-shell-extensions.gcampax.github.com', 'native-windo > w-placem...@gnome-shell-extensions.gcampax.github.com', 'windowsNavig > a...@gnome-shell-extensions.gcampax.github.com', 'extensions@abteil.o > rg', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'user-the > m...@gnome-shell-extensions.gcampax.github.com', 'places-menu@gnome-she > ll-extensions.gcampax.github.com', 'TaskBar@zpydr', 'drive-menu@gnome > -shell-extensions.gcampax.github.com', 'window-list@gnome-shell-exten > sions.gcampax.github.com']" > > You might want to try disabling extensions to find which, if any, are > causing the crash. > Good idea Daniel I'll give that a try and see how it goes. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 21:24:07 up 4:14, 1 user, load average: 1.25, 1.18, 1.15 Description:Ubuntu 16.04.4 LTS, kernel 4.13.0-39-generic -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() Status in gnome-shell package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 Version table: *** 3.18.5-0ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages Happened during update of these packages Start-Date: 2017-07-24 16:09:37 Commandline: apt-get -y install imagemagick imagemagick-6.q16 imagemagick-common libimage-magick-perl libimage-magick-q16-perl libmagick++-6.q16-5v5 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra libmagickwand-6.q16-2 perlmagick xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy Upgrade: libimage-magick-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xorg-core:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), libimage-magick-q16-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xephyr:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), perlmagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8) End-Date: 2017-07-24 16:12:37 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid next size (fast): 0x05eed540 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jul 24 16:11:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1496068513 InstallationDate: Installed on 2014-10-24 (1004 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/chris ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7cec07de98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7f7cec07df10 "free(): invalid next size (fast)", action=3) at malloc.c:5006 _int_free (av=, p=, have_lock=0) at malloc.c:3867 __GI___libc_free (mem=) at malloc.c:2968 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell
[Desktop-packages] [Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
I'm guessing the reason why we don't see many reports of this crash is because it's possibly triggered by shell extensions that Ubuntu doesn't normally ship with. Yours are: b'org.gnome.shell' b'enabled-extensions' b"['freon@UshakovVasilii_Github.yahoo.com', 'netsp...@hedayaty.gmail.com', 'uptime-indica...@gniourfgniourf.gmail.com', 'screenshot-window-si...@gnome-shell-extensions.gcampax.github.com', 'openweather-extens...@jenslody.de', 'launch-new-insta...@gnome-shell-extensions.gcampax.github.com', 'native-window-placem...@gnome-shell-extensions.gcampax.github.com', 'windowsnaviga...@gnome-shell-extensions.gcampax.github.com', 'extensi...@abteil.org', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'places-m...@gnome-shell-extensions.gcampax.github.com', 'TaskBar@zpydr', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'window-l...@gnome-shell-extensions.gcampax.github.com']" You might want to try disabling extensions to find which, if any, are causing the crash. -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() Status in gnome-shell package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 Version table: *** 3.18.5-0ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages Happened during update of these packages Start-Date: 2017-07-24 16:09:37 Commandline: apt-get -y install imagemagick imagemagick-6.q16 imagemagick-common libimage-magick-perl libimage-magick-q16-perl libmagick++-6.q16-5v5 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra libmagickwand-6.q16-2 perlmagick xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy Upgrade: libimage-magick-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xorg-core:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), libimage-magick-q16-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xephyr:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), perlmagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8) End-Date: 2017-07-24 16:12:37 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid next size (fast): 0x05eed540 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jul 24 16:11:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1496068513 InstallationDate: Installed on 2014-10-24 (1004 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/chris ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7cec07de98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7f7cec07df10 "free(): invalid next size (fast)", action=3) at malloc.c:5006 _int_free (av=, p=, have_lock=0) at malloc.c:3867 __GI___libc_free (mem=) at malloc.c:2968 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid next size (fast): 0x05eed540 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to:
[Desktop-packages] [Bug 1767229] Re: Gnome Shell Freezes after Login
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1766137, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1766137 [regression] Password accepted but login fails (blank purple screen and mouse pointer only) -- 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/1767229 Title: Gnome Shell Freezes after Login Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.04 gnome-shell 3.28.1 After login, the screen stays blank (not black but the default ubuntu purpleish color) with only the mouse cursor on. After force restarting, can sometimes log on the restart. When the login is completed, a message about a gnome-shell crash pops up in a bug reporter dialog box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767229/+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
Re: [Desktop-packages] [Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize()
On Fri, 2018-04-27 at 01:32 +, Daniel van Vugt wrote: > Chris, > > You seem to have opened two bugs for this crash. Bug 1706203 is > almost > the same. > > If it's still happening then let's continue using bug 1706203. > Sounds good to me, I'll just have to remember the next time it happens and 1616651 comes up to actually post any output into 1706203. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 20:57:55 up 3:48, 1 user, load average: 0.91, 0.79, 0.75 Description:Ubuntu 16.04.4 LTS, kernel 4.13.0-39-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() Status in libgweather: Fix Released Status in Ubuntu GNOME: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Zesty: In Progress Bug description: [Impact] Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions I believe this should also fix bug 1688208 and potentially a couple of other high ranking crashes on errors.ubuntu.com. I have not however found reliable reproducers for those other bugs. [Test Case] After update of libgweather 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) 2. Disable Location Services 3. gnome-shell should not crash [Regression Potential] Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. === original bug report This happened while installing Xfce with Synaptic. chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.1 Candidate: 3.18.5-0ubuntu0.1 Version table: *** 3.18.5-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Aug 24 16:21:37 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-10-24 (670 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007 _int_free (av=, p=, have_lock=0) at malloc.c:3868 __GI___libc_free (mem=) at malloc.c:2969 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. Sorry To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+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 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
Yes it's possible one of your icons uses 16-bit colour, and explains why we don't see other/many reports of this crash. In theory we should hit this problem more often, given that we have: /usr/share/icons/hicolor/ and "high color" means 16-bit (or 15-bit). But apparently most icons in there are "true colour" instead. ** Also affects: mutter (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1239129 Importance: Unknown Status: Unknown -- 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in mutter package in Fedora: Unknown Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+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 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out
Please also run this command to automatically attach more system information: apport-collect 1767065 P.S. Ubuntu 18.04 was released a few hours ago :) https://www.ubuntu.com/ -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+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 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from
Chris, You seem to have opened two bugs for this crash. Bug 1706203 is almost the same. If it's still happening then let's continue using bug 1706203. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() Status in libgweather: Fix Released Status in Ubuntu GNOME: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Zesty: In Progress Bug description: [Impact] Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions I believe this should also fix bug 1688208 and potentially a couple of other high ranking crashes on errors.ubuntu.com. I have not however found reliable reproducers for those other bugs. [Test Case] After update of libgweather 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) 2. Disable Location Services 3. gnome-shell should not crash [Regression Potential] Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. === original bug report This happened while installing Xfce with Synaptic. chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.1 Candidate: 3.18.5-0ubuntu0.1 Version table: *** 3.18.5-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Aug 24 16:21:37 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-10-24 (670 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007 _int_free (av=, p=, have_lock=0) at malloc.c:3868 __GI___libc_free (mem=) at malloc.c:2969 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. Sorry To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+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 1767229] [NEW] Gnome Shell Freezes after Login
Public bug reported: Ubuntu 18.04 gnome-shell 3.28.1 After login, the screen stays blank (not black but the default ubuntu purpleish color) with only the mouse cursor on. After force restarting, can sometimes log on the restart. When the login is completed, a message about a gnome-shell crash pops up in a bug reporter dialog box. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: gdm3 (Ubuntu) ** Description changed: Ubuntu 18.04 gnome-shell 3.28.1 After login, the screen stays blank (not black but the default ubuntu purpleish color) with only the mouse cursor on. After force restarting, - can sometimes log on the restart. + can sometimes log on the restart. When the login is completed, a message + about a gnome-shell crash pops up in a bug reporter dialog box. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767229 Title: Gnome Shell Freezes after Login Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.04 gnome-shell 3.28.1 After login, the screen stays blank (not black but the default ubuntu purpleish color) with only the mouse cursor on. After force restarting, can sometimes log on the restart. When the login is completed, a message about a gnome-shell crash pops up in a bug reporter dialog box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767229/+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 1767162] Re: Random vertical stripes
Bug reports requires the "Package" information. So, here it goes. But the bug is not limited to "rhythmbox," it is a general bug to Ubuntu 18.04 LTS. ** Package changed: ubuntu => rhythmbox (Ubuntu) ** Summary changed: - Random vertical stripes + Random stripes and dots ** Description changed: Ubuntu 18.04 LTS. Random stripes and dots appear on some texts. It happens on various - applications. See the attached (an example of Rhythmbox) + applications. See the attached (an example of Rhythmbox). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1767162 Title: Random stripes and dots Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 18.04 LTS. Random stripes and dots appear on some texts. It happens on various applications. See the attached (an example of Rhythmbox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767162/+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 1767228] [NEW] Plasma Could Not Correctly Use OpenGL 2 after upgrading to 18.04
Public bug reported: After I upgrade Kubuntu from 17.10 to 18.04, and restarted it, all I'm seeing is my mouse cursor, which responds to my movements, and that's pretty much it. I tried to see if I can start up sddm, but that failed. I got to login by installing slick-greeter and use that instead. After logging in, the message says: Plasma is unable to start as it could not correctly use OpenGL 2. Please check that your graphics drivers are set up correctly. I checked the environment variable `$DISPLAY`, but it seems to be unset. I tried reinstalling `plasma-desktop`, `sddm`, `mesa` drivers, `xorg`, `xserver-xorg*intel`, `kde*`, `kwin`, and `nvidia-340` drivers. My laptop is a Lenovo Z40 with NVIDIA GT810m (currently disabled and using Intel HD Graphics). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 26 20:51:46 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed nvidia-340, 340.106, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical 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:380d] Subsystem: Lenovo GeForce 820M [17aa:380d] InstallationDate: Installed on 2017-04-11 (380 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411) MachineType: LENOVO 20366 ProcEnviron: LANGUAGE=en_CA:en TERM=linux PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8258f7ec-7593-4407-95b1-cf77cc95da6c ro nogpumanager quiet splash nouveau.runpm=0 vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z40-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70: dmi.product.family: IDEAPAD dmi.product.name: 20366 dmi.product.version: Lenovo Z40-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1767228 Title: Plasma Could Not Correctly Use OpenGL 2 after upgrading to 18.04 Status in xorg package in Ubuntu: New Bug description: After I upgrade Kubuntu from 17.10 to 18.04, and restarted it, all I'm seeing is my mouse cursor, which responds to my movements, and that's pretty much it. I tried to see if I can start up sddm, but that failed. I got to login by installing slick-greeter and use that instead. After logging in, the message says: Plasma is unable to start as it could not correctly use OpenGL 2. Please check that your graphics drivers are set up correctly. I checked the environment variable `$DISPLAY`, but it seems to be unset. I tried reinstalling `plasma-desktop`, `sddm`, `mesa` drivers, `xorg`, `xserver-xorg*intel`, `kde*`, `kwin`, and `nvidia-340` drivers. My laptop is a Lenovo Z40 with NVIDIA GT810m (currently disabled and using Intel HD Graphics). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 26 20:51:46 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus:
[Desktop-packages] [Bug 1767162] [NEW] Random vertical stripes
You have been subscribed to a public bug: Ubuntu 18.04 LTS. Random stripes and dots appear on some texts. It happens on various applications. See the attached (an example of Rhythmbox) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Random vertical stripes https://bugs.launchpad.net/bugs/1767162 You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox 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 1101825] Re: IPv6 static default route added incorrectly by network-manager
I believe I am affected by this issue as well. I have a Google WiFi device as a router, and everything works well for the first few days, with the link-local address used on the Google WiFi's RA used as the IPv6 default route. After a couple of days however, the Google WiFi device changes its link- local address (for some reason) on the LAN subnet, and although an RA goes out with this new link-local address, NetworkManager still hangs onto the old default route (which is marked "static" as well) and as such I lose IPv6 connectivity to the outside world. I have to run "nmcli conn up Ethernet" to force NM to delete the old default route and use a the new one. Also, if I manually "ip -6 replace default ..." leaving the line otherwise intact as it comes from NM, changing only "proto static" to "proto ra", as soon as the Google WiFi sends another RA, NM re-writes the default as "proto static"- yet does NOT update the actual "via" link-local address to the one the RA came in on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 1767219] [NEW] Audio Delay - [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
Public bug reported: When I put the audio out on the TV through HDMI there is a delay for the sound to start appearing after leaving a video or music paused for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: diogo 2410 F pulseaudio /dev/snd/pcmC0D3p: diogo 2410 F...m pulseaudio /dev/snd/controlC0: diogo 2410 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 20:01:34 2018 InstallationDate: Installed on 2018-04-20 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Áudio interno - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02RDQ.029.160707.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5K-KF1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8732A0Z-C01-G001-S0001+10.0.10586 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02RDQ.029.160707.JJ:bd07/07/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5K/300E5Q:pvrP02RDQ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5K-KF1BR:rvrSGL8732A0Z-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5K/300E5Q dmi.product.version: P02RDQ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1767219 Title: Audio Delay - [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: When I put the audio out on the TV through HDMI there is a delay for the sound to start appearing after leaving a video or music paused for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: diogo 2410 F pulseaudio /dev/snd/pcmC0D3p: diogo 2410 F...m pulseaudio /dev/snd/controlC0: diogo 2410 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 20:01:34 2018 InstallationDate: Installed on 2018-04-20 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Áudio interno - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [300E5K/300E5Q, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02RDQ.029.160707.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5K-KF1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8732A0Z-C01-G001-S0001+10.0.10586 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02RDQ.029.160707.JJ:bd07/07/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5K/300E5Q:pvrP02RDQ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5K-KF1BR:rvrSGL8732A0Z-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5K/300E5Q dmi.product.version: P02RDQ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1767219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Regarding Adam's comment and bamfdaemon that was fixed in Ubuntu 16.04, see bug 1589097. Fixing the triggers in libglib2.0-0 and desktop-file-utils did not resolve the issue for me. Additionally, both of those packages are included in standard or the the ubuntu-desktop task and a stock system does not fail to upgrade. -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see
[Desktop-packages] [Bug 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1751252 ** Tags added: iso-testing -- 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/1751252 Title: ubiquity crashed with signal 5 in _XEventsQueued() Status in glib2.0 package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Triaged Status in glib2.0 source package in Bionic: Incomplete Status in ubiquity source package in Bionic: Triaged Bug description: Crashed in a VM in the middle of installation. The host is Bionic up to date. From the journal Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 ip:7f5a76936961 sp:7ffde5090c50 error:0 in libglib-2.0.so.0.5400.1[7f5a768e6000+111000] Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation: Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last): Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 757, in Feb 23 12:52:41 ubuntu /install.py[6858]: install.run() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 135, in run Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 505, in copy_all Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + copy_progress) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 83, in Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: self.command(command, *args, **kw)) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 104, in command Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status) Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for int() with base 10: '' ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 Date: Fri Feb 23 12:52:28 2018 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss InterpreterPath: /usr/bin/python3.6 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 5 SourcePackage: ubiquity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: ubiquity crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+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 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from
Happened again during software update. Hopefully this is fixed in 18.04LTS Syslog output here - https://pastebin.com/yhW3ZSJP -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() Status in libgweather: Fix Released Status in Ubuntu GNOME: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Zesty: In Progress Bug description: [Impact] Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions I believe this should also fix bug 1688208 and potentially a couple of other high ranking crashes on errors.ubuntu.com. I have not however found reliable reproducers for those other bugs. [Test Case] After update of libgweather 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) 2. Disable Location Services 3. gnome-shell should not crash [Regression Potential] Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. === original bug report This happened while installing Xfce with Synaptic. chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.1 Candidate: 3.18.5-0ubuntu0.1 Version table: *** 3.18.5-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Aug 24 16:21:37 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-10-24 (670 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007 _int_free (av=, p=, have_lock=0) at malloc.c:3868 __GI___libc_free (mem=) at malloc.c:2969 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. Sorry To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+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 1754864] Re: Flatpak runtime extensions are not installed when using GNOME Software on Ubuntu
** Tags added: flatpak-usability -- 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/1754864 Title: Flatpak runtime extensions are not installed when using GNOME Software on Ubuntu Status in gnome-software package in Ubuntu: New Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions using GNOME Software on Ubuntu 18.04, the runtime extensions are not installed. They are installed if you run "flatpak update" from Terminal after the installation. This issue should be already fixed in GNOME Software upstream so I believe that this is a downstream Ubuntu issue. Please, fix this. Steps to Reproduce: 1. Use the latest, fully updated Ubuntu 18.04 image. 2. Install "flatpak" and "gnome-software-plugin-flatpak" packages. 3. Restart the system. 4. Download and add the Flathub repo file: https://dl.flathub.org/repo/flathub.flatpakrepo 5. Search and install the "GNOME Web" Flatpak package using GNOME Software. 6. Run the installed "Web" application. Actual results: GNOME Web is started with the default (Adwaita) theme (and without the correct locale if you use non-English system). Expected results: GNOME Web is started with the correct (Ubuntu) theme (and with the correct locale if you use non-English system). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+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 1504387] Re: [regression] Software client windows appear all-black on wily desktop
** Changed in: mesa Status: Confirmed => Fix Released -- 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/1504387 Title: [regression] Software client windows appear all-black on wily desktop Status in Mesa: Fix Released Status in Mir: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: [regression] Software client windows appear all-black, as of today on wily desktop. Although Mir has not changed. It seems like some other part of the OS is broken. $ sudo mir_proving_server & $ sudo mir_demo_client_progressbar The bug appeared in: mesa (11.0.2-1ubuntu3) wily; urgency=medium To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1504387/+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 1767206] [NEW] package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debi
Public bug reported: I have OpenOffice installed. Maybe this is the origin of the problem. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 16:12:28 2018 ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.1.5-9789 InstallationDate: Installed on 2018-03-30 (27 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.1.5-9789 UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1767206 Title: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.1.5-9789 Status in libreoffice package in Ubuntu: New Bug description: I have OpenOffice installed. Maybe this is the origin of the problem. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 16:12:28 2018 ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.1.5-9789 InstallationDate: Installed on 2018-03-30 (27 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian-menus 4.1.5-9789 UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1767206/+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 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages
** Tags added: flatpak-usability -- 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/1721049 Title: "Got unknown content type text/html" error viewing flatpack packages Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Confirmed Bug description: Whenever I view a Flatpak package in gnome-software, an in-app notification appears saying: > Sorry, something went wrong > Got unknown content type text/html from reviews.ubuntu.com Since this is modal, I then need to dismiss it before being able to do anything else. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 4 01:31:10 2017 InstallationDate: Installed on 2015-07-22 (804 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InstalledPlugins: gnome-software-plugin-flatpak 3.26.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snapN/A SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1721049/+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 1765479] Re: In ubuntu 18.04, when I unplug the screen cable, the user session close's
Hello Today when I have removed the screen cable from the main unit and plug it again after few moments, the session did not closes and all running programs stay running. I did it again another time, the same thing happened: all the programs stayed running. It seems that the updates of theses few last days solved the problem. Thanks for all ubuntu developers for the great job they are doing. -- 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/1765479 Title: In ubuntu 18.04,when I unplug the screen cable, the user session close's Status in xorg package in Ubuntu: New Bug description: I have submitted the first rapport yesterday, at the following link: https://bugs.launchpad.net/ubuntu/+bug/1765160 And after the first reply from Ubuntu Foundations Team Bug Bot (crichton) I go to the page provided in this automated reply: https://wiki.ubuntu.com/Bugs/FindRightPackage and from this page I go to the following pages and I apply the step that match this case. https://wiki.ubuntu.com/X/Backtracing https://wiki.ubuntu.com/Apport https://wiki.ubuntu.com/Apport/DeveloperHowTo https://help.ubuntu.com/community/ReportingBugs https://help.ubuntu.com/community/DebuggingSystemCrash After I read the step described in these pages I run the following command in konsole (as root) ubuntu-bug xorg I click on submit, and then it take me to this page. In the description I have done yesterday, i wrote: "Hello. If I unplug the cable of the screen when I am logged to my user session in ubuntu 18.04, and then I plug again the cable of the screen, I found my session closed, and when I login again to my user session, I found all previous running programs closed. This bug reproduce every time I unplug the cable screen from the unit. what I expect: when I plug the screen cable to the unit, I must find my session open as I let it, and programs that were running still open or running What happened: after I plug the cable screen to the unit, i find my session and all programs closed, and when I login again to my account session, I find all previous programs closed. Distro: Ubuntu Bionic Beaver (development branch) CPU: Intel® Pentium(R) CPU G645 @ 2.90GHz × 2 Graphic: Intel® Sandybridge Desktop Gnome: 3.28.1 OS type: 64 bit If there is any other information needed to help solving this bug that i must submit, just let me know it." And today, I have included _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash Edit (2.4 MiB, text/plain) And I submit it again now Please tell me were I must continue with this bug, at this page or the previous (https://bugs.launchpad.net/ubuntu/+bug/1765160) or both of them, or it will be merged automatically ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Apr 19 11:08:03 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] InstallationDate: Installed on 2018-03-18 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=ar_DZ:ar TERM=xterm-256color PATH=(custom, no user) LANG=ar_DZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic root=UUID=18c8c08f-eab6-491b-b3aa-b8b9a415e1f8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H61M-HVS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd09/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1767189] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
Public bug reported: Just upgraded from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 19:40:10 2018 Dependencies: ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2017-07-21 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (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 gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1767189 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in gnome-menus package in Ubuntu: New Bug description: Just upgraded from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 19:40:10 2018 Dependencies: ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2017-07-21 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767189/+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 1767190] 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
*** This bug is a duplicate of bug 1762827 *** https://bugs.launchpad.net/bugs/1762827 ** This bug has been marked a duplicate of bug 1762827 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 -- 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/1767190 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: error occurred when Lubuntu booted up, and booted after I had a critical power warning on startup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Wed Apr 25 22:06:13 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-zPXXPT/133-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 2018-04-24 (1 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1767190/+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 1767185] [NEW] Must click logout twice to log out.
Public bug reported: Upgraded from Xenial to Bionic. Now, when I select Logout from the menu (on both Unity and Gnome) I must do so twice before the logout is initiated. Steps: click the menu in the upper right corner click the Logout option Menu closes Click the menu again Click the logout option again Logout dialog appears Expected steps: Same as above, without having to repeat myself. Note I tried this in both Unity and Gnome3 and the results are the same in both. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:58:16 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (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-session in Ubuntu. https://bugs.launchpad.net/bugs/1767185 Title: Must click logout twice to log out. Status in gnome-session package in Ubuntu: New Bug description: Upgraded from Xenial to Bionic. Now, when I select Logout from the menu (on both Unity and Gnome) I must do so twice before the logout is initiated. Steps: click the menu in the upper right corner click the Logout option Menu closes Click the menu again Click the logout option again Logout dialog appears Expected steps: Same as above, without having to repeat myself. Note I tried this in both Unity and Gnome3 and the results are the same in both. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:58:16 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1767185/+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 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1763648 Title: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04 Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: nvidia-304 is not available in the Ubuntu 18.04. Newer versions are available but I have an old nVidia 7600 GT, so I need 304.137. I searched online and found that at https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2 it has Status: Deleted :( Could you please pack this for the new release of Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1763648/+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 1767190] 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
*** This bug is a duplicate of bug 1762827 *** https://bugs.launchpad.net/bugs/1762827 ** 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/1767190 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: error occurred when Lubuntu booted up, and booted after I had a critical power warning on startup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Wed Apr 25 22:06:13 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-zPXXPT/133-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 2018-04-24 (1 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1767190/+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 1767190] [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
*** This bug is a duplicate of bug 1762827 *** https://bugs.launchpad.net/bugs/1762827 Public bug reported: error occurred when Lubuntu booted up, and booted after I had a critical power warning on startup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Wed Apr 25 22:06:13 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-zPXXPT/133-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 2018-04-24 (1 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: No upgrade log present (probably fresh install) ** 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/1767190 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: error occurred when Lubuntu booted up, and booted after I had a critical power warning on startup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Wed Apr 25 22:06:13 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-zPXXPT/133-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 2018-04-24 (1 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1767190/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: In Progress Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 1765336] Re: Problems configuring LivePatch from Gnome Initial Setup
** Changed in: gnome-initial-setup (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1765336 Title: Problems configuring LivePatch from Gnome Initial Setup Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: Entering the user and password in GNOME Initial Setup to configure LivePatch closes the window. The wizard does not show any information that the configuration was successful or that there is a problem. If you do this when you enter the wrong password ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-initial-setup 3.28.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 05:26:12 2018 InstallationDate: Installed on 2018-04-11 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1765336/+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 1766747] Re: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127
*** This bug is a duplicate of bug 1764858 *** https://bugs.launchpad.net/bugs/1764858 ** This bug is no longer a duplicate of bug 1765803 package installs fail due to missling libzstd.so.1 ** This bug has been marked a duplicate of bug 1764858 Can't update / install / delete packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1766747 Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 Status in appstream package in Ubuntu: New Bug description: doesnt work ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt-config-icons (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Tue Apr 24 20:50:23 2018 DuplicateSignature: package:apt-config-icons:(not installed) Removing sessioninstaller (0.20+bzr150-0ubuntu4.1) ... dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-1Qdb18/0-appstream_0.12.0-3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6~beta1 SourcePackage: appstream Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1766747/+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 1767174] [NEW] my bookmarks removed and i tried every way to restore it but couldnt
Public bug reported: Hi, i tried almost every way to restore my bookmarks but still not successful in restoring it please guide me to get new download mozilla firefox or other solution Umar ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1767174 Title: my bookmarks removed and i tried every way to restore it but couldnt Status in firefox package in Ubuntu: New Bug description: Hi, i tried almost every way to restore my bookmarks but still not successful in restoring it please guide me to get new download mozilla firefox or other solution Umar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1767174/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I also think we have enough information to work on this and no further logs are necessary. -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Definitely not TLP-related since I experience the same difference without TLP installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1767159] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1767159 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: while upgrade from 16.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 26 19:04:38 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-17 (678 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1767159/+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 1767159] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: while upgrade from 16.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 26 19:04:38 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-17 (678 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2018-04-26 (0 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1767159 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: while upgrade from 16.04 to 17.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 26 19:04:38 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-17 (678 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1767159/+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 1767161] Re: Please remove libpam-freerdp
Setting as Incomplete since we should try to find someone to sign off on this removal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpam-freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1767161 Title: Please remove libpam-freerdp Status in libpam-freerdp package in Ubuntu: Incomplete Bug description: libpam-freerdp is an Ubuntu-specific package (not in Debian) and is one of the blockers for removing the old freerdp from Ubuntu. (freerdp2 is the supported version). If libpam-freerdp won't be ported to freerdp2, then it should be removed from Ubuntu. Last upload was 3.5 years ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-freerdp/+bug/1767161/+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 1767161] [NEW] Please remove libpam-freerdp
Public bug reported: libpam-freerdp is an Ubuntu-specific package (not in Debian) and is one of the blockers for removing the old freerdp from Ubuntu. (freerdp2 is the supported version). If libpam-freerdp won't be ported to freerdp2, then it should be removed from Ubuntu. Last upload was 3.5 years ago. ** Affects: libpam-freerdp (Ubuntu) Importance: Undecided Status: Incomplete ** Changed in: libpam-freerdp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpam-freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1767161 Title: Please remove libpam-freerdp Status in libpam-freerdp package in Ubuntu: Incomplete Bug description: libpam-freerdp is an Ubuntu-specific package (not in Debian) and is one of the blockers for removing the old freerdp from Ubuntu. (freerdp2 is the supported version). If libpam-freerdp won't be ported to freerdp2, then it should be removed from Ubuntu. Last upload was 3.5 years ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-freerdp/+bug/1767161/+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 1739797] Re: Please remove gnome-python-desktop from Ubuntu
Aaaand it seems I somehow forgot one of the reverse-depends? $ remove-package -m "Forgot about it; LP: #1739797" hamster-indicator Removing packages from bionic: hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic amd64 hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic arm64 hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic armhf hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic i386 hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic ppc64el hamster-indicator 0.1+037dd2e-0ubuntu2 in bionic s390x Comment: Forgot about it; LP: #1739797 Remove [y|N]? y 1 package successfully removed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-python-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1739797 Title: Please remove gnome-python-desktop from Ubuntu Status in gnome-python-desktop package in Ubuntu: Fix Released Status in hamster-applet package in Ubuntu: Fix Released Status in memaker package in Ubuntu: Fix Released Status in sugar-presence-service package in Ubuntu: Fix Released Status in sugar-toolkit package in Ubuntu: Fix Released Status in xword package in Ubuntu: Fix Released Bug description: gnome-python-desktop was recently removed from Debian Testing since it is GNOME2 tech that has been unmaintained for years. I'm filing this bug since I don't think we should ship gnome-python-desktop in Ubuntu 18.04 LTS and it may take quite a while before gnome-python-desktop is removed from Debian Unstable. See also the gnome-python removal bug LP: #1739800 which this bug blocks. $ reverse-depends src:gnome-python-desktop Reverse-Depends === * hamster-applet(for python-wnck) * memaker (for python-rsvg) * python-sugar-toolkit (for python-rsvg) [src:sugar-toolkit] * winswitch (for python-rsvg) * xword (for python-wnck) $ reverse-depends src:sugar-toolkit Reverse-Recommends == * sucrose (for python-sugar-toolkit) Reverse-Depends === * sugar-presence-service(for python-sugar-toolkit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-python-desktop/+bug/1739797/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I believe the issue is with the libglib2.0-0 triggers which were changed to interest-noawait in bionic but probably also need fixing in xenial. -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia:
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Dell-XPS-13-9350.tar is a tarball log containing 3 different SKU log of 9350. All of them could reproduce this issue. ** Attachment added: "Dell-XPS-13-9350.tar" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127769/+files/Dell-XPS-13-9350.tar -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
[Desktop-packages] [Bug 1767157] [NEW] Duplicate Folders
Public bug reported: I use Ubuntu in Brazilian Portuguese and nautillus usually creates folders with English names. I delete the folders and they are re-created some time later. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 13:38:00 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'201' b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+666+205'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-04-20 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot with duplicated folders" https://bugs.launchpad.net/bugs/1767157/+attachment/5127765/+files/Captura%20de%20tela%20de%202018-04-26%2013-43-40.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767157 Title: Duplicate Folders Status in nautilus package in Ubuntu: New Bug description: I use Ubuntu in Brazilian Portuguese and nautillus usually creates folders with English names. I delete the folders and they are re- created some time later. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 13:38:00 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'201' b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+666+205'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-04-20 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767157/+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 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
Anyone affected, please attach your journalctl /usr/bin/gnome-shell ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c --- trying to get vpn up and running ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 18:00:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['vpn-indica...@howdoicomputer.fastmail.com']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 'cisco-anyconnect.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-03-23 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fd17cf23d3d: movzbl 0x16(%rax),%edx PC (0x7fd17cf23d3d) ok source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Reproduced similar issue on different platform and SKU (will attach /var/log/dist-upgrade in this bug report): https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767153 https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767154 -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage:
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Running Quadro M1000M, no crash running Nouveau (just poor perf as everybody) Well, if I select intel through prime, the line nouveau.run-pm=0 is put in kernel parameters in grub. I've excluded nvidia & nouveau from runtime pm in tlp, to not interfere here. The result is that I get 15 W power usage. If I delete the nouveau.run-pm=0 kernel option & update grub, and if I do not exclude nvidia nouveau from runtime pm in TLP, I get 5 W running the same backlight & wifi settings. cat /sys/kernel/debug/vgaswitcheroo/switch shows 0:IGD:+:Pwr::00:02.0 1:DIS: :Off::01:00.0 too, but anyway the FACT is that the power usage on my Dell 7510 is much higher, and is 100 % related to some stuff involving nvidia/prime. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1767010] Re: [SRU] java-atk-wrapper: replace javah usage with a call to javac
This bug was fixed in the package java-atk-wrapper - 0.33.3-20ubuntu0.1 --- java-atk-wrapper (0.33.3-20ubuntu0.1) bionic; urgency=medium * debian/patches/remove-javah: remove the javah checks as it has been removed from openjdk 10 and it is not actually used by the java-atk-wrapper. LP: #1767010. -- Tiago Stürmer DaitxWed, 25 Apr 2018 21:40:46 + ** Changed in: java-atk-wrapper (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/1767010 Title: [SRU] java-atk-wrapper: replace javah usage with a call to javac Status in java-atk-wrapper package in Ubuntu: Fix Released Bug description: [Impact] Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] because it can't find the javah binary. The javah binary has been removed from OpenJDK 10 and the java compiler should be used in its place to build native headers by calling "javac -h". [Test Case] Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. depends on openjdk-11-jdk), it should FTBFS with: checking for javah... no configure: error: Java 1.6 or later is required to build java-access-bridge When fixed the build is build is expected to succeed. [Regression Potential] No regression is expected as javah is not used by java-atk-wrapper. [Other Info] * java-atk-wrapper does not use javah although it is currently declared in configure.ac, the build succeeds by simply removing the javah check. [References] [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
FWIW, it's entirely possible I had other issues that just also included this one, or just exposed this one where I may not have seen it otherwise. This just happened to be the only one that Apport was able to create and submit. -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping,
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
@seb, per discussion via IRC, here are my logs from /var/log/dist- upgrade (upgrade started last night and finally wrapped up this morning after a lot of coffee and swearing). To answer the questions: I started off with 'do-release-upgrade -d' last night and ended up this morning with a reboot into rescue mode and a lot of 'apt-get -f install', 'dpkg --reconfigure -a' and finally an 'apt-get dist-upgrade' (or was it a -f install again?) to get the remaining held 2400+ packages updated. NOW I believe I'm finally updated to Bionic and running again. Also, will asked if I had manually modified anything in /etc/apt/sources.list and the answer is no, all that was handled by the upgrader. ** Attachment added: "xenial-bionic-upgrade-logs.tgz" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127748/+files/xenial-bionic-upgrade-logs.tgz -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER]
[Desktop-packages] [Bug 1767155] Re: /usr/bin/gnome-shell:6:__libc_signal_restore_set:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr
*** This bug is a duplicate of bug 1713034 *** https://bugs.launchpad.net/bugs/1713034 ** This bug has been marked a duplicate of bug 1713034 gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"] -- 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/1767155 Title: /usr/bin/gnome- shell:6:__libc_signal_restore_set:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767155/+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 1725312] Re: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
Yeah, I can look at it. Preventing the crash is easy, the root cause a bit more complex. I can look at it, but I'd need some way to reproduce. -- 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/1725312 Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a --- I was restoring a backup when this occurred. I was not interacting with the system at the time. 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 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 06:58:55 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) 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: 0x7f840ef624f1: orb $0x1,0x30(%rbx) PC (0x7f840ef624f1) ok source "$0x1" ok destination "0x30(%rbx)" (0xfbf0) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed() 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/gnome-shell/+bug/1725312/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
201606-22355.dist-upgrade.tar.gz 201610-25144.dist-upgrade.tar.gz are attachments for comment#18 ** Attachment added: "201610-25144.dist-upgrade.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127757/+files/201610-25144.dist-upgrade.tar.gz -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
[Desktop-packages] [Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]
** Description changed: https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745 + https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56 --- - ProblemType: Crash - DistroRelease: Ubuntu 17.10 + ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 25 12:05:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-08-13 (1107 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash - Signal: 6 - SourcePackage: gnome-shell + Signal: 6SourcePackage: gnome-shell StacktraceTop: g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo -- 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/1713034 Title: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"] Status in GLib: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745 https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56 --- ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 25 12:05:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-08-13 (1107 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1713034/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Attachment added: "201606-22355.dist-upgrade.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127756/+files/201606-22355.dist-upgrade.tar.gz -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on
[Desktop-packages] [Bug 1767153] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1766890 *** https://bugs.launchpad.net/bugs/1766890 Public bug reported: Dell Precision 5520 Laptop 201610-25144 pre-installed (oem) image ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 27 00:19:25 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-26 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check ** This bug has been marked a duplicate of bug 1766890 package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned -- 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/1767153 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: Dell Precision 5520 Laptop201610-25144 pre-installed (oem) image ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 27 00:19:25 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-26 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767153/+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 1767154] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, a
*** This bug is a duplicate of bug 1766890 *** https://bugs.launchpad.net/bugs/1766890 Public bug reported: Dell XPS 13 9360 Laptop 201606-22355 pre-installed (oem) image ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 27 00:23:24 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-26 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check ** This bug has been marked a duplicate of bug 1766890 package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned -- 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/1767154 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, a Status in gnome-menus package in Ubuntu: New Bug description: Dell XPS 13 9360 Laptop 201606-22355 pre-installed (oem) image ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 27 00:23:24 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-26 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767154/+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 1767095] Re: intel vga
** Information type changed from Private Security to Public -- 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/1767095 Title: intel vga Status in xorg package in Ubuntu: New Bug description: intel vga 00:02.0 vga compatible controller: intel corporation haswell-ult integrated graphics controller (rev 0b) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 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 Apr 26 10:49:19 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.34, 4.13.0-38-generic, x86_64: installed virtualbox, 5.1.34, 4.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2212] Subsystem: Hewlett-Packard Company GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [103c:2212] InstallationDate: Installed on 2018-04-18 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=d91e6cc6-a7c9-46f9-8754-9fe5402454f9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 Apr 26 09:46:31 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. modeset(0): failed to set mode: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767095/+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 1767155] [NEW] /usr/bin/gnome-shell:6:__libc_signal_restore_set:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr
*** This bug is a duplicate of bug 1713034 *** https://bugs.launchpad.net/bugs/1713034 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: artful 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/1767155 Title: /usr/bin/gnome- shell:6:__libc_signal_restore_set:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767155/+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 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
optimized out, alas. But: (gdb) frame 9 #9 surface_from_pixmap (xdisplay=xdisplay@entry=0x56149472f000, xpixmap=xpixmap@entry=31457330, height=, width=) at x11/iconcache.c:325 325 return cairo_xlib_surface_create_with_xrender_format (xdisplay, xpixmap, DefaultScreenOfDisplay (xdisplay), (gdb) list 320 321 if (!XGetGeometry (xdisplay, xpixmap, _return, 322 _ret, _ret, _ret, _ret, _ret, _ret)) 323 return NULL; 324 325 return cairo_xlib_surface_create_with_xrender_format (xdisplay, xpixmap, DefaultScreenOfDisplay (xdisplay), 326 pict_format_for_depth (xdisplay, depth_ret), w_ret, h_ret); 327 } 328 329 static gboolean (gdb) print depth_ret $2 = 16 So, not corrupt, just not handled? FWIW, see also https://bugzilla.redhat.com/show_bug.cgi?id=1239129 I'm having a little trouble believing my screen was using 16 bit mode, could one of the cached icons have been 16 bits? ** Bug watch added: Red Hat Bugzilla #1239129 https://bugzilla.redhat.com/show_bug.cgi?id=1239129 -- 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1767148] [NEW] Exclusion list treats home directory differently
Public bug reported: Adding to Folders to ignore, you can navigate to /home/greg/.gvfs in the GUI, but it gets stored as ~/.gvfs in the exclusion list. When the backup runs, it gives the "Backup Finished" but Could not back up the following files. Please make sure you are able to open them. /home/greg/.gvfs /home/greg/.gvfs /home/greg/.gvfs The same diretory is listed 3 times n the warning message. As a workaround, I want to add the fully qualified pathname to the exclusion file to see if that fixes it, but basically I just want to properly ingore the folder. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 26 09:02:36 2018 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1767148 Title: Exclusion list treats home directory differently Status in deja-dup package in Ubuntu: New Bug description: Adding to Folders to ignore, you can navigate to /home/greg/.gvfs in the GUI, but it gets stored as ~/.gvfs in the exclusion list. When the backup runs, it gives the "Backup Finished" but Could not back up the following files. Please make sure you are able to open them. /home/greg/.gvfs /home/greg/.gvfs /home/greg/.gvfs The same diretory is listed 3 times n the warning message. As a workaround, I want to add the fully qualified pathname to the exclusion file to see if that fixes it, but basically I just want to properly ingore the folder. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 26 09:02:36 2018 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1767148/+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 1767145] [NEW] Power status says my battery is fully charged. I'm on a desktop. I have no battery
Public bug reported: Just upgraded to bionic. Gnome says my battery is fully charged. ONly thing is, this isn't a laptop. I have no batter. It is impossible for my battery to be fully charged, since it doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-power-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 11:38:12 2018 InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "See my non-existent battery's status." https://bugs.launchpad.net/bugs/1767145/+attachment/5127725/+files/gnome-power-panel.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1767145 Title: Power status says my battery is fully charged. I'm on a desktop. I have no battery Status in gnome-power-manager package in Ubuntu: New Bug description: Just upgraded to bionic. Gnome says my battery is fully charged. ONly thing is, this isn't a laptop. I have no batter. It is impossible for my battery to be fully charged, since it doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-power-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 11:38:12 2018 InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1767145/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
@Jeff, did you use apt instead of the dist-upgrader as well? Was your xenial uptodate before the upgrade? -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
FWIW, this error (my bug was marked a duplicate) completely broke my Xenial - Bionic upgrade, leaving me with a nearly unbeatable system. I had to boot into Rescue Mode and do a lot of ctrl-C ing to get around this, and once I thought it had finally installed all the bionic packages, I rebooted into the OS proper, and STILL found it hadn't actually upgraded so I had to run 'apt-get -f install' again to finish the other 2400+ package updates. I spent most of my morning just trying to get back to a bootable system that was only half-way upgraded (lsb-release told me I was in 18.04, name -a said I was still on 4.13 from 16.04.4, and apt said I still had 2400+ packages to update). If I was not an experienced user who knew roughly how to manually kick this stuff to get around broken package updates, I'd have been considerably more upset than I already am. -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER]
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Grr... autocorrect on OSX while I wait for Ubuntu to work again (finish upgrading). That should have said "leaving me with a nearly unbootable system." -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago)
[Desktop-packages] [Bug 1533232] Re: missing many apparmor rules on Xenial
*** This bug is a duplicate of bug 1659988 *** https://bugs.launchpad.net/bugs/1659988 Hello. It seems, that 'member=' needs some new values. Today, I noticed a few new entries in a log files, such as '/var/log/syslog'. Each entry had icluded "/org/gtk/Private/RemoteVolumeMonitor" with a dbus "receive" etc. Now, I'm using such a rule in a Firefox profile: dbus (send) bus=session interface=org.gtk.Private.RemoteVolumeMonitor, But according to a new log entries, above rule should be updated, at least in my case, with a new values in 'member=' and there should be added 'receive' to 'dbus (send)'. Mr. Simon Déziel rule (see post #2) already contains two options: I saw both in log files. However, there were also: ✗ VolumeChanged, ✗ DriveConnected, ✗ DriveDisconnected, ✗ MountChanged, ✗ MountAdded, ✗ MountRemoved, ✗ MountPreUnmount I hope, that I didn't miss any option. So, what do You think Mr. Déziel? Should these new options be added to the Firefox profile? If yes, what do You think about something like this: - dbus (send) + dbus (send, receive) - member={VolumeAdded,VolumeRemoved}, + member={VolumeAdded,VolumeRemoved,VolumeChanged,DriveConnected,DriveDisconnected,MountChanged,MountAdded,MountRemoved,MountPreUnmount}, I don't know if there should be 'dbus (send, receive)', but I already have a rule with 'send' in Firefox profile (unfortunately, I do not remember and I do not have any log entries. Sorry.) So, what to do? Here are some technical informations: ● Firefox: v59.0.2 (i386) ● Release: 16.04.4 LTS Thanks, best regards. -- 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/1533232 Title: missing many apparmor rules on Xenial Status in firefox package in Ubuntu: Confirmed Bug description: I've been accumulating many rules in my /etc/apparmor.d/local/usr.bin.firefox. It's been a few days since I didn't add any so it's time to report about my local additions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 43.0.4+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: simon 16762 F...m pulseaudio /dev/snd/controlC0: simon 16762 F pulseaudio BuildID: 20160106234842 Channel: Unavailable CurrentDesktop: Unity CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Jan 12 09:04:59 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js [Profile]/extensions/dns...@nic.cz/defaults/preferences/dnssec.js [Profile]/extensions/https-everywhere-...@eff.org/defaults/preferences/preferences.js Profiles: Profile0 (Default) - LastVersion=43.0.4/20160106234842 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2516CTO 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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1533232/+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 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop
Should be good. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758589 Title: The wifi will be disconnected and the only thing I can do is to reboot the laptop Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: First of all, I am not sure whether it's true that this is a bug of network-manager, but it is true that this should be a bug related with network (wifi connection). Here is the issue: Every time after I login into the account, about 20 minutes later, the wifi will be disconnected automatically. I even cannot reconnect the wifi manually, the only thing that I can do is to reboot the laptop. After login again, wifi can be connected (but through manual way). By the way, during the period of wifi disconnection, I checked the "Wi-Fi Networks" by click "Select Network" in order to try to reconnect it manually. But I found that there is only one SSID which previously the laptop connected to. However, I was definitely sure that there should be more than one SSID being showed in the wifi list. Even for this only one SSID, like I mentioned before, I cannot reconnect manually unless I reboot the system. Finally, I set the wifi to be connected automatically after I login to the system, however, it just can't. I can only connect to the wifi manually after I login to the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 19:02:12 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (68 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 WolfieNet-Secure eb45c742-ba31-4f31-acf2-13a2768bcc29 /org/freedesktop/NetworkManager/ActiveConnection/5 enp5s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled disabled --- ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kevin 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (70 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.148 metric 600 MachineType: Lenovo F31 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false NonfreeKernelModules: nvidia Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=02a1b417-5beb-4eae-82cb-e3063372bf6d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic package-from-proposed Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
This trigger loop is almost certainly because bamfdaemon's trigger wasn't fixed to be interest-noawait until yakkety, and nothing forces it to deconfigure or upgrade early (ie: with a Breaks like we used in dpkg between trusty and xenial). -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers
[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup
That's saying that duplicity logged 199 errors. They should be present in the log before this summary. It most likely is IO retries, but you should check and let us know what you find. -- 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/1767122 Title: duplicity Errors 199 at end backup Status in Déjà Dup: New Status in Python: New Status in duplicity package in Ubuntu: New Bug description: Hello, I use duplicity to backup my file. However. I get always this message at end backup with Error 199 --[ Backup Statistics ]-- StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018) EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018) ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds) SourceFiles 3821570 SourceFileSize 191576839080 (178 GB) NewFiles 2088902 NewFileSize 19156070 (178 GB) DeletedFiles 3 ChangedFiles 54 ChangedFileSize 1834439 (1.75 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2088959 RawDeltaSize 0 (0 bytes) TotalDestinationSizeChange 0 (0 bytes) Errors 199lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic Step to reproduce : 1. Configure duplicity 2. Run a bakup. Result 3. At end backup, you should get Error 199 - uname -r 4.15.0-20-generic My configuration : lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic apt-cache policy duplicity duplicity: Installed: 0.7.17-0ubuntu1 Candidate: 0.7.17-0ubuntu1 Version table: *** 0.7.17-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy python python: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 Version table: *** 2.7.15~rc1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Could you help me please to fix this issues ? Thanks by advance for your support Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: duplicity 0.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 15:58:41 2018 SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1767122/+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 1767129] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1766890 *** https://bugs.launchpad.net/bugs/1766890 ** This bug has been marked a duplicate of bug 1766890 package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned -- 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/1767129 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT of broken package upgrades. I've finally managed to get through a lot of them and this one prompted apart once I had rebooted into a rescue shell and tried to run 'apt-get -f install' ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 16:43:42 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767129/+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 1767122] Re: duplicity Errors 199 at end backup
** Also affects: python Importance: Undecided Status: New ** Also affects: deja-dup Importance: Undecided Status: New -- 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/1767122 Title: duplicity Errors 199 at end backup Status in Déjà Dup: New Status in Python: New Status in duplicity package in Ubuntu: New Bug description: Hello, I use duplicity to backup my file. However. I get always this message at end backup with Error 199 --[ Backup Statistics ]-- StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018) EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018) ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds) SourceFiles 3821570 SourceFileSize 191576839080 (178 GB) NewFiles 2088902 NewFileSize 19156070 (178 GB) DeletedFiles 3 ChangedFiles 54 ChangedFileSize 1834439 (1.75 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2088959 RawDeltaSize 0 (0 bytes) TotalDestinationSizeChange 0 (0 bytes) Errors 199lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic Step to reproduce : 1. Configure duplicity 2. Run a bakup. Result 3. At end backup, you should get Error 199 - uname -r 4.15.0-20-generic My configuration : lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic apt-cache policy duplicity duplicity: Installed: 0.7.17-0ubuntu1 Candidate: 0.7.17-0ubuntu1 Version table: *** 0.7.17-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy python python: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 Version table: *** 2.7.15~rc1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Could you help me please to fix this issues ? Thanks by advance for your support Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: duplicity 0.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 15:58:41 2018 SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1767122/+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 1767129] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- 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/1767129 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT of broken package upgrades. I've finally managed to get through a lot of them and this one prompted apart once I had rebooted into a rescue shell and tried to run 'apt-get -f install' ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 16:43:42 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767129/+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 1767129] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT of broken package upgrades. I've finally managed to get through a lot of them and this one prompted apart once I had rebooted into a rescue shell and tried to run 'apt-get -f install' ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 16:43:42 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (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 gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1767129 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT of broken package upgrades. I've finally managed to get through a lot of them and this one prompted apart once I had rebooted into a rescue shell and tried to run 'apt-get -f install' ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 16:43:42 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767129/+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 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop
OK, @Kai-Heng Feng, thank you for suggestions! I will have a try, and report the result after about one week, do you think it is OK? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758589 Title: The wifi will be disconnected and the only thing I can do is to reboot the laptop Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: First of all, I am not sure whether it's true that this is a bug of network-manager, but it is true that this should be a bug related with network (wifi connection). Here is the issue: Every time after I login into the account, about 20 minutes later, the wifi will be disconnected automatically. I even cannot reconnect the wifi manually, the only thing that I can do is to reboot the laptop. After login again, wifi can be connected (but through manual way). By the way, during the period of wifi disconnection, I checked the "Wi-Fi Networks" by click "Select Network" in order to try to reconnect it manually. But I found that there is only one SSID which previously the laptop connected to. However, I was definitely sure that there should be more than one SSID being showed in the wifi list. Even for this only one SSID, like I mentioned before, I cannot reconnect manually unless I reboot the system. Finally, I set the wifi to be connected automatically after I login to the system, however, it just can't. I can only connect to the wifi manually after I login to the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 19:02:12 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (68 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 WolfieNet-Secure eb45c742-ba31-4f31-acf2-13a2768bcc29 /org/freedesktop/NetworkManager/ActiveConnection/5 enp5s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled disabled --- ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kevin 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (70 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.148 metric 600 MachineType: Lenovo F31 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false NonfreeKernelModules: nvidia Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=02a1b417-5beb-4eae-82cb-e3063372bf6d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic package-from-proposed Uname: Linux
[Desktop-packages] [Bug 1767122] [NEW] duplicity Errors 199 at end backup
Public bug reported: Hello, I use duplicity to backup my file. However. I get always this message at end backup with Error 199 --[ Backup Statistics ]-- StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018) EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018) ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds) SourceFiles 3821570 SourceFileSize 191576839080 (178 GB) NewFiles 2088902 NewFileSize 19156070 (178 GB) DeletedFiles 3 ChangedFiles 54 ChangedFileSize 1834439 (1.75 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2088959 RawDeltaSize 0 (0 bytes) TotalDestinationSizeChange 0 (0 bytes) Errors 199lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic Step to reproduce : 1. Configure duplicity 2. Run a bakup. Result 3. At end backup, you should get Error 199 - uname -r 4.15.0-20-generic My configuration : lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy duplicity duplicity: Installed: 0.7.17-0ubuntu1 Candidate: 0.7.17-0ubuntu1 Version table: *** 0.7.17-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy python python: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 Version table: *** 2.7.15~rc1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Could you help me please to fix this issues ? Thanks by advance for your support Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: duplicity 0.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 15:58:41 2018 SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: duplicity (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 duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1767122 Title: duplicity Errors 199 at end backup Status in duplicity package in Ubuntu: New Bug description: Hello, I use duplicity to backup my file. However. I get always this message at end backup with Error 199 --[ Backup Statistics ]-- StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018) EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018) ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds) SourceFiles 3821570 SourceFileSize 191576839080 (178 GB) NewFiles 2088902 NewFileSize 19156070 (178 GB) DeletedFiles 3 ChangedFiles 54 ChangedFileSize 1834439 (1.75 MB) ChangedDeltaSize 0 (0 bytes) DeltaEntries 2088959 RawDeltaSize 0 (0 bytes) TotalDestinationSizeChange 0 (0 bytes) Errors 199lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic Step to reproduce : 1. Configure duplicity 2. Run a bakup. Result 3. At end backup, you should get Error 199 - uname -r 4.15.0-20-generic My configuration : lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic apt-cache policy duplicity duplicity: Installed: 0.7.17-0ubuntu1 Candidate: 0.7.17-0ubuntu1 Version table: *** 0.7.17-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy python python: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 Version table: *** 2.7.15~rc1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Could you help me please to fix this issues ? Thanks by advance for your support Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: duplicity 0.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 15:58:41 2018 SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1767122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1765888] Re: Please revert to debian-alternatives based prime-select
I think this is all a repercussion of using glvnd. I tried switching to intel mode and this results in a machine that cannot be logged in to. Also, the other framebuffer ttys are nt accessible. I recovered by going into friendly-recovery, getting a root shell, remounting my ssd as rw and executing prime-select nvidia then rebooting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select Status in nvidia-prime package in Ubuntu: Confirmed Bug description: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+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 1765888] Re: Please revert to debian-alternatives based prime-select
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select Status in nvidia-prime package in Ubuntu: Confirmed Bug description: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
After the initial reboot, x seems to keep crashing, but if you can get to a vt and run apt-get install -f, it seems to at least allow the system to boot -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago)
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: oem-priority Status: New => Confirmed -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Unfortunately, nouveau makes laptops with a Pascal dGPU (GeForce 10xx series) really unstable. For example my Dell XPS 9560 with a GTX 1050 won't boot without "nouveau.runpm=0". With "nouveau.runpm=0", boot will be slow, and multiple freezes with a recovery a few seconds later will occur after graphical login. The system remains sluggish even as the iGPU is used. See: https://bugs.freedesktop.org/show_bug.cgi?id=100228 (there might be other bugs affecting general stability with Pascal dGPUs) If I blacklist nouveau completely (both as a kernel boot option and in /etc/modprobe.d/), the system will function normally, but the dGPU will stay on. Forcing the use of nouveau on these recent laptops, especially for a LTS, really is a step backwards compared to what we had in 17.10. ** Bug watch added: freedesktop.org Bugzilla #100228 https://bugs.freedesktop.org/show_bug.cgi?id=100228 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I've reproduced this with an XPS13 9370, same errors and now X is completely broken -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
[Desktop-packages] [Bug 1767116] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1767116 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 16:22:30 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2016-05-19 (706 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1767116/+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 1767116] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 16:22:30 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2016-05-19 (706 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1767116 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 16:22:30 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2016-05-19 (706 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1767116/+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 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out
Update, I noticed the pattern so far and turning off pulseaudio seems to have stopped the behaviour. I obviously can't leave the system without sound, so I'm still looking for a permanent fix. The pattern is allways like this: Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: sender=:1.445 path=/MediaEndpoint/A2DPSource Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: sender=:1.445 path=/MediaEndpoint/A2DPSink Apr 26 15:06:07 ESS-PC26 pulseaudio[12799]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.of Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Apr 26 15:06:07 ESS-PC26 rtkit-daemon[1524]: Successfully made thread 12829 of process 12829 (n/a) owned by '108' high priority at nice level -11. Apr 26 15:06:07 ESS-PC26 rtkit-daemon[1524]: Supervising 9 threads of 3 processes of 2 users. Apr 26 15:06:07 ESS-PC26 pulseaudio[12829]: [pulseaudio] pid.c: Daemon already running. Apr 26 15:06:14 ESS-PC26 org.gtk.vfs.Daemon[12708]: A connection to the bus can't be made Bluetooth tries to register a device or something, pulse fails and system loggs out. My current workaround is to completely turn off pulseaudio by creating a ~/.pulse/client.conf file with autospawn=no inside. As I've already mentioned before, pulseaudio crashing leves no crash log. How an I get this fixed/debugged? -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+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 1765363] Re: prime-select intel is not powering off the nvidia card
Great, thanks for testing! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
I reproduced the issue with the clone attached. ** Changed in: gnome-menus (Ubuntu) Importance: Undecided => Critical -- 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/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: New Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" -
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I didn't know about the SLI breakage, my bad. Just did a clean install and I can confirm that it's working as it should: $ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x65 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:modesetting Provider 1: id: 0x3f cap: 0x4, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:nouveau # cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr::00:02.0 1:DIS: :Off::01:00.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1765363] Re: prime-select intel is not powering off the nvidia card
When switching to Intel, nouveau is loaded manually (overriding the blacklist), and switches off the dGPU. The leftover /etc/modprobe.d/blacklist-nvidia.conf should be removed when switching back to Nvidia. P.S. We cannot enable nvidia-drm.modeset by default, because it breaks SLI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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