[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Updated debdiff for bionic. ** Patch added: "bionic_cups_2.2.7-1ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5221596/+files/bionic_cups_2.2.7-1ubuntu2.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Updated debdiff for xenial. ** Patch added: "xenial_cups_2.1.3-4ubuntu0.7.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5221597/+files/xenial_cups_2.1.3-4ubuntu0.7.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Updated debdiff for cosmic. ** Patch removed: "cosmic_cups_2.2.8-5ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219665/+files/cosmic_cups_2.2.8-5ubuntu2.debdiff ** Patch removed: "bionic_cups_2.2.7-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219666/+files/bionic_cups_2.2.7-1ubuntu2.2.debdiff ** Patch removed: "xenial_cups_2.1.3-4ubuntu0.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219667/+files/xenial_cups_2.1.3-4ubuntu0.6.debdiff ** Patch added: "cosmic_cups_2.2.8-5ubuntu1.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5221595/+files/cosmic_cups_2.2.8-5ubuntu1.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Thanks. It sounds like I need to get back to my CPU fix relating to the Ubuntu Dock impacting gnome-shell (bug 1743976). The only way to avoid that is to not have any windows near the dock. That's a separate but also related bug to this and should be tracked in bug 1743976. As for cursor movement, please open a new bug if you want to discuss that (and mention in it upstream bug https://gitlab.gnome.org/GNOME/mutter/issues/283). That leaves this bug as being just about Chrome impacting gnome-shell's CPU usage. -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Triaged Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Unpinned the chrome from the Dock but gnome shell is consuming high CPU but not constantly. If I keep idle gnome-shell usage becomes low untill I move the curser. Chromium also consuming high usage. Please find the screenshot. ** Attachment added: "Screenshot.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+attachment/5221565/+files/Screenshot.png -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Triaged Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1808098] Re: /usr/bin/Xwayland:6:xwl_glamor_gbm_get_wl_buffer_for_pixmap:xwl_window_post_damage:xwl_screen_post_damage:block_handler:BlockHandler
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/340 Upstream fix: https://gitlab.freedesktop.org/xorg/xserver/commit/036794bebce72a3fa2f95996d2e537ff568e0ff1 ** Summary changed: - /usr/bin/Xwayland:6:xwl_glamor_gbm_get_wl_buffer_for_pixmap:xwl_window_post_damage:xwl_screen_post_damage:block_handler:BlockHandler + Xwayland crashed with SIGSEGV in xwl_glamor_gbm_get_wl_buffer_for_pixmap → xwl_window_post_damage → xwl_screen_post_damage → block_handler → BlockHandler -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1808098 Title: Xwayland crashed with SIGSEGV in xwl_glamor_gbm_get_wl_buffer_for_pixmap → xwl_window_post_damage → xwl_screen_post_damage → block_handler → BlockHandler Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/869a5ccb23a15937a80562b869c091edd3ed6b88 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/xorg-server/+bug/1808098/+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 1808098] [NEW] Xwayland crashed with SIGSEGV in xwl_glamor_gbm_get_wl_buffer_for_pixmap → xwl_window_post_damage → xwl_screen_post_damage → block_handler → BlockHandler
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/869a5ccb23a15937a80562b869c091edd3ed6b88 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: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1808098 Title: Xwayland crashed with SIGSEGV in xwl_glamor_gbm_get_wl_buffer_for_pixmap → xwl_window_post_damage → xwl_screen_post_damage → block_handler → BlockHandler Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/869a5ccb23a15937a80562b869c091edd3ed6b88 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/xorg-server/+bug/1808098/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Finally, please try moving the Chrome window away from the dock on the left so it is definitely not touching (not even the window shadow). Does that reduce the CPU usage of gnome-shell when using Chrome? -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Triaged Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Thanks, that confirms gnome-shell's CPU usage is due to Chrome redrawing. Moving the cursor is a different bug (https://gitlab.gnome.org/GNOME/mutter/issues/283) so be careful to not confuse the two. A third and unrelated issue is that your monitor is only running at 40Hz even though it supports 60Hz: 1366x768 60.22 + 40.03* If that's an attempt at reducing CPU then it will certainly help, but it will cause visible flickering and judder which you may find annoying. You can change the display frequency in Settings. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Triaged Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1807761] Re: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi
It would appear the issue is that a gdebi instance opened from the context menu on a desktop item is unable to do any action on any .deb file located anywhere. In other words it's doomed to fail upon simply opening. Can be easily seen by opening gdebi-gtk as described but then switching to another .deb somewhere else from gdebi's open menu item. This will also fail. gdebi-gtk opened from app menu has no issues acting on a .deb from anywhere inc. the desktop -- 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/1807761 Title: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi Status in gdebi package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 18.04 LTS or Ubuntu 18.10 2. Download some deb-file to the desktop - for with help of terminal: cd ~/Desktop apt-get download meld 3. Install GDebi package installer with sudo apt install gdebi 4. Select deb-file on desktop, make right click on it, select *Open With Other Application* select *GDebi Package Installer*, click *Select*, in opened window select *Install Package* Expected results: * GDebi asks user (sudo-able) password and installs the package Actual results: * GDebi do not ask user for password and do not install the package Notes: * first seen on AskUbuntu ( https://askubuntu.com/q/1099387/66509 ) * you can view my screencast to get first person view :) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 10 23:14:16 2018 GsettingsChanges: 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/gdebi/+bug/1807761/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Stopping chrome is not stopping the gnome-shell usage. If I keep idle then the load is becoming low 1.xx if the move the cursor then the gnome-shell is going high. I have tried with chromium but facing the same issue. xrandr Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 277mm x 156mm 1366x768 60.22 + 40.03* 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) Subsystem: Dell 7 Series/C210 Series Chipset Family USB xHCI Host Controller Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell 7 Series/C216 Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04) Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville) Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) Subsystem: Dell 7 Series/C216 Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) Subsystem: Dell 7 Series/C216 Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) Kernel driver in use: pcieport 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) Kernel driver in use: pcieport 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4) Kernel driver in use: pcieport 00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4) Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) Subsystem: Dell 7 Series/C216 Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) Subsystem: Dell QM77 Express Chipset LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) Subsystem: Dell 82801 Mobile
[Desktop-packages] [Bug 1796888] Re: Lock screen does not unlock with valid password if non-english keyboard layout was selected before screen was locked
This bug affect me too - can't enter correct password in gnome- screensaver. I'm using lightdm for login, if it matters -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1796888 Title: Lock screen does not unlock with valid password if non-english keyboard layout was selected before screen was locked Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: The bug could be reproduced the following way: 1) Select EN keyboard layout - Lock the screen - Enter the valid password - Success 2) Select other keyboard layout (RU in my case) - Lock the screen - Enter the valid password (lock screen shows that EN layout is used) - Password is not accepted Keyboard shortcuts for input source switch does not work properly when the screen is locked. Also, I tried to switch input source with the button displayed in the lock screen - it shows as if the input source was changed, but it does not produce any effect, the password is still rejected. Also, have checked that the Caps lock is switched in the proper position. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 15:55:06 2018 InstallationDate: Installed on 2018-09-04 (34 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to bionic on 2018-10-08 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1796888/+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 1796888] Re: Lock screen does not unlock with valid password if non-english keyboard layout was selected before screen was locked
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1796888 Title: Lock screen does not unlock with valid password if non-english keyboard layout was selected before screen was locked Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: The bug could be reproduced the following way: 1) Select EN keyboard layout - Lock the screen - Enter the valid password - Success 2) Select other keyboard layout (RU in my case) - Lock the screen - Enter the valid password (lock screen shows that EN layout is used) - Password is not accepted Keyboard shortcuts for input source switch does not work properly when the screen is locked. Also, I tried to switch input source with the button displayed in the lock screen - it shows as if the input source was changed, but it does not produce any effect, the password is still rejected. Also, have checked that the Caps lock is switched in the proper position. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 15:55:06 2018 InstallationDate: Installed on 2018-09-04 (34 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to bionic on 2018-10-08 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1796888/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Can someone submit a PR to linux kernel? I did not see one when searching. I'd be happy to upvote it. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Also, please run these commands and send us the output: xrandr lspci -k -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Does closing Chrome also stop the gnome-shell CPU usage? -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
I think the fix is in Ubuntu 18.04.1 (not 18.04) so please use 18.04.1:
http://releases.ubuntu.com/18.04/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Unknown
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
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/cairo/+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
[Desktop-packages] [Bug 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
gnome shell consuming min 15% and chrome consuming 5-10% with 2 tabs, If I play any youtube videos it goes like more than 100%. No other applications are running in the system. -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
an able to upgrade from 17.04 to 18.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Unknown
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
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/cairo/+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 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
Hello @Steve, Checked your pkg/ppa in Bionic 32 bit - all back to normal Thanks for your quick fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Confirmed Status in gnome-desktop3 source package in Cosmic: In Progress Bug description: Impact == Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs. Test Case = Install Ubuntu 18.10 32-bit Install the update. Log out and log back in. Download a picture from the internet. Open your file browser to the directory that contains the picture. The file should show a thumbnail preview. Regression Potential This fix was cherry-picked to the stable gnome-3-30 branch. It was additionally tested by Iain Lane on usrmerged and non-usrmerged systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.) Other Info == Triaged as Critical for 18.04 LTS since this was a regression introduced in the security update that backported the bubblewrap hardening to the gnome-desktop3 thumbnailer. Original Bug Report === Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+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 1034049] Re: hplip Error 5012 on Kubuntu but not Lubuntu
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1034049 Title: hplip Error 5012 on Kubuntu but not Lubuntu Status in hplip package in Ubuntu: Expired Bug description: I first installed this printer on a computer running Lubuntu. After a few shenanigans getting hp-setup to work properly, I got everything working. When I switched back to Kubuntu, however, I started having problems with print jobs not going through until the printer was power- cycled. When I reinstalled hplip-gui, the device manager tells me that after I turn on or restart my computer, I get error 5012. The end result is that I have to restart the printer whenever I want to print or scan something, instead of it just working every single time as it did on Lubuntu. There were also issues with the scanner not being detectable by xsane until the printer was power- cycled as well. These were also not present in Lubuntu. Figured a discrepancy like this is worth reporting as a bug, since the hplip version should be the same across the two versions. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: hplip 3.12.2-1ubuntu3.1 [modified: var/lib/hp/hplip.state] ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Tue Aug 7 11:09:12 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) Lpstat: device for HP-LaserJet-Professional-M1212nf-MFP: hp:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ5236JSI1c device for HP-LaserJet-Professional-M1212nf-MFP-Fax-3: hpfax:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ5236JSI1c MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7597 Papersize: letter PpdFiles: HP-LaserJet-Professional-M1212nf-MFP-Fax-3: HP Fax3 hpcups HP-LaserJet-Professional-M1212nf-MFP: HP LaserJet Professional m1212nf MFP, hpcups 3.12.2, requires proprietary plugin ProcEnviron: LANGUAGE= TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=7f26f62c-1db1-4d41-be02-22efb59f45c4 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: GF615M-P33 (MS-7597) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd01/04/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7597:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnGF615M-P33(MS-7597):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7597 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD --- ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) Lpstat: device for HP_LaserJet_Professional_M1212nf_MFP: hp:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ5236JPR1a device for HP_LaserJet_Professional_M1212nf_MFP_fax: hpfax:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ5236JPR1a MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7597 NonfreeKernelModules: nvidia Package: hplip 3.12.2-1ubuntu3.1 [modified: var/lib/hp/hplip.state] PackageArchitecture: amd64 Papersize: letter PpdFiles: HP_LaserJet_Professional_M1212nf_MFP: HP LaserJet Professional m1212nf MFP, hpcups 3.12.2, requires proprietary plugin HP_LaserJet_Professional_M1212nf_MFP_fax: HP Fax3 hpcups ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=e7fcb2c0-9eef-49d5-b7d3-664ed998f040 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Tags: precise Uname: Linux 3.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: GF615M-P33 (MS-7597) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
[Desktop-packages] [Bug 1014777] Re: package hplip-data 3.12.2-1ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 101
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1014777 Title: package hplip-data 3.12.2-1ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 101 Status in hplip package in Ubuntu: Expired Bug description: 12.04 Impossibile trovare il pacchetto pkgname ProblemType: Package DistroRelease: Ubuntu 12.04 Package: hplip-data ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 CupsErrorLog: CurrentDmesg: [ 37.128035] wlan0: no IPv6 routers present Date: Mon Jun 18 19:24:52 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 101 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 04f2:b057 Chicony Electronics Co., Ltd integrated USB webcam MachineType: Hewlett-Packard Presario C700 GZ914EA#ABZ PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic root=UUID=cc0c160f-b02d-4fd4-91e3-7e964e99204a ro quiet splash vt.handoff=7 SourcePackage: hplip Title: package hplip-data 3.12.2-1ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 101 UpgradeStatus: Upgraded to precise on 2012-06-18 (0 days ago) dmi.bios.date: 02/29/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30D9 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.31:bd02/29/2008:svnHewlett-Packard:pnPresarioC700GZ914EA#ABZ:pvrF.31:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: Presario C700 GZ914EA#ABZ dmi.product.version: F.31 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1014777/+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 819694] Re: Unable to scan with Laserjet M1536dnf MFP
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/819694 Title: Unable to scan with Laserjet M1536dnf MFP Status in hplip package in Ubuntu: Expired Bug description: It seems there is some missing files with hplip from natty (3.11.1). This version is said supporting my printer (http://hplipopensource.com/hplip-web/release_notes.html). Printing is working correctly. However when I try to scan with simple-scan (launched from terminal) I get this error : ** (simple-scan:3431): WARNING **: Unable to get open device: Error during device I/O Further investigation show error in syslog : simple-scan: scan/sane/soapht.c 89: unable to load restricted library /usr/share/hplip/scan/plugins/bb_soapht.so: /usr/share/hplip/scan/plugins/bb_soapht.so: cannot open shared object file: No such file or directory I've seen some bugreports with this error, but none explicitly talking about this file. Installing latest (3.11.7) hplip from the hplip website and installing printer with hp-setup made scanning work. And with this method, the bb_soapht.so file is installed (a symlink pointing to /usr/share/hplip/scan/plugins/bb_soapht-x86_32.so) Installing the printer with the natty stock hplip hp-setup tool lead to the error : "unable to download plugin". Let me know if more details is needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/819694/+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 709992] Re: package hplip-data 3.10.2-2ubuntu2.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/709992 Title: package hplip-data 3.10.2-2ubuntu2.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in hplip package in Ubuntu: Expired Bug description: Binary package hint: hplip When performing update manager, it crashed my system. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: hplip-data 3.10.2-2ubuntu2.2 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 Architecture: i386 CurrentDmesg: [ 20.886216] usb 2-1: usbfs: interface 1 claimed by usblp while 'usb' sets config #1 [ 27.784015] eth0: no IPv6 routers present Date: Sat Jan 29 21:59:13 2011 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) Lpstat: device for OfficeJet-6100-Series: hp:/usb/OfficeJet_6100_Series?serial=MY36PF71062R MachineType: Dell Computer Corporation OptiPlex GX260 PackageArchitecture: all Papersize: letter PpdFiles: OfficeJet-6100-Series: HP Officejet 6100 Series hpijs, 3.10.2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-28-generic root=/dev/sda1 loop=/hostname/disks/root.disk ro quiet splash SourcePackage: hplip Title: package hplip-data 3.10.2-2ubuntu2.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 dmi.bios.date: 07/25/2002 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A02 dmi.board.name: OptiPlex GX260 dmi.board.vendor: Dell Computer Corporation dmi.chassis.type: 3 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA02:bd07/25/2002:svnDellComputerCorporation:pnOptiPlexGX260:pvr:rvnDellComputerCorporation:rnOptiPlexGX260:rvr:cvnDellComputerCorporation:ct3:cvr: dmi.product.name: OptiPlex GX260 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/709992/+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 1529939] Re: BJNP Canon network printer no longer auto-detected
[Expired for system-config-printer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: system-config-printer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1529939 Title: BJNP Canon network printer no longer auto-detected Status in system-config-printer package in Ubuntu: Expired Bug description: Up to Ubuntu 15.04, I only needed to install the cups-backend-bjnp package, and my (wifi-connected) Canon Pixma MG5250 would then show up automatically in the Add printers/Network printers dialog. This is no longer the case in 15.10 -- I need to manually add it by entering bnjp://my.printers.ip.address. This bug is present both on Ubuntu and Ubuntu Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1529939/+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 1797529] Re: Everything crushes when I try to open Settings
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1797529 Title: Everything crushes when I try to open Settings Status in gnome-control-center package in Ubuntu: Expired Bug description: Ubuntu 18.04 When I try to open Settings everything crashes! After selecting Settings app or clicking Settings icon from top right corner, I see black screen and a bit after that the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797529/+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 1797553] Re: file-roller extract and replace does not replace
[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.] ** Changed in: file-roller (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1797553 Title: file-roller extract and replace does not replace Status in file-roller package in Ubuntu: Expired Bug description: When extracting a file over an existing file, clicking "Replace" in the dialog that asks to confirm overwriting a file, does not replace the file. Reproduce: - Open any archive (I've tested zip and 7z) - Right click a file and extract - Edit the extracted file so you can see that it will not be replaced - Right click and extract the file again, to the same file name - In the dialog asking whether to replace the file, click "Replace". - File roller confirms extraction, however the file was *not* replaced by the copy from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+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 1807997] Re: xorg crashed
On 2018-12-11 9:31 p.m., Daniel van Vugt wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. The most recent link is https://errors.ubuntu.com/oops/6944-e46a-11e8-93f6-fa163e102db1 There are a lot of other crash-bugs that I didn't report, is reporting automatic? > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. Unfortunately I've only had the crash happen once. I had hoped the .crash file would be useful. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. Could the attach form detect it is a .crash file? > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1807997 Title: xorg crashed Status in xorg-server package in Ubuntu: Incomplete Bug description: ubuntu-bug didn't open a web browser after it uploaded the crash file. I was using firefox and everything crashed. -rw-r- 1 rjl whoopsie 1506299 Dec 11 11:34 _usr_bin_lxqt-globalkeysd.1000.crash -rw-r- 1 root whoopsie 6502766 Dec 11 11:41 _usr_lib_xorg_Xorg.0.crash This was in dmesg: [ 941.428542] do_general_protection: 11 callbacks suppressed [ 941.428547] traps: lxqt-globalkeys[1437] general protection ip:7f816ac0c3f7 sp:7fff95cd7cb0 error:0 in libc-2.28.so[7f816abea000+171000] [ 941.511120] Chrome_~dThread[2865]: segfault at 0 ip 7facf7e58a4b sp 7facf2d26b00 error 6 in libxul.so[7facf7e44000+3e9a000] [ 941.511135] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d [ 941.511185] Chrome_~dThread[2805]: segfault at 0 ip 7f9f47a40a4b sp 7f9f4290eb00 error 6 [ 941.511187] 68 01 b0 [ 941.511192] in libxul.so[7f9f47a2c000+3e9a000] [ 941.511194] 04 [ 941.511196] Code: [ 941.511197] 48 89 [ 941.511199] fa 05 [ 941.511201] 08 [ 941.511203] 48 [ 941.511205] 04 [ 941.511206] 8d 15 [ 941.511208] 25 00 [ 941.511210] 1e 01 [ 941.511212] 00 00 [ 941.511214] b0 04 [ 941.511216] 00 00 [ 941.511218] 48 89 [ 941.511220] 00 00 [ 941.511222] 10 c7 [ 941.511224] 00 0f [ 941.511226] 04 25 [ 941.511228] 0b e8 [ 941.511230] 00 00 [ 941.511232] 4d f4 [ 941.511234] 00 00 [ 941.511236] ff ff [ 941.511238] 00 00 [ 941.511240] 48 8b [ 941.511242] 00 00 [ 941.511244] 05 e4 [ 941.511246] 0f 0b [ 941.511249] 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 [ 941.579142] Chrome_~dThread[3153]: segfault at 0 ip 7f11b0208a4b sp 7f11ab0d6b00 error 6 in libxul.so[7f11b01f4000+3e9a000] [ 941.579155] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1807997/+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 1808002] Re: Gnome shell is consuming high cpu usage when running Chrome
Also, please run 'top' and tell us which processes are using how much CPU each. -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1808002] Re: Gnome shell is consuming high cpu usage
Does the high CPU usage stop after you close Chrome? ** Tags added: performance ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - Gnome shell is consuming high cpu usage + Gnome shell is consuming high cpu usage when running Chrome -- 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/1808002 Title: Gnome shell is consuming high cpu usage when running Chrome Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1807997] Re: xorg crashed
The attached crash file in comment #1 is unfortunately not debuggable: Stacktrace: #0 0x7f507a1a1077 in raise () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f507a182535 in abort () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x558a5f1dcd4a in () #3 0x558a5f1e2853 in () #4 0x558a5f1e36b9 in FatalError () #5 0x558a5f1da161 in () #6 0x7f507a362dd0 in () at /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7f5078aea3ed in () at /usr/lib/xorg/modules/libglamoregl.so #8 0x7f5078af4f38 in () at /usr/lib/xorg/modules/libglamoregl.so #9 0x7f5078af536c in () at /usr/lib/xorg/modules/libglamoregl.so #10 0x7f5078af597e in () at /usr/lib/xorg/modules/libglamoregl.so #11 0x7f5078af797c in () at /usr/lib/xorg/modules/libglamoregl.so #12 0x558a5f15c2ff in () #13 0x7f5078afe7ae in () at /usr/lib/xorg/modules/libglamoregl.so #14 0x558a5f1510e5 in () #15 0x558a5f07b91e in () #16 0x558a5f07f8c6 in () #17 0x7f507a18409b in __libc_start_main () at /lib/x86_64-linux-gnu/libc.so.6 #18 0x558a5f06967a in _start () StacktraceAddressSignature: /usr/lib/xorg/Xorg:6:/lib/x86_64-linux-gnu/libc-2.28.so+1f077:/lib/x86_64-linux-gnu/libc-2.28.so+535:/usr/lib/xorg/Xorg+17ed4a:/usr/lib/xorg/Xorg+184853:/usr/lib/xorg/Xorg+1856b9:/usr/lib/xorg/Xorg+17c161:/lib/x86_64-linux-gnu/libpthread-2.28.so+cdd0:/usr/lib/xorg/modules/libglamoregl.so+33ed:/usr/lib/xorg/modules/libglamoregl.so+df38:/usr/lib/xorg/modules/libglamoregl.so+e36c:/usr/lib/xorg/modules/libglamoregl.so+e97e:/usr/lib/xorg/modules/libglamoregl.so+1097c:/usr/lib/xorg/Xorg+fe2ff:/usr/lib/xorg/modules/libglamoregl.so+177ae:/usr/lib/xorg/Xorg+f30e5 Please follow the steps in comment #3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1807997 Title: xorg crashed Status in xorg-server package in Ubuntu: Incomplete Bug description: ubuntu-bug didn't open a web browser after it uploaded the crash file. I was using firefox and everything crashed. -rw-r- 1 rjl whoopsie 1506299 Dec 11 11:34 _usr_bin_lxqt-globalkeysd.1000.crash -rw-r- 1 root whoopsie 6502766 Dec 11 11:41 _usr_lib_xorg_Xorg.0.crash This was in dmesg: [ 941.428542] do_general_protection: 11 callbacks suppressed [ 941.428547] traps: lxqt-globalkeys[1437] general protection ip:7f816ac0c3f7 sp:7fff95cd7cb0 error:0 in libc-2.28.so[7f816abea000+171000] [ 941.511120] Chrome_~dThread[2865]: segfault at 0 ip 7facf7e58a4b sp 7facf2d26b00 error 6 in libxul.so[7facf7e44000+3e9a000] [ 941.511135] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d [ 941.511185] Chrome_~dThread[2805]: segfault at 0 ip 7f9f47a40a4b sp 7f9f4290eb00 error 6 [ 941.511187] 68 01 b0 [ 941.511192] in libxul.so[7f9f47a2c000+3e9a000] [ 941.511194] 04 [ 941.511196] Code: [ 941.511197] 48 89 [ 941.511199] fa 05 [ 941.511201] 08 [ 941.511203] 48 [ 941.511205] 04 [ 941.511206] 8d 15 [ 941.511208] 25 00 [ 941.511210] 1e 01 [ 941.511212] 00 00 [ 941.511214] b0 04 [ 941.511216] 00 00 [ 941.511218] 48 89 [ 941.511220] 00 00 [ 941.511222] 10 c7 [ 941.511224] 00 0f [ 941.511226] 04 25 [ 941.511228] 0b e8 [ 941.511230] 00 00 [ 941.511232] 4d f4 [ 941.511234] 00 00 [ 941.511236] ff ff [ 941.511238] 00 00 [ 941.511240] 48 8b [ 941.511242] 00 00 [ 941.511244] 05 e4 [ 941.511246] 0f 0b [ 941.511249] 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 [ 941.579142] Chrome_~dThread[3153]: segfault at 0 ip 7f11b0208a4b sp 7f11ab0d6b00 error 6 in libxul.so[7f11b01f4000+3e9a000] [ 941.579155] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1807997/+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 1807997] Re: xorg crashed
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1807997 Title: xorg crashed Status in xorg-server package in Ubuntu: Incomplete Bug description: ubuntu-bug didn't open a web browser after it uploaded the crash file. I was using firefox and everything crashed. -rw-r- 1 rjl whoopsie 1506299 Dec 11 11:34 _usr_bin_lxqt-globalkeysd.1000.crash -rw-r- 1 root whoopsie 6502766 Dec 11 11:41 _usr_lib_xorg_Xorg.0.crash This was in dmesg: [ 941.428542] do_general_protection: 11 callbacks suppressed [ 941.428547] traps: lxqt-globalkeys[1437] general protection ip:7f816ac0c3f7 sp:7fff95cd7cb0 error:0 in libc-2.28.so[7f816abea000+171000] [ 941.511120] Chrome_~dThread[2865]: segfault at 0 ip 7facf7e58a4b sp 7facf2d26b00 error 6 in libxul.so[7facf7e44000+3e9a000] [ 941.511135] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d [ 941.511185] Chrome_~dThread[2805]: segfault at 0 ip 7f9f47a40a4b sp 7f9f4290eb00 error 6 [ 941.511187] 68 01 b0 [ 941.511192] in libxul.so[7f9f47a2c000+3e9a000] [ 941.511194] 04 [ 941.511196] Code: [ 941.511197] 48 89 [ 941.511199] fa 05 [ 941.511201] 08 [ 941.511203] 48 [ 941.511205] 04 [ 941.511206] 8d 15 [ 941.511208] 25 00 [ 941.511210] 1e 01 [ 941.511212] 00 00 [ 941.511214] b0 04 [ 941.511216] 00 00 [ 941.511218] 48 89 [ 941.511220] 00 00 [ 941.511222] 10 c7 [ 941.511224] 00 0f [ 941.511226] 04 25 [ 941.511228] 0b e8 [ 941.511230] 00 00 [ 941.511232] 4d f4 [ 941.511234] 00 00 [ 941.511236] ff ff [ 941.511238] 00 00 [ 941.511240] 48 8b [ 941.511242] 00 00 [ 941.511244] 05 e4 [ 941.511246] 0f 0b [ 941.511249] 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 [ 941.579142] Chrome_~dThread[3153]: segfault at 0 ip 7f11b0208a4b sp 7f11ab0d6b00 error 6 in libxul.so[7f11b01f4000+3e9a000] [ 941.579155] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1807997/+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 1807951] Re: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problemas de dependencias - se deja sin configurar
*** This bug is a duplicate of bug 1779552 *** https://bugs.launchpad.net/bugs/1779552 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 1779552, 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 1779552 [regression] package gnome-shell ... failed to install/upgrade: dependency problems - leave unconfigured. [... depends on python3 however: Package python3 is not configured yet.] preceded by [E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory')] -- 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/1807951 Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in gnome-shell package in Ubuntu: New Bug description: En mi sistema operativo aparece una leyenda que dice no puede iniciar correctamente. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libraw16:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Dec 10 06:23:44 2018 DisplayManager: gdm3 ErrorMessage: problemas de dependencias - se deja sin configurar GsettingsChanges: InstallationDate: Installed on 2018-09-21 (80 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gnome-shell Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807951/+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 1797381] Re: In tablet mode, step "Who are you" OSK hides when the password field is focused
** Summary changed: - In tablet mode, step "Who are you" OSK hides when the passwordd field is focused + In tablet mode, step "Who are you" OSK hides when the password field is focused -- 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/1797381 Title: In tablet mode, step "Who are you" OSK hides when the password field is focused Status in gnome-shell package in Ubuntu: Incomplete Bug description: Test Case: 1. On a 2 in 1 in tablet mode, launch the installer and proceed to the user setup step (Who are you) 2. With the OSK, enter the username, login, hostname and password then proceed zith the rest of the installation Actual result The OSK hides when the password field has the focus and the user cannot enter a password. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 15:15:14 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181011) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797381/+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 1803271] Re: [regression] Much higher CPU during some gnome-shell operations
** Description changed: [Impact] Since fixing bug 1672297 in release 18.04 we experience much higher (almost double) CPU usage during gnome-shell JavaScript operations, such as the icon spring animation [1]. Even just moving the mouse is a little more expensive now [2]. [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349 [2] https://gitlab.gnome.org/GNOME/mutter/issues/283 [Test Case] Use 'top' to measure the CPU usage of the gnome-shell process while tapping Super+A repeatedly. It should be much lower with the fix than without. [Regression Potential] Low. This particular fix is tiny (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been released and used in a couple of upstream gjs versions already without issue. [Other Info] The fix is already released to 19.04 as part of gjs version 1.54.2-1. + And already released to 18.10 as part of gjs version + 1.54.3-1~ubuntu18.10.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1803271 Title: [regression] Much higher CPU during some gnome-shell operations Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Bionic: Triaged Status in gjs source package in Cosmic: Fix Released Bug description: [Impact] Since fixing bug 1672297 in release 18.04 we experience much higher (almost double) CPU usage during gnome-shell JavaScript operations, such as the icon spring animation [1]. Even just moving the mouse is a little more expensive now [2]. [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349 [2] https://gitlab.gnome.org/GNOME/mutter/issues/283 [Test Case] Use 'top' to measure the CPU usage of the gnome-shell process while tapping Super+A repeatedly. It should be much lower with the fix than without. [Regression Potential] Low. This particular fix is tiny (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been released and used in a couple of upstream gjs versions already without issue. [Other Info] The fix is already released to 19.04 as part of gjs version 1.54.2-1. And already released to 18.10 as part of gjs version 1.54.3-1~ubuntu18.10.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 1803271] Re: [regression] Much higher CPU during some gnome-shell operations
gjs (1.54.3-1~ubuntu18.10.1) cosmic; urgency=medium * No-change SRU backport from unstable / disco to cosmic (LP: #1804641) * Also fixes crash on `gnome-shell --replace' (LP: #1796238) gjs (1.54.3-1) unstable; urgency=medium * Team upload * New upstream release * Force time zone to UTC when running tests. This hopefully fixes FTBFS in the pathological time zone used to test reproducible builds. gjs (1.54.2-1) unstable; urgency=medium * Team upload * Upload to unstable (starts transition: #906016) * d/watch: Only watch for versions from a stable branch * New upstream release * Bump Standards-Version to 4.2.1 (no changes required) * Use dpkg's default.mk to get upstream version number for dependencies. This avoids relying on the differently-named variables in gnome-get-source.mk, and also does the right thing if gjs ever gains an epoch. * d/rules: Remove gnome-get-source.mk (please use uscan instead) -- Iain Lane Thu, 22 Nov 2018 12:21:13 + ** Changed in: gjs (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1803271 Title: [regression] Much higher CPU during some gnome-shell operations Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Bionic: Triaged Status in gjs source package in Cosmic: Fix Released Bug description: [Impact] Since fixing bug 1672297 in release 18.04 we experience much higher (almost double) CPU usage during gnome-shell JavaScript operations, such as the icon spring animation [1]. Even just moving the mouse is a little more expensive now [2]. [1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/349 [2] https://gitlab.gnome.org/GNOME/mutter/issues/283 [Test Case] Use 'top' to measure the CPU usage of the gnome-shell process while tapping Super+A repeatedly. It should be much lower with the fix than without. [Regression Potential] Low. This particular fix is tiny (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been released and used in a couple of upstream gjs versions already without issue. [Other Info] The fix is already released to 19.04 as part of gjs version 1.54.2-1. And already released to 18.10 as part of gjs version 1.54.3-1~ubuntu18.10.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 1766827] Re: Missing icons on the status bar (top bar)
Sorry for the delay. We didn't see this bug while it was in the wrong category. Please: 1. Tell us if the problem is still happening with the latest system updates. 2. Take a photo or screenshot of the problem. 3. Run this command: dpkg -l > allpackages.txt and send us the resulting file 'allpackages.txt'. 4. Run this command: journalctl > journal.txt and send us the resulting file 'journal.txt'. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766827 Title: Missing icons on the status bar (top bar) Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: Ubuntu 18 LTS / 64 Missing icons in the top bar (status bar) for Dropbox, Mega, Skype, Classic menu indicator etc after update. Language, Wifi, Sound are there no problem with them. I searched for a solution, but find only 2 that doesn't work. There is a temporary solution here https://gist.github.com/molotovbliss/67c54e628c55c48891fd322983c2011a But after the last update it stopped working too. Regards, Rumen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 25 11:31:39 2018 ExecutablePath: /usr/bin/nautilus-desktop GsettingsChanges: b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-03-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=bg_BG.UTF-8 SHELL=/bin/bash 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/gnome-shell/+bug/1766827/+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 1774957] Re: Network icons in status menu disappearing
Sasa, That doesn't sound right. I thought the fix for this bug was already in Ubuntu 18.10. Can you please check again what version of the 'gnome- shell' package you have installed and also attach a screenshot of what you see? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774957 Title: Network icons in status menu disappearing Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 --- Ever since the update to Ubuntu 18.04 I'm having issues with the status menu at the top right of the screen. Normally you'd have a wired network connection icon displayed at the top without opening the menu. In my case it is not displayed half of the time. In the menu list no icon nor label is displayed for the wired connection menu item. When talking about half of the time it means that I can randomly make it display again when removing the USB network adapter and reconnecting it e.g. This does not work reliably though. When connecting to a VPN, normally you'd get an additional icon at the top. This is not the case any more, nor does the switch behind an activated VPN turns change to an active state. The result is that you can activate a VPN using the switch, but you can verify that it is activated, nor can you de-active the VPN through the menu. This does change in settings though. Wireless settings are no longer displayed in the menu at all. So no way to activate it or connect to a specific network. I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as network-manager-gnome, to no avail. Attached you'll find a screenshot illustrating the issue. You'll see two icons missing to the left of the volume icon, as well as the wireless menu missing completely and no icon and text label for the wired connection menu item. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 4 10:47:05 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (604 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+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 1808075] Re: Backport Unicode/Emoji 11 updates
** Description changed: Impact == Once a year, there is a new Unicode and Emoji release. 2018's release is Unicode 11. Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are able to display the new combinations introduced in Unicode 11 such as red-haired people. Test Case = Copy and paste the red-hair man 聆 into gedit. It should show as a single character. Regression Potential Although the code was written several weeks ago, it was only released in pango 1.43 (a development release) today so it's not seen many users yet. On the other hand, pango does have a test suite run during the build and as autopkgtest and those tests still pass. I haven't seen any issues yet and we'll work to fix any issues that do develop. A significant portion of the change set comes from the Unicode data sets and from the Chromium Unicode/Emoji parser. Both of those parts have received wider testing and use over several months. Other Info == - GTK's "Insert Emoji" feature will need to be updated to offer these new emoji. + This issue is easy to fix with Ubuntu 18.10 but it may not be practical to try to update Ubuntu 18.04 LTS for this feature. + + GTK's "Insert Emoji" feature will need to be updated to offer these new + emoji. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808075 Title: Backport Unicode/Emoji 11 updates Status in pango1.0 package in Ubuntu: Fix Committed Status in pango1.0 source package in Cosmic: Triaged Bug description: Impact == Once a year, there is a new Unicode and Emoji release. 2018's release is Unicode 11. Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are able to display the new combinations introduced in Unicode 11 such as red-haired people. Test Case = Copy and paste the red-hair man 聆 into gedit. It should show as a single character. Regression Potential Although the code was written several weeks ago, it was only released in pango 1.43 (a development release) today so it's not seen many users yet. On the other hand, pango does have a test suite run during the build and as autopkgtest and those tests still pass. I haven't seen any issues yet and we'll work to fix any issues that do develop. A significant portion of the change set comes from the Unicode data sets and from the Chromium Unicode/Emoji parser. Both of those parts have received wider testing and use over several months. Other Info == This issue is easy to fix with Ubuntu 18.10 but it may not be practical to try to update Ubuntu 18.04 LTS for this feature. GTK's "Insert Emoji" feature will need to be updated to offer these new emoji. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
This bug is closed so please open a new bug if you have any problems at all. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+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 1808075] [NEW] Backport Unicode/Emoji 11 updates
Public bug reported: Impact == Once a year, there is a new Unicode and Emoji release. 2018's release is Unicode 11. Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are able to display the new combinations introduced in Unicode 11 such as red-haired people. Test Case = Copy and paste the red-hair man 聆 into gedit. It should show as a single character. Regression Potential Although the code was written several weeks ago, it was only released in pango 1.43 (a development release) today so it's not seen many users yet. On the other hand, pango does have a test suite run during the build and as autopkgtest and those tests still pass. I haven't seen any issues yet and we'll work to fix any issues that do develop. A significant portion of the change set comes from the Unicode data sets and from the Chromium Unicode/Emoji parser. Both of those parts have received wider testing and use over several months. Other Info == GTK's "Insert Emoji" feature will need to be updated to offer these new emoji. ** Affects: pango1.0 (Ubuntu) Importance: Low Status: Fix Committed ** Affects: pango1.0 (Ubuntu Cosmic) Importance: Low Assignee: Jeremy Bicha (jbicha) Status: Triaged ** Tags: bionic cosmic ** Also affects: pango1.0 (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: pango1.0 (Ubuntu Cosmic) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: pango1.0 (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: pango1.0 (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808075 Title: Backport Unicode/Emoji 11 updates Status in pango1.0 package in Ubuntu: Fix Committed Status in pango1.0 source package in Cosmic: Triaged Bug description: Impact == Once a year, there is a new Unicode and Emoji release. 2018's release is Unicode 11. Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are able to display the new combinations introduced in Unicode 11 such as red-haired people. Test Case = Copy and paste the red-hair man 聆 into gedit. It should show as a single character. Regression Potential Although the code was written several weeks ago, it was only released in pango 1.43 (a development release) today so it's not seen many users yet. On the other hand, pango does have a test suite run during the build and as autopkgtest and those tests still pass. I haven't seen any issues yet and we'll work to fix any issues that do develop. A significant portion of the change set comes from the Unicode data sets and from the Chromium Unicode/Emoji parser. Both of those parts have received wider testing and use over several months. Other Info == GTK's "Insert Emoji" feature will need to be updated to offer these new emoji. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+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 1807076] Re: gnome-control-center doesn't start
Ok, I have tried again on the new account but I couldn't reproduce it again following the steps above. I have done a lot of other system configuration at the time it had happened to me, it might be tricky to get to this state again. -- 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/1807076 Title: gnome-control-center doesn't start Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control-center doesn't start. There is no crash, core dump, etc. This bit in syslog (/var/log/syslog) gives us some information: gnome-control-c[2962]: invalid unclassed pointer in cast to 'GtkWindow' gnome-control-c[2962]: gtk_window_present_with_time: assertion 'GTK_IS_WINDOW (window)' failed Actually something similar has been seen already in the past but it hasn't been resolved: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1745846 I might not be the only person affected: https://askubuntu.com/questions/1094442/gnome-control-center- disappears-on-ubuntu-18-10-after-repostioning-ubuntu- dock/1098815#1098815 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Dec 6 11:08:42 2018 InstallationDate: Installed on 2018-11-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1807076/+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 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
This bug was fixed in the package gnome-desktop3 - 3.30.2-3ubuntu1 --- gnome-desktop3 (3.30.2-3ubuntu1) disco; urgency=medium * Merge with Debian. Remaining changes: - Add 04_compute_average_color.patch: Compute the avergage color in gnome-desktop itself, not in unity to fix some races (LP #963140) - Add tweak_color_computation.patch, Patch from Gord, no patch header, no bug link. - Add git_revert_draw_background.patch - Add ubuntu_language.patch, Port relevant bits from gnome-control-center's 52_region_language.patch, as required for gnome 3.8+ region panel - Add ubuntu_language_list_from_SUPPORTED.patch, Add API to get list of available languages from SUPPORTED file. To be used by gnome 3.8 region panel language installation. - Add gnomebg_hidpi_image.patch, gnome_bg_create_surface: always honor device scale, that fixes the wallpaper rendering in HiDPI config under ubiquity (LP: #1382291) - debian/control.in: Don't depend on bubblewrap - debian/libgnome-desktop-3-17.symbols: + Add symbols included in Ubuntu patches - Update Vcs fields and debian/gbp.conf for Ubuntu gnome-desktop3 (3.30.2-3) unstable; urgency=medium * Cherry-pick thumbnail-Fix-use-after-free-when-getting-a-preview-icon.patch: - Fix from gnome-3-30 branch for a potential crash bug gnome-desktop3 (3.30.2-2) unstable; urgency=medium * Cherry-pick thumbnail-Handle-non-usrmerged-systems.patch: - Fix thumbnailer on 32-bit systems where /lib64 is not available. Also improve handling of usrmerged and non-usrmerged systems. (LP: #1807127) -- Jeremy Bicha Tue, 11 Dec 2018 10:45:20 -0500 ** Changed in: gnome-desktop3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Confirmed Status in gnome-desktop3 source package in Cosmic: In Progress Bug description: Impact == Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs. Test Case = Install Ubuntu 18.10 32-bit Install the update. Log out and log back in. Download a picture from the internet. Open your file browser to the directory that contains the picture. The file should show a thumbnail preview. Regression Potential This fix was cherry-picked to the stable gnome-3-30 branch. It was additionally tested by Iain Lane on usrmerged and non-usrmerged systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.) Other Info == Triaged as Critical for 18.04 LTS since this was a regression introduced in the security update that backported the bubblewrap hardening to the gnome-desktop3 thumbnailer. Original Bug Report === Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+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 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
For bionic, I've uploaded the gnome-desktop3 package with the fix for 32bit systems to the ubuntu-security-proposed ppa (https://launchpad.net /~ubuntu-security-proposed/+archive/ubuntu/ppa/) for people to test. Any feedback would be appreciated. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Confirmed Status in gnome-desktop3 source package in Cosmic: In Progress Bug description: Impact == Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs. Test Case = Install Ubuntu 18.10 32-bit Install the update. Log out and log back in. Download a picture from the internet. Open your file browser to the directory that contains the picture. The file should show a thumbnail preview. Regression Potential This fix was cherry-picked to the stable gnome-3-30 branch. It was additionally tested by Iain Lane on usrmerged and non-usrmerged systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.) Other Info == Triaged as Critical for 18.04 LTS since this was a regression introduced in the security update that backported the bubblewrap hardening to the gnome-desktop3 thumbnailer. Original Bug Report === Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Hello Daniel, or anyone else affected, Accepted gnome-shell into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.28.3-0ubuntu0.18.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 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: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1796238] Re: [SRU][regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript()
This bug was fixed in the package gjs - 1.54.3-1~ubuntu18.10.1 --- gjs (1.54.3-1~ubuntu18.10.1) cosmic; urgency=medium * No-change SRU backport from unstable / disco to cosmic (LP: #1804641) * Also fixes crash on `gnome-shell --replace' (LP: #1796238) gjs (1.54.3-1) unstable; urgency=medium * Team upload * New upstream release * Force time zone to UTC when running tests. This hopefully fixes FTBFS in the pathological time zone used to test reproducible builds. gjs (1.54.2-1) unstable; urgency=medium * Team upload * Upload to unstable (starts transition: #906016) * d/watch: Only watch for versions from a stable branch * New upstream release * Bump Standards-Version to 4.2.1 (no changes required) * Use dpkg's default.mk to get upstream version number for dependencies. This avoids relying on the differently-named variables in gnome-get-source.mk, and also does the right thing if gjs ever gains an epoch. * d/rules: Remove gnome-get-source.mk (please use uscan instead) -- Iain Lane Thu, 22 Nov 2018 12:21:13 + ** Changed in: gjs (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796238 Title: [SRU][regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() Status in gjs package in Ubuntu: Fix Released Status in mozjs60 package in Ubuntu: Invalid Status in gjs source package in Cosmic: Fix Released Status in mozjs60 source package in Cosmic: Invalid Bug description: [Impact] gnome-shell crashes on shutdown and on `gnome-shell --replace`. A proper fix for `gnome-shell --replace` requires mutter 3.30.2-1 too. [Test Case] Given https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test this fix, but the SRU will be more generally verified by the testing outlined in bug #1804641. [Regression Potential] The new stable version of gjs includes changes to fix random crashes when a gjs application is closed. Possible regressions are leaks and other crashes but none has been observed until now. [Original Bug] https://errors.ubuntu.com/problem/f64145b51a9d0fd20bfff57836b8f743e56c50ba https://gitlab.gnome.org/GNOME/gjs/issues/212 --- mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52 which was still the latest yesterday) Steps to reproduce: 1. Start gnome-shell (master) 2. Super+A to show applications 3. Alt+F2 and type "debugexit" to exit cleanly. Backtrace: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 161 ./js/src/vm/JSContext.h: No such file or directory. [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))] (gdb) bt #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 #1 0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834 #2 0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418 #3 0x7f3bf403f0d1 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x55d07921beb0, args=..., construct=) at ./js/src/vm/Interpreter.cpp:490 #4 0x7f3bf403f339 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle) (cx=cx@entry=0x55d07921beb0, fval=..., fval@entry=..., thisv=..., thisv@entry=..., args=..., rval=...) at ./js/src/vm/Interpreter.cpp:536 #5 0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, JS::Handle, JS::Handle, JS::HandleValueArray const&, JS::MutableHandle) (cx=0x55d07921beb0, obj=..., fval=..., args=..., rval=...) at ./debian/build/dist/include/js/RootingAPI.h:1128 #6 0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0 #7 0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0 #8 0x7f3bf7625573 in () at /usr/lib/libgjs.so.0 #9 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f3bf7f788f3 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f3bf7f81882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f3bf7f81ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0) at clutter-actor.c:5932 #14 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-widget.c:354 #15 0x7f3bf7025d48 in
[Desktop-packages] [Bug 1804641] Update Released
The verification of the Stable Release Update for gjs has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1804641 Title: [SRU] 1.54.3 Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Cosmic: Fix Released Bug description: Description --- Update cosmic from 1.54.1 to 1.54.3. This will be a no-change backport from disco. There are some changes in debian/, but I think they should be OK. NEWS. The upstream changes are covered by https://wiki.ubuntu.com/StableReleaseUpdates/GNOME: Version 1.54.3 -- - Closed bugs and merge requests: * object: Fix write-only properties [!246, Philip Chimento] * SIGSEGV when exiting gnome-shell [#212, !247, Andrea Azzarone] * SelectionData.get_targets crashes with "Unable to resize vector" [#201, !241, Philip Chimento] * Gnome-shell crashes on destroying cached param specs [#213, !240, Marco Trevisan] * GType memleak fixes [!244, Marco Trevisan] * Fix build with --enable-dtrace and create CI job to ensure it doesn't break in the future [#196, !253, Philip Chimento] Version 1.54.2 -- - Closed bugs and merge requests: * context: Defer and therefore batch forced GC runs [performance] [!236, Daniel van Vugt] * context: use timeout with seconds to schedule a gc trigger [!239, Marco Trevisan] * fundamental: Check if gtype is valid before using it [!242, Georges Basile Stavracas Neto] - Backported a fix for a crash in the interactive interpreter when executing something like `throw "foo"` [Philip Chimento] - Backported various maintenance from 3.31 [Philip Chimento] Test Case - GNOME Shell is written in gjs so let's test GNOME Shell. After installing the update, reboot. Also check some of these apps: gnome-characters gnome-documents gnome-maps gnome-sound-recorder gnome-sushi gnome-weather polari All of them except for gnome-sound-recorder and polari are included in Ubuntu GNOME and Ubuntu Budgie. Regression Potential Well if gjs has a problem, it could leave Ubuntu GNOME users unable to log in to their computer at all since gdm uses part of gnome-shell to work. But I did test build, install and reboot before uploading this update to Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1804641/+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 1796238] Update Released
The verification of the Stable Release Update for gjs has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796238 Title: [SRU][regression] mozjs60 crashes with SIGSEGV on gnome-shell exit, in GetPropertyOperation() from Interpret() from js::RunScript() Status in gjs package in Ubuntu: Fix Released Status in mozjs60 package in Ubuntu: Invalid Status in gjs source package in Cosmic: Fix Released Status in mozjs60 source package in Cosmic: Invalid Bug description: [Impact] gnome-shell crashes on shutdown and on `gnome-shell --replace`. A proper fix for `gnome-shell --replace` requires mutter 3.30.2-1 too. [Test Case] Given https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test this fix, but the SRU will be more generally verified by the testing outlined in bug #1804641. [Regression Potential] The new stable version of gjs includes changes to fix random crashes when a gjs application is closed. Possible regressions are leaks and other crashes but none has been observed until now. [Original Bug] https://errors.ubuntu.com/problem/f64145b51a9d0fd20bfff57836b8f743e56c50ba https://gitlab.gnome.org/GNOME/gjs/issues/212 --- mozjs60 crashes on gnome-shell exit (didn't happen with mozjs52 which was still the latest yesterday) Steps to reproduce: 1. Start gnome-shell (master) 2. Super+A to show applications 3. Alt+F2 and type "debugexit" to exit cleanly. Backtrace: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 161 ./js/src/vm/JSContext.h: No such file or directory. [Current thread is 1 (Thread 0x7f3bebd2e340 (LWP 4269))] (gdb) bt #0 0x7f3bf4033a4e in GetPropertyOperation (vp=..., lval=..., pc=, script=..., fp=, cx=) at ./js/src/vm/JSContext.h:161 #1 0x7f3bf4033a4e in Interpret(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:2834 #2 0x7f3bf403eb06 in js::RunScript(JSContext*, js::RunState&) (cx=0x55d07921beb0, state=...) at ./js/src/vm/Interpreter.cpp:418 #3 0x7f3bf403f0d1 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x55d07921beb0, args=..., construct=) at ./js/src/vm/Interpreter.cpp:490 #4 0x7f3bf403f339 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle) (cx=cx@entry=0x55d07921beb0, fval=..., fval@entry=..., thisv=..., thisv@entry=..., args=..., rval=...) at ./js/src/vm/Interpreter.cpp:536 #5 0x7f3bf4372b81 in JS_CallFunctionValue(JSContext*, JS::Handle, JS::Handle, JS::HandleValueArray const&, JS::MutableHandle) (cx=0x55d07921beb0, obj=..., fval=..., args=..., rval=...) at ./debian/build/dist/include/js/RootingAPI.h:1128 #6 0x7f3bf7631310 in gjs_call_function_value () at /usr/lib/libgjs.so.0 #7 0x7f3bf76045d5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0 #8 0x7f3bf7625573 in () at /usr/lib/libgjs.so.0 #9 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7f3bf7f788f3 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7f3bf7f81882 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7f3bf7f81ecf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7f3bf74a9c33 in clutter_actor_dispose (object=0x55d0795aa5c0) at clutter-actor.c:5932 #14 0x7f3bf70529b4 in st_widget_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-widget.c:354 #15 0x7f3bf7025d48 in st_bin_dispose (gobject=0x55d0795aa5c0) at ../src/st/st-bin.c:188 #16 0x7f3bf7f6c448 in g_object_run_dispose () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #17 0x7f3bf749d023 in clutter_actor_destroy (self=0x55d0795aa5c0) at clutter-actor.c:8615 #18 0x7f3bf74a4404 in clutter_actor_iter_destroy (iter=0x7fff3285e4e0) at clutter-actor.c:19002 #19 0x7f3bf74a44b8 in clutter_actor_real_destroy (actor=0x55d0795a9ba0) at clutter-actor.c:6264 #20 0x7f3bf7f65b6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7f3bf7f78c4a in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7f3bf7f81882 in
[Desktop-packages] [Bug 1804641] Re: [SRU] 1.54.3
This bug was fixed in the package gjs - 1.54.3-1~ubuntu18.10.1 --- gjs (1.54.3-1~ubuntu18.10.1) cosmic; urgency=medium * No-change SRU backport from unstable / disco to cosmic (LP: #1804641) * Also fixes crash on `gnome-shell --replace' (LP: #1796238) gjs (1.54.3-1) unstable; urgency=medium * Team upload * New upstream release * Force time zone to UTC when running tests. This hopefully fixes FTBFS in the pathological time zone used to test reproducible builds. gjs (1.54.2-1) unstable; urgency=medium * Team upload * Upload to unstable (starts transition: #906016) * d/watch: Only watch for versions from a stable branch * New upstream release * Bump Standards-Version to 4.2.1 (no changes required) * Use dpkg's default.mk to get upstream version number for dependencies. This avoids relying on the differently-named variables in gnome-get-source.mk, and also does the right thing if gjs ever gains an epoch. * d/rules: Remove gnome-get-source.mk (please use uscan instead) -- Iain Lane Thu, 22 Nov 2018 12:21:13 + ** Changed in: gjs (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1804641 Title: [SRU] 1.54.3 Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Cosmic: Fix Released Bug description: Description --- Update cosmic from 1.54.1 to 1.54.3. This will be a no-change backport from disco. There are some changes in debian/, but I think they should be OK. NEWS. The upstream changes are covered by https://wiki.ubuntu.com/StableReleaseUpdates/GNOME: Version 1.54.3 -- - Closed bugs and merge requests: * object: Fix write-only properties [!246, Philip Chimento] * SIGSEGV when exiting gnome-shell [#212, !247, Andrea Azzarone] * SelectionData.get_targets crashes with "Unable to resize vector" [#201, !241, Philip Chimento] * Gnome-shell crashes on destroying cached param specs [#213, !240, Marco Trevisan] * GType memleak fixes [!244, Marco Trevisan] * Fix build with --enable-dtrace and create CI job to ensure it doesn't break in the future [#196, !253, Philip Chimento] Version 1.54.2 -- - Closed bugs and merge requests: * context: Defer and therefore batch forced GC runs [performance] [!236, Daniel van Vugt] * context: use timeout with seconds to schedule a gc trigger [!239, Marco Trevisan] * fundamental: Check if gtype is valid before using it [!242, Georges Basile Stavracas Neto] - Backported a fix for a crash in the interactive interpreter when executing something like `throw "foo"` [Philip Chimento] - Backported various maintenance from 3.31 [Philip Chimento] Test Case - GNOME Shell is written in gjs so let's test GNOME Shell. After installing the update, reboot. Also check some of these apps: gnome-characters gnome-documents gnome-maps gnome-sound-recorder gnome-sushi gnome-weather polari All of them except for gnome-sound-recorder and polari are included in Ubuntu GNOME and Ubuntu Budgie. Regression Potential Well if gjs has a problem, it could leave Ubuntu GNOME users unable to log in to their computer at all since gdm uses part of gnome-shell to work. But I did test build, install and reboot before uploading this update to Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1804641/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Hello, For the record I reproduce this bug on a fresh new install of Ubuntu 18.10. As it sounds like a 7-months-old critical security bug, I'm very interested in a reliable workaround. Should I remove gnome-shell-extension-ubuntu-dock, and install upstream Dash to dock from https://extensions.gnome.org/extension/307/dash-to- dock/ ? (I already had to remove gnome-shell-extension-appindicator to install the 'almost' bug free upstream app-indicator) Thanks for your help ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1702873] Re: [snap] artifacts when using HiDPI display
Can someone with a HiDPI display please try to reproduce this bug with revision 96 or later? This bug is quite old and we have since made great improvements in regard to theme integration which includes cursor themes. It's possible the snap is still not getting the proper scale, but I would like to confirm before digging in to much. -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
This bug affected me, but got past it by adding "nouveau.modeset=0" after the text "quiet splash" in the bootparameters for Ubuntu in the grub menu. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Sebastien, could you explain the 'status: Triaged → Won't Fix' meaning? Is this bug going to stay with us or what? -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Me to. Would love to be able to use my HDMI monitor: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.06*+ 60.0159.9759.9659.9340.04 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98
[Desktop-packages] [Bug 1807504] Re: Evince segfaults when opening PDF
Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1807504 Title: Evince segfaults when opening PDF Status in poppler package in Ubuntu: Fix Released Bug description: After a recent poppler update neither Evince nor Qpdfview will open pdf files that opened before the update. These files open properly using gv (which uses Ghostview instead of poppler). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpoppler73 0.62.0-2ubuntu2.4 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Sat Dec 8 08:48:01 2018 InstallationDate: Installed on 2016-08-25 (834 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: poppler UpgradeStatus: Upgraded to bionic on 2018-08-14 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1807504/+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 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package gnome-desktop3 - 3.8.4-0ubuntu3.3 --- gnome-desktop3 (3.8.4-0ubuntu3.3) trusty; urgency=medium * libgnome-desktop/display-name.c - some vendors encode the screen ratio (e.g 16/9) in the EDID instead of including the screen size, detect those cases and display the product name instead of the screen diagonal. (lp: #1755490) -- Dariusz Gadomski Fri, 30 Nov 2018 08:27:43 +0100 ** Changed in: gnome-desktop3 (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: hwdata (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Released Status in hwdata source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+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 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package hwdata - 0.249-1ubuntu1 --- hwdata (0.249-1ubuntu1) trusty; urgency=medium * Change PNP vendor name for GSM to LG Electronics (LP: #1755490) -- Dariusz Gadomski Thu, 29 Nov 2018 17:17:30 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Released Status in hwdata source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+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 1807761] Re: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi
Thanks for idea, but on launch gdebi is shown in `htop` as /usr/bin/python3 /usr/bin/gdebi-gtk /home/user/Desktop/meld_3.18.0-6_all.deb then it closes after clicking on *Install package* button. I do not know how to debug this deeper. ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- 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/1807761 Title: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi Status in gdebi package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 18.04 LTS or Ubuntu 18.10 2. Download some deb-file to the desktop - for with help of terminal: cd ~/Desktop apt-get download meld 3. Install GDebi package installer with sudo apt install gdebi 4. Select deb-file on desktop, make right click on it, select *Open With Other Application* select *GDebi Package Installer*, click *Select*, in opened window select *Install Package* Expected results: * GDebi asks user (sudo-able) password and installs the package Actual results: * GDebi do not ask user for password and do not install the package Notes: * first seen on AskUbuntu ( https://askubuntu.com/q/1099387/66509 ) * you can view my screencast to get first person view :) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 10 23:14:16 2018 GsettingsChanges: 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/gdebi/+bug/1807761/+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 1804576] Proposed package upload rejected
An upload of cups to xenial-proposed has been rejected from the upload queue for the following reason: "This SRU was shadowed by a security update of cups in xenial. Please reupload these changes on top of that update.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1803059] Re: Nullpointer dereference
Thank you, the bug is fixed for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1803059 Title: Nullpointer dereference Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Bionic: Fix Released Status in poppler source package in Cosmic: Fix Released Bug description: * Impact Evince segfaults on some pdf documents * Test case Download and try to open https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't segfault * Regression potential Nothing special to test, make sure evince still opens pdfs without issue - System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Evince version: GNOME Document Viewer 3.28.4 While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04 LTS), a null-pointer dereference was observed, initially this was reported to evince but the evince team advised that the issue is in poppler, the library used by evince to render PDF, poppler version: 0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the issue is already fixed in poppler 0.70, but this will still crash your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70. Fuzzing result showing a very important vulnerability in a package currently shipped by a major Linux distribution is still of interest, even if that Linux distribution does not package the latest released upstream version. I think Ubuntu is still using, Source: poppler Version: 0.62.0-2ubuntu2.2 So, most of the systems will be affected to this issue. Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1804576] Proposed package upload rejected
An upload of cups to bionic-proposed has been rejected from the upload queue for the following reason: "This SRU was shadowed by a security update of cups in cosmic. Please reupload these changes on top of that update.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1781597] Re: [SRU] WoWLAN settings are not supported
Hello Alfonso, or anyone else affected, Accepted network-manager into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.12.4-1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: [Impact] - WoWLAN lets us wake up the system by sending wake packages over the wifi + WoWLAN lets us wake up the system by sending wake packets over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: - * wake up on magic packet + * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. ** Changed in: network-manager (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Committed Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to
[Desktop-packages] [Bug 1067434] Re: Sound output device keeps changing when using headphones
I really dont want to leave a headphone connected at all times in my desktop computer so I tried more things and this seems to have fixed the issue: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/comments/31 To restart pulseaudio, either reboot your computer or run "pulseaudio -k" More references: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535 https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084 https://askubuntu.com/questions/69001/volume-blinking-up-and-down-rapidly-on-gnome-shell https://ubuntuforums.org/showthread.php?t=2132324=2=48b8508c3653cf0dfc724cbd533eba52 https://forums.linuxmint.com/viewtopic.php?t=157635 -- 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/1067434 Title: Sound output device keeps changing when using headphones Status in alsa-driver package in Ubuntu: Expired Bug description: Recently upgraded to 12.10. Having issues with sound when using headphones plugged into the front ports. Something that doesn't happen when booting to windows - so fairly confident it's an Ubuntu issue. When listening to any sound, music, video etc the sound levels jump up and down and click. If I open "sound" from the settings menu when playing videos or music and viewing the "output" tab I can see "headphone - built-in audio disappear and reappear (very quickly) so I'm guessing the system is jumping back to the "analogue output" and back again which is why the sound volume changes and clicks. Worth noting I never used my headphones when 12.04 was installed so not sure if it's this OS or Ubuntu hates my hardware generally. Booted from live cd (usb) to 12.04 and there wasnt any issue. Anyone seen this before? any advice? Sound is built in to motherboard. I have the Gigabyte GA-X58A-UD5. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Tue Oct 16 18:07:44 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-09-29 (17 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1067434/+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 related refs are not installed when using GNOME Software on Ubuntu 18.04
** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Released => Triaged ** Tags removed: verification-done-bionic -- 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 related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Triaged Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) 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 1802586] Re: sane-backends library name issues
Debian only had libsane1 in Unstable so Debian's situation is not as serious as Ubuntu's. -- 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/1802586 Title: sane-backends library name issues Status in sane-backends package in Ubuntu: New Bug description: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+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 1804576] Proposed package upload rejected
An upload of cups to cosmic-proposed has been rejected from the upload queue for the following reason: "This SRU was shadowed by a security update of cups in cosmic. Please reupload these changes on top of that update.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1789356] Re: The wrong background flashes up briefly during the login animation since Yaru was introduced
I gather from Daniel's testing that this makes things worse for users of Cosmic. If that is correct, even if a fix for mutter is coming, I don't think releasing gnome-shell to -updates is the right idea. ** Changed in: gnome-shell (Ubuntu Cosmic) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789356 Title: The wrong background flashes up briefly during the login animation since Yaru was introduced Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Incomplete Status in mutter source package in Cosmic: Triaged Bug description: [Impact] The wrong background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+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 1802586] Re: sane-backends library name issues
It's been blocked in disco-proposed for 32 days. This package is in testing. Why hasn't the sky fallen in in Debian? -- 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/1802586 Title: sane-backends library name issues Status in sane-backends package in Ubuntu: New Bug description: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+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 1808002] Re: Gnome shell is consuming high cpu usage
** Description changed: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome - consuming high cpu usage (min 30%). I dont have any extensions enabled + consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1808002 Title: Gnome shell is consuming high cpu usage Status in gnome-shell package in Ubuntu: New Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 50%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 1795991] Re: Difficulty setting up multimonitor with fractional scaling
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795991 Title: Difficulty setting up multimonitor with fractional scaling Status in mutter package in Ubuntu: Confirmed Bug description: I've enabled fractional scaling and set my laptop's 3840x2160 screen to 175% scaling. Upon plugging in an external 1920x1080 monitor, my laptop's screen resets to 200% scaling, and the external screen is set to 100%, to the right of my laptop's screen. If I try to set the laptop screen back to 175%, the Displays panel does not allow me to Apply, and journalctl outputs: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjecent Putting the external screen on the left or top of the laptop screen allows Apply to work (bottom or right does not work), but immediately reverts to the auto-set settings (200% laptop with 100% external on the right) and then clicking "revert" on the "revert or keep" dialog sets things to the requested scale factor and position (175% laptop with 100% external on the top/left). I've also seen the settings randomly reset to 200% laptop with 100% external on the right upon doing things like clicking reply in evolution to open up a new compose window. That's a bit long winded, so here's a shorter rundown of bugs description: 1) Upon connecting an external screen, the laptop screen scaling changes 2) Can't set external screen to the bottom or right of laptop screen with fractional scaling 3) Upon Application, the requested settings are reverted, and then reverting the reversion applies them, while "keeping" the change reverts 4) Certain random actions appear to reset to the undesired settings ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.0-4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 3 15:17:03 2018 InstallationDate: Installed on 2018-09-26 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-09-28 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795991/+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 1781597] Re: [SRU] WoWLAN settings are not supported
This bug was fixed in the package network-manager - 1.12.6-0ubuntu2 --- network-manager (1.12.6-0ubuntu2) disco; urgency=medium [ Robie Basak ] * debian/tests: - Make dep8 nm test directly invokable -- Sebastien Bacher Mon, 10 Dec 2018 22:03:01 +0100 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- 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/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packages over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1802586] Re: sane-backends library name issues
No, see LP: #1804550 I believe we need to add a transitional package for the update to work smoothly. I haven't worked on this yet because I wanted to take the time to test the situation with and without a proposed transitional package and honestly, it didn't look to me like a very high priority yet. -- 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/1802586 Title: sane-backends library name issues Status in sane-backends package in Ubuntu: New Bug description: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+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 1803059] Re: Nullpointer dereference
Fix released for trusty, bionic, xenial and cosmic https://usn.ubuntu.com/3837-2/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1803059 Title: Nullpointer dereference Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Bionic: Fix Released Status in poppler source package in Cosmic: Fix Released Bug description: * Impact Evince segfaults on some pdf documents * Test case Download and try to open https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't segfault * Regression potential Nothing special to test, make sure evince still opens pdfs without issue - System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Evince version: GNOME Document Viewer 3.28.4 While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04 LTS), a null-pointer dereference was observed, initially this was reported to evince but the evince team advised that the issue is in poppler, the library used by evince to render PDF, poppler version: 0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the issue is already fixed in poppler 0.70, but this will still crash your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70. Fuzzing result showing a very important vulnerability in a package currently shipped by a major Linux distribution is still of interest, even if that Linux distribution does not package the latest released upstream version. I think Ubuntu is still using, Source: poppler Version: 0.62.0-2ubuntu2.2 So, most of the systems will be affected to this issue. Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1807504] Re: Evince segfaults when opening PDF
Fix released for trusty, bionic, xenial and cosmic https://usn.ubuntu.com/3837-2/ ** Changed in: poppler (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1807504 Title: Evince segfaults when opening PDF Status in poppler package in Ubuntu: Fix Released Bug description: After a recent poppler update neither Evince nor Qpdfview will open pdf files that opened before the update. These files open properly using gv (which uses Ghostview instead of poppler). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpoppler73 0.62.0-2ubuntu2.4 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Sat Dec 8 08:48:01 2018 InstallationDate: Installed on 2016-08-25 (834 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: poppler UpgradeStatus: Upgraded to bionic on 2018-08-14 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1807504/+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 1808002] [NEW] Gnome shell is consuming high cpu usage
Public bug reported: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 30%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1808002 Title: Gnome shell is consuming high cpu usage Status in gnome-shell package in Ubuntu: New Bug description: Today, I have installed the ubuntu 18.10 and now gnome-shell and chrome consuming high cpu usage (min 30%). I dont have any extensions enabled in chrome (Version 71.0) and opened only 5 tabs. No other applications are running in the system. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 22:55:00 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808002/+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 related refs are not installed when using GNOME Software on Ubuntu 18.04
Was this issue really fixed? I thought the patches were reverted. -- 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 related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) 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 1803142] Please test proposed package
Hello Olivier, or anyone else affected, Accepted libreoffice-l10n into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libreoffice-l10n/1:6.1.3-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1803142 Title: [SRU] libreoffice 6.1.3 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: [Impact] * LibreOffice 6.1.3 is the third bugfix release of the fresh 6.1 line. Version 6.1.2 is currently in cosmic. For a list of fixed bugs compared to 6.1.2 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.3/RC2#List_of_fixed_bugs (that's a total of 66 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 66 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803142/+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 1803142] Re: [SRU] libreoffice 6.1.3 for cosmic
Hello Olivier, or anyone else affected, Accepted libreoffice into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:6.1.3-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: libreoffice-l10n (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1803142 Title: [SRU] libreoffice 6.1.3 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: [Impact] * LibreOffice 6.1.3 is the third bugfix release of the fresh 6.1 line. Version 6.1.2 is currently in cosmic. For a list of fixed bugs compared to 6.1.2 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.3/RC2#List_of_fixed_bugs (that's a total of 66 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 66 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803142/+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 1802586] Re: sane-backends library name issues
As far as I can see the Debian bugs are all closed - looks like the maintainer isn't pushing on this further. Can we close this bug and let 1.0.27-3.1 migrate? -- 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/1802586 Title: sane-backends library name issues Status in sane-backends package in Ubuntu: New Bug description: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+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 1807997] Re: xorg crashed
_usr_bin_lxqt-globalkeysd.1000.crash ** Attachment added: "_usr_bin_lxqt-globalkeysd.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1807997/+attachment/5221408/+files/_usr_bin_lxqt-globalkeysd.1000.crash -- 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/1807997 Title: xorg crashed Status in xorg package in Ubuntu: New Bug description: ubuntu-bug didn't open a web browser after it uploaded the crash file. I was using firefox and everything crashed. -rw-r- 1 rjl whoopsie 1506299 Dec 11 11:34 _usr_bin_lxqt-globalkeysd.1000.crash -rw-r- 1 root whoopsie 6502766 Dec 11 11:41 _usr_lib_xorg_Xorg.0.crash This was in dmesg: [ 941.428542] do_general_protection: 11 callbacks suppressed [ 941.428547] traps: lxqt-globalkeys[1437] general protection ip:7f816ac0c3f7 sp:7fff95cd7cb0 error:0 in libc-2.28.so[7f816abea000+171000] [ 941.511120] Chrome_~dThread[2865]: segfault at 0 ip 7facf7e58a4b sp 7facf2d26b00 error 6 in libxul.so[7facf7e44000+3e9a000] [ 941.511135] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d [ 941.511185] Chrome_~dThread[2805]: segfault at 0 ip 7f9f47a40a4b sp 7f9f4290eb00 error 6 [ 941.511187] 68 01 b0 [ 941.511192] in libxul.so[7f9f47a2c000+3e9a000] [ 941.511194] 04 [ 941.511196] Code: [ 941.511197] 48 89 [ 941.511199] fa 05 [ 941.511201] 08 [ 941.511203] 48 [ 941.511205] 04 [ 941.511206] 8d 15 [ 941.511208] 25 00 [ 941.511210] 1e 01 [ 941.511212] 00 00 [ 941.511214] b0 04 [ 941.511216] 00 00 [ 941.511218] 48 89 [ 941.511220] 00 00 [ 941.511222] 10 c7 [ 941.511224] 00 0f [ 941.511226] 04 25 [ 941.511228] 0b e8 [ 941.511230] 00 00 [ 941.511232] 4d f4 [ 941.511234] 00 00 [ 941.511236] ff ff [ 941.511238] 00 00 [ 941.511240] 48 8b [ 941.511242] 00 00 [ 941.511244] 05 e4 [ 941.511246] 0f 0b [ 941.511249] 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 [ 941.579142] Chrome_~dThread[3153]: segfault at 0 ip 7f11b0208a4b sp 7f11ab0d6b00 error 6 in libxul.so[7f11b01f4000+3e9a000] [ 941.579155] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1807997/+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 1807744] Re: Print to File writes to incorrect file
>I think the bug happens when the dialogue self-flips the type selector to 'Portable Document Format'. Yep ... if I manually flip the type selector to 'Portable Document Format' it loses my desired file name and pseudo-randomly selects a pdf file from the list of files in the folder. So there are actually 2 incorrect behaviours going on: 1) changing type selector to 'Portable Document Format' should not change the file name in the 'name' field IF the user has already made some edits in that field (i.e. has taken the trouble to choose a name) 2) pressing Enter (or Save button) should not trigger the type selector to change -- 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/1807744 Title: Print to File writes to incorrect file Status in libreoffice package in Ubuntu: New Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1807744/+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 1807997] [NEW] xorg crashed
Public bug reported: ubuntu-bug didn't open a web browser after it uploaded the crash file. I was using firefox and everything crashed. -rw-r- 1 rjl whoopsie 1506299 Dec 11 11:34 _usr_bin_lxqt-globalkeysd.1000.crash -rw-r- 1 root whoopsie 6502766 Dec 11 11:41 _usr_lib_xorg_Xorg.0.crash This was in dmesg: [ 941.428542] do_general_protection: 11 callbacks suppressed [ 941.428547] traps: lxqt-globalkeys[1437] general protection ip:7f816ac0c3f7 sp:7fff95cd7cb0 error:0 in libc-2.28.so[7f816abea000+171000] [ 941.511120] Chrome_~dThread[2865]: segfault at 0 ip 7facf7e58a4b sp 7facf2d26b00 error 6 in libxul.so[7facf7e44000+3e9a000] [ 941.511135] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d [ 941.511185] Chrome_~dThread[2805]: segfault at 0 ip 7f9f47a40a4b sp 7f9f4290eb00 error 6 [ 941.511187] 68 01 b0 [ 941.511192] in libxul.so[7f9f47a2c000+3e9a000] [ 941.511194] 04 [ 941.511196] Code: [ 941.511197] 48 89 [ 941.511199] fa 05 [ 941.511201] 08 [ 941.511203] 48 [ 941.511205] 04 [ 941.511206] 8d 15 [ 941.511208] 25 00 [ 941.511210] 1e 01 [ 941.511212] 00 00 [ 941.511214] b0 04 [ 941.511216] 00 00 [ 941.511218] 48 89 [ 941.511220] 00 00 [ 941.511222] 10 c7 [ 941.511224] 00 0f [ 941.511226] 04 25 [ 941.511228] 0b e8 [ 941.511230] 00 00 [ 941.511232] 4d f4 [ 941.511234] 00 00 [ 941.511236] ff ff [ 941.511238] 00 00 [ 941.511240] 48 8b [ 941.511242] 00 00 [ 941.511244] 05 e4 [ 941.511246] 0f 0b [ 941.511249] 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 [ 941.579142] Chrome_~dThread[3153]: segfault at 0 ip 7f11b0208a4b sp 7f11ab0d6b00 error 6 in libxul.so[7f11b01f4000+3e9a000] [ 941.579155] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_lib_xorg_Xorg.0.crash" https://bugs.launchpad.net/bugs/1807997/+attachment/5221407/+files/_usr_lib_xorg_Xorg.0.crash -- 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/1807997 Title: xorg crashed Status in xorg package in Ubuntu: New Bug description: ubuntu-bug didn't open a web browser after it uploaded the crash file. I was using firefox and everything crashed. -rw-r- 1 rjl whoopsie 1506299 Dec 11 11:34 _usr_bin_lxqt-globalkeysd.1000.crash -rw-r- 1 root whoopsie 6502766 Dec 11 11:41 _usr_lib_xorg_Xorg.0.crash This was in dmesg: [ 941.428542] do_general_protection: 11 callbacks suppressed [ 941.428547] traps: lxqt-globalkeys[1437] general protection ip:7f816ac0c3f7 sp:7fff95cd7cb0 error:0 in libc-2.28.so[7f816abea000+171000] [ 941.511120] Chrome_~dThread[2865]: segfault at 0 ip 7facf7e58a4b sp 7facf2d26b00 error 6 in libxul.so[7facf7e44000+3e9a000] [ 941.511135] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d [ 941.511185] Chrome_~dThread[2805]: segfault at 0 ip 7f9f47a40a4b sp 7f9f4290eb00 error 6 [ 941.511187] 68 01 b0 [ 941.511192] in libxul.so[7f9f47a2c000+3e9a000] [ 941.511194] 04 [ 941.511196] Code: [ 941.511197] 48 89 [ 941.511199] fa 05 [ 941.511201] 08 [ 941.511203] 48 [ 941.511205] 04 [ 941.511206] 8d 15 [ 941.511208] 25 00 [ 941.511210] 1e 01 [ 941.511212] 00 00 [ 941.511214] b0 04 [ 941.511216] 00 00 [ 941.511218] 48 89 [ 941.511220] 00 00 [ 941.511222] 10 c7 [ 941.511224] 00 0f [ 941.511226] 04 25 [ 941.511228] 0b e8 [ 941.511230] 00 00 [ 941.511232] 4d f4 [ 941.511234] 00 00 [ 941.511236] ff ff [ 941.511238] 00 00 [ 941.511240] 48 8b [ 941.511242] 00 00 [ 941.511244] 05 e4 [ 941.511246] 0f 0b [ 941.511249] 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 [ 941.579142] Chrome_~dThread[3153]: segfault at 0 ip 7f11b0208a4b sp 7f11ab0d6b00 error 6 in libxul.so[7f11b01f4000+3e9a000] [ 941.579155] Code: fa 05 48 8d 15 1e 01 b0 04 48 89 10 c7 04 25 00 00 00 00 00 00 00 00 0f 0b 48 8b 05 07 32 fa 05 48 8d 0d 68 01 b0 04 48 89 08 04 25 00 00 00 00 00 00 00 00 0f 0b e8 4d f4 ff ff 48 8b 05 e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1807997/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing
it's the same in GNOME 3.30 (Ubuntu 18.10). -- 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/1774957 Title: Network icons in status menu disappearing Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 --- Ever since the update to Ubuntu 18.04 I'm having issues with the status menu at the top right of the screen. Normally you'd have a wired network connection icon displayed at the top without opening the menu. In my case it is not displayed half of the time. In the menu list no icon nor label is displayed for the wired connection menu item. When talking about half of the time it means that I can randomly make it display again when removing the USB network adapter and reconnecting it e.g. This does not work reliably though. When connecting to a VPN, normally you'd get an additional icon at the top. This is not the case any more, nor does the switch behind an activated VPN turns change to an active state. The result is that you can activate a VPN using the switch, but you can verify that it is activated, nor can you de-active the VPN through the menu. This does change in settings though. Wireless settings are no longer displayed in the menu at all. So no way to activate it or connect to a specific network. I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as network-manager-gnome, to no avail. Attached you'll find a screenshot illustrating the issue. You'll see two icons missing to the left of the volume icon, as well as the wireless menu missing completely and no icon and text label for the wired connection menu item. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 4 10:47:05 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-07 (604 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+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 1807618] Re: package gir1.2-udisks-2.0:amd64 2.7.6-3ubuntu0.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar conf
thank you for your bug report, that looks like a local issue/corruption rather than an udisk bug though ** Changed in: udisks2 (Ubuntu) Importance: Undecided => Low ** Changed in: udisks2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1807618 Title: package gir1.2-udisks-2.0:amd64 2.7.6-3ubuntu0.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in udisks2 package in Ubuntu: Invalid Bug description: fatal erro ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-udisks-2.0:amd64 2.7.6-3ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 9 16:40:10 2018 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: udisks2 Title: package gir1.2-udisks-2.0:amd64 2.7.6-3ubuntu0.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1807618/+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 1807761] Re: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi
Could you look in the list of process what url was called exactly for gdebi? maybe it's using a x-desktop: url which gdebu doesn't handle? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- 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/1807761 Title: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi Status in gdebi package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Install Ubuntu 18.04 LTS or Ubuntu 18.10 2. Download some deb-file to the desktop - for with help of terminal: cd ~/Desktop apt-get download meld 3. Install GDebi package installer with sudo apt install gdebi 4. Select deb-file on desktop, make right click on it, select *Open With Other Application* select *GDebi Package Installer*, click *Select*, in opened window select *Install Package* Expected results: * GDebi asks user (sudo-able) password and installs the package Actual results: * GDebi do not ask user for password and do not install the package Notes: * first seen on AskUbuntu ( https://askubuntu.com/q/1099387/66509 ) * you can view my screencast to get first person view :) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 10 23:14:16 2018 GsettingsChanges: 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/gdebi/+bug/1807761/+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 1796717] Re: Update to 0.71
This bug was fixed in the package poppler - 0.71.0-0ubuntu3 --- poppler (0.71.0-0ubuntu3) disco; urgency=medium * Re-upload the 0.71 update which was deleted from disco-proposed to not get in the way of other transitions (lp: #1796717) - include a fix for a crash due to missing embedded file (lp: #1803059) poppler (0.71.0-0ubuntu2) disco; urgency=medium * Declare some symbols optional to fix the build poppler (0.71.0-0ubuntu1) disco; urgency=medium * New upstream version * Changed the binary name according to the soname update * Updated the symbols -- Sebastien Bacher Fri, 23 Nov 2018 15:35:31 +0100 ** Changed in: poppler (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1796717 Title: Update to 0.71 Status in poppler package in Ubuntu: Fix Released Bug description: The new version has new features and poppler updates require transition due to soname changes, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1796717/+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 1803059] Re: Nullpointer dereference
This bug was fixed in the package poppler - 0.71.0-0ubuntu3 --- poppler (0.71.0-0ubuntu3) disco; urgency=medium * Re-upload the 0.71 update which was deleted from disco-proposed to not get in the way of other transitions (lp: #1796717) - include a fix for a crash due to missing embedded file (lp: #1803059) poppler (0.71.0-0ubuntu2) disco; urgency=medium * Declare some symbols optional to fix the build poppler (0.71.0-0ubuntu1) disco; urgency=medium * New upstream version * Changed the binary name according to the soname update * Updated the symbols -- Sebastien Bacher Fri, 23 Nov 2018 15:35:31 +0100 ** Changed in: poppler (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1803059 Title: Nullpointer dereference Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Bionic: Fix Released Status in poppler source package in Cosmic: Fix Released Bug description: * Impact Evince segfaults on some pdf documents * Test case Download and try to open https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't segfault * Regression potential Nothing special to test, make sure evince still opens pdfs without issue - System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Evince version: GNOME Document Viewer 3.28.4 While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04 LTS), a null-pointer dereference was observed, initially this was reported to evince but the evince team advised that the issue is in poppler, the library used by evince to render PDF, poppler version: 0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however the issue is already fixed in poppler 0.70, but this will still crash your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70. Fuzzing result showing a very important vulnerability in a package currently shipped by a major Linux distribution is still of interest, even if that Linux distribution does not package the latest released upstream version. I think Ubuntu is still using, Source: poppler Version: 0.62.0-2ubuntu2.2 So, most of the systems will be affected to this issue. Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi
Could you try if installing those updates fixes it for you? https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/15763469/+files/libnm-gtk0_1.8.10-2ubuntu2~test1_amd64.deb https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/15763469/+files/libnma0_1.8.10-2ubuntu2~test1_amd64.deb https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/15763469/+files/network-manager-gnome_1.8.10-2ubuntu2~test1_amd64.deb download then in a new directory, then you can install them from a command line using "sudo dpkg -iO *.deb" in that directory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1807460 Title: Filenames with spaces not accepted when connecting to certificate- authenticated wifi Status in network-manager-applet package in Ubuntu: New Bug description: This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS When connecting to a certificate-authenticated wifi network (WPA/WPA2 Enterprise, authentication TLS) for the first time, the "Wi-Fi Network Authentication Required" dialogue is displayed, prompting the user to select their CA and user certificates. Unexpected behaviour: If any of the files have spaces in their filenames, after choosing them in the file picker the field is highlighted by a red box, and the 'Connect' button is greyed out. This is depicted in the attachment network-authentication-red-box- spaces-filename.png There is also no explanation offered for why the red box highlight is present - no tooltip, no help from pressing F1, no popup, and as far as I can find no logs. If you move/rename the file, so there are no spaces in the filename, the problem is worked around. The problem is not present on the edit connection dialogue; filenames with spaces are acceptable there. The problem was also not present on Ubuntu 16.04, and users who upgrade from 16.04 to 18.04 will find their connection keeps working. It is only when creating an entirely new connection (or after forgetting the connection and recreating it) that the problem dialog appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1807460/+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 1552792] Re: gnome software leaves dependencies installed
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1802895] Re: SRU current 0.28 version to bionic
This bug was fixed in the package shotwell - 0.28.4-0ubuntu1 --- shotwell (0.28.4-0ubuntu1) bionic; urgency=medium * New bugfix update (lp: #1802895) - Fix "Out of memory" issues when scrolling through large collections (lp: #1606491) * debian/patches/git_notifications_segfault.patch: - direct: Fix crash when dismissing modifications (lp: #1723181) -- Sebastien Bacher Mon, 12 Nov 2018 11:43:31 +0100 ** Changed in: shotwell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1802895 Title: SRU current 0.28 version to bionic Status in shotwell package in Ubuntu: Fix Released Status in shotwell source package in Bionic: Fix Released Bug description: * Impact The update is a GNOME stable update (https://wiki.ubuntu.com/StableReleaseUpdates/GNOME), it include only important bugfixes, it would be good to get into the LTS * Test case Nothing specific, test that your photos are still listed, than you can import new ones, view pictures, etc * Regression potential There are fixes about ptp/mtp devices handling, we should check with different camera/phones/etc that it creates no new issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1802895/+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] Update Released
The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1754864 Title: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) 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 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
** Changed in: gnome-desktop3 (Ubuntu Bionic) Assignee: (unassigned) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: Fix Committed Status in gnome-desktop3 source package in Bionic: Confirmed Status in gnome-desktop3 source package in Cosmic: In Progress Bug description: Impact == Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs. Test Case = Install Ubuntu 18.10 32-bit Install the update. Log out and log back in. Download a picture from the internet. Open your file browser to the directory that contains the picture. The file should show a thumbnail preview. Regression Potential This fix was cherry-picked to the stable gnome-3-30 branch. It was additionally tested by Iain Lane on usrmerged and non-usrmerged systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.) Other Info == Triaged as Critical for 18.04 LTS since this was a regression introduced in the security update that backported the bubblewrap hardening to the gnome-desktop3 thumbnailer. Original Bug Report === Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+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 1723181] Re: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
This bug was fixed in the package shotwell - 0.28.4-0ubuntu1 --- shotwell (0.28.4-0ubuntu1) bionic; urgency=medium * New bugfix update (lp: #1802895) - Fix "Out of memory" issues when scrolling through large collections (lp: #1606491) * debian/patches/git_notifications_segfault.patch: - direct: Fix crash when dismissing modifications (lp: #1723181) -- Sebastien Bacher Mon, 12 Nov 2018 11:43:31 +0100 ** Changed in: shotwell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1723181 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() Status in shotwell package in Ubuntu: Fix Released Status in shotwell source package in Bionic: Fix Released Status in shotwell source package in Cosmic: Fix Released Status in shotwell package in Fedora: Confirmed Bug description: * Impact Shotwell hits a segfault in some situations * Test case There is no specific steps described to lead to the issue. The upstream commit "Fix crash when dismissing modifications". The issue is being reported to e.u.c though at least under those ids https://errors.ubuntu.com/problem/9dfc154a07b6ec76929e2c3c74419ac85a1de015 https://errors.ubuntu.com/problem/44455d848d6d64d4838e9a5af557eb0b092bd669 If the fix is right the new version should get no report * Regression potential Check that the notifications still work as they should and that there is no other visible regressions It happened during opening and closing some raw photos. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: shotwell 0.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 18:27:38 2017 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2017-10-06 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: shotwell /media/username/podatki\ in\ backup/SLIKE\ iz\ MY\ PICTURES\ 18GB/PIKNIK\ 3.VS/IMG_3803.CR2 SegvAnalysis: Segfault happened at: 0x7fa291b2e510 : mov (%rdi),%rax PC (0x7fa291b2e510) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell StacktraceTop: g_menu_model_get_n_items () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723181/+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 1719797] Re: Firmware update seemingly not working
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1719797 Title: Firmware update seemingly not working Status in fwupd package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in fwupd source package in Bionic: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software package in Fedora: Confirmed Bug description: The fix for this particular issue is tracked in SRU bug https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 Regression potential: Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. Test case: 1) Run a UEFI firmware update from Gnome software. 2) Make sure that the update disappears from the listing after pressing the update button. Original bug: Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+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 related refs are not installed when using GNOME Software on Ubuntu 18.04
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Released -- 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 related refs are not installed when using GNOME Software on Ubuntu 18.04 Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: When installing a Flatpak application that depends on some runtimes and they depend on some additional runtime extensions (related refs) 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 1798228] Update Released
The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798228 Title: Snap search results not in the same order as command line Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Won't Fix Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] When searching in GNOME Software, the Snap results are not returned in the same order as the command line. This is due to classic snaps being considered a lower quality than strict snaps. [Test Case] 1. Open GNOME Software 2. Search for "sky" Expected result: Snaps matching "sky" are returned, with the same order as the command line (Skype is first) Observed result: While mostly in the same order, some snaps are not (Skype is the last snap in the list, in eighth position). [Regression Potential] The fix is to set the "match value" of each Snap GsApp to be the order the results are returned in. This field is checked before the "kudo" field which is populated based on the confinement used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798228/+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 1785240] Re: Cancelling snapd authorization triggers error notification
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1785240 Title: Cancelling snapd authorization triggers error notification Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Bug description: To reproduce: 1. Open gnome-software 2. Try to install a snap application 3. Cancel the polkit authorization Expected results: Nothing happens Actual results: An error notification is shown as per attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1785240/+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 1606491] Re: scrolling through many photos breaks the view
This bug was fixed in the package shotwell - 0.28.4-0ubuntu1 --- shotwell (0.28.4-0ubuntu1) bionic; urgency=medium * New bugfix update (lp: #1802895) - Fix "Out of memory" issues when scrolling through large collections (lp: #1606491) * debian/patches/git_notifications_segfault.patch: - direct: Fix crash when dismissing modifications (lp: #1723181) -- Sebastien Bacher Mon, 12 Nov 2018 11:43:31 +0100 ** Changed in: shotwell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1606491 Title: scrolling through many photos breaks the view Status in Shotwell: Fix Released Status in shotwell package in Ubuntu: Fix Committed Status in shotwell source package in Bionic: Fix Released Bug description: * Impact Sometimes when scrolling in a photo collection the view becomes white and shotwell needs to be restarted * Test case No specific steps, but it seems that scrolling on a big collection sometime trigger the issue. It seems more likely on a 4k display. Scroll on a big collection, it should keep working * Regression potential Nothing special, make sure that scrolling works without visual artifacts. --- Having some couple of thousand pictures in the photo library, scrolling through them with shotwell makes the picture view just go white. Shotwell needs to be restarted in order to recover. See attached video. This is printed in the log: (shotwell:9274): Gtk-WARNING **: drawing failure for widget `CheckerboardLayout': out of memory (shotwell:9274): Gtk-WARNING **: drawing failure for widget `GtkViewport': out of memory (shotwell:9274): Gtk-WARNING **: drawing failure for widget `LibraryMainPage': out of memory (shotwell:9274): Gtk-WARNING **: drawing failure for widget `GtkNotebook': out of memory (shotwell:9274): Gtk-WARNING **: drawing failure for widget `GtkBox': out of memory (shotwell:9274): Gtk-WARNING **: drawing failure for widget `GtkPaned': out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1606491/+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 1798228] Re: Snap search results not in the same order as command line
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1798228 Title: Snap search results not in the same order as command line Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Won't Fix Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] When searching in GNOME Software, the Snap results are not returned in the same order as the command line. This is due to classic snaps being considered a lower quality than strict snaps. [Test Case] 1. Open GNOME Software 2. Search for "sky" Expected result: Snaps matching "sky" are returned, with the same order as the command line (Skype is first) Observed result: While mostly in the same order, some snaps are not (Skype is the last snap in the list, in eighth position). [Regression Potential] The fix is to set the "match value" of each Snap GsApp to be the order the results are returned in. This field is checked before the "kudo" field which is populated based on the confinement used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798228/+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 1798470] Re: gnome-software can't handle composite CAB files
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1798470 Title: gnome-software can't handle composite CAB files Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+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
