[Desktop-packages] [Bug 2063965] Re: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error
** Changed in: sgml-base (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/2063965 Title: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error Status in sgml-base package in Ubuntu: Invalid Bug description: Summary: Running `sudo apt install libpam-mount` I get ``` pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating. pam-auth-update: Run pam-auth-update --force to override. Setting up libpam-mount-bin (2.19-1) ... Processing triggers for libc-bin (2.38-1ubuntu6.2) ... Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: sgml-base E: Sub-process /usr/bin/dpkg returned an error code (1) ``` Plus apport-gtk pop-up My `/etc/pam.d/common-authentication` is modified. 1) Release ```$ lsb_release -r Release: 23.10 ``` 2) Package version ```$ apt-cache policy sgml-base libpam-mount sgml-base: Installed: 1.31 Candidate: 1.31 Version table: *** 1.31 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status 1.30 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu jammy/main i386 Packages libpam-mount: Installed: 2.19-1 Candidate: 2.19-1 Version table: *** 2.19-1 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status 2.18-2build2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` 3) What is expected Usually in this situation I get a dpkg prompt saying something like "package maintainer provided a different configuration file" and asking me which version of the configuration file. Or to see the differences. Some file are then saved and `NAME.dpkg-new`/`NAME.dpkg- old`. This way I can install the module and care about editing `/etc/pam.d/common-auth` later. 4) What happened See error above ProblemType: Package DistroRelease: Ubuntu 23.10 Package: sgml-base 1.31 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 AptOrdering: libhx32:amd64: Install libpam-mount:amd64: Install libpam-mount-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 27 20:54:15 2024 ErrorMessage: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2023-04-23 (370 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.31 failed to install/upgrade: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 UpgradeStatus: Upgraded to mantic on 2023-10-20 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063965] Re: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error
** Attachment removed: "Df.txt" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+attachment/5771676/+files/Df.txt ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+attachment/5771677/+files/Dmesg.txt ** Attachment removed: "DpkgHistoryLog.txt" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+attachment/5771678/+files/DpkgHistoryLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/2063965 Title: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error Status in sgml-base package in Ubuntu: New Bug description: Summary: Running `sudo apt install libpam-mount` I get ``` pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating. pam-auth-update: Run pam-auth-update --force to override. Setting up libpam-mount-bin (2.19-1) ... Processing triggers for libc-bin (2.38-1ubuntu6.2) ... Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: sgml-base E: Sub-process /usr/bin/dpkg returned an error code (1) ``` Plus apport-gtk pop-up My `/etc/pam.d/common-authentication` is modified. 1) Release ```$ lsb_release -r Release: 23.10 ``` 2) Package version ```$ apt-cache policy sgml-base libpam-mount sgml-base: Installed: 1.31 Candidate: 1.31 Version table: *** 1.31 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status 1.30 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu jammy/main i386 Packages libpam-mount: Installed: 2.19-1 Candidate: 2.19-1 Version table: *** 2.19-1 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status 2.18-2build2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` 3) What is expected Usually in this situation I get a dpkg prompt saying something like "package maintainer provided a different configuration file" and asking me which version of the configuration file. Or to see the differences. Some file are then saved and `NAME.dpkg-new`/`NAME.dpkg- old`. This way I can install the module and care about editing `/etc/pam.d/common-auth` later. 4) What happened See error above ProblemType: Package DistroRelease: Ubuntu 23.10 Package: sgml-base 1.31 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 AptOrdering: libhx32:amd64: Install libpam-mount:amd64: Install libpam-mount-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 27 20:54:15 2024 ErrorMessage: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2023-04-23 (370 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.31 failed to install/upgrade: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 UpgradeStatus: Upgraded to mantic on 2023-10-20 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2063965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063965] [NEW] package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error
Public bug reported: Summary: Running `sudo apt install libpam-mount` I get ``` pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating. pam-auth-update: Run pam-auth-update --force to override. Setting up libpam-mount-bin (2.19-1) ... Processing triggers for libc-bin (2.38-1ubuntu6.2) ... Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: sgml-base E: Sub-process /usr/bin/dpkg returned an error code (1) ``` Plus apport-gtk pop-up My `/etc/pam.d/common-authentication` is modified. 1) Release ```$ lsb_release -r Release:23.10 ``` 2) Package version ```$ apt-cache policy sgml-base libpam-mount sgml-base: Installed: 1.31 Candidate: 1.31 Version table: *** 1.31 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status 1.30 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu jammy/main i386 Packages libpam-mount: Installed: 2.19-1 Candidate: 2.19-1 Version table: *** 2.19-1 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status 2.18-2build2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` 3) What is expected Usually in this situation I get a dpkg prompt saying something like "package maintainer provided a different configuration file" and asking me which version of the configuration file. Or to see the differences. Some file are then saved and `NAME.dpkg-new`/`NAME.dpkg-old`. This way I can install the module and care about editing `/etc/pam.d/common-auth` later. 4) What happened See error above ProblemType: Package DistroRelease: Ubuntu 23.10 Package: sgml-base 1.31 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 AptOrdering: libhx32:amd64: Install libpam-mount:amd64: Install libpam-mount-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 27 20:54:15 2024 ErrorMessage: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 InstallationDate: Installed on 2023-04-23 (370 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.31 failed to install/upgrade: il sottoprocesso installato pacchetto sgml-base script post-installation ha restituito lo stato di errore 2 UpgradeStatus: Upgraded to mantic on 2023-10-20 (190 days ago) ** Affects: sgml-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/2063965 Title: package sgml-base 1.31 failed to install/upgrade: Local modifications to /etc/pam.d/common-* triggered dpkg error Status in sgml-base package in Ubuntu: New Bug description: Summary: Running `sudo apt install libpam-mount` I get ``` pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating. pam-auth-update: Run pam-auth-update --force to override. Setting up libpam-mount-bin (2.19-1) ... Processing triggers for libc-bin (2.38-1ubuntu6.2) ... Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: sgml-base E: Sub-process /usr/bin/dpkg returned an error code (1) ``` Plus apport-gtk pop-up My `/etc/pam.d/common-authentication` is modified. 1) Release ```$ lsb_release -r Release: 23.10 ``` 2) Package version ```$ apt-cache policy sgml-base libpam-mount sgml-base: Installed: 1.31 Candidate: 1.31 Version table: *** 1.31 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status 1.30 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu jammy/main i386 Packages libpam-mount: Installed: 2.19-1 Candidate: 2.19-1 Version table: *** 2.19-1 500 500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status 2.18-2build2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ``` 3) What is expected Usually in this situation I get a dpkg prompt saying something like "package maintainer provided a
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
I can confirm this is still happening in mantic, using the following versions: chromium 118.0.5993.88 fonts-ubuntu 0.869-0ubuntu1 -- 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/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031232] Re: Thunderbird 115 Snap Version in Ubuntu 22.04 - does not send email nor saves drafts
Hi, I don't have records, but I can say I don't have any non conventional encryption method. When I tried to install under SNAP, I noticed the data folder had been moved to the Snap area. I tried to make the import with the Thunderbird tool and it was ultimately successful. But then I discovered the issue of not sending emails. Therefore I tried to move the personal folder out of the Snap area and load it editing the ini file hoping it was an issue with the snap folders rights. That did not work as well with the same symptoms of not being able to write. For time reasons I had to give up. Now fortunately Thunderbird has updated via repository and I'm able to use everything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2031232 Title: Thunderbird 115 Snap Version in Ubuntu 22.04 - does not send email nor saves drafts Status in thunderbird package in Ubuntu: Incomplete Bug description: I've tried to install via Snap Store in Ubuntu 22.04 the new released Thunderbird 115. I've successfully imported my old profile from Thunderbird 102 (switching it to the new location in Snap path). Email download works flawlessly and the system looks good. However, with whatever account I try to send emails I get "Impossible to send message". Moreover it also does not save into the draft folder with a similar message. I made all the standard checks refreshing passwords of SMTP. Nothing was successful. I tried to link to my account on a fresh install, but still not possible to send messages. I'm inclined to think there is an issue with Snap space. But I can't troubleshoot on it because I am not expert enough. Any hint? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2031232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] Ubuntu font with normal weight displayed incorrectly in Google Docs after upgrading to Lunar
** Attachment added: "Lunar_font_test_Firefox_112.0.2-1.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+attachment/5671998/+files/Lunar_font_test_Firefox_112.0.2-1.png -- 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/2019045 Title: [snap] Ubuntu font with normal weight displayed incorrectly in Google Docs after upgrading to Lunar Status in chromium-browser package in Ubuntu: New Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] [NEW] [snap] Ubuntu font with normal weight displayed incorrectly in Google Docs after upgrading to Lunar
Public bug reported: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Lunar_font_test_Chromium_112.0.5615.49.png" https://bugs.launchpad.net/bugs/2019045/+attachment/5671997/+files/Lunar_font_test_Chromium_112.0.5615.49.png -- 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/2019045 Title: [snap] Ubuntu font with normal weight displayed incorrectly in Google Docs after upgrading to Lunar Status in chromium-browser package in Ubuntu: New Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990563] Re: Some maximized/fullscreen windows appear on both monitors
Problem is that there are so far no plans to release it for 22.10. It seems 23.04 will indeed have to 43.2 https://code.launchpad.net/ubuntu/+source/mutter Let's hope it fixes it, or another year-long iteration will be necessary. -- 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/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1680750] Re: pm-hibernate does nothing at all
Do you find something in /var/log/pm-suspend.log ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1680750 Title: pm-hibernate does nothing at all Status in pm-utils package in Ubuntu: Confirmed Bug description: I have run from a command line: # sudo pm-hibernate and NOTHING f***ing happens. Usually it works (except for lots of issues on resume), but now I have tried it twice and it does nothing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: powerman (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 7 10:47:47 2017 InstallationDate: Installed on 2013-10-11 (1273 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: powerman UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1680750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990563] Re: Some maximized/fullscreen windows appear on both monitors
I can see here that there are no updates to 43.1 for ubuntu https://code.launchpad.net/ubuntu/+source/mutter And lunar is using 43.0 as well. -- 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/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990563] Re: Some maximized/fullscreen windows appear on both monitors
43.1 seems to exist at https://gitlab.gnome.org/GNOME/mutter/-/tags Does anybody have a package to see if it actually fixes it? -- 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/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995773] Re: Citrix fullscreen on wayland: bad rendering
This is what the window should look like. if I press ALT-TAB the problem goes away temporary, till I click and it goes bad again. ** Attachment added: "Correct screen (after ALT-TAB)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1995773/+attachment/5629325/+files/20221105_192750.jpg ** Description changed: I have just updated from 22.04 to 22.10 and the Citrix Workspace app is now unable to work full screen properly. This happens only on 22.10+Wayland with Citrix 2209 and 2207. What happens is that the window goes fullscreen over 2 monitors, but one of them quickly becomes a mirror of the other one. On Xorg everything works as expected. My 2 screen do not have the same size, but this has never caused any issues. Citrix workspace is basically a remote desktop app, so what you can see in the pictures is the remote Windows 10 desktop. The window is sometimes rendered correctly, but as soon as I interact with it (mouse), the 2nd screen becomes a copy of the first (and being a - big bigger, has a bit extra on it). + bit bigger, has a bit extra on it). I noticed that if I press ALT-SPACE, the window is rendered correctly (as you can see in the 2nd picture), but again, as soon as I click, the 2nd screen is lost. The application works as if the window was rendered correctly: I can tell it by locating an object with ALT-SPACE, then hitting it with the mouse, it works as expected. Problem is that I cannot see it. I tried to change position of the screen, change the primary one, change the cable, nothing. I have just tried as well Fedora 37 Beta Live and it behaves exactly the same. -- 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/1995773 Title: Citrix fullscreen on wayland: bad rendering Status in mutter package in Ubuntu: New Bug description: I have just updated from 22.04 to 22.10 and the Citrix Workspace app is now unable to work full screen properly. This happens only on 22.10+Wayland with Citrix 2209 and 2207. What happens is that the window goes fullscreen over 2 monitors, but one of them quickly becomes a mirror of the other one. On Xorg everything works as expected. My 2 screen do not have the same size, but this has never caused any issues. Citrix workspace is basically a remote desktop app, so what you can see in the pictures is the remote Windows 10 desktop. The window is sometimes rendered correctly, but as soon as I interact with it (mouse), the 2nd screen becomes a copy of the first (and being a bit bigger, has a bit extra on it). I noticed that if I press ALT-SPACE, the window is rendered correctly (as you can see in the 2nd picture), but again, as soon as I click, the 2nd screen is lost. The application works as if the window was rendered correctly: I can tell it by locating an object with ALT-SPACE, then hitting it with the mouse, it works as expected. Problem is that I cannot see it. I tried to change position of the screen, change the primary one, change the cable, nothing. I have just tried as well Fedora 37 Beta Live and it behaves exactly the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1995773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995773] [NEW] Citrix fullscreen on wayland: bad rendering
Public bug reported: I have just updated from 22.04 to 22.10 and the Citrix Workspace app is now unable to work full screen properly. This happens only on 22.10+Wayland with Citrix 2209 and 2207. What happens is that the window goes fullscreen over 2 monitors, but one of them quickly becomes a mirror of the other one. On Xorg everything works as expected. My 2 screen do not have the same size, but this has never caused any issues. Citrix workspace is basically a remote desktop app, so what you can see in the pictures is the remote Windows 10 desktop. The window is sometimes rendered correctly, but as soon as I interact with it (mouse), the 2nd screen becomes a copy of the first (and being a bit bigger, has a bit extra on it). I noticed that if I press ALT-SPACE, the window is rendered correctly (as you can see in the 2nd picture), but again, as soon as I click, the 2nd screen is lost. The application works as if the window was rendered correctly: I can tell it by locating an object with ALT-SPACE, then hitting it with the mouse, it works as expected. Problem is that I cannot see it. I tried to change position of the screen, change the primary one, change the cable, nothing. I have just tried as well Fedora 37 Beta Live and it behaves exactly the same. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bad fullscreen" https://bugs.launchpad.net/bugs/1995773/+attachment/5629324/+files/20221105_192742.jpg -- 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/1995773 Title: Citrix fullscreen on wayland: bad rendering Status in mutter package in Ubuntu: New Bug description: I have just updated from 22.04 to 22.10 and the Citrix Workspace app is now unable to work full screen properly. This happens only on 22.10+Wayland with Citrix 2209 and 2207. What happens is that the window goes fullscreen over 2 monitors, but one of them quickly becomes a mirror of the other one. On Xorg everything works as expected. My 2 screen do not have the same size, but this has never caused any issues. Citrix workspace is basically a remote desktop app, so what you can see in the pictures is the remote Windows 10 desktop. The window is sometimes rendered correctly, but as soon as I interact with it (mouse), the 2nd screen becomes a copy of the first (and being a bit bigger, has a bit extra on it). I noticed that if I press ALT-SPACE, the window is rendered correctly (as you can see in the 2nd picture), but again, as soon as I click, the 2nd screen is lost. The application works as if the window was rendered correctly: I can tell it by locating an object with ALT-SPACE, then hitting it with the mouse, it works as expected. Problem is that I cannot see it. I tried to change position of the screen, change the primary one, change the cable, nothing. I have just tried as well Fedora 37 Beta Live and it behaves exactly the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1995773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I have found a (dirty?) workaround for this. The idea is simple: use a
udev rule to suspend the laptop before UPower shuts it down. This can be
done by creating a file /etc/udev/rules.d/99-lowbat.rules with the
following content:
# Suspend the system when battery level drops to 5% or lower
SUBSYSTEM=="power_supply", ATTR{status}=="Discharging",
ATTR{capacity}=="[0-5]", RUN+="/usr/bin/systemctl suspend"
You can of course tune the threshold.
This method seems to work well for me. If you want to use a threshold
that's lower than the UPower one, *I think* you could set the
PercentageAction parameter to 0% or 1% in /etc/UPower/UPower.conf,
although I'm not 100% sure this is a good idea (the disclaimer at the
beginning of the file seems to discourage users from directly modifying
the file).
Reference:
https://wiki.archlinux.org/title/laptop#Hibernate_on_low_battery_level
On a side note, I definitely wish this bug could be addressed. It's not normal
that a computer just shuts down and makes you lose your work when there's still
battery. Also note that afaik there's currently no way to enable hibernation
with full disk encryption, so this limitation of UPower will become
increasingly serious as more and more users will make the (right) choice to use
FDE.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
Status in Upower:
New
Status in upower package in Ubuntu:
Triaged
Bug description:
The action to take when the battery is critical can only be one of the
following:
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
Adding Suspend to that list makes perfect sense. My laptop is
currently powering off on low power which is useless as I'll be losing
my work anyway. Might as well suspend and allow me to notice that and
connect a charger. If the thinking is that suspend uses power I can
set a high enough threshold to give me some margin.
The failovers are:
# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used
I'd argue Suspend should actually come before PowerOff in that list.
For most laptop users having their computer suspend because they
didn't notice the battery was running out is very easy to fix and
takes no time. They'll just connect the charger. If however the
computer needs to be completely rebooted, not only does that take a
lot more time it will very likely cause lost work.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: upower 0.99.10-1
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 17 14:32:13 2019
InstallationDate: Installed on 2019-05-09 (191 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Also, a few comments for debugging: 0. I agree that this is a pretty nasty bug for usability on an LTS release, it doesn't give a very professional feeling (which is too bad as otherwise Ubuntu 22.04 is amazing). 1. Not all windows end up underneath the dock, only some (and I can't identify a pattern). 2. I can't reliably reproduce the issue. On my setup it doesn't happen every time I unlock the screen, and it seems to happen less frequently in the first few unlocks after a full system restart. It gets worse after a few hours/days of system usage. 3. I'm not sure, but I have the feeling this might be related to the fact that I often switch between two displays (the laptop's one and an external one, with same resolution 1920x1200). I always use a single display but I use the laptop's one when I'm not at my desk. I have the impression that if I always use the same display, the issue does arise. (note that the issue does *not* come up only when I lock on one screen and unlock on the other one) 4. Every time I unlock the screen, it looks like there's always some flickering under the dock for the first few milliseconds. This seems to happen even when the bug does not arise, but it does look suspicious. Hypothesis: the position of the windows is reset every time after a screen unlock, and sometimes it happens that some windows are "left behind". -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
I'm experiencing the same bug on Ubuntu 22.04. I have found a semi- workaround: moving the dock to the other side of the screen and back fixes the positions of all the windows, and this can be done quickly with a custom keyboard shortcut that executes the following script: #!/bin/bash gsettings set org.gnome.shell.extensions.dash-to-dock dock-position 'RIGHT' sleep 1 gsettings set org.gnome.shell.extensions.dash-to-dock dock-position 'LEFT' (make sure you make the script executable and then just use the script's path in the "Command" field in Custom Shortcuts) Of course this is still super annoying as it requires manual intervention every time you unlock the screen, but it's still much better than having to manually fix the position of *each* window. -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Also affects: network-manager (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: urfkill (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in urfkill package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in network-manager source package in Jammy: Invalid Status in urfkill source package in Jammy: New Status in linux source package in Kinetic: Invalid Status in network-manager source package in Kinetic: Invalid Status in urfkill source package in Kinetic: New Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981716] Re: bbswitch fails to build on 5.19 kernel (kinetic)
** Also affects: bbswitch (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1981716 Title: bbswitch fails to build on 5.19 kernel (kinetic) Status in bbswitch package in Ubuntu: New Status in bbswitch source package in Kinetic: New Bug description: [Impact] bbswitch fails to build with the latest 5.19 kernel, the error is the following: /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:273:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] 273 | r = acpi_bus_get_device(dis_handle, ); | ^~~ | acpi_is_pnp_device cc1: some warnings being treated as errors [Test case] $ sudo apt install bbswitch-dkms [Fix] Replace acpi_bus_get_device() with the equivalent interface - acpi_fetch_acpi_dev() - in 5.19 kernels. [Regression potential] We may see bbswitch regressions in kernels >= 5.19 (fix isn't affecting older kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1981716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981716] Re: bbswitch fails to build on 5.19 kernel (kinetic)
Fix to support 5.19 kernels in attach. ** Patch added: "bbswitch-support-kernel-5.19.debdiff" https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1981716/+attachment/5603157/+files/bbswitch-support-kernel-5.19.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1981716 Title: bbswitch fails to build on 5.19 kernel (kinetic) Status in bbswitch package in Ubuntu: New Bug description: [Impact] bbswitch fails to build with the latest 5.19 kernel, the error is the following: /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:273:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] 273 | r = acpi_bus_get_device(dis_handle, ); | ^~~ | acpi_is_pnp_device cc1: some warnings being treated as errors [Test case] $ sudo apt install bbswitch-dkms [Fix] Replace acpi_bus_get_device() with the equivalent interface - acpi_fetch_acpi_dev() - in 5.19 kernels. [Regression potential] We may see bbswitch regressions in kernels >= 5.19 (fix isn't affecting older kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1981716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981716] [NEW] bbswitch fails to build on 5.19 kernel (kinetic)
Public bug reported: [Impact] bbswitch fails to build with the latest 5.19 kernel, the error is the following: /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:273:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] 273 | r = acpi_bus_get_device(dis_handle, ); | ^~~ | acpi_is_pnp_device cc1: some warnings being treated as errors [Test case] $ sudo apt install bbswitch-dkms [Fix] Replace acpi_bus_get_device() with the equivalent interface - acpi_fetch_acpi_dev() - in 5.19 kernels. [Regression potential] We may see bbswitch regressions in kernels >= 5.19 (fix isn't affecting older kernels). ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1981716 Title: bbswitch fails to build on 5.19 kernel (kinetic) Status in bbswitch package in Ubuntu: New Bug description: [Impact] bbswitch fails to build with the latest 5.19 kernel, the error is the following: /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:273:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] 273 | r = acpi_bus_get_device(dis_handle, ); | ^~~ | acpi_is_pnp_device cc1: some warnings being treated as errors [Test case] $ sudo apt install bbswitch-dkms [Fix] Replace acpi_bus_get_device() with the equivalent interface - acpi_fetch_acpi_dev() - in 5.19 kernels. [Regression potential] We may see bbswitch regressions in kernels >= 5.19 (fix isn't affecting older kernels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1981716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
Here is another one. When I finally got back inside (with both screens working) it was 16:57:15. ** Attachment added: "journal.zip" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5589849/+files/journal.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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
Hi it happened again. This time pretty bad, the monitor did not wake up, even after various Ctrl-Alt-F. But after I switched it off-on, it worked. I was able to login using the other monitor and I immediately check the time: 18:23:37. The other monitor finally came back after that time. I attach the journal file. ** Attachment added: "journal.zip" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5589626/+files/journal.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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
I would like to amend the description of the problem. It happened twice today. I press a kew, and the screen comes back, with the password request, but it is "frozen". If I move the mouse, it only moves on the other screen, and no typing happens. After doing some Ctrl-Alt-F. I land on the "select users" screen and it works again. -- 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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] Re: One screen does not come back from lock
Still on wayland ** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+attachment/5587892/+files/journal.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/1972059 Title: One screen does not come back from lock Status in mutter package in Ubuntu: Incomplete Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972059] [NEW] One screen does not come back from lock
Public bug reported: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/1972059 Title: One screen does not come back from lock Status in xorg package in Ubuntu: New Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10
[Desktop-packages] [Bug 1971593] Re: make wireless-tools a dependency for network-manager
** Description changed: The wpa-dhclient autopkgtest is always failing without wireless-tools - installed. Maybe wireless-tools should be an explicit dependency of - network-manager. + installed. Maybe wireless-tools should be added to the test dependencies + (debian/tests/control). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971593 Title: make wireless-tools a dependency for network-manager Status in network-manager package in Ubuntu: New Bug description: The wpa-dhclient autopkgtest is always failing without wireless-tools installed. Maybe wireless-tools should be added to the test dependencies (debian/tests/control). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971593] [NEW] make wireless-tools a dependency for network-manager
Public bug reported: The wpa-dhclient autopkgtest is always failing without wireless-tools installed. Maybe wireless-tools should be an explicit dependency of network-manager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971593 Title: make wireless-tools a dependency for network-manager Status in network-manager package in Ubuntu: New Bug description: The wpa-dhclient autopkgtest is always failing without wireless-tools installed. Maybe wireless-tools should be an explicit dependency of network-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956434] [NEW] bbswitch-dkms: drop support for armhf and ppc64el
Public bug reported: [Impact] bbswitch is a kernel module that is supposed to detect certain ACPI calls and toggle power on NVIDIA optimus video cards. There is no reason to provide this feature on architectures that don't have an ACPI bus. This will also prevent potential build failures in the future. [Test case] On armhf or ppc64el: apt install bbswitch-dkms ... ERROR: modpost: "acpi_root_dir" [/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko] undefined! [Fix] Simply drop support for armhf and ppc64el. [Regression potential] This module won't be available if there's any "special" armhf or ppc64el system with an NVIDIA optimus card (I doubt a system like this will ever exist). ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New ** Affects: bbswitch (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: bbswitch (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1956434 Title: bbswitch-dkms: drop support for armhf and ppc64el Status in bbswitch package in Ubuntu: New Status in bbswitch source package in Jammy: New Bug description: [Impact] bbswitch is a kernel module that is supposed to detect certain ACPI calls and toggle power on NVIDIA optimus video cards. There is no reason to provide this feature on architectures that don't have an ACPI bus. This will also prevent potential build failures in the future. [Test case] On armhf or ppc64el: apt install bbswitch-dkms ... ERROR: modpost: "acpi_root_dir" [/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko] undefined! [Fix] Simply drop support for armhf and ppc64el. [Regression potential] This module won't be available if there's any "special" armhf or ppc64el system with an NVIDIA optimus card (I doubt a system like this will ever exist). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1956434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956434] Re: bbswitch-dkms: drop support for armhf and ppc64el
debdiff in attach fixes the issue. ** Patch added: "bbswitch-drop-armhf-and-ppc64el.debdiff" https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1956434/+attachment/5551394/+files/bbswitch-drop-armhf-and-ppc64el.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1956434 Title: bbswitch-dkms: drop support for armhf and ppc64el Status in bbswitch package in Ubuntu: New Status in bbswitch source package in Jammy: New Bug description: [Impact] bbswitch is a kernel module that is supposed to detect certain ACPI calls and toggle power on NVIDIA optimus video cards. There is no reason to provide this feature on architectures that don't have an ACPI bus. This will also prevent potential build failures in the future. [Test case] On armhf or ppc64el: apt install bbswitch-dkms ... ERROR: modpost: "acpi_root_dir" [/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko] undefined! [Fix] Simply drop support for armhf and ppc64el. [Regression potential] This module won't be available if there's any "special" armhf or ppc64el system with an NVIDIA optimus card (I doubt a system like this will ever exist). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1956434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
At the moment, in Ubuntu 21.10 we have gnome-shell 40.5, which is the same version for "jammy". When will Ubuntu ship 40.6? -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
I disagree with #21. Ubuntu should disable WAYLAND for thunderbird until it is ready to be used. The problem has existed for a log time and nobody seems to "own" it (Ubuntu? Gnome? Thunderbird?), redirecting users to some other bug report, and nothing changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Released Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950925] Re: alt-tab doesnt work anymore after upgrade to 21.10
I am on 21.10 (fully updated) and the Thunderbird issue continues. -- 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/1950925 Title: alt-tab doesnt work anymore after upgrade to 21.10 Status in gnome-shell package in Ubuntu: Confirmed Bug description: I want to swicth windows with alt-tab. This worked until before I just upgraded from 21.4 to 21.10. Now nothing happens anymore. In Settings -> Keyboard -> Customize Shortcuts -> Navigation the Shortcut for "Switch Windows" is set to alt-tab, but pressing these doesnt do anything. Super-Tab works, but it switches applications, not windows. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 00:47:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-12 (581 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-11-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el
New debdiff in attach that relies on CONFIG_ACPI to determine if we need
to check the power state in bbswitch_off().
** Patch added: "bbswitch-fix-build-error-when-acpi-is-not-available.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+attachment/5544007/+files/bbswitch-fix-build-error-when-acpi-is-not-available.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in bbswitch package in Ubuntu:
New
Status in bbswitch source package in Jammy:
New
Bug description:
[Impact]
bbswitch is failing to build with the latest jammy kernel 5.15 on
armhf and ppc64el.
The build error that we get looks like the following:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
[Test case]
Install bbswitch-dkms.
[Fix]
It looks like bbswitch is using acpi_bus_get_device() on any
architectures to check for suspend events, but this function is not
available on armhf or ppc64el. The fix would be to avoid doing this
check (and using acpi_bus_get_device()) on architectures that don't
have this capability.
[Regression potential]
We should see potential bbswitch regressions on armhf or ppc64el if
they have suspend events (similar problem that is addressed on amd64 /
arm64).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950925] Re: alt-tab doesnt work anymore after upgrade to 21.10
I come from https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328 For me, they look related. Before using Thunderbird (or before it mis-behaves), Alt-TAB works. When Thunderbird goes wrong, Alt-TAB stops working. -- 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/1950925 Title: alt-tab doesnt work anymore after upgrade to 21.10 Status in gnome-shell package in Ubuntu: Confirmed Bug description: I want to swicth windows with alt-tab. This worked until before I just upgraded from 21.4 to 21.10. Now nothing happens anymore. In Settings -> Keyboard -> Customize Shortcuts -> Navigation the Shortcut for "Switch Windows" is set to alt-tab, but pressing these doesnt do anything. Super-Tab works, but it switches applications, not windows. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 00:47:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-12 (581 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-11-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
In reply to #56. I can confirm Alt-TAB stops working when Thunderbird mis-behaves. Normally it would show 1 more red (i.e. Window) dot than necessary. But today it is showing 5 extra dots. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el
** Description changed:
- It looks like bbswitch is using acpi_bus_get_device() on any
- architectures, but this function is not available on armhf or ppc64el:
+ [Impact]
+
+ bbswitch is failing to build with the latest jammy kernel 5.15 on armhf
+ and ppc64el.
+
+ The build error that we get looks like the following:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
+
+ [Test case]
+
+ Install bbswitch-dkms.
+
+ [Fix]
+
+ It looks like bbswitch is using acpi_bus_get_device() on any
+ architectures to check for suspend events, but this function is not
+ available on armhf or ppc64el. The fix would be to avoid doing this
+ check (and using acpi_bus_get_device()) on architectures that don't have
+ this capability.
+
+ [Regression potential]
+
+ We should see potential bbswitch regressions on armhf or ppc64el if they
+ have suspend events (similar problem that is addressed on amd64 /
+ arm64).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in bbswitch package in Ubuntu:
New
Status in bbswitch source package in Jammy:
New
Bug description:
[Impact]
bbswitch is failing to build with the latest jammy kernel 5.15 on
armhf and ppc64el.
The build error that we get looks like the following:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
[Test case]
Install bbswitch-dkms.
[Fix]
It looks like bbswitch is using acpi_bus_get_device() on any
architectures to check for suspend events, but this function is not
available on armhf or ppc64el. The fix would be to avoid doing this
check (and using acpi_bus_get_device()) on architectures that don't
have this capability.
[Regression potential]
We should see potential bbswitch regressions on armhf or ppc64el if
they have suspend events (similar problem that is addressed on amd64 /
arm64).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el
** Also affects: bbswitch (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Status in bbswitch package in Ubuntu:
New
Status in bbswitch source package in Jammy:
New
Bug description:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit
declaration of function ‘acpi_bus_get_device’; did you mean
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
| ^~
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
| ^~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing
Firefox screenshot example ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489522/+files/20210418_180028.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924910 Title: Massive screen flashing artefacts - tearing Status in xorg package in Ubuntu: New Bug description: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen- heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 13:53:28 2021 DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (441 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1924910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing
Screenshot of damaged application bar. See the blue square below VLC and compare with the other image. There should be the zoom icon. ** Attachment added: "20210418_180321.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489525/+files/20210418_180321.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924910 Title: Massive screen flashing artefacts - tearing Status in xorg package in Ubuntu: New Bug description: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen- heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 13:53:28 2021 DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (441 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1924910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing
Screenshot of the normal application bar. ** Attachment added: "20210418_180315.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489524/+files/20210418_180315.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924910 Title: Massive screen flashing artefacts - tearing Status in xorg package in Ubuntu: New Bug description: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen- heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 13:53:28 2021 DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (441 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1924910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing
Firefox screenshot example ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489523/+files/20210418_180038.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924910 Title: Massive screen flashing artefacts - tearing Status in xorg package in Ubuntu: New Bug description: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen- heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 13:53:28 2021 DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (441 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1924910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing
Firefox screenshot example ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489521/+files/20210418_180021.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924910 Title: Massive screen flashing artefacts - tearing Status in xorg package in Ubuntu: New Bug description: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen- heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 13:53:28 2021 DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (441 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1924910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924910] [NEW] Massive screen flashing artefacts - tearing
Public bug reported: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen-heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 13:53:28 2021 DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (441 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 corruption groovy 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/1924910 Title: Massive screen flashing artefacts - tearing Status in xorg package in Ubuntu: New Bug description: On Ubuntu 20.10 x64 frequently updated. I noticed in the last week that after a while there are huge screen artefacts, that I would describe as flashing. Squares of screen flash, normally linked to widgets on screen. E.g.: the app bars on the left can start flashing blue, or parts of editors. I noticed it more in firefox, made worse by scrolling. VirtualBox is severely affected too. VS Code. It does not happen immediately and the feeling I get is that it starts happening when there is a lot on screen. For example has not happened at all in this session, but I have done little or nothing screen- heavy. The issue gets worse, then might settle down for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu50.5
[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
As well as in 20.10 (gnome-online-accounts 3.37.90-1ubuntu1). By the way, the upstream bug link is now https://gitlab.gnome.org/GNOME /gnome-online-accounts/-/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #17 https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Nothing to do for me. Ubuntu 20.10 HP spectre x360. 5.11.22 Kernel (no microphone) -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922723] Re: Weird CTRL+SHIFT+KEY behaviour in Xorg sessions
I found a solution. I turned off the "Locate Pointer" accessibility setting. So SHIFT+CTRL+KEY does not work in xorg session if "Locate Pointer" is turned on. ** Summary changed: - Weird CTRL+SHIFT+KEY behaviour in Xorg sessions + Weird CTRL+SHIFT+KEY behaviour in Xorg sessions with "Locate Pointer" on ** Description changed: I run a newly installed Ubuntu Hirsute. Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut normally. If I press first CTRL, then SHIFT, then KEY everything works. If I press SHIFT, then CTRL then KEY nothing happens. On the Ubuntu (GNOME Wayland) session things works out normal. Step to reproduce: * Log in in a Xorg session + * Turn on the "Locate Pointer" setting in Setting/Accessibility * Open gnome-terminal * Press CTRL + SHIFT + "N" (in this order), a new terminal window appears * Press SHIFT + CTRL + "N" (in this order), nothing happens. The same happens with Firefox, Nautilus and other apps. Possibly, Related to this, I also found that, only on a Xorg session, during a Wine-runned gamed I play "CTRL + KEY" behaves just like "KEY". But this might be a Wine bug. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 14:14:37 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: - rtl8821ce, 5.5.2.1, 5.11.0-13-generic, x86_64: installed - virtualbox, 6.1.18, 5.11.0-13-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.11.0-13-generic, x86_64: installed + virtualbox, 6.1.18, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a7] -Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84a7] + Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a7] + Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84a7] InstallationDate: Installed on 2021-03-31 (5 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter - Bus 001 Device 002: ID 05c8:03c7 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera - Bus 001 Device 004: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter + Bus 001 Device 002: ID 05c8:03c7 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera + Bus 001 Device 004: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=81ec23d7-e690-4f52-b570-c2c252d1f0e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.release: 15.7 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.31 dmi.modalias: dmi:bvnInsyde:bvrF.07:bd11/21/2018:br15.7:efr80.31:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4YC20EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 -- You
[Desktop-packages] [Bug 1922723] Re: Weird CTRL+SHIFT+KEY behaviour in Xorg sessions
I tried with an external USB keyboard. Same issue. I have also run `dpkg-reconfigure keyboard-configuration`. Nothing has changed. -- 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/1922723 Title: Weird CTRL+SHIFT+KEY behaviour in Xorg sessions Status in xorg-server package in Ubuntu: Incomplete Bug description: I run a newly installed Ubuntu Hirsute. Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut normally. If I press first CTRL, then SHIFT, then KEY everything works. If I press SHIFT, then CTRL then KEY nothing happens. On the Ubuntu (GNOME Wayland) session things works out normal. Step to reproduce: * Log in in a Xorg session * Open gnome-terminal * Press CTRL + SHIFT + "N" (in this order), a new terminal window appears * Press SHIFT + CTRL + "N" (in this order), nothing happens. The same happens with Firefox, Nautilus and other apps. Possibly, Related to this, I also found that, only on a Xorg session, during a Wine-runned gamed I play "CTRL + KEY" behaves just like "KEY". But this might be a Wine bug. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 14:14:37 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.11.0-13-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a7] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84a7] InstallationDate: Installed on 2021-03-31 (5 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 05c8:03c7 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 004: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=81ec23d7-e690-4f52-b570-c2c252d1f0e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.release: 15.7 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.31 dmi.modalias: dmi:bvnInsyde:bvrF.07:bd11/21/2018:br15.7:efr80.31:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4YC20EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1922723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922723] [NEW] Weird CTRL+SHIFT+KEY behaviour
Public bug reported: I run a newly installed Ubuntu Hirsute. Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut normally. If I press first CTRL, then SHIFT, then KEY everything works. If I press SHIFT, then CTRL then KEY nothing happens. On the Ubuntu (GNOME Wayland) session things works out normal. Step to reproduce: * Log in in a Xorg session * Open gnome-terminal * Press CTRL + SHIFT + "N" (in this order), a new terminal window appears * Press SHIFT + CTRL + "N" (in this order), nothing happens. The same happens with Firefox, Nautilus and other apps. Possibly, Related to this, I also found that, only on a Xorg session, during a Wine-runned gamed I play "CTRL + KEY" behaves just like "KEY". But this might be a Wine bug. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 14:14:37 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.11.0-13-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a7] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84a7] InstallationDate: Installed on 2021-03-31 (5 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 05c8:03c7 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 004: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=81ec23d7-e690-4f52-b570-c2c252d1f0e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.release: 15.7 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.31 dmi.modalias: dmi:bvnInsyde:bvrF.07:bd11/21/2018:br15.7:efr80.31:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4YC20EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1922723 Title: Weird CTRL+SHIFT+KEY behaviour Status in xorg package in Ubuntu: New Bug description: I run a newly installed Ubuntu Hirsute. Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut normally. If I press first CTRL, then SHIFT, then KEY everything works. If I press SHIFT, then CTRL then KEY nothing happens. On the Ubuntu (GNOME Wayland) session things works out normal. Step to reproduce: * Log in in a Xorg session * Open gnome-terminal * Press CTRL + SHIFT + "N" (in this order), a new terminal window appears * Press SHIFT + CTRL + "N" (in this order), nothing happens. The same happens with Firefox, Nautilus and other apps. Possibly, Related to this, I also found that, only on a Xorg session, during a Wine-runned gamed I play "CTRL + KEY" behaves just like "KEY". But this might be a Wine bug. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64
[Desktop-packages] [Bug 1921618] [NEW] Black wallpaper instead than set image
Public bug reported: The image set as wallpaper appears for one second and then is replaced by a black screen. This occurs after a hard reset. After a suspension: nothing worked and I had to do a hard reset by switching the machine off. At restart I'm in the mentioned situation and the usual methods to reset the wall paper do not fix the problem. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 28 13:23:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a7] InstallationDate: Installed on 2017-06-16 (1381 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 005: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=0db16900-e9f1-49a7-b5db-508d231aac23 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0NDFXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0NDFXD:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.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 compiz-0.9 focal 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/1921618 Title: Black wallpaper instead than set image Status in xorg package in Ubuntu: New Bug description: The image set as wallpaper appears for one second and then is replaced by a black screen. This occurs after a hard reset. After a suspension: nothing worked and I had to do a hard reset by switching the machine off. At restart I'm in the mentioned situation and the usual methods to reset the wall paper do not fix the problem. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Mar 28 13:23:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a7] InstallationDate: Installed on 2017-06-16 (1381 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 005: ID 0a5c:5832
[Desktop-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
** Description changed: - As of a couple of days ago, I am unable to get network manager to - connect to any wifi network. + If the /etc/NetworkManager/system-connections directory is a cross- + filesystem symlink, activating connections will fail with the unrelated + messages: - It looks like the groovy network manager packages have not received any - updates since release, but since I can successfully use wpasupplicant - directly I'm ruling out issues with my specific home wifi or wifi card. + * "failed to create file ...: Read-only file system" (TRACE level) - Though this might still ultimately be due to my specific setup, the - error message logged by network manager is really insufficient for - determining where the failure may lie, even when debug mode is turned - on[0]. The Gnome UI doesn't display an error at all. + * "failure adding connection: settings plugin does not support adding + connections" (DEBUG level and above) + + * no error message (Gnome UI) + + I suspect moving the systems-connections directory onto a separate + filesystem is not supported because network manager tries to atomically + move a connection temp file into place and fails, but this is really + hard to figure out since the error messages are completely unrelated. + Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 + How to reproduce: + sudo mv /etc/NetworkManager/system-connections /some/other/mountpoint/system-connections + sudo ln -s /some/other/mountpoint/system-connections /etc/NetworkManager/system-connections + + Then: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui + Symptoms: - * no UI popup is produced when using the Gnome UI - * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui - * debug logs include slightly more information: + * "failed to create file ...: Read-only file system" (TRACE level, + journalctl) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state deactivated, no master) - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22' - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8811] audit: op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" - Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8812] active-connection[0x55b6b9a25b50]: disposing + * "failure adding connection: settings plugin does not support adding + connections" (DEBUG level and above, journalctl and nmtui/nmcli output) - Workaround: - - * connect to networks by using wpasupplicant directly[1] + * no error message (Gnome UI) - [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging - [1] https://shapeshed.com/linux-wifi/ + Relevant sample logs: + + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4038] active-connection[0x56274f6f0a60]: creating + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00] + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5' + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, type managed) + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] auth: call[37]: CheckAuthorization(org.freedesktop.NetworkManager.network-control), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[37]: completed: authorized=1, challenge=0 (simulated) + Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[38]:
[Desktop-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
** Summary changed: - settings plugin does not support adding connections + misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1913979 Title: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink Status in network-manager package in Ubuntu: New Bug description: As of a couple of days ago, I am unable to get network manager to connect to any wifi network. It looks like the groovy network manager packages have not received any updates since release, but since I can successfully use wpasupplicant directly I'm ruling out issues with my specific home wifi or wifi card. Though this might still ultimately be due to my specific setup, the error message logged by network manager is really insufficient for determining where the failure may lie, even when debug mode is turned on[0]. The Gnome UI doesn't display an error at all. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * no UI popup is produced when using the Gnome UI * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui * debug logs include slightly more information: Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state deactivated, no master) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8811] audit: op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8812] active-connection[0x55b6b9a25b50]: disposing Workaround: * connect to networks by using wpasupplicant directly[1] [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging [1] https://shapeshed.com/linux-wifi/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1913979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913979] [NEW] settings plugin does not support adding connections
Public bug reported: As of a couple of days ago, I am unable to get network manager to connect to any wifi network. It looks like the groovy network manager packages have not received any updates since release, but since I can successfully use wpasupplicant directly I'm ruling out issues with my specific home wifi or wifi card. Though this might still ultimately be due to my specific setup, the error message logged by network manager is really insufficient for determining where the failure may lie, even when debug mode is turned on[0]. The Gnome UI doesn't display an error at all. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * no UI popup is produced when using the Gnome UI * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui * debug logs include slightly more information: Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state deactivated, no master) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8811] audit: op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8812] active-connection[0x55b6b9a25b50]: disposing Workaround: * connect to networks by using wpasupplicant directly[1] [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging [1] https://shapeshed.com/linux-wifi/ ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1913979 Title: settings plugin does not support adding connections Status in network-manager package in Ubuntu: New Bug description: As of a couple of days ago, I am unable to get network manager to connect to any wifi network. It looks like the groovy network manager packages have not received any updates since release, but since I can successfully use wpasupplicant directly I'm ruling out issues with my specific home wifi or wifi card. Though this might still ultimately be due to my specific setup, the error message logged by network manager is really insufficient for determining where the failure may lie, even when debug mode is turned on[0]. The Gnome UI doesn't display an error at all. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * no UI popup is produced when using the Gnome UI * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui * debug logs include slightly more information: Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) Jan 31 20:32:57 laptop
[Desktop-packages] [Bug 1913895] [NEW] [6cb:00df ] Synaptics fingerprint sensor not working
Public bug reported: I have been trying to enable the fingerprint reader on my laptop (Ubuntu 20.10) for a while without succeeding. When trying to enroll a fingerprint (both via Ubuntu gui or fprintd-enroll) I get this error yaxit@chronos:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: The driver encountered a protocol error with the device. On the second attempt, the error turns to: Device 06cb:00df is already open If I understand correctly, the sensor should be supported by libfprint since https://bugs.launchpad.net/oem-priority/+bug/1893719 The issue is also described here: https://askubuntu.com/questions/1307127/synaptics-6cb00df-fingerprint-sensor-not-working ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1913895 Title: [6cb:00df ] Synaptics fingerprint sensor not working Status in libfprint package in Ubuntu: New Bug description: I have been trying to enable the fingerprint reader on my laptop (Ubuntu 20.10) for a while without succeeding. When trying to enroll a fingerprint (both via Ubuntu gui or fprintd-enroll) I get this error yaxit@chronos:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: The driver encountered a protocol error with the device. On the second attempt, the error turns to: Device 06cb:00df is already open If I understand correctly, the sensor should be supported by libfprint since https://bugs.launchpad.net/oem-priority/+bug/1893719 The issue is also described here: https://askubuntu.com/questions/1307127/synaptics-6cb00df-fingerprint-sensor-not-working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1913895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)
Ubuntu 20.04..using the PPA as explained in this other bug https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950 it builds and works too.. sudo add-apt-repository ppa:kelebek333/nvidia-legacy -- 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/1885344 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel) Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Nvidia kernel module fails to build with linux kernel 5.6.0. Exits with error code 2. Description: Ubuntu 20.04 LTS Release: 20.04 linux-image-unsigned-5.6.0-1018-oem: Installed: 5.6.0-1018.18 Candidate: 5.6.0-1018.18 Version table: *** 5.6.0-1018.18 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.6.0-1018-oem Date: Sat Jun 27 02:15:51 2020 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25: error: implicit declaration of function ‘drm_pci_init’; did you mean ‘drm_mm_init’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-04-24 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu2 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: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build 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/1885344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898335] Re: Vino server stops when connecting to VPN after upgrade to 20.04
I've installed 20.04.1 from the scratch and unfortunately i'm able to reproduce the issue, so is not related to release upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1898335 Title: Vino server stops when connecting to VPN after upgrade to 20.04 Status in vino package in Ubuntu: Confirmed Bug description: After I upgraded from 18.04 to 20.04, whenever I am making a connection to a VPN server (using Network Manager), vino-server will stop when the VPN connection is established. This did not happen in 18.04 before the upgrade. syslog show the following when I connect to VPN 10:02:00 systemd: Stopped Vino VNC server. 10:02:00 systemd: Stopped Vino VNC server. 10:02:00 systemd: vino-server.service: Succeeded. 10:02:00 systemd: Stopping Vino VNC server... 10:02:00 NetworkManager: [1601712120.6080] device (tun0): Activation: successful, device activated. 10:02:00 NetworkManager: [1601712120.6080] device (tun0): Activation: successful, device activated. 10:02:00 NetworkManager: [1601712120.6065] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') 10:02:00 NetworkManager: [1601712120.6059] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') 10:02:00 NetworkManager: [1601712120.6030] policy: set 'CH-Zurich-zur-c04' (tun0) as default for IPv4 routing and DNS 10:02:00 systemd: Started Network Manager Script Dispatcher Service. 10:02:00 dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 10:02:00 NetworkManager: [1601712120.5706] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') 10:02:00 systemd: Starting Network Manager Script Dispatcher Service... 10:02:00 NetworkManager: [1601712120.5442] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') 10:02:00 dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=817 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") 10:02:00 NetworkManager: [1601712120.5428] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",4:(tun0)]: VPN connection: (IP Config Get) complete 10:02:00 openvpn: Initialization Sequence Completed 10:02:00 NetworkManager: [1601712120.5307] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",4:(tun0)]: VPN plugin: state changed: started (4) 10:02:00 openvpn: UID set to nm-openvpn 10:02:00 NetworkManager: [1601712120.5297] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",4:(tun0)]: Data: Internal Point-to-Point Address: 172.21.24.45 10:02:00 openvpn: GID set to nm-openvpn 10:02:00 NetworkManager: [1601712120.5202] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",0]: VPN connection: (IP Config Get) reply received. 10:02:00 openvpn: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 2287 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_2 --tun -- tun0 1500 1553 172.21.24.45 255.255.254.0 init 10:02:00 systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. 10:02:00 openvpn: TUN/TAP device tun0 opened 10:01:58 NetworkManager: [1601712118.4499] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",0]: VPN connection: (ConnectInteractive) reply received 10:01:54 gnome-shell: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 10:08:27 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-09-29 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1898335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879580] Re: Screencast interface missing
As stay-at-home request intensifies having screen-sharing capabilities are becoming more important. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879580] Re: Screencast interface missing
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 240133]
But marking it as WONTFIX means that there's been a conscious decision made not to implement it, right? Here it's just a case that nobody's done it. It might be done someday. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 240133]
It's a shame that after 18 years, Mozilla still has no support for MIME HTML. If I knew C++ and the codebase, I'd write a patch, but alas. I hope this comment might remind someone this exists and spur them into action. -- 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/240133 Title: MHTML Format - Web Archive Files - Standard not supported in Firefox Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 this location http://www.militarybadges.org.uk/badget11.mht displays This document is a Web archive file. If you are seeing this message, this means your browser or editor doesn't support Web archive files. For more information on the Web archive format, go to http://officeupdate.microsoft.com/office/webarchive.htm I am using ubuntu 8.04 ProblemType: Bug Architecture: i386 Date: Sun Jun 15 10:28:40 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic i686 WORKAROUND : http://www.unmht.org/unmht/en_index.html To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/240133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877294] [NEW] graphic problem and no internet connection
Public bug reported: every time I start my personal computer there is an error on the graphics module and I have to restart the service network manager in the terminal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 7 13:53:42 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90ab] InstallationDate: Installed on 2020-05-01 (5 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Sony Corporation SVE1511F1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=c4e39bf2-5485-4178-b290-aa431b8a172b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0180E5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0180E5:bd04/24/2012:svnSonyCorporation:pnSVE1511F1EW:pvrC107K8GJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE1511F1EW dmi.product.version: C107K8GJ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 7 13:44:28 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877294 Title: graphic problem and no internet connection Status in xorg package in Ubuntu: New Bug description: every time I start my personal computer there is an error on the graphics module and I have to restart the service network manager in the terminal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu May 7 13:53:42 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90ab] InstallationDate: Installed on 2020-05-01 (5 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Sony Corporation SVE1511F1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=c4e39bf2-5485-4178-b290-aa431b8a172b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0180E5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias:
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
Hi Colton, thanks for testing it! It looks like the kernel correctly receives and delivers the ACPI events, but then it fails to perform the actual suspend to mem. Can you try one more test? echo 1 > /sys/power/pm_debug_messages echo 0 > /sys/power/pm_async echo mem > /sys/power/state The first setting simply increases the PM debugging level (...and hopefully we can get more info from dmesg -w). The second one disables the asynchronous execution of the PM suspend and resume callbacks. If the problem is a race condition in some of those callbacks, this should prevent the race. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
Thanks for reporting this. The CurrentDmesg.txt that you posted doesn't seem to include the part when you close the lid, am I correct? In that case could you run `dmesg -w` on a console session, close the lid and post what you get in dmesg? Another interesting test could be to check if the ACPI events are properly handled by the kernel and passed to user-space. For this you can try to run `acpi_listen` (as root) in another console session, close the lid, re-open it, and you should see something like: button/lid LID close button/lid LID open Then, I'm not sure if you tried it already, but what happens if you try to suspend manually via `echo mem > /sys/power/state`. Does it actually suspend? Do you get any error in dmesg? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A
[Desktop-packages] [Bug 1853893] [NEW] Firefox maximized CSD using double space on Plasma with "global menu" widget
Public bug reported: Kubuntu 19.10 Firefox 70.0.1+build1-0ubuntu0.19.10.1 Using Firefox's CSD on KDE Plasma and using KDE's "global menu" widget in a panel, Firefox takes useless space for the "title bar". Screenshot here: https://pasteboard.co/IImEuh3.png By right clicking on the empty space in the "title bar", this space disappears for a few seconds giving this: https://pasteboard.co/IImFha5.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: KDE Date: Mon Nov 25 19:57:39 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox InstallationDate: Installed on 2019-11-14 (11 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1853893 Title: Firefox maximized CSD using double space on Plasma with "global menu" widget Status in firefox package in Ubuntu: New Bug description: Kubuntu 19.10 Firefox 70.0.1+build1-0ubuntu0.19.10.1 Using Firefox's CSD on KDE Plasma and using KDE's "global menu" widget in a panel, Firefox takes useless space for the "title bar". Screenshot here: https://pasteboard.co/IImEuh3.png By right clicking on the empty space in the "title bar", this space disappears for a few seconds giving this: https://pasteboard.co/IImFha5.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191031091608 CurrentDesktop: KDE Date: Mon Nov 25 19:57:39 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox InstallationDate: Installed on 2019-11-14 (11 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0.1/20191031091608 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1853893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
Hi, I added Eoan series to the bug report as it hasn't been fixed there. (The bug had been automatically marked as Fix Released after the Focal update) ** Also affects: mutter (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Also affects: gnome-shell (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Won't Fix ** Changed in: mutter (Ubuntu Eoan) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: mutter (Ubuntu Eoan) Importance: Undecided => Medium -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Triaged Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor
** Changed in: gnome-system-monitor (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: Invalid Status in libgtop2 package in Ubuntu: Fix Released Status in libgtop2 source package in Bionic: Fix Released Bug description: * Impact snaps mount at listed in the system monitor but they are an implementation detail and not interesting there. We already filter them out of the Disks UI, we should do the same in the system monitor * Test case - have a snap installed (wshich is true in the default installation of Ubuntu) - open gnome-system-monitor - check the filesystem tabs content, snaps mounts shouldn't be listed * Regression potential Check that the system mounted partitions are still correctly listed -- As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827029] [NEW] Extended characters in OSK don't get entered
Public bug reported:
[Impact]
This bug affects any of the "extended characters" clicked on from the
long-press popup in the Screen Keyboard.
[Test Case]
1. Open GNOME Settings > Universal Access
2. Enable the Screen Keyboard. (Optionally, turn on Always Show Universal
Access Menu to make turning the Screen Keyboard on and off easier.)
3. Open Text Editor
4. Click the u button on the Screen Keyboard
5. Long-press the u button on the Screen Keyboard for a few seconds.
6. On the popup, click the ü character.
What Happens
In Step 4, u is entered in the Text Editor document.
Nothing is entered in Step 5.
[Regression Potential]
The code to be backported only affects OSK. Check that normal OSK keys (e.g.
a,b,c,...) normally works.
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Assignee: Andrea Azzarone (azzar1)
Status: Fix Released
** Affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Affects: gnome-shell (Ubuntu Cosmic)
Importance: Undecided
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
** Affects: gnome-shell (Ubuntu Disco)
Importance: Undecided
Assignee: Andrea Azzarone (azzar1)
Status: Fix Released
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Andrea Azzarone (azzar1)
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
** Also affects: gnome-shell (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Disco)
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu Disco)
Assignee: (unassigned) => Andrea Azzarone (azzar1)
** Changed in: gnome-shell (Ubuntu Cosmic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu Bionic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu Cosmic)
Status: New => In Progress
--
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/1827029
Title:
Extended characters in OSK don't get entered
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Bionic:
In Progress
Status in gnome-shell source package in Cosmic:
In Progress
Status in gnome-shell source package in Disco:
Fix Released
Bug description:
[Impact]
This bug affects any of the "extended characters" clicked on from the
long-press popup in the Screen Keyboard.
[Test Case]
1. Open GNOME Settings > Universal Access
2. Enable the Screen Keyboard. (Optionally, turn on Always Show Universal
Access Menu to make turning the Screen Keyboard on and off easier.)
3. Open Text Editor
4. Click the u button on the Screen Keyboard
5. Long-press the u button on the Screen Keyboard for a few seconds.
6. On the popup, click the ü character.
What Happens
In Step 4, u is entered in the Text Editor document.
Nothing is entered in Step 5.
[Regression Potential]
The code to be backported only affects OSK. Check that normal OSK keys (e.g.
a,b,c,...) normally works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827029/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823167] Re: /usr/lib/tracker/tracker-extract:31:chdir:do_exec:fork_exec_with_fds:fork_exec_with_pipes:g_spawn_async_with_pipes
The fix has been merged upstream. I think it's worth SRUing it to disco because it's one of the most reported errors in errors.ubuntu.com. Tagging as rls-dd-incoming. ** Bug watch added: gitlab.gnome.org/GNOME/tracker-miners/issues #61 https://gitlab.gnome.org/GNOME/tracker-miners/issues/61 ** Also affects: tracker via https://gitlab.gnome.org/GNOME/tracker-miners/issues/61 Importance: Unknown Status: Unknown ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1823167 Title: /usr/lib/tracker/tracker- extract:31:chdir:do_exec:fork_exec_with_fds:fork_exec_with_pipes:g_spawn_async_with_pipes Status in Tracker: Unknown Status in tracker-miners package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker-miners. This problem was most recently seen with package version 2.1.6-1, the problem page at https://errors.ubuntu.com/problem/2d3540bf66f1db4ac13f98446641b0d9c512c19c 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/tracker/+bug/1823167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826056] Re: Desktop context: Keep aligned, Organize desktop by name missing in 19.04
** Package changed: tracker (Ubuntu) => gnome-shell-extension-desktop- icons (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1826056 Title: Desktop context: Keep aligned, Organize desktop by name missing in 19.04 Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: After upgrading from 18.10 to 19.04 the desktop context menu no longer contains the choices: Keep aligned Organize desktop by name These were very useful to me. I would like them to be restored. Ubuntu 19.04, 64bit Gnome 3.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu Disco) Status: New => Fix Released ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu) ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Disco) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-shell (Ubuntu Disco) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- 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/1817020 Title: Touching and dragging an icon on the dock blocks input to other apps Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Released Bug description: Steps to reproduce In GNOME Shell, make sure the Ubuntu dock is visible Using a finger drag, for example, a LibreOffice icon up and down the dock and then drop it on Nautilus. Notice that (sometimes?) the icon will continue to float above the dock and that the mouse will keep the clicky-finger icon. Notice that you can still open Activities and launch an application Notice however, that you can't actually interact with the application you have just launched = What I expected to happen = When releasing the drag the icon would land back on the dock and I could continue to use the desktop as usual. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822629] Re: /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb
Fixed in tracker 2.1.8-2. ** Changed in: tracker-miners (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1822629 Title: /usr/lib/tracker/tracker-miner- fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb Status in tracker-miners package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker-miners. This problem was most recently seen with package version 2.1.6-1, the problem page at https://errors.ubuntu.com/problem/d74b7e2c225d68f36ba3587ca110e0f0923aae8a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1822629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825085] Re: Ctrl+F search does not work
Fix proposed upstream: https://gitlab.gnome.org/GNOME/file- roller/merge_requests/12 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1825085 Title: Ctrl+F search does not work Status in File Roller: Unknown Status in file-roller package in Ubuntu: In Progress Bug description: Problem: When I browse an archive in a file-roller window, and press Ctrl+F to do a search, it just pops up the search bar and disappears immediately. The workaround is to click the search icon or use Tab to navigate to it. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1825085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825085] Re: Ctrl+F search does not work
** Bug watch added: gitlab.gnome.org/GNOME/file-roller/issues #37 https://gitlab.gnome.org/GNOME/file-roller/issues/37 ** Also affects: file-roller via https://gitlab.gnome.org/GNOME/file-roller/issues/37 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1825085 Title: Ctrl+F search does not work Status in File Roller: Unknown Status in file-roller package in Ubuntu: In Progress Bug description: Problem: When I browse an archive in a file-roller window, and press Ctrl+F to do a search, it just pops up the search bar and disappears immediately. The workaround is to click the search icon or use Tab to navigate to it. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1825085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825085] Re: [Ubuntu 18.10] Ctrl+F search does not work
** Changed in: file-roller (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: file-roller (Ubuntu) Status: Confirmed => In Progress ** Summary changed: - [Ubuntu 18.10] Ctrl+F search does not work + Ctrl+F search does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1825085 Title: Ctrl+F search does not work Status in file-roller package in Ubuntu: In Progress Bug description: Problem: When I browse an archive in a file-roller window, and press Ctrl+F to do a search, it just pops up the search bar and disappears immediately. The workaround is to click the search icon or use Tab to navigate to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1825085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
Fix proposed upstream: https://gitlab.gnome.org/GNOME/gnome- software/merge_requests/199 ** Changed in: gnome-software (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: In Progress Bug description: I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #641 https://gitlab.gnome.org/GNOME/gnome-software/issues/641 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/641 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Confirmed Bug description: I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825153] [NEW] Spinner in "apps" page keeps spinning if there is no connectivity
Public bug reported: If the system is not connected to the internet, the spinner in the last page keeps spinning without indication of what's going on. ** Affects: gnome-initial-setup (Ubuntu) Importance: Medium Assignee: Andrea Azzarone (azzar1) Status: New ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-initial-setup (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1825153 Title: Spinner in "apps" page keeps spinning if there is no connectivity Status in gnome-initial-setup package in Ubuntu: New Bug description: If the system is not connected to the internet, the spinner in the last page keeps spinning without indication of what's going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1825153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822753] Re: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref
** Description changed: + [Impact] + Gedit crashes when it is closed while a file is being loaded or just after the file has been loaded. + + The bug is a regression in Disco: in Cosmic Gedit is built using + autotools while in Disco we use meson. During the port to meson upstream + forgot to port a build option (in particular 'enable-gvfs-metadata', + enabled by default). Without this option a broken - and untested - code + path is activated. + + To fix thisd bug we should reintroduce the 'enable-gvfs-metadata' + option. + + [Test case] + 1. Create a big text file + 2. Open gedit + 3. Close the window while the file is still being loaded + + Also check there are no more reports in e.u.c. + + [Regression Potential] + The change affects the way gedit stores the file metadata. Try for example + 1. open a file + 2. focus a random line + 3. close the file + 4. re-open the file + 5. make sure the random line that you focused in point 2. is focused + + [Original report] The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 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/. ** Description changed: [Impact] Gedit crashes when it is closed while a file is being loaded or just after the file has been loaded. The bug is a regression in Disco: in Cosmic Gedit is built using autotools while in Disco we use meson. During the port to meson upstream forgot to port a build option (in particular 'enable-gvfs-metadata', enabled by default). Without this option a broken - and untested - code path is activated. - To fix thisd bug we should reintroduce the 'enable-gvfs-metadata' - option. + To fix this bug we should reintroduce the 'enable-gvfs-metadata' option. [Test case] 1. Create a big text file 2. Open gedit 3. Close the window while the file is still being loaded Also check there are no more reports in e.u.c. [Regression Potential] The change affects the way gedit stores the file metadata. Try for example 1. open a file 2. focus a random line 3. close the file 4. re-open the file 5. make sure the random line that you focused in point 2. is focused [Original report] The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 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/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822753 Title: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref Status in gedit: New Status in gedit package in Ubuntu: In Progress Bug description: [Impact] Gedit crashes when it is closed while a file is being loaded or just after the file has been loaded. The bug is a regression in Disco: in Cosmic Gedit is built using autotools while in Disco we use meson. During the port to meson upstream forgot to port a build option (in particular 'enable-gvfs- metadata', enabled by default). Without this option a broken - and untested - code path is activated. To fix this bug we should reintroduce the 'enable-gvfs-metadata' option. [Test case] 1. Create a big text file 2. Open gedit 3. Close the window while the file is still being loaded Also check there are no more reports in e.u.c. [Regression Potential] The change affects the way gedit stores the file metadata. Try for example 1. open a file 2. focus a random line 3. close the file 4. re-open the file 5. make sure the random line that you focused in point 2. is focused [Original report] The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 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
[Desktop-packages] [Bug 1824996] [NEW] Spinner in "apps" page is huge
Public bug reported: The spinner in the last page is huge. ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-initial-setup (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824996 Title: Spinner in "apps" page is huge Status in gnome-initial-setup package in Ubuntu: In Progress Bug description: The spinner in the last page is huge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1824996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823459] Re: guile-2.2 ftbfs in disco (arm64 only)
Fix proposed upstream: http://lists.gnu.org/archive/html/guile- devel/2019-04/msg00015.html ** Changed in: guile-2.2 (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to guile-2.2 in Ubuntu. https://bugs.launchpad.net/bugs/1823459 Title: guile-2.2 ftbfs in disco (arm64 only) Status in guile-2.2 package in Ubuntu: In Progress Status in guile-2.2 source package in Disco: In Progress Bug description: https://launchpadlibrarian.net/417969614/buildlog_ubuntu-disco- arm64.guile-2.2_2.2.4+1-1ubuntu2_BUILDING.txt.gz Totals for this test run: passes: 41515 failures: 1 unexpected passes: 0 expected failures: 10 unresolved test cases: 577 untested test cases:1 unsupported test cases: 1 errors: 0 warning: call to primitive-fork while multiple threads are running; further behavior unspecified. See "Processes" in the manual, for more information. warning: call to primitive-fork while multiple threads are running; further behavior unspecified. See "Processes" in the manual, for more information. ;;; SSAX warning: Skipping PI: xml ;;; SSAX warning: Skipping PI: PI ;;; SSAX warning: Skipping PI: PI1 ;;; SSAX warning: ( Warning: DOCTYPE DECL T system1 found and skipped) ;;; SSAX warning: ( Warning: Internal DTD subset is not currently handled ) ;;; SSAX warning: ( Warning: DOCTYPE DECL T system1 found and skipped) ;;; SSAX warning: Skipping PI: pi ;;; SSAX warning: DOCTYPE DECL T system1 found and skipped WARNING: (test-suite sxml-xpath): imported module (sxml xpath) overrides core binding `filter' FAIL: check-guile == 1 of 1 test failed Please report to bug-gu...@gnu.org == make[4]: *** [Makefile:1956: check-TESTS] Error 1 make[4]: Leaving directory '/<>/guile-2.2-2.2.4+1' make[3]: *** [Makefile:2241: check-am] Error 2 make[3]: Leaving directory '/<>/guile-2.2-2.2.4+1' make[2]: *** [Makefile:1856: check-recursive] Error 1 make[2]: Leaving directory '/<>/guile-2.2-2.2.4+1' make[1]: *** [Makefile:2243: check] Error 2 make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1' dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1823459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822753] Re: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref
General fix proposed upstream: https://gitlab.gnome.org/GNOME/gedit/merge_requests/35 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/issues #145 https://gitlab.gnome.org/GNOME/gedit/issues/145 ** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/issues/145 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822753 Title: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref Status in gedit: Unknown Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 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/gedit/+bug/1822753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1646762] Re: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch
Fix proposed upstream: https://gitlab.gnome.org/GNOME/gedit/merge_requests/34 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1646762 Title: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.22.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1646762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1646762] Re: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch
** Changed in: gedit (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gedit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1646762 Title: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.22.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1646762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821522] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1821522 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: Was using gedit to examine multiple files. When completed close with wondow "X" and let my system. When returning found the crash alert. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 08:43:38 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-06 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f25840ba67a : mov(%rax),%esi PC (0x7f25840ba67a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () at /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () at /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so () at /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () at /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1821522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821453] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1821453 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: None ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 19:27:52 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-03-23 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190315) ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff67c30967a : mov(%rax),%esi PC (0x7ff67c30967a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1821453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821946] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1821946 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: No significant information about the bug ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 27 16:46:53 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-26 (28 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f41e7e1367a : mov(%rax),%esi PC (0x7f41e7e1367a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1821946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822349] Re: gedit crashed with SIGSEGV in gedit_metadata_manager_set()
*** This bug is a duplicate of bug 1822753 *** https://bugs.launchpad.net/bugs/1822753 ** This bug is no longer a duplicate of private bug 1821404 ** This bug has been marked a duplicate of bug 1822753 /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822349 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() Status in gedit package in Ubuntu: New Bug description: Gedit sometimes takes some time before opening and sometimes forcefully shuts down.Sometimes it works perfectly,but then also it asks that gedit has stopped working and to restart it. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 21:38:00 2019 ExecutablePath: /usr/bin/gedit ProcCmdline: /usr/bin/gedit --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_IN SegvAnalysis: Segfault happened at: 0x7f8a52b0067a : mov(%rax),%esi PC (0x7f8a52b0067a) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_metadata_manager_set () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so gedit_document_set_metadata () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_text_view_set_buffer () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gedit_metadata_manager_set() UpgradeStatus: Upgraded to disco on 2019-03-17 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1822349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822753] Re: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref
The first issues it that gedit should use gvfs to store file metadata. Since the port of gedit to meson this feature has been lost. I've proposed a fix upstream here: https://gitlab.gnome.org/GNOME/gedit/merge_requests/32 ** Changed in: gedit (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gedit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822753 Title: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref Status in gedit package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1822753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755007] Re: tracker-miner-fs crashed with SIGSEGV
*** This bug is a duplicate of bug 1822629 *** https://bugs.launchpad.net/bugs/1822629 ** This bug is no longer a duplicate of bug 1713629 tracker-miner-fs crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1822629 /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1755007 Title: tracker-miner-fs crashed with SIGSEGV Status in tracker-miners package in Ubuntu: New Bug description: Dont know ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: tracker-miner-fs 2.0.4-1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 11 19:00:48 2018 EcryptfsInUse: Yes ExecutablePath: /usr/lib/tracker/tracker-miner-fs ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1b5ed6056a:mov0x40(%rbp),%ebx PC (0x7f1b5ed6056a) ok source "0x40(%rbp)" (0x0040) not located in a known VMA region (needed readable region)! destination "%ebx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1755007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723645] Re: tracker-miner-fs crashed with SIGSEGV
*** This bug is a duplicate of bug 1822629 *** https://bugs.launchpad.net/bugs/1822629 ** This bug is no longer a duplicate of bug 1713629 tracker-miner-fs crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1822629 /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1723645 Title: tracker-miner-fs crashed with SIGSEGV Status in tracker-miners package in Ubuntu: New Bug description: Mah!!! ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: tracker-miner-fs 2.0.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 21:07:38 2017 ExecutablePath: /usr/lib/tracker/tracker-miner-fs ProcCmdline: /usr/lib/tracker/tracker-miner-fs SegvAnalysis: Segfault happened at: 0x7f919a0ee04a:mov0x40(%rbp),%ebx PC (0x7f919a0ee04a) ok source "0x40(%rbp)" (0x0040) not located in a known VMA region (needed readable region)! destination "%ebx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1723645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724801] Re: tracker-miner-fs crashed with SIGSEGV
*** This bug is a duplicate of bug 1822629 *** https://bugs.launchpad.net/bugs/1822629 ** This bug is no longer a duplicate of bug 1713629 tracker-miner-fs crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1822629 /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1724801 Title: tracker-miner-fs crashed with SIGSEGV Status in tracker-miners package in Ubuntu: New Bug description: ...some litle instabilities since last upgrade. Crash eventualy few minutes after login. No known cause. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: tracker-miner-fs 2.0.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 08:20:19 2017 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationDate: Installed on 2017-09-29 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe990b74046:mov0x18(%rdi),%rbp PC (0x7fe990b74046) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom clamav dip firebird input lpadmin plugdev pulse sambashare sudo utmp uucp uuidd vboxusers video voice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1724801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724475] Re: tracker-miner-fs crashed with SIGSEGV
*** This bug is a duplicate of bug 1822629 *** https://bugs.launchpad.net/bugs/1822629 ** This bug is no longer a duplicate of bug 1713629 tracker-miner-fs crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1822629 /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1724475 Title: tracker-miner-fs crashed with SIGSEGV Status in tracker-miners package in Ubuntu: New Bug description: Tracker processes using up >90% of the processor too often. Unplugging laptop from power causes processes to crash. Something needs to be done to keep tracker from running my machine hot all the time, else I will be forced to remove it. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: tracker-miner-fs 2.0.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 08:39:44 2017 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationDate: Installed on 2016-12-03 (318 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd7fa91a046:mov0x18(%rdi),%rbp PC (0x7fd7fa91a046) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-09-28 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1724475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762974] Re: tracker-miner-fs crashed with SIGSEGV
*** This bug is a duplicate of bug 1822629 *** https://bugs.launchpad.net/bugs/1822629 ** This bug is no longer a duplicate of bug 1713629 tracker-miner-fs crashed with SIGSEGV ** This bug has been marked a duplicate of bug 1822629 /usr/lib/tracker/tracker-miner-fs:11:process_func_start:enumerate_next_cb:next_async_callback_wrapper:g_task_return_now:complete_in_idle_cb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1762974 Title: tracker-miner-fs crashed with SIGSEGV Status in tracker-miners package in Ubuntu: New Bug description: It crashed while I was adding and removing folders in Search Locations in Settings. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: tracker-miner-fs 2.0.4-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 11:07:37 2018 ExecutablePath: /usr/lib/tracker/tracker-miner-fs InstallationDate: Installed on 2017-10-02 (190 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) ProcCmdline: /usr/lib/tracker/tracker-miner-fs SegvAnalysis: Segfault happened at: 0x7f723f68a566:mov0x18(%rdi),%rbp PC (0x7f723f68a566) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-27 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1762974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
I proposed a fix upstream [1]. A workaround can be added to apport to workaroud this while polkit is fixed upstream: we could for example spawn pkttyagent manually (a similar approach is used by systemd). [1] https://gitlab.freedesktop.org/polkit/polkit/merge_requests/28 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in policykit-1 package in Ubuntu: New Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740869] Re: is not responding window is constantly showing when debugging a program
This has already been fixed both in Disco and Cosmic. The commit to be SRUed in Bionic is this one: https://gitlab.gnome.org/GNOME/gnome- shell/commit/b3045cb964459d050c280a4a4958131cfa24ebfb @3v1n0 Do you want to take care of it or should I do that? -- 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/1740869 Title: is not responding window is constantly showing when debugging a program Status in mutter package in Ubuntu: Confirmed Bug description: Mentioned window about no responding program is showing and stealing focus when I try to debug a Java program in Eclipse. When I click on Wait, it disappears for a moment and opens again. This renders Ubuntu 17.10 with Gnome 3 nearly useless for program debugging. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 2 14:22:56 2018 InstallationDate: Installed on 2017-12-04 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819757] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: nautilus (Ubuntu) Status: Confirmed => In Progress -- 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/1819757 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in Nautilus: New Status in nautilus package in Ubuntu: In Progress Bug description: Crash while display content trash ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 15:55:24 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'208' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-02-10 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_UY:es LANG=es_UY.UTF-8 SegvAnalysis: Segfault happened at: 0x56397cd040d9 : mov(%rbx),%rdi PC (0x56397cd040d9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_get_selection () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1819757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814159] Re: can't move icons to second screen
Fixed in https://launchpad.net/ubuntu/+source/gnome-shell-extension- desktop-icons/19.01.1-1 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) 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-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1814159 Title: can't move icons to second screen Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Bug description: When I try to drag and drop an icon from my left (primary) screen to my right one and let go, it ends up sitting on the right edge of my left screen, instead of landing where I dropped it on the right screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 13:43:18 2019 InstallationDate: Installed on 2018-09-27 (126 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-29 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1814159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812881] Re: backup file (files ending in ~) visible in Desktop on disco, were correctly) hidden in cosmic and previous releases
Fixed in https://launchpad.net/ubuntu/+source/gnome-shell-extension- desktop-icons/19.01.1-1 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) 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-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1812881 Title: backup file (files ending in ~) visible in Desktop on disco, were correctly) hidden in cosmic and previous releases Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Bug description: Prior to disco, if I edited a file on my desktop with an editor such as emacs that created a backup file whose name ended in "~", then this file would be hidden from the Desktop view, which is arguably correct and useful behavior. In disco, the file is annoyingly visible on the desktop. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 11:34:48 2019 InstallationDate: Installed on 2019-01-02 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1812881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps
** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic) ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic) ** Tags added: rls-bb-incoming rls-cc-incoming -- 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/1817020 Title: Touching and dragging an icon on the dock blocks input to other apps Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: Steps to reproduce In GNOME Shell, make sure the Ubuntu dock is visible Using a finger drag, for example, a LibreOffice icon up and down the dock and then drop it on Nautilus. Notice that (sometimes?) the icon will continue to float above the dock and that the mouse will keep the clicky-finger icon. Notice that you can still open Activities and launch an application Notice however, that you can't actually interact with the application you have just launched = What I expected to happen = When releasing the drag the icon would land back on the dock and I could continue to use the desktop as usual. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1817020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
Using gnome-shell and gnome-settings-daemon from bionic-proposed the OSK shows up when clicking on a text entry and the osk is enabled from the a11y settings. Marking a fixed confirmed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-settings-daemon source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
Using gnome-settings-daemon from cosmic-proposed (3.30.1.2-1ubuntu3.1) the OSK shows up when clicking on a text entry and the osk is enabled from the a11y settings. Marking a fixed confirmed. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-settings-daemon source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
