[Desktop-packages] [Bug 1878776] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from m
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1274 https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878776 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_timeout() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1~20.04.1, the problem page at https://errors.ubuntu.com/problem/124f859bf032d7ff89d6cc900eebf3dbda6716a2 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/mutter/+bug/1878776/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
*** This bug is a duplicate of bug 1878776 *** https://bugs.launchpad.net/bugs/1878776 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 1878776, 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 1878776 gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_timeout() -- 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/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880742/+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 1878776] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from m
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878776 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_timeout() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1~20.04.1, the problem page at https://errors.ubuntu.com/problem/124f859bf032d7ff89d6cc900eebf3dbda6716a2 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/mutter/+bug/1878776/+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 1880764] Re: Gnome sidebar freezes when dragging around icons while there is high memory pressure, but fails to resume when the memory pressure is down, causing icons stuck mov
Please run this command and tell us what you get: gsettings list-recursively org.gnome.shell ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete ** Summary changed: - Gnome sidebar freezes when dragging around icons while there is high memory pressure, but fails to resume when the memory pressure is down, causing icons stuck moving to remain in their position onscreen + Dragging icons frozen in place without finishing -- 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/1880764 Title: Dragging icons frozen in place without finishing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: When I was dragging around the discord icon around, Gnome froze and the icon remained in place. This was happening when I was compiling gettext and it was using memory. However, even after the compilation stopped and the memory went down, Gnome keeps the icons in place, refusing to finish what it started. In this state, the Grid button on the bottom has no effect, and clicking on the icons have no effect, though they will update when a new program launches or closes, and if a new window opens. I expect the Gnome Shell to become responsive once the memory has gone down. It has enough memory to finish the animations; it just won't finish them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 26 17:24:53 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-07 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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-extension-ubuntu-dock/+bug/1880764/+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 1821585] Re: Ubuntu/Gnome dock not working with drag and drop
Thank you for reporting this bug to Ubuntu. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Won't Fix -- 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/1821585 Title: Ubuntu/Gnome dock not working with drag and drop Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Bug description: Description: Ubuntu Disco Dingo (development branch) Release: 19.04 latest updates installed To drag and drop a file to the Ubuntu/Gnome dock (favorites) is not working. For example I tried to drag the file .local/share/applications/example.desktop and drop it to favorites the result is that the starter is not created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1821585/+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 1880785] Re: Cannot enable 'Lock screen on suspend'
Please run this command and tell us what you get: gsettings get org.gnome.desktop.lockdown disable-lock-screen Also your lock delay is set to 1800 (30 minutes?) so please try: gsettings set org.gnome.desktop.screensaver lock-delay 0 gsettings set org.gnome.desktop.screensaver lock-enabled true and then log out and in again to be sure. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880785 Title: Cannot enable 'Lock screen on suspend' Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am trying to make my laptop lock the screen upon unsuspending. I have made sure that the setting is enabled in 'Settings > Privacy > Screen lock > Lock screen on suspend', but my laptop opens without a lock screen when I open it or press a key. This only started since upgrading to Ubuntu 20.04. Previously, I would have a locked screen and be prompted for a password upon unsuspending. $ gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 21:28:39 2020 DisplayManager: lightdm DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-16 (680 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-23 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880785/+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 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Please also run the command in comment #1. -- 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/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 Status in mutter package in Ubuntu: Incomplete Bug description: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+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 1880801] Re: gnome-shell with Dash To Panel extension enabled crashes when locking screen
*** This bug is a duplicate of bug 184 *** https://bugs.launchpad.net/bugs/184 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 184, 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 184 gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel -- 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/1880801 Title: gnome-shell with Dash To Panel extension enabled crashes when locking screen Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashes when locking screen with Win+L key (or automatic screen lock) if the Dash To Panel extension is installed. (Installed with 'apt get install gnome-shell-extension-dash-to-panel') [55200.555021] traps: gnome-shell[111390] general protection fault ip:7fab74def252 sp:7fff339e1290 error:0 in libst-1.0.so[7fab74dcf000+4c000] I believe this is the same bug here, where a fix is available: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2709 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 27 14:55:18 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-10 (959 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880801/+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 1880801] Re: gnome-shell with Dash To Panel extension enabled crashes when locking screen
See also: https://github.com/home-sweet-gnome/dash-to-panel/issues/976 -- 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/1880801 Title: gnome-shell with Dash To Panel extension enabled crashes when locking screen Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashes when locking screen with Win+L key (or automatic screen lock) if the Dash To Panel extension is installed. (Installed with 'apt get install gnome-shell-extension-dash-to-panel') [55200.555021] traps: gnome-shell[111390] general protection fault ip:7fab74def252 sp:7fff339e1290 error:0 in libst-1.0.so[7fab74dcf000+4c000] I believe this is the same bug here, where a fix is available: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2709 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 27 14:55:18 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-10 (959 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880801/+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 1880801] [NEW] gnome-shell with Dash To Panel extension enabled crashes when locking screen
Public bug reported: gnome-shell crashes when locking screen with Win+L key (or automatic screen lock) if the Dash To Panel extension is installed. (Installed with 'apt get install gnome-shell-extension-dash-to-panel') [55200.555021] traps: gnome-shell[111390] general protection fault ip:7fab74def252 sp:7fff339e1290 error:0 in libst-1.0.so[7fab74dcf000+4c000] I believe this is the same bug here, where a fix is available: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2709 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 27 14:55:18 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-10 (959 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #976 https://github.com/home-sweet-gnome/dash-to-panel/issues/976 -- 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/1880801 Title: gnome-shell with Dash To Panel extension enabled crashes when locking screen Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashes when locking screen with Win+L key (or automatic screen lock) if the Dash To Panel extension is installed. (Installed with 'apt get install gnome-shell-extension-dash-to-panel') [55200.555021] traps: gnome-shell[111390] general protection fault ip:7fab74def252 sp:7fff339e1290 error:0 in libst-1.0.so[7fab74dcf000+4c000] I believe this is the same bug here, where a fix is available: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2709 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 27 14:55:18 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-10 (959 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880801/+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 689659] Re: Gtk.window.set_keep_above (true) doesn't work.
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/689659 Title: Gtk.window.set_keep_above (true) doesn't work. Status in mutter package in Ubuntu: Expired Bug description: Binary package hint: mutter let tpwindow be a Gtk.Window tpwindow.set_keep_above (true); This code should place my tpwindow above all other windows, but it doesn't. If you open ie a terminal, and then from the terminal decoration menu select "Keep this window above all other windows", you'll notice that the terminal stays above the tpwindow. So this is a wrong behavior. I call for fixes, or for a way to keep my window always on top. Thank you Alberto @ lp.net/synapse-project To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/689659/+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 777130] Re: mutter installs .gir files incorrectly
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/777130 Title: mutter installs .gir files incorrectly Status in mutter package in Ubuntu: Expired Bug description: Binary package hint: mutter All the packages (around 50) I've examined install their .gir files to /usr/share/gir-1.0/ mutter installs /usr/lib/mutter/Meta-3.0.gir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/777130/+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 1880794] Re: Screen Not Wakeup After Suspend
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1880794 Title: Screen Not Wakeup After Suspend if Fractional Scaling is enabled Status in mutter package in Ubuntu: New Bug description: if you do fractional scaling(setting->display->Fractional Scaling),means you do change it from 100% to 125% then screen is not wake up after suspend and when again i set Fractional scaling to 100% it resume to wake up. Means after Fractional Scaling screen wake up not work after suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 27 08:16:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-05-22 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=48467cc2-835d-4375-b148-3a312b7c4351 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880794/+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 1880794] Re: Screen Not Wakeup After Suspend
** Tags added: xrandr-scaling ** Summary changed: - Screen Not Wakeup After Suspend + Screen Not Wakeup After Suspend if Fractional Scaling is enabled ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1880794 Title: Screen Not Wakeup After Suspend if Fractional Scaling is enabled Status in mutter package in Ubuntu: New Bug description: if you do fractional scaling(setting->display->Fractional Scaling),means you do change it from 100% to 125% then screen is not wake up after suspend and when again i set Fractional scaling to 100% it resume to wake up. Means after Fractional Scaling screen wake up not work after suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 27 08:16:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-05-22 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=48467cc2-835d-4375-b148-3a312b7c4351 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880794/+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 1880794] [NEW] Screen Not Wakeup After Suspend
You have been subscribed to a public bug: if you do fractional scaling(setting->display->Fractional Scaling),means you do change it from 100% to 125% then screen is not wake up after suspend and when again i set Fractional scaling to 100% it resume to wake up. Means after Fractional Scaling screen wake up not work after suspend. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 27 08:16:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-05-22 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=48467cc2-835d-4375-b148-3a312b7c4351 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Screen Not Wakeup After Suspend https://bugs.launchpad.net/bugs/1880794 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877670] Re: [Intel Braswell][Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears.
** Summary changed: - [Intel Braswell][Acer Aspire R3-131T] Display Freezes and frequently mouse cursor disappears. + [Intel Braswell][Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears. ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Summary changed: - [Intel Braswell][Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears. + [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1877670 Title: [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears. Status in linux package in Ubuntu: Incomplete Bug description: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 02:25:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire R3-131T ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.family: BSW dmi.product.name: Aspire R3-131T dmi.product.sku: Aspire R3-131T_1022_1.17 dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I am also affected by this bug. I am on Kubuntu 20.04 on a Dell XPS L502x. When I am on my Intel card, my computer reports my consumption as around 22 W. I checked my 'nvidia-prime' package, and it is 0.8.14. According to Vasyl, the bug should be fixed in this version, but unfortunately it is not, at least not for me. Please fix this bug, as the excessive power consumption essentially renders prime-select useless. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880411] Re: Tweaks > Keyboard & Mouse > Overview Shortcut = Right Super does not work
** Summary changed: - right super key does not show the overlay + Tweaks > Keyboard & Mouse > Overview Shortcut = Right Super does not work ** Package changed: mutter (Ubuntu) => gnome-tweaks (Ubuntu) ** Changed in: gnome-tweaks (Ubuntu) Status: Invalid => 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/1880411 Title: Tweaks > Keyboard & Mouse > Overview Shortcut = Right Super does not work Status in gnome-tweaks package in Ubuntu: Triaged Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1880411/+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 1877670] Re: [Intel Braswell] Display Freezes and frequently mouse cursor disappears.
Sorry! It's the touchpad. Scrolling using touchscreen also seem to cause these things. Sometimes, it comes out of the hang on it's own. It goes to a solid screen for a second and everything's fine again. Other times, I log off and log on to make the cursor work. On Wed, 27 May 2020, 07:45 Daniel van Vugt, <1877...@bugs.launchpad.net> wrote: > When you say "mouse cursor", is that using the touchpad or a USB mouse? > If the problem mostly happens with the touchpad then these messages > might be relevant: > > May 26 17:39:21 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - > SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and > discarded. > May 26 17:39:21 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See > https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html > for details > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - > SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and > discarded. > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See > https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html > for details > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - > SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and > discarded. > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See > https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html > for details > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - > SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and > discarded. > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See > https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html > for details > May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - > SYN1B7F:00 06CB:74DE Touchpad: WARNING: log rate limit exceeded (5 msgs per > 720ms). Discarding future messages. > > ** Summary changed: > > - [Intel Braswell] Display Freezes and frequently mouse cursor disappears. > + [Intel Braswell][Acer Aspire R3-131T] Display Freezes and frequently > mouse cursor disappears. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877670 > > Title: > [Intel Braswell][Acer Aspire R3-131T] Display Freezes and frequently > mouse cursor disappears. > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > Display Freezes and frequently mouse cursor disappears. After restart > mouse cursor comes back again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 > Uname: Linux 5.4.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat May 9 02:25:55 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] > InstallationDate: Installed on 2020-04-23 (14 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2a Intel Corp. >Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch > System >Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Acer Aspire R3-131T > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic > root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/30/2016 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V1.17 > dmi.board.name: Aspire R3-131T > dmi.board.vendor: Acer > dmi.board.version: V1.17 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.17 > dmi.modalias: > dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: > dmi.product.family: BSW > dmi.product.name: Aspire R3-131T > dmi.product.sku: Aspire R3-131T_1022_1.17 >
[Desktop-packages] [Bug 1716639] Re: gnome-screensaver issue when using Wayland
I see this on Ubuntu 18.04 as well, but I have a gnome-based gui that works. Here's my log snippet: May 26 12:23:47 cerberus org.gnome.ScreenSaver[2217]: Unable to init server: Could not connect: Connection refused May 26 12:23:47 cerberus gnome-screensav[2263]: Cannot open display: May 26 12:23:47 cerberus dbus-daemon[2217]: [session uid=130 pid=2217] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1 May 26 12:23:47 cerberus gnome-session[2223]: gnome-session-binary[2223]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSav May 26 12:23:47 cerberus gnome-session-binary[2223]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f -- 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/1716639 Title: gnome-screensaver issue when using Wayland Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: When using a Wayland session instead of X11 from the standard lightdm- gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+ initialisation, causing the gnome-session-binary to exit and subsequently a greeter loop where a user is unable to log in. The following is an excerpt from the syslog: ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service name='org.gnome.ScreenSaver' Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init server: Could not connect: Connection refused Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+ S Running an identical session without Wayland produces the expected behaviour: a user can log into his desktop session and start working as usual. Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share /gnome-session/sessions/gnome.session doesn't have any effect. I'm suspecting foul play between the screensaver proxy and the screensaver binary itself, but don't have the bandwidth to analyse the source at the moment. More than happy to provide more information as required - just let me know. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-screensaver 3.6.1-7ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 12 11:29:30 2017 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2017-08-31 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716639/+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 1880411] Re: right super key does not show the overlay
Can we assign this to gnome-tweaks, since that's what calls it "Right Super" ? -- 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/1880411 Title: right super key does not show the overlay Status in mutter package in Ubuntu: Invalid Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880411/+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 1880411] Re: right super key does not show the overlay
Done. Though the original issue is invalid, not a bug. If you disagree then please explain why. ** Summary changed: - Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R" + right super key does not show the overlay ** Description changed: - Settings > Language and Region keyboard preview mislabels the - compose/menu key as "Super R". + The right super key doesn't show the overlay. Ubuntu 20.04 LTS ** Package changed: gnome-control-center (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Invalid -- 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/1880411 Title: right super key does not show the overlay Status in mutter package in Ubuntu: Invalid Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880411/+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 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Included attachments: lspcik.txt & journal.txt ** Attachment added: "mutter_rel_bug_05_27.zip" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+attachment/5377179/+files/mutter_rel_bug_05_27.zip -- 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/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 Status in mutter package in Ubuntu: Incomplete Bug description: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+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 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
My system has a raid filesystem present. -- 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/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+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 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
Present in 18.04: jlquinn@cerberus:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic jlquinn@cerberus:~$ dpkg -l udisks2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii udisks22.7.6-3ubuntu0.2 amd64 D-Bus service to access and manipulate storage devices -- 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/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+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 1880411] Re: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R"
I disagree with you Daniel. So far I know, Gnome doesn't have a default compose key. Of course you can set it with gnome-tweaks, but for all keybinding this one is . May be you restore the original issue name and move it to mutter? -- 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/1880411 Title: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R" Status in gnome-control-center package in Ubuntu: New Bug description: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R". Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1880411/+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 1880728] Re: Xorg freeze
Also if the freeze happens again then immediately after rebooting please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: amdgpu ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1880728 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: was logged in through team viewer and got kicked out. when i was able to physically access the machine the screens were on, but was not able to move the mouse or interact with the computer. performed hard reboot to get it back on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 26 11:24:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2020-05-09 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LM dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE(MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880728/+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 1880787] Re: The super key doesn't show the overlay when the keyboard layout is a non latin one
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Thanks. New mutter update 3.36.2-1ubuntu1~20.04.1 fixed 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/1880787 Title: The super key doesn't show the overlay when the keyboard layout is a non latin one Status in gnome-shell package in Ubuntu: New Bug description: So you have some exotic keyboard layouts, say russian, hebrew or sanskrit, and you switched to some of it. The super key doesn't show the overlay with it. fresh Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880787/+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 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Please also run: lspci -k > lspcik.txt journalctl -b0 > journal.txt and attach the resulting text files. ** Tags added: regression-update -- 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/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 Status in mutter package in Ubuntu: Incomplete Bug description: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+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 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1880739 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 Status in mutter package in Ubuntu: Incomplete Bug description: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+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 1880728] Re: Xorg freeze
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. -- 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/1880728 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: was logged in through team viewer and got kicked out. when i was able to physically access the machine the screens were on, but was not able to move the mouse or interact with the computer. performed hard reboot to get it back on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 26 11:24:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2020-05-09 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LM dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE(MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880728/+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 1880793] [NEW] When I do any screen lock action it screen fickers (lock fails)
Public bug reported: When I look at dmesg it appears that screen lock is causing a segfault: [ 595.735328] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 597.651594] gnome-shell[7692]: segfault at 1195 ip 7f94d6bcee41 sp 7fffe593b4f8 error 4 in libc-2.31.so[7f94d6a6d000+178000] [ 597.651601] Code: 01 0f 84 e2 03 00 00 0f 82 cc 03 00 00 49 89 d3 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f ef 03 00 00 fe 6f 0f c5 f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 [ 599.073507] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 19:45:14 2020 InstallationDate: Installed on 2019-11-25 (183 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1880793 Title: When I do any screen lock action it screen fickers (lock fails) Status in gnome-screensaver package in Ubuntu: New Bug description: When I look at dmesg it appears that screen lock is causing a segfault: [ 595.735328] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 597.651594] gnome-shell[7692]: segfault at 1195 ip 7f94d6bcee41 sp 7fffe593b4f8 error 4 in libc-2.31.so[7f94d6a6d000+178000] [ 597.651601] Code: 01 0f 84 e2 03 00 00 0f 82 cc 03 00 00 49 89 d3 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f ef 03 00 00 fe 6f 0f c5 f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 [ 599.073507] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 19:45:14 2020 InstallationDate: Installed on 2019-11-25 (183 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1880793/+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 1880411] Re: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R"
Yes the feature you want is a mutter/gnome-shell thing, but that's not a bug. The only bug here is in the gnome-control-center GUI. -- 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/1880411 Title: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R" Status in gnome-control-center package in Ubuntu: New Bug description: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R". Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1880411/+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 1880725] Re: Video Stream are hanging/buffering around every 10seconds
** Package changed: xorg (Ubuntu) => kodi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1880725 Title: Video Stream are hanging/buffering around every 10seconds Status in kodi package in Ubuntu: New Bug description: I am using KODI on Ubuntu and every Video stream I use is hanging after around 10 seconds. Ubuntu is setup on a Proxmox VM and the GPU is passed through. I tried to reinstall the driver without any effect. Network connection is a 50MBit/s line, so should not be the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Tue May 26 18:00:26 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2074] InstallationDate: Installed on 2020-05-15 (11 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=09ee74bf-e5a7-489d-bfed-27c845c2e9c1 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.0:cvnQEMU:ct1:cvrpc-q35-5.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1880725/+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 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
> Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. This is a little too vague for us to be able to action right now, but I can suggest checking a few things that commonly cause high CPU for other people: 1. Uninstall all non-Ubuntu gnome-shell extensions. 2. Uninstall 'indicator-multiload' if you have it (bug 784055). 3. Try disabling 'Ubuntu AppIndicators' in gnome-shell-extension-prefs. 4. Make sure the clock in your Gnome panel at the top of the screen is NOT set to show seconds. If the problem is still not solved then please run these commands: lspci -k > lspcik.txt journalctl -b0 > journal.txt and attach the resulting text files. And if you are willing then please attach a screenshot of your desktop so we can see if it entails anything unusual I haven't yet thought of. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: performance -- 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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569
[Desktop-packages] [Bug 1880708] Re: ubuntu 14 не видит съемных носителей
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1880708 Title: ubuntu 14 не видит съемных носителей Status in nautilus package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: usb cd dvd диски не читаются ноутбуком ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 26 17:43:52 2020 DistUpgraded: 2019-12-27 21:41:16,366 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.19-3.13, 3.19.1, 3.13.0-53-generic, x86_64: installed oem-audio-hda-daily, 0.201601261029~ubuntu14.04.1, 3.13.0-53-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06ac] InstallationDate: Installed on 2019-08-22 (278 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 15-3552 ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic.efi.signed root=UUID=27278fc3-e93d-4645-a39a-08d31e3b9369 ro locale=ru_RU drm.debug=0xe plymouth:debug quiet splash radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2019-12-27 (150 days ago) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.13 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 26 17:15:09 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 28908 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1880708/+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 1880411] Re: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R"
It's looks like that this is a mutter thing. If I understand that correctly from a short gsettings dig, you can set only one key as overlay-key, not a combo, not several separate keys. -- 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/1880411 Title: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R" Status in gnome-control-center package in Ubuntu: New Bug description: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R". Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1880411/+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 878277] Re: Keyboard Layout Options | Alt/Win behavior incomprehensible
All of the releases mentioned are past end of life so this bug is being marked "Won't Fix". If you would like to continue discussing issues in this area then please run this command to open a new bug: ubuntu-bug gnome-control-center ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix -- 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/878277 Title: Keyboard Layout Options | Alt/Win behavior incomprehensible Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: Just upgraded to oneiric. The Keyboard Layout Options | Alt/Win key behavior alternatives are: * Default - So what is the "default"? * Add the standard behaviour to Menu key - What is the "standard behaviour"? What is its relation to "the default"? - Which is the "Menu key"? * Alt is mapped to Right Win, Super to Menu - What does "mapped to" mean? The term "map" is symmetrical, but the application here is asymmetrical. Does this option map the Alt function to the Right Win key, or the Right Win function to the Alt keys? Presumably the first, but it isn't clear. Please say something like "Alt functionality...". * Alt and Meta are on Alt keys - Does this mean that Alt functionality is mapped to the left Alt key and Meta to the right Alt key? Or what? Not clear. * Left Alt is swapped with Left Win - This and other options are not inherently mutually exclusive. So why are these options on radio buttons? A Help button on the dialog would be nice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/878277/+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 1070449] Re: "Login without password" option effectively locks super user out!
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix -- 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/1070449 Title: "Login without password" option effectively locks super user out! Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: I installed Ubuntu 12.10 with the option to log my main user with a password. Then I added two other users and changed all three accounts to log in without a password. This nulled my main user's password and stopped the ability to sudo and make any system wide changes! Also the password can not be set back on, as there is no valid password to authorize any actions! In effect, you are completely left without a super user for your computer and cannot install updates or programs or do a whole lot of anything. There is a remedy to this and it is to go to the terminal and typing passwd, after which you can re-set your password. However this is not clear to many users, and that's why the Users panel simply should not be able to null your password even if you prefer to login without one. Very critical to get fixed asap! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070449/+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 1880787] Re: The super key doesn't show the overlay when the keyboard layout is a non latin one
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 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 1871913, 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. ** Tags added: focal ** This bug has been marked a duplicate of bug 1871913 super key does not work with secondary keyboard layout -- 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/1880787 Title: The super key doesn't show the overlay when the keyboard layout is a non latin one Status in gnome-shell package in Ubuntu: New Bug description: So you have some exotic keyboard layouts, say russian, hebrew or sanskrit, and you switched to some of it. The super key doesn't show the overlay with it. fresh Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880787/+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 1880411] Re: right super key does not show the overlay
Thanks for the screenshot. That's just a bug in gnome-control-center giving it the wrong label. The "Super R" key is actually called "Compose" by the kernel, and it is called "Menu" by gnome-shell. That key is not meant to open the overview. ** Package changed: gnome-shell (Ubuntu) => gnome-control-center (Ubuntu) ** Summary changed: - right super key does not show the overlay + Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R" ** Description changed: - The right super key doesn't show the overlay. + Settings > Language and Region keyboard preview mislabels the + compose/menu key as "Super R". Ubuntu 20.04 LTS ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880411 Title: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R" Status in gnome-control-center package in Ubuntu: New Bug description: Settings > Language and Region keyboard preview mislabels the compose/menu key as "Super R". Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1880411/+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 1877670] Re: [Intel Braswell] Display Freezes and frequently mouse cursor disappears.
When you say "mouse cursor", is that using the touchpad or a USB mouse? If the problem mostly happens with the touchpad then these messages might be relevant: May 26 17:39:21 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and discarded. May 26 17:39:21 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and discarded. May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and discarded. May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - SYN1B7F:00 06CB:74DE Touchpad: kernel bug: Touch jump detected and discarded. May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details May 26 17:39:22 HisGrace /usr/lib/gdm3/gdm-x-session[1750]: (EE) event5 - SYN1B7F:00 06CB:74DE Touchpad: WARNING: log rate limit exceeded (5 msgs per 720ms). Discarding future messages. ** Summary changed: - [Intel Braswell] Display Freezes and frequently mouse cursor disappears. + [Intel Braswell][Acer Aspire R3-131T] Display Freezes and frequently mouse cursor disappears. -- 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/1877670 Title: [Intel Braswell][Acer Aspire R3-131T] Display Freezes and frequently mouse cursor disappears. Status in xorg-server package in Ubuntu: Incomplete Bug description: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 02:25:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire R3-131T ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.family: BSW dmi.product.name: Aspire R3-131T dmi.product.sku: Aspire R3-131T_1022_1.17 dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1880787] [NEW] The super key doesn't show the overlay when the keyboard layout is a non latin one
Public bug reported: So you have some exotic keyboard layouts, say russian, hebrew or sanskrit, and you switched to some of it. The super key doesn't show the overlay with it. fresh Ubuntu 20.04 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880787 Title: The super key doesn't show the overlay when the keyboard layout is a non latin one Status in gnome-shell package in Ubuntu: New Bug description: So you have some exotic keyboard layouts, say russian, hebrew or sanskrit, and you switched to some of it. The super key doesn't show the overlay with it. fresh Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880787/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
That's excellent news. We can't ask for a better result than the PulseAudio developers to offer a direct fix against the original bug report. It hasn't landed upstream yet though so please wait. -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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
JPM, This bug is closed. If you still have issues then please open a new bug by running: ubuntu-bug gnome-shell -- 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: Won't Fix 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 1880784] [NEW] Gamemode sets incorrect default governor
Public bug reported: gamemode 1.5.1-0ubuntu3 in Ubuntu 20.04 LTS Gamemode sets the incorrect default cpu governor which causes huge performance decreases in some scenarios. What I expect to happen: Gamemode on exit should set the cpu governor back to system default (ondemand in Ubuntu's case I believe) What happens instead: Gamemode currently will set the cpu governor to powersave when exiting Fix: /etc/gamemode.ini - Commenting out line `defaultgov=powersave` will correctly set the cpu governor back to the system default https://github.com/FeralInteractive/gamemode/commit/1c9cd2de5bd47c04a124445eb5b567f37ec3e85f A fix is currently in gamemode master, but I hope this can be addressed in Ubuntu 20.04 ** Affects: gamemode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/1880784 Title: Gamemode sets incorrect default governor Status in gamemode package in Ubuntu: New Bug description: gamemode 1.5.1-0ubuntu3 in Ubuntu 20.04 LTS Gamemode sets the incorrect default cpu governor which causes huge performance decreases in some scenarios. What I expect to happen: Gamemode on exit should set the cpu governor back to system default (ondemand in Ubuntu's case I believe) What happens instead: Gamemode currently will set the cpu governor to powersave when exiting Fix: /etc/gamemode.ini - Commenting out line `defaultgov=powersave` will correctly set the cpu governor back to the system default https://github.com/FeralInteractive/gamemode/commit/1c9cd2de5bd47c04a124445eb5b567f37ec3e85f A fix is currently in gamemode master, but I hope this can be addressed in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1880784/+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 1880785] [NEW] Cannot enable 'Lock screen on suspend'
Public bug reported: I am trying to make my laptop lock the screen upon unsuspending. I have made sure that the setting is enabled in 'Settings > Privacy > Screen lock > Lock screen on suspend', but my laptop opens without a lock screen when I open it or press a key. This only started since upgrading to Ubuntu 20.04. Previously, I would have a locked screen and be prompted for a password upon unsuspending. $ gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 21:28:39 2020 DisplayManager: lightdm DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-16 (680 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-23 (33 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1880785 Title: Cannot enable 'Lock screen on suspend' Status in gnome-shell package in Ubuntu: New Bug description: I am trying to make my laptop lock the screen upon unsuspending. I have made sure that the setting is enabled in 'Settings > Privacy > Screen lock > Lock screen on suspend', but my laptop opens without a lock screen when I open it or press a key. This only started since upgrading to Ubuntu 20.04. Previously, I would have a locked screen and be prompted for a password upon unsuspending. $ gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend true $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.2-1ubuntu1~20.04.1 Version table: *** 3.36.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 21:28:39 2020 DisplayManager: lightdm DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-07-16 (680 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-23 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880785/+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 1853094] Re: [modeset] Screen tearing when using multiple monitors
I am using the free drivers for my Nvidia card, since the private drivers gave more trouble than ever. I reported it too and the suggestion they gave me was to remove them and use the free drivers, but I have a serious problem with screen tearing, and I can't find a solution anywhere about it. I have Nvidia card and Integrated video Intel, Use Ubuntu 20.04 with a clean installing -- 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/1853094 Title: [modeset] Screen tearing when using multiple monitors Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1853094/+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 1864307] Re: Many apps have no icon in Software on Focal
Nice :-) Now only the gnome-software patch is missing to fix this issue completely (at least for the package, according to Launchpad) ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-software (Ubuntu Focal) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Triaged Status in ubuntu-meta source package in Focal: Fix Released Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1877468] Re: GNOME dictionary uses symbolic icon
This bug was fixed in the package yaru-theme - 20.04.7 --- yaru-theme (20.04.7) focal; urgency=medium [ ubuntujaggers ] * adding full colour app icon for accessories-dictionary (LP: #1877468) * Let Gnome Software use upstream icon (LP: #1878198) [ Carlo Lobrano ] * use colored radio/check buttons in menu (LP: #1878199) [ Marco Trevisan (Treviño) ] * gnome-shell, dock: Remove the top/bottom padding (LP: #1873321) * gnome-shell, dock: Sync style parameters with upstream -- Carlo Lobrano Fri, 08 May 2020 15:26:23 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1877468 Title: GNOME dictionary uses symbolic icon Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: Gnome dictionary installed from Ubuntu software, uses the dictionary's symbolic icon. It might use a proper fullcolor icon from Yaru set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1877468/+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 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen
This bug was fixed in the package yaru-theme - 20.04.7 --- yaru-theme (20.04.7) focal; urgency=medium [ ubuntujaggers ] * adding full colour app icon for accessories-dictionary (LP: #1877468) * Let Gnome Software use upstream icon (LP: #1878198) [ Carlo Lobrano ] * use colored radio/check buttons in menu (LP: #1878199) [ Marco Trevisan (Treviño) ] * gnome-shell, dock: Remove the top/bottom padding (LP: #1873321) * gnome-shell, dock: Sync style parameters with upstream -- Carlo Lobrano Fri, 08 May 2020 15:26:23 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1873321 Title: The Show Applications button should be clickable in the corner or bottom of the screen Status in Dash to dock: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Focal: Fix Committed Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. [ Test case ] - Ensure the dock is positioned on the left side of the screen - Move the cursor at the bottom left corner - Clicking should open the app grid [ Regression potential ] Dash has missing padding ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1878198] Re: Ubuntu-Software icon should not be used for Gnome-Software
This bug was fixed in the package yaru-theme - 20.04.7 --- yaru-theme (20.04.7) focal; urgency=medium [ ubuntujaggers ] * adding full colour app icon for accessories-dictionary (LP: #1877468) * Let Gnome Software use upstream icon (LP: #1878198) [ Carlo Lobrano ] * use colored radio/check buttons in menu (LP: #1878199) [ Marco Trevisan (Treviño) ] * gnome-shell, dock: Remove the top/bottom padding (LP: #1873321) * gnome-shell, dock: Sync style parameters with upstream -- Carlo Lobrano Fri, 08 May 2020 15:26:23 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1878198 Title: Ubuntu-Software icon should not be used for Gnome-Software Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: org.gnome.Software and ubuntu software use the same icon This causes confusion for users that choose to install gnome-software for flatpak support. First reported here https://github.com/ubuntu/yaru/issues/2144#issuecomment-620092334 Steps to reproduce: 1. install org.gnome.Software 2. open both org.gnome.Software and Ubuntu Software, or even just search for "software" in gnome-shell 3. The icons of both applications are shown, and they are the same The fix is to allow org.gnome.Software to use its upstream icon, removing a Yaru symlink between gnome-software app name and Yaru's icon. The system is expected to automatically use the application provided icon if the selected icon set does not provide one, so no regression is expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1878198/+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 1878199] Re: Check and Radio buttons state is unclear in GTK2
This bug was fixed in the package yaru-theme - 20.04.7 --- yaru-theme (20.04.7) focal; urgency=medium [ ubuntujaggers ] * adding full colour app icon for accessories-dictionary (LP: #1877468) * Let Gnome Software use upstream icon (LP: #1878198) [ Carlo Lobrano ] * use colored radio/check buttons in menu (LP: #1878199) [ Marco Trevisan (Treviño) ] * gnome-shell, dock: Remove the top/bottom padding (LP: #1873321) * gnome-shell, dock: Sync style parameters with upstream -- Carlo Lobrano Fri, 08 May 2020 15:26:23 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1878199 Title: Check and Radio buttons state is unclear in GTK2 Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: Some GTK2 applications use the new black and white menu-radio buttons in an inconsistent way outside the menus, resulting in a confused representation of their state. Steps to reproduce: 1. open Inkscape > edit > preferences 2. look at the "Tools" view: "Visual bounding box" label uses b/w radio-button (that should only be used in menu), while "Geometric bounding box" uses the colored unchecked radio button. Note that check-button is used correctly in the colored form just below in the same view. Our solution consists in have both menu-radio and normal radio buttons use the same colored style to show no differences whatever asset is used by GTK2 applications. No regression is expected because this is how the assets looked like in previous Yaru version and so is well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1878199/+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 1873321] Update Released
The verification of the Stable Release Update for yaru-theme has completed successfully and the package is now being 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-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button should be clickable in the corner or bottom of the screen Status in Dash to dock: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Focal: Fix Committed Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. [ Test case ] - Ensure the dock is positioned on the left side of the screen - Move the cursor at the bottom left corner - Clicking should open the app grid [ Regression potential ] Dash has missing padding ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1864307] Re: Many apps have no icon in Software on Focal
This bug was fixed in the package ubuntu-meta - 1.450.1 --- ubuntu-meta (1.450.1) focal; urgency=medium * Added apt-config-icons-hidpi to desktop-minimal-recommends, desktop- recommends (LP: #1864307) -- Ken VanDine Mon, 11 May 2020 10:37:00 -0400 ** Changed in: ubuntu-meta (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Released Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Released Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1864307] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package is now being 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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Released Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Released Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1880775] [NEW] HP Envy 4524 All In One - Device communication error - code 5012;
Public bug reported: Situation: Ubuntu 20.04 LTS after fresh install, NOT upgrade on desktop (had 16.04 LTS before). Printer was attached during fresh install of 20.04 LTS and internet connection, third party downloads ticked. Bug description: USB connected HP Envy 4524 All In One is recognized multiple times as printer but does not print, scans occasionally but unreliable in getting recognized by 20.04 LTS. Additional Information: HP Envy 4524 All In One works flawless with Ubuntu 18.04 LTS on Laptop. Worked flawless with Ubuntu 16.04 LTS on the desktop used above. Steps taken so far: De-installed/purged hplip 3.20.3 as sudo hp-check -i showed multiple errors and missing dependencies. Installed hplip 3.20.5 from the HPLIP site and ran the script which resulted in compiling and installing the printer with nil errors running sudo hp-check -i. However, after reboot Device communication error - code 5012 re-occured (current hp-check log attached). Log ___ administrator@office-server:~$ sudo hp-check -i [sudo] password for administrator: /usr/bin/hp-check:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: Saving output in log file: /home/administrator/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.5) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version |Gtk-Message: 09:51:18.656: Failed to load module "canberra-gtk-module" --- | SYSTEM INFO | --- Kernel: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux Host: office-server Proc: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux Distribution: 12 20.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.20.5 HPLIP-Home: /usr/share/hplip HPLIP-Installation: Auto installation is supported for ubuntu distro 20.04 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.20.5 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/HP ppdbase=/usr/share/ppd doc=/usr/share/doc/hplip-3.20.5 html=/usr/share/doc/hplip-3.20.5 icon=/usr/share/applications cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv/hp bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure]
[Desktop-packages] [Bug 1853266] Re: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()
>From the upstream bug report, the failure in OsLookupColor() is just a common point where the system falls over once it's run out of graphics memory. There could be a number of reasons why the memory got exhausted in the first place (e.g. video drivers leaking memory, misc. bugs in GL apps, ...) which would be the root cause of the problem. (Fwiw, I stumbled across this bug report because I also got a crash in /usr/lib/xorg/Xorg (OsLookupColor+0x13c), but this was with radeon_drv, unrelated to any GL errors. So, likely a different underlying bug than the OP, just that the crash looks similar.) -- 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/1853266 Title: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc() Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Fedora: Won't Fix Bug description: Recently, my the xserver on my system has started randomly crashing due to a segmentation fault. As far as I can tell, this segmentation fault occurs as a result of libglamoregl encountering a GL_OUT_OF_MEMORY error (see attached Xorg.log). I have had a hard time reproducing this bug reliably, but it mostly happens when I have been using Inkscape for a while. This appears to be the same bug that has been reported here https://bugs.freedesktop.org/show_bug.cgi?id=110500 https://bugs.freedesktop.org/show_bug.cgi?id=110714 In those bug reports, the usual recommendation is to switch from the -modesetting video driver to the -nouveau video driver. By default, Ubuntu is not configured in this way, so this bug probably needs to be addressed in some other way. My graphics card is listed as follows: *-display description: VGA compatible controller product: GK208B [GeForce GT 710] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:69 memory:d700-d7ff memory:c800-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 Please let me know if you need any additional information. More information: Release of Ubuntu: 19.04 Installed package versions: xserver-xorg-video-nouveau/disco,now 1:1.0.16-1 amd64 [installed] xserver-xorg-core/disco,now 2:1.20.4-1ubuntu3 amd64 [installed] xserver-xorg/disco,now 1:7.7+19ubuntu12 amd64 [installed] inkscape/disco,now 0.92.4-3 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1853266/+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 1873996] Re: DevTools does not open at 84.0.4115.5
Ok. Should the upstream bug be closed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1873996
Title:
DevTools does not open at 84.0.4115.5
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
https://bugs.chromium.org/p/chromium/issues/detail?id=1071961
Steps to reproduce the problem:
1. Ctrl+Shift+I or right-click, click Inspect
2. Navigate to chrome://inspect/#pages, click inspect
3.
What is the expected behavior?
DevTools to open
What went wrong?
DevTools does not open.
Did this work before? Yes Chromium 83
Chrome version: 84.0.4115.5 Channel: dev
$ chromium-browser --temp-profile
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:600:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:787:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
error: gtk.css:1096:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1096:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1099:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4428:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4428:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4499:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4549:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error:
gtk.css:4549:12: Expected a string.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open i915 (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: i915
MESA-LOADER: failed to open kms_swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.195989:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.197368:ERROR:CONSOLE(70)] "Uncaught TypeError:
Cannot read property 'setInspectedTabId' of undefined", source:
devtools://devtools/bundled/devtools_compatibility.js (70)
** Message: 03:42:21.246: Remote error from secret
[Desktop-packages] [Bug 1845797] Re: Microphone not detected Lenovo Yoga S940
New report generated and new bug reported here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1880766 As now is not mic not detected, is the whole card not detected. -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+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 1880766] [NEW] PCI/internal sound card not detected
Public bug reported: Something got wrong with audio on my laptop, where for the first 6 weeks using Focal it was working ok, both sound and mic. Lenovo Yoga S940 Intel® Core™ i7-1065G7 CPU @ 1.30GHz × 8 Mesa Intel® Iris(R) Plus Graphics (ICL GT2) Ubuntu 20.04 focal $ uname -r 5.4.0-31-generic $ lspci | grep Audio 00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology Audio Controller (rev 30) $ aplay -l aplay: device_list:274: no soundcards found... $ cat /proc/asound/cards --- no soundcards --- This got worst from this: https://bugs.launchpad.net/linux/+bug/1845797 But for a while, all focal kernel until the last one, it was working properly, now the whole audio is gone despite lspci still see the Audio Controller. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 22:57:56 2020 InstallationDate: Installed on 2020-04-16 (40 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BQCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBQCN29WW:bd10/21/2019:svnLENOVO:pn81Q8:pvrLenovoYogaS940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IIL: dmi.product.family: Yoga S940-14IIL dmi.product.name: 81Q8 dmi.product.sku: LENOVO_MT_81Q8_BU_idea_FM_Yoga S940-14IIL dmi.product.version: Lenovo Yoga S940-14IIL dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "lspci -b -vv" https://bugs.launchpad.net/bugs/1880766/+attachment/5377118/+files/lspci -- 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/1880766 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Something got wrong with audio on my laptop, where for the first 6 weeks using Focal it was working ok, both sound and mic. Lenovo Yoga S940 Intel® Core™ i7-1065G7 CPU @ 1.30GHz × 8 Mesa Intel® Iris(R) Plus Graphics (ICL GT2) Ubuntu 20.04 focal $ uname -r 5.4.0-31-generic $ lspci | grep Audio 00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology Audio Controller (rev 30) $ aplay -l aplay: device_list:274: no soundcards found... $ cat /proc/asound/cards --- no soundcards --- This got worst from this: https://bugs.launchpad.net/linux/+bug/1845797 But for a while, all focal kernel until the last one, it was working properly, now the whole audio is gone despite lspci still see the Audio Controller. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 22:57:56 2020 InstallationDate: Installed on 2020-04-16 (40 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BQCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBQCN29WW:bd10/21/2019:svnLENOVO:pn81Q8:pvrLenovoYogaS940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IIL: dmi.product.family: Yoga S940-14IIL dmi.product.name: 81Q8 dmi.product.sku: LENOVO_MT_81Q8_BU_idea_FM_Yoga S940-14IIL dmi.product.version: Lenovo Yoga S940-14IIL dmi.sys.vendor: LENOVO To manage notifications
[Desktop-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"
** Branch linked: lp:~chromium-team/chromium-browser/xenial-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1868117 Title: [snap] Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1880508/+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 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1880508/+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 1875011] Re: package chromium-browser (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto chromium-browser script pre-installation ha restituito lo stat
*** This bug is a duplicate of bug 1875841 *** https://bugs.launchpad.net/bugs/1875841 ** This bug is no longer a duplicate of bug 1849119 package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: error: snap "chromium" has "install-snap" change in progress ** This bug has been marked a duplicate of bug 1875841 package chromium-browser 80.0.3987.163-0ubuntu1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1875011 Title: package chromium-browser (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto chromium-browser script pre-installation ha restituito lo stato di errore 10 Status in chromium-browser package in Ubuntu: Incomplete Bug description: from the app store chromium was not installed, while with apt it was installed but it still gave an error ProblemType: Package DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Apr 25 12:46:28 2020 ErrorMessage: il sottoprocesso nuovo pacchetto chromium-browser script pre-installation ha restituito lo stato di errore 10 InstallationDate: Installed on 2020-04-15 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto chromium-browser script pre-installation ha restituito lo stato di errore 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1875011/+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 1857889] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1875841 *** https://bugs.launchpad.net/bugs/1875841 ** This bug is no longer a duplicate of bug 1849119 package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: error: snap "chromium" has "install-snap" change in progress ** This bug has been marked a duplicate of bug 1875841 package chromium-browser 80.0.3987.163-0ubuntu1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1857889 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 Status in chromium-browser package in Ubuntu: Confirmed Bug description: snap "chromium" has "install-snap" change in progress ProblemType: Package DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Dec 30 21:28:41 2019 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-30 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1857889/+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 1849119] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: error: snap "chromium" has "install-snap" change in progress
*** This bug is a duplicate of bug 1875841 ***
https://bugs.launchpad.net/bugs/1875841
** This bug has been marked a duplicate of bug 1875841
package chromium-browser 80.0.3987.163-0ubuntu1 failed to install/upgrade:
new chromium-browser package pre-installation script subprocess returned error
exit status 10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849119
Title:
package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: error: snap "chromium" has "install-snap" change in
progress
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Showing system error
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 21 18:05:24 2019
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 10
InstallationDate: Installed on 2019-10-21 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.4
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849119/+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 1880267] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1875841 *** https://bugs.launchpad.net/bugs/1875841 This looks like an intermittent problem, whereby the chromium snap was already being installed. Can you try reinstalling chromium-browser? sudo apt install --reinstall chromium-browser and share the output here. ** This bug has been marked a duplicate of bug 1875841 package chromium-browser 80.0.3987.163-0ubuntu1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1880267 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 Status in chromium-browser package in Ubuntu: New Bug description: i am a newbie ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 AptOrdering: chromium-browser:amd64: Install flashplugin-installer:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 24 04:04:43 2020 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-05-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1880267/+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 1880261] Re: package chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e
Relevant error message (from DpkgTerminalLog.txt): error: cannot perform the following tasks: - Download snap "chromium" (1165) from channel "stable" (read tcp 192.168.1.28:52856->91.189.88.178:443: read: no route to host) This looks like a transient network failure. Can you please try reinstalling the package? sudo apt reinstall chromium-browser ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1880261 Title: package chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: Package chromium-browser did not install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 23 07:57:12 2020 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1880261/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"
** Branch linked: lp:~chromium-team/chromium-browser/bionic-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1868117 Title: [snap] Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap- from-source/commit/?id=c43fb4096ff701f80b2993b486931915f4e6c895 ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1868117 Title: [snap] Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1868117 Title: [snap] Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1880764] [NEW] Gnome sidebar freezes when dragging around icons while there is high memory pressure, but fails to resume when the memory pressure is down, causing icons stuck m
Public bug reported: When I was dragging around the discord icon around, Gnome froze and the icon remained in place. This was happening when I was compiling gettext and it was using memory. However, even after the compilation stopped and the memory went down, Gnome keeps the icons in place, refusing to finish what it started. In this state, the Grid button on the bottom has no effect, and clicking on the icons have no effect, though they will update when a new program launches or closes, and if a new window opens. I expect the Gnome Shell to become responsive once the memory has gone down. It has enough memory to finish the animations; it just won't finish them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 26 17:24:53 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-07 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-05-26 17-25-30.png" https://bugs.launchpad.net/bugs/1880764/+attachment/5377114/+files/Screenshot%20from%202020-05-26%2017-25-30.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/1880764 Title: Gnome sidebar freezes when dragging around icons while there is high memory pressure, but fails to resume when the memory pressure is down, causing icons stuck moving to remain in their position onscreen Status in gnome-shell package in Ubuntu: New Bug description: When I was dragging around the discord icon around, Gnome froze and the icon remained in place. This was happening when I was compiling gettext and it was using memory. However, even after the compilation stopped and the memory went down, Gnome keeps the icons in place, refusing to finish what it started. In this state, the Grid button on the bottom has no effect, and clicking on the icons have no effect, though they will update when a new program launches or closes, and if a new window opens. I expect the Gnome Shell to become responsive once the memory has gone down. It has enough memory to finish the animations; it just won't finish them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 26 17:24:53 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-07 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1880764/+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 1282294] Re: "Cannot open pixbuf loader module file"
Same here when upgrading 16.04 LTS to 18.04 The bug is six years old ? We should send it to preschool =) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+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 1876435] Re: package firefox-locale-pt 75.0~b11+build1-0ubuntu0.16.04.1 [origin: unknown] failed to install/upgrade: Versuch, »/usr/lib/firefox-addons/extensions/.xpi« zu übers
That PPA is used to build beta candidates of firefox, in preparation for actual releases. Unless you're willing to test unstable (and possibly uninstallable) packages and file bug reports for issues you encounter, you shouldn't be using it. If you do want to test and report issues, you're very welcome to do so, but beware that this may break your firefox installation in unintended ways, so don't do that on a production system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1876435 Title: package firefox-locale-pt 75.0~b11+build1-0ubuntu0.16.04.1 [origin: unknown] failed to install/upgrade: Versuch, »/usr/lib/firefox- addons/extensions/.xpi« zu überschreiben, welches auch in Paket firefox-locale-de 76.0~b8+build1-0ubuntu0.16.04.2 ist Status in firefox package in Ubuntu: Invalid Bug description: i got a crash while updatinf firefox by terminal command and a running firefox. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: firefox-locale-pt 75.0~b11+build1-0ubuntu0.16.04.1 [origin: unknown] ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 2455 F pulseaudio BuildID: 20200424000239 Channel: beta Date: Sat May 2 12:05:16 2020 Dependencies: DpkgHistoryLog: Start-Date: 2020-05-02 12:04:53 Commandline: apt full-upgrade -y Requested-By: thomas (1000) Upgrade: signal-desktop:amd64 (1.33.1, 1.33.4), google-chrome-stable:amd64 (81.0.4044.113-1, 81.0.4044.129-1), firefox-locale-de:amd64 (75.0~b11+build1-0ubuntu0.16.04.1, 76.0~b8+build1-0ubuntu0.16.04.2), firefox-locale-en:amd64 (75.0~b11+build1-0ubuntu0.16.04.1, 76.0~b8+build1-0ubuntu0.16.04.2), firefox-locale-pt:amd64 (75.0~b11+build1-0ubuntu0.16.04.1, 76.0~b8+build1-0ubuntu0.16.04.2), firefox:amd64 (75.0~b11+build1-0ubuntu0.16.04.1, 76.0~b8+build1-0ubuntu0.16.04.2), teamviewer:amd64 (15.4.4445, 15.5.3) ErrorMessage: Versuch, »/usr/lib/firefox-addons/extensions/.xpi« zu überschreiben, welches auch in Paket firefox-locale-de 76.0~b8+build1-0ubuntu0.16.04.2 ist ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-14 (1356 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 10.0.1.1 dev wlp3s0 proto static metric 600 10.0.1.0/24 dev wlp3s0 proto kernel scope link src 10.0.1.14 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox-locale-pt 75.0~b11+build1-0ubuntu0.16.04.1 [origin: unknown] failed to install/upgrade: Versuch, »/usr/lib/firefox-addons/extensions/.xpi« zu überschreiben, welches auch in Paket firefox-locale-de 76.0~b8+build1-0ubuntu0.16.04.2 ist UpgradeStatus: Upgraded to xenial on 2016-08-15 (1355 days ago) dmi.bios.date: 08/05/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.19 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 5730 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1876435/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
** Tags added: groovy
--
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/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-lib (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1877711] Re: Libreoffice snap can read but not save files over SSH
Trying to reproduce the issue, here are my findings: I have two focal systems on the same network: a host and a vm. The host has a test.odt file and the vm has the host's ip added to nautilus and can see the host's files (including test.odt). I double click on the test.odt icon which opens up libreoffice writer as expected but I have an error message saying that the file is locked for editing (see attached screenshot), even though the test.odt file is not open on the host. A workaround is to open a copy of the document, make edits, save it locally and then in nautilus on the vm you can move the file to the remote system to overwrite the file. The snap should however be able to save remote files directly. ** Attachment added: "lo-cannot-open-for-writing.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+attachment/5377097/+files/lo-cannot-open-for-writing.png ** Changed in: libreoffice (Ubuntu) Status: New => Triaged -- 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/1877711 Title: Libreoffice snap can read but not save files over SSH Status in libreoffice package in Ubuntu: Triaged Bug description: With Ubuntu 20.04 libreoffice can not anymore save files over SSH share. When trying to save, it says: Error saving the document. General Error. General input/output error. In addition, starting from Ubuntu 20.04 libreoffice has become very slow to start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+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 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
Well, similar experience for me today, booted and logged in okay, but
then the desktop session died leaving monitor backlight and keyboard
lights on, but no other sign of life. Shutting lid to suspend then
resume didn't help, had to hard power off. Then on next boot, it hung
after login, but recovered and was fine thereafter. More oddness, but
not the gpu in the blame this time.
Log sequence extracts:
May 26 09:28:03 xps2020 systemd[1]: Startup finished in 5.461s (firmware) +
3.431s (loader) + 14.216s (kernel) + 20.511s (userspace) = 43.620s.
...
May 26 09:29:14 xps2020 update-notifier.desktop[4555]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
May 26 09:29:14 xps2020 update-notifier.desktop[4555]: from gi.repository
import Gtk
May 26 09:29:14 xps2020 update-notifier.desktop[4555]: WARNING:root:timeout
reached, exiting
May 26 09:29:14 xps2020 gnome-session[1422]: gnome-session-binary[1422]:
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to
register before timeout
May 26 09:29:14 xps2020 gnome-session-binary[1422]: WARNING: Application
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
May 26 09:29:14 xps2020 gnome-session-binary[1422]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Color.desktop
May 26 09:29:14 xps2020 gnome-session[1422]: gnome-session-binary[1422]:
CRITICAL: We failed, but the fail whale is dead. Sorry
May 26 09:29:14 xps2020 gnome-session-binary[1422]: CRITICAL: We failed, but
the fail whale is dead. Sorry
...
May 26 09:29:15 xps2020 systemd[1]: Stopped User Manager for UID 121.
May 26 09:29:15 xps2020 systemd[1]: Removed slice User Slice of gdm.
May 26 09:29:54 xps2020 PackageKit[1605]: get-updates transaction /309_bcbe
from uid 1001 finished with success after 398ms
May 26 09:29:57 xps2020 org.gnome.Shell.desktop[3032]: ###!!!
[Parent][RunMessage] Error: Channel closing: too late to send/recv, messages
will be lost
May 26 09:29:57 xps2020 org.gnome.Shell.desktop[3032]: ###!!!
[Parent][RunMessage] Error: Channel closing: too late to send/recv, messages
will be lost
May 26 09:30:09 xps2020 systemd-logind[1187]: Lid closed.
May 26 09:30:09 xps2020 systemd-logind[1187]: Suspending...
...
May 26 09:30:13 xps2020 systemd-logind[1187]: Lid opened.
May 26 09:30:23 xps2020 systemd-logind[1187]: Power key pressed.
May 26 09:30:31 xps2020 systemd-logind[1187]: Power key pressed.
May 26 09:30:39 xps2020 systemd-logind[1187]: Delay lock is active (UID
1001/martin, PID 3032/gnome-shell) but inhibitor timeout is reached.
May 26 09:30:39 xps2020 systemd[1]: Starting TLP suspend/resume...
May 26 09:30:39 xps2020 systemd[1]: Started TLP suspend/resume.
May 26 09:30:39 xps2020 systemd[1]: Reached target Sleep.
May 26 09:30:39 xps2020 systemd[1]: Starting Suspend...
May 26 09:30:39 xps2020 systemd-sleep[4909]: Suspending system...
May 26 09:30:39 xps2020 kernel: PM: suspend entry (s2idle)
May 26 09:30:41 xps2020 kernel: PM: Syncing filesystems ... done.
May 26 09:30:41 xps2020 kernel: Freezing user space processes ... (elapsed
0.002 seconds) done.
May 26 09:30:41 xps2020 kernel: OOM killer disabled.
May 26 09:30:41 xps2020 kernel: Freezing remaining freezable tasks ... (elapsed
0.001 seconds) done.
May 26 09:30:41 xps2020 kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
May 26 09:30:41 xps2020 kernel: psmouse serio1: Failed to disable mouse on
isa0060/serio1
May 26 09:30:41 xps2020 kernel: PM: Some devices failed to suspend, or early
wake event detected
May 26 09:30:41 xps2020 kernel: OOM killer enabled.
May 26 09:30:41 xps2020 kernel: Restarting tasks ... done.
May 26 09:30:41 xps2020 kernel: thermal thermal_zone6: failed to read out
thermal zone (-61)
-- Reboot --
...
May 26 09:32:03 xps2020 systemd[1]: Startup finished in 5.443s
(firmware) + 3.530s (loader) + 11.642s (kernel) + 33.978s (userspace) =
54.594s.
...
May 26 09:33:37 xps2020 kernel: snd_hda_intel :00:1f.3: No response from
codec, resetting bus: last cmd=0x20170500
May 26 09:33:38 xps2020 kernel: snd_hda_intel :00:1f.3: No response from
codec, resetting bus: last cmd=0x20370500
May 26 09:33:39 xps2020 kernel: snd_hda_intel :00:1f.3: No response from
codec, resetting bus: last cmd=0x20470500
May 26 09:33:40 xps2020 gnome-session[2043]: gnome-session-binary[2043]:
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
May 26 09:33:40 xps2020 gnome-session-binary[2043]: WARNING: Application
'org.gnome.Shell.desktop' failed to register before timeout
May 26 09:33:40 xps2020 gnome-session-binary[2043]: Unrecoverable failure in
required component org.gnome.Shell.desktop
May 26 09:33:40 xps2020 gnome-session[2043]: gnome-session-binary[2043]:
CRITICAL: We failed, but the fail whale is
Re: [Desktop-packages] [Bug 1877670] Re: [Intel Braswell] Display Freezes and frequently mouse cursor disappears.
Hello, I'm attaching the prevboot.txt from my recent system freeze. On Thu, May 14, 2020 at 7:50 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please: > > 1. Wait until the system freezes again. > > 2. Reboot once only. > > 3. Run: > >journalctl -b-1 > prevboot.txt > >and attach the resulting text file here. > > > ** Summary changed: > > - Display Freezes and frequently mouse cursor disappears. > + [Intel Braswell] Display Freezes and frequently mouse cursor disappears. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877670 > > Title: > [Intel Braswell] Display Freezes and frequently mouse cursor > disappears. > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > Display Freezes and frequently mouse cursor disappears. After restart > mouse cursor comes back again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 > Uname: Linux 5.4.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat May 9 02:25:55 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] > InstallationDate: Installed on 2020-04-23 (14 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2a Intel Corp. >Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch > System >Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Acer Aspire R3-131T > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic > root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/30/2016 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V1.17 > dmi.board.name: Aspire R3-131T > dmi.board.vendor: Acer > dmi.board.version: V1.17 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.17 > dmi.modalias: > dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: > dmi.product.family: BSW > dmi.product.name: Aspire R3-131T > dmi.product.sku: Aspire R3-131T_1022_1.17 > dmi.product.version: V1.17 > dmi.sys.vendor: Acer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1877670/+subscriptions > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1877670/+attachment/5377096/+files/prevboot.txt -- 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/1877670 Title: [Intel Braswell] Display Freezes and frequently mouse cursor disappears. Status in xorg-server package in Ubuntu: Incomplete Bug description: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9
[Desktop-packages] [Bug 1880752] Re: German help does not show; message states access rights problem instead
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 ** This bug has been marked a duplicate of bug 1869561 Libreoffice Help does not work -- 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/1880752 Title: German help does not show; message states access rights problem instead Status in libreoffice package in Ubuntu: New Bug description: How to see the problem (on xubuntu 20.04, upgraded from 19.10): * LibreOffice installed, including (at first) the help packages libreoffice-help-en-us, libreoffice-help-en-gb, and libreoffice-help-de, running XFCE4 in a German localization setting. * Run LOWriter * Click on Help -> LibreOffice Help ... (or press F1) * Help window opens, but instead of showing the German language help, it claims there are access right problems preventing it of opening some object. After a quick search on the web I tried purging libreoffice-help-en- us, libreoffice-help-en-gb, but this didn't end the problem. Any suggestions? Kind regards Andreas ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-help-de 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 21:52:01 2020 InstallationDate: Installed on 2017-09-03 (996 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-18 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1880752/+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 1880752] [NEW] German help does not show; message states access rights problem instead
Public bug reported: How to see the problem (on xubuntu 20.04, upgraded from 19.10): * LibreOffice installed, including (at first) the help packages libreoffice-help-en-us, libreoffice-help-en-gb, and libreoffice-help-de, running XFCE4 in a German localization setting. * Run LOWriter * Click on Help -> LibreOffice Help ... (or press F1) * Help window opens, but instead of showing the German language help, it claims there are access right problems preventing it of opening some object. After a quick search on the web I tried purging libreoffice-help-en-us, libreoffice-help-en-gb, but this didn't end the problem. Any suggestions? Kind regards Andreas ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-help-de 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 21:52:01 2020 InstallationDate: Installed on 2017-09-03 (996 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-18 (7 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1880752 Title: German help does not show; message states access rights problem instead Status in libreoffice package in Ubuntu: New Bug description: How to see the problem (on xubuntu 20.04, upgraded from 19.10): * LibreOffice installed, including (at first) the help packages libreoffice-help-en-us, libreoffice-help-en-gb, and libreoffice-help-de, running XFCE4 in a German localization setting. * Run LOWriter * Click on Help -> LibreOffice Help ... (or press F1) * Help window opens, but instead of showing the German language help, it claims there are access right problems preventing it of opening some object. After a quick search on the web I tried purging libreoffice-help-en- us, libreoffice-help-en-gb, but this didn't end the problem. Any suggestions? Kind regards Andreas ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-help-de 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 21:52:01 2020 InstallationDate: Installed on 2017-09-03 (996 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-18 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1880752/+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 1880416] Re: libreoffice symbol bars/toolbars load and react with very high latency
Thank you for your bug report! Well we could consider re-adding the SAL_USE_VCLPLUGIN=gen back (like this [0]) but there would be significant testing required on the more common graphics systems, like AMD Radeon and Intel, to make sure this change doesn't affect the performance on those systems. It seems the AMD Picasso graphics are quite new [1] so this is something that should be fixed eventually but is not a high priority. [0] https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/89c9b6e690836024d12dd7010bb5609a361119d6 [1] https://www.techpowerup.com/gpu-specs/radeon-picasso.c3286 ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low ** Changed in: libreoffice (Ubuntu) Status: New => Triaged -- 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/1880416 Title: libreoffice symbol bars/toolbars load and react with very high latency Status in libreoffice package in Ubuntu: Triaged Bug description: Latency disappears when setting envirionment variable SAL_USE_VCLPLUGIN to 'gen' (This overrides the autodetect of libreoffice for which desktop the interface has to be renderd and switch to gerneric) Using Gnome, default for this variable im my case is 'gtk3': With default SAL_USE_VCLPLUGIN=gtk3 menu bar and toolbars will need more than 10 Seconds to be displayed after application startup - while editor-window is displayed immediately. While running the application latency between clicking an item and reaction is also abnormal high. As example: Clicking "Save as ..." results in waiting for some seconds until the "Save as ..."-dialog appears. This bug does not appear with my systems using intel-igpu. It only affects the machine with amd picasso-igpu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun May 24 17:25:42 2020 InstallationDate: Installed on 2020-05-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1880416/+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 1880411] Re: right super key does not show the overlay
Here is it. I put a red circle on it so you can find it better. ** Attachment added: "right super key.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880411/+attachment/5377078/+files/right%20super%20key.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/1880411 Title: right super key does not show the overlay Status in gnome-shell package in Ubuntu: Invalid Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880411/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 + https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1274 https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880742/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+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 1880744] [NEW] package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git
Public bug reported: Hey, I upgraded to ubuntu 20 and a red little minus sign popped up on my top right corner about unmet package dependencies. I have tried all the commands like "sudo dpkg --configure -a" "sudo apt install -f" but nothing seems to solve my problem. This is a big problem because I cant install new packages on my laptop without solving this first. Please reply as soon as possible. The error message: You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: emacs : Depends: emacs-gtk (>= 1:26.3) but it is not installed or emacs-lucid (>= 1:26.3) but it is not installed or emacs-nox (>= 1:26.3) but it is not installed emacs-bin-common : Depends: emacs-common (= 1:26.3+1-1ubuntu2) but it is not installed emacs-el : Depends: emacs-common (= 1:26.3+1-1ubuntu2) but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs-gtk (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: emacs-common:amd64: Install emacs-gtk:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 26 20:45:47 2020 ErrorMessage: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git96dd019-kk1+19.10 InstallationDate: Installed on 2020-04-20 (35 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: emacs Title: package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git96dd019-kk1+19.10 UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1880744 Title: package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git96dd019-kk1+19.10 Status in emacs package in Ubuntu: New Bug description: Hey, I upgraded to ubuntu 20 and a red little minus sign popped up on my top right corner about unmet package dependencies. I have tried all the commands like "sudo dpkg --configure -a" "sudo apt install -f" but nothing seems to solve my problem. This is a big problem because I cant install new packages on my laptop without solving this first. Please reply as soon as possible. The error message: You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: emacs : Depends: emacs-gtk (>= 1:26.3) but it is not installed or emacs-lucid (>= 1:26.3) but it is not installed or emacs-nox (>= 1:26.3) but it is not installed emacs-bin-common : Depends: emacs-common (= 1:26.3+1-1ubuntu2) but it is not installed emacs-el : Depends: emacs-common (= 1:26.3+1-1ubuntu2) but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs-gtk (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: emacs-common:amd64: Install emacs-gtk:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 26 20:45:47 2020 ErrorMessage: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git96dd019-kk1+19.10 InstallationDate: Installed on 2020-04-20 (35 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: emacs Title: package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git96dd019-kk1+19.10 UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1880744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 + + --- + I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2840 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 -- 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/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+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 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
** Information type changed from Private to Public -- 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/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() Status in gnome-shell package in Ubuntu: New Bug description: I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+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 1480207] Re: eog (a GNOME image viewer) doesn't support HiDPI display.
This is actually a GNOME issue, so commented on their issue tracker at https://gitlab.gnome.org/GNOME/eog/-/issues/63 ** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #63 https://gitlab.gnome.org/GNOME/eog/-/issues/63 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1480207 Title: eog (a GNOME image viewer) doesn't support HiDPI display. Status in Eye of GNOME: Confirmed Status in eog package in Ubuntu: Triaged Bug description: Ubuntu 14.04.2 Reproducible Steps: 1. Login Unity desktop environment. 2. Change the scale factor to 2 in Displays of System Settings. 3. Open any image by eog with 1:1 mode on HiDPI display, such Dell new XPS (2015) 13 9343. Expected Result: * The image won't become blurred. Actual Result: * The image becomes blurred. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1480207/+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 1480207] Re: eog (a GNOME image viewer) doesn't support HiDPI display.
To add to this, the zoom factor is doubled (halved?). That is, when the zoom is set to 100% it's actually displaying the image at 200% resolution. To see the image at it's correct size the zoom must be set to 50%. ** Attachment added: "Example of 50% zoom rendering at (actuall) 100% resolution" https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1480207/+attachment/5377047/+files/Screenshot%202020-05-26%2010%3A37%3A47.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1480207 Title: eog (a GNOME image viewer) doesn't support HiDPI display. Status in Eye of GNOME: Confirmed Status in eog package in Ubuntu: Triaged Bug description: Ubuntu 14.04.2 Reproducible Steps: 1. Login Unity desktop environment. 2. Change the scale factor to 2 in Displays of System Settings. 3. Open any image by eog with 1:1 mode on HiDPI display, such Dell new XPS (2015) 13 9343. Expected Result: * The image won't become blurred. Actual Result: * The image becomes blurred. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1480207/+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 1480207] Re: eog (a GNOME image viewer) doesn't support HiDPI display.
And in case it wasn't clear, this is still an issue in Ubuntu 20.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1480207 Title: eog (a GNOME image viewer) doesn't support HiDPI display. Status in Eye of GNOME: Confirmed Status in eog package in Ubuntu: Triaged Bug description: Ubuntu 14.04.2 Reproducible Steps: 1. Login Unity desktop environment. 2. Change the scale factor to 2 in Displays of System Settings. 3. Open any image by eog with 1:1 mode on HiDPI display, such Dell new XPS (2015) 13 9343. Expected Result: * The image won't become blurred. Actual Result: * The image becomes blurred. To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1480207/+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 1880739] [NEW] Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Public bug reported: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- 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/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 Status in mutter package in Ubuntu: New Bug description: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+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 1880337] Re: Screen lock won't work
No I can't. I see screen freeze, then timing out and then blank default color and immediately after that unfreeze -- 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/1880337 Title: Screen lock won't work Status in gnome-shell package in Ubuntu: Confirmed Bug description: Screen lock won't work i focal. Used to work fine on Super-L and now what happens it freezes for awhile (suspect time out defined) and then blinks and comes back into windows session. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gdm3 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+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 1880337] Re: Screen lock won't work
I am seeing this exact behavior as well. In my case, hitting Super-L will blank the screen for a half second, and when it comes back, all of my hidden windows (windows behind other windows) have been brought forward. I need to repeat this process and hit Super-L a total of four times before I see the lockscreen. Yuri, are you able to lock the desktop at all by hitting Super-L several times? -- 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/1880337 Title: Screen lock won't work Status in gnome-shell package in Ubuntu: Confirmed Bug description: Screen lock won't work i focal. Used to work fine on Super-L and now what happens it freezes for awhile (suspect time out defined) and then blinks and comes back into windows session. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (46 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gdm3 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2020-04-16T12:53:22.919694 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+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 1880723] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1880723/+attachment/5377029/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: New Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569 3 54115 27576 recvmsg 35.250.190224 3 53266 poll 26.920.145275 5 26592 writev 0.300.001631 4 405 write 0.230.001245 5 248 mprotect 0.230.001229 9 136 close 0.210.001120 1 621 ioctl 0.160.000889 6 136 timerfd_create 0.130.000711 5 136 timerfd_settime 0.060.000328 1 300 getpid 0.030.000180 268 3 futex 0.030.000159 185 read 0.010.53 8 6 sendmsg 0.010.27 3 9
