[Desktop-packages] [Bug 184510] A patch has been submitted for review
Patch for "19.10_STABLE" branch: https://reviews.mahara.org/10535 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 Status in onboard package in Ubuntu: Fix Released Bug description: Binary package hint: onboard hardy upgrade from wubi 7.04 install ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Jan 19 22:35:51 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/share/onboard/run-onboard.py InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: nvidia Package: onboard 0.87 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py ProcCwd: /home/wx3200 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: onboard StacktraceTop: ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () Title: run-onboard.py crashed with SIGSEGV Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 184510] A change has been merged
Reviewed: https://reviews.mahara.org/10510 Committed: https://git.mahara.org/mahara/mahara/commit/e76f515b85be75fc04b55b938cdcab262a1fb38e Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit e76f515b85be75fc04b55b938cdcab262a1fb38e Author: Evonne Date: Wed Oct 30 15:46:20 2019 +1300 Bug 184510 Small theme changes - gridstack left/right alignment fix while old layouts need to work - loading messages on dark background - view footer markup - list-group borders behatnotneeded Change-Id: Ib4b9a2b33ad3f18e8fa23a05545bb25bb2eb5d1d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 Status in onboard package in Ubuntu: Fix Released Bug description: Binary package hint: onboard hardy upgrade from wubi 7.04 install ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Jan 19 22:35:51 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/share/onboard/run-onboard.py InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: nvidia Package: onboard 0.87 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py ProcCwd: /home/wx3200 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: onboard StacktraceTop: ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () Title: run-onboard.py crashed with SIGSEGV Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen
i got an email about released. I also notice on here that a fix has been released. I don't see it as an update via software updates. How to I get the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: [Impact] * Shutdown and restart options don't work from the login screen, when the user is not logged in. [Test Case] * Start the system and don't log in, or log out in case the system is set up with autologin. * Restart, then shut down the system using the option in the upper right corner of the login screen. * Observe both operations working. [Regression Potential] * The fix is treating treating the greeter as user display sessions by cherry-picking upstream's change released in v243. The fix itself is very small, but there may be non-obvious security implications. [Original Bug Text] When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580274] Re: Firefox should allow you to set New Tab to certain fixed values
Launchpad has imported 5 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1271727. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-05-10T17:51:11+00:00 U552789 wrote: >From Firefox 41 one is now unable in about:config to set the New Tab to a custom URL, and as far as I remember this is due to certain security issues with New Tab hijacking. So before one could set it to any URL, now one cannot set it to anything, but I think that something in between would be better, so I propose that one is allowed to set the New Tab URL in about:config to certain fixed values. Probably it would allow you to set it to: - about:newtab (Default New Tab page) - about:blank (Blank page) - about:home (Default Firefox home page) But nothing else so there shouldn't be any security issues around New Tab hijacking. Another thing to add, if this does get implemented then I think that the settings should also be accessible through about:preferences and not just about:config as these are essential settings like the home page and will be useful for all users and not just advanced ones. I originally filed a report on this issue here but thought I should also do so upstream: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/1 On 2017-09-10T22:00:16+00:00 Alex Mayorga wrote: [Tracking Requested - why for this release]: ¡Hola Nikita! I ended up here while investigating on https://support.mozilla.org/questions/1174370 https://addons.mozilla.org/firefox/addon/newtaburl/ apparently provided a fix but per the most recent comments and compatibility details it has stopped working since around Firefox 41. Hope this helps. Confirming per the SuMo question. ¡Gracias! Alex Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/2 On 2018-07-21T17:23:15+00:00 U552789 wrote: This is now allowed in about:preferences#home. So as this feature has now been implemented please mark as "FIXED". Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/3 On 2018-07-21T17:24:17+00:00 U552789 wrote: Whoops! Didn't mean to close the bug! It would really be better if it was given proper status. Rather than what a standard user can give it. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/4 On 2019-10-29T21:17:20+00:00 Jdavis-5 wrote: Hello! This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience. Please help us triage by reopening if this issue still persists and should be addressed. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580274/comments/6 ** Changed in: firefox Status: Confirmed => Won't Fix ** Changed in: firefox Importance: Wishlist => Medium -- 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/1580274 Title: Firefox should allow you to set New Tab to certain fixed values Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Fix Released Bug description: From Firefox 41 one is now unable in about:config to set the New Tab to a custom URL, and as far as I remember this is due to certain security issues with New Tab hijacking. So before one could set it to any URL, now one cannot set it to anything, but I think that something in between would be better, so I propose that one is allowed to set the New Tab URL in about:config to certain fixed values. Probably it would allow you to set it to: - about:newtab (Default New Tab page) - about:blank (Blank page) - about:home (Default Firefox home page) But nothing else so there shouldn't be any security issues around New Tab hijacking. Another thing to add, if this does get implemented then I think that the settings should also be accessible through about:preferences and not just about:config as these are essential settings like the home page and will be useful for all users and not just advanced ones. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1580274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https:
[Desktop-packages] [Bug 1847772] Re: E-mail folder names are not localized in thunderbird 68
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Low ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Committed -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Committed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850159] Re: dhclient can't obtain IPv6 addr
closing since the description isn't clear, feel free to reopen if the requested screenshot showing the problem is added though ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid -- 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/1850159 Title: dhclient can't obtain IPv6 addr Status in network-manager package in Ubuntu: Invalid Bug description: gnome-control-center reports Ethernet Connection Failure with TLS Authentication 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Show Connected for Wired Connection 4) Show Disconnected for Wired Connection ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 17:06:43 2019 InstallationDate: Installed on 2019-08-01 (88 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850214] Re: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value()
One thing we discussed with Marco a bit earlier is that it would be nice of apport included some flag if the gsettings cache was coming from /usr/local which is a common cause for reports like this one -- 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/1850214 Title: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value() from g_settings_get_boolean() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2b1107a85955c863c2829d7fe9671b0d20868308 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850696] Re: Regression: cannot close notifications
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1803 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850696 Title: Regression: cannot close notifications Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Upstream reports: * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1805 * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850664] Re: setting-window size overflow
Thank you for your bug report. It's a consequence of the number of panels and the way they are categorized, sort of known but also could be considered as a design issue. It would be nice if they would fit on the screen even for small vertical resolutions though ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1850664 Title: setting-window size overflow Status in gnome-control-center package in Ubuntu: Incomplete Bug description: please refer to the screenshot. did you realize the window length is flowing below the visible screen area in my laptop? this is happening in my newly installed ubuntu 19.10 system unlike all earlier versions from 9.04 to 19.04. Is this according to the plan or just a mistake? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850664] Re: setting-window size overflow
I see the same, and my understanding is that it's intentional when the screen resolution is not high enough to show the whole window. That's why there is a scrollbar, so you can scroll to the menu items at the bottom of the list. Is there anything the current design prevents you from accessing? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1850664 Title: setting-window size overflow Status in gnome-control-center package in Ubuntu: Incomplete Bug description: please refer to the screenshot. did you realize the window length is flowing below the visible screen area in my laptop? this is happening in my newly installed ubuntu 19.10 system unlike all earlier versions from 9.04 to 19.04. Is this according to the plan or just a mistake? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850563] Re: [snap] Google Search via Microphone says No Internet Connection
The only workaround I'm aware of is to use chrome packaged by Google. ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) -- 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/1850563 Title: [snap] Google Search via Microphone says No Internet Connection Status in chromium-browser package in Ubuntu: Won't Fix Bug description: In Ubuntu 19.10, I have Chromium installed via this snap package: sudo snap install chromium With a working internet connect, if I attempt to search google, using the microphone-icon (on the right-side of the google search box), it says I do not have an internet connection. Video: https://youtu.be/pNDKydvUL74 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850673] Re: autofill and password sync does not work for snap version
*** This bug is a duplicate of bug 1849160 *** https://bugs.launchpad.net/bugs/1849160 This is bug #1849160, an unfortunate regression caused by the deb->snap migration. A fix is being SRUed, in the meantime the workaround is to run the following command in a terminal, then close and re-open chromium: snap connect chromium:password-manager-service ** This bug has been marked a duplicate of bug 1849160 after deb->snap transition, chromium no longer sees local password store -- 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/1850673 Title: autofill and password sync does not work for snap version Status in chromium-browser package in Ubuntu: New Bug description: the autofill forms and passwords does not work anymore although one is logged into google account. opening the settings|passwords shows an empty list of username\passwords for sites. nevertheless, clicking on the link [sic] to the passwords in the google account shows they are all stored remotely, just the sync somehow fails to get them over and store them locally. might be $HOME access problem (again). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850702] [NEW] No sound output with headphones
Public bug reported: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa-driver amd64 eoan ** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/bugs/1850702/+attachment/5301496/+files/alsa-info.txt ** Package changed: ubuntu-release-upgrader (Ubuntu) => alsa-driver (Ubuntu) ** Description changed: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but - the sound remains very low. + the sound remains very low. After some time, the buzzing effect comes + back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1850702 Title: No sound output with headphones Status in alsa-driver package in Ubuntu: New Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Changed in: network-manager Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN Status in gnome-control-center: New Status in L2TP over IPsec VPN Manager: New Status in NetworkManager: New Status in strongSwan: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. In case it matters, these additional packages were also required for my initial VPN setup: sudo apt-get install -y network-manager-l2tp network-manager-l2tp- gnome strongswan Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02
[Desktop-packages] [Bug 1850702] [NEW] No sound output with headphones
You have been subscribed to a public bug: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa-driver amd64 eoan -- No sound output with headphones https://bugs.launchpad.net/bugs/1850702 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850696] [NEW] Regression: cannot close notifications
Public bug reported: Upstream reports: * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1805 * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850696 Title: Regression: cannot close notifications Status in gnome-shell package in Ubuntu: New Bug description: Upstream reports: * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1805 * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849285] Re: [SRU] 3.34.2
This bug was fixed in the package gnome-terminal - 3.34.2-1ubuntu1 --- gnome-terminal (3.34.2-1ubuntu1) eoan; urgency=medium * Merge with debian as SRU (LP: #1849285), remaining changes: + gnome-terminal.wrap, debian/rules: - Add a wrapper script to restore command line compatibility. + debian/control.in: - gnome-terminal depends on python3, python3-gi and gir1.2-glib-2.0 for the wrapper script. + Add 0001-Restore-transparency.patch: - Restore transparency support + Add 0001-Add-style-classes-and-CSS-names-to-some-of-our-widge.patch: - Add CSS names and style classes so we can theme things more easily. + Add 0001-screen-window-Extra-padding-around-transparent-termi.patch: - Fix transparency on Wayland. Patch by Owen Taylor, via Debarshi Ray @ Fedora + Add 52_support_apturl.patch: - Support apt: urls. + Add 60_add_lp_handler.patch: - Add a handler for launchpad bug URLs. + Add scrollbar-background-theming.patch: - Draw background under the scrollbar that matches the actual terminal background color. This allows proper theming. gnome-terminal (3.34.2-1) unstable; urgency=medium * New upstream translations update gnome-terminal (3.34.1-1) unstable; urgency=medium * New upstream release * Bump minimum libvte-2.91-dev to 0.58.1 -- Iain Lane Tue, 22 Oct 2019 11:22:40 +0100 ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1849285 Title: [SRU] 3.34.2 Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Eoan: Fix Committed Bug description: [ Description ] We missed the release with this one, but we ought to catch up with upstream. [ QA ] Uploaded under the GNOME SRU policy exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Please test the terminal keeps working, including changing themes, multiple tabs and whatever else you can think of. [ Regression potential ] The substantive change is around full screen terminals not remaining full screen sometimes. So check that this keeps working and nothing else breaks regarding full screening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1849285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Also important information from my side (as above) - when I try to
restore old version of app: 70.0+build2-0ubuntu0.16.04.1 - I have
information that my profile files are too old and aren't compatible
anymore. So beside update from 70 to 71 - there is something wrong with
profile files inconsistency.
--
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/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status in firefox package in Ubuntu:
Confirmed
Bug description:
After update from: 70.0+build2-0ubuntu0.16.04.1 to
71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
message that I can Refresh Firefox (crash) or Start in safe mode (also
crash).
Tech details:
Description: Ubuntu 16.04.6 LTS
Release: 16.04
package name: 71.0~b5+build1-0ubuntu0.16.04.1
Crash log details:
AdapterDeviceID: 0x1616
AdapterDriverVendor: mesa/i965
AdapterDriverVersion: 18.0.5.0
AdapterVendorID: 0x8086
BuildID: 20191028161640
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 4
CrashTime: 1572373123
DOMIPCEnabled: 1
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1572364967
IsWayland: 0
IsWaylandDRM: 0
MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is
invalid)
Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP-
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: beta
SafeMode: 1
SecondsSinceLastCrash: 816
StartupCrash: 0
StartupTime: 1572373025
TelemetryEnvironment:
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
DRI Intel(R) HD Graphics 5500 (Broadwell GT2)
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM
Worker",7584:"QuotaManager
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
[Desktop-packages] [Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1820850/+addcomment ** Changed in: gnome-control-center (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) ** Changed in: mutter (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => martin (mukamuka) -- 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/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Bug description: The first part of our work on better handling of HI-DPI screens got merged upstream in 3.32, but it's for wayland only https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/ Since our default session in Ubuntu is based on xorg we would like to distro patch the x11 equivalent for Disco so our users can benefit from the feature. Updates packages are up for testing in that ppa https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling The main change is https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz The ppa also includes a bugfix and a settings change to allow easy configuration. Note that the feature is behind an experimental gsettings key and the code has no impact on the rendering for users who don't enable it, which means it shouldn't be too risk. It's available as a opt-in for those who want to test it. From our testing it works fine and we feel like it's ready to be included. We do plan to get that work merged upstream in the next cycle so it should not be an Ubuntu delta to carry over forever. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Created attachment 9104193 1575512-follow-up.patch OK, this makes my TB 68.2.1 work. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
TB 68.2.1 (follow-up): https://hg.mozilla.org/releases/comm-esr68/rev/c540ca7f085dcc455cf0250bb7dc5a4d0d02eddd I'll land the C-C part soon after review, yes, a little unorthodox ;-) -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
(In reply to Jorg K (GMT+2) from comment #118) > Yes, what I'm about to land on 68 is not required for 71+. We can deliberate > whether we still want if for consistency. Since TB71 is far from being published, I would give your patch a try. Thx. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Comment on attachment 9104194 1575512-follow-up-trunk.patch I guess it's hard to review since it makes no difference on trunk. You have have to trust me that is fixes TB 68 or do the experiment yourself of getting a version from treeherder and patching the file. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Created attachment 9104180 1575512-follow-up-trunk.patch Hold on, I assume that intl:app-locales-changed doesn't fire in a stock- standard installation with no language packs. We still need to initialisation to make sure the IMAP processing is unblocked. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
(In reply to Jorg K (GMT+2) from comment #116) > I've done a bit more debugging here. > > On trunk, at startup, the events fire in this order: intl:app-locales-changed > en-US, final-ui-startup. So we get the folder names when the latter event > fires, and we're cool. All working as observed on beta. > > On TB 68 I see: intl:app-locales-changed es-ES, final-ui-startup and then > another intl:app-locales-changed en-US. en-US is the chosen language. So > frankly, mozilla68 seems buggy, it advertises the wrong language first and > then the correct language after the UI event has fired :-( > > So the 68 patch is correct to work around it. I'm not sure whether we want to > land the trunk/beta part. > > Axel, thanks again for your suggestion. As you can see, the behaviour has > changed, in 68 it wasn't quite correct, now it is. Maybe it's faster to go > with the workaround for TB 68 instead of trying to locate where the Mozilla > platform changed and then trying to backport that. Does this mean that your patch is obsolete for TB 71+? -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
(In reply to Jorg K (GMT+2) from comment #124) > Eckard, if you're not bored yet, this version will do it: > https://queue.taskcluster.net/v1/task/WQERYcM6Ty68YSs7ngJnNQ/runs/0/artifacts/public/build/target.dmg Excellent!! I just tested this version for two hours. No more problem with the folder names when switching locales! -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Pushed by mozi...@jorgk.com: https://hg.mozilla.org/comm-central/rev/3834c3b93900 Follow-up: Re-initialise folder names on intl:app-locales-changed. r=aceman -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
I'd recommend to keep watching the intl notification. I would totally expect more changes to startup code paths as we extend more fluent and intl stuff in m-c, and that's what we expect the app to respond to. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Yes, what I'm about to land on 68 is not required for 71+. We can deliberate whether we still want if for consistency. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
On the contrary, I'm eager to go on and will do some testing tonight with your patched version! -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
TB 71 beta 2: https://hg.mozilla.org/releases/comm-beta/rev/5da939a404338d73dd43e51cb5d360cdceabc8f6 (In reply to :aceman from comment #123) > Thanks, I think this will be useful on trunk too. I doubt it. If the language changes without a restart, we can re- initialise the folder name cache all we want, but that won't update the names in the UI. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Comment on attachment 9104194 1575512-follow-up-trunk.patch Review of attachment 9104194: - Thanks, I think this will be useful on trunk too. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Eckard, if you're not bored yet, this version will do it: https://queue.taskcluster.net/v1/task/WQERYcM6Ty68YSs7ngJnNQ/runs/0/artifacts/public/build/target.dmg -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
> Since TB71 is far from being published, I would give your patch a try. Thx. Available as beta now from https://www.thunderbird.net/en- US/thunderbird/beta/all/ @Axel: OK, we'll land the C-C part then as well. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
> I'd suggest to invalidate that caching on intl:app-locales-changed Wow, that works, I've locally patched my TB 68.2.1 installation. That's an easy fix on top of what we have already, thanks, Axel!! -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
I've done a bit more debugging here. On trunk, at startup, the events fire in this order: intl:app-locales- changed en-US, final-ui-startup. So we get the folder names when the latter event fires, and we're cool. All working as observed on beta. On TB 68 I see: intl:app-locales-changed es-ES, final-ui-startup and then another intl:app-locales-changed en-US. en-US is the chosen language. So frankly, mozilla68 seems buggy, it advertises the wrong language first and then the correct language after the UI event has fired :-( So the 68 patch is correct to work around it. I'm not sure whether we want to land the trunk/beta part. Axel, thanks again for your suggestion. As you can see, the behaviour has changed, in 68 it wasn't quite correct, now it is. Maybe it's faster to go with the workaround for TB 68 instead of trying to locate where the Mozilla platform changed and then trying to backport that. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Created attachment 9104194 1575512-follow-up-trunk.patch Sigh, `fs` was declared twice. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Please get them from here: http://ftp.mozilla.org/pub/thunderbird/releases/71.0b1/linux-x86_64/xpi/ -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Created attachment 9104178 1575512-follow-up.patch This is the beta/ESR 68 version, trunk to follow. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
I confirm the issue you describe in comment #101. I installed TB 68.2.1 (en-US) from the above link, created a new profile and in Preferences (Options) > Advanced > General > Languages > Set Alternatives added French and German as alternatives, thus installing the French and the German language packs in Add-ons > Languages. Switching from English to French or to German and then switching between German and French works flawlessly and the folder names or correctly localized. But switching back to English from German or from French doesn't localize the folder names back in English, they would stay respectively in German or in French. Removing French and/or German via "Set Alternatives" doesn't work for me. After restarting TB the French and/or German languages are still displayed in the "Thunderbird Language Settings" window and the folder names are still localized in French or German instead of English. You'll have to remove or at least disable both language packs in Add-ons > Languages to force TB to localize the folder names back to English. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
(In reply to Jorg K (GMT+2) from comment #106) > Please get them from here: > http://ftp.mozilla.org/pub/thunderbird/releases/71.0b1/linux-x86_64/xpi/ Thanks. I installed en-US English and German as supplementary UI languages in my French TB 71.0b1 version, switched a dozen times from one language to another, restarted TB, allowed remote contents for several correspondents and restarted, switched again . Folder names are always correctly localized. So it seems that this issue is not reproducible in TB 71. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850681] Re: Touchpad and touchsrceen not working
Thanks again :-) -- 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/1850681 Title: Touchpad and touchsrceen not working Status in xorg package in Ubuntu: New Bug description: touchpad not working, only usb-mouse is recognized. touchscreen functionality not working, but that would be rather less important. Everything else is perfectly fine. (18.04 LTS) TREKSTOR Primebook C11B Thanks :-) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 18:43:32 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2019-10-26 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TREKSTOR Primebook C11B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1.2 dmi.board.asset.tag: Default string dmi.board.name: Apollolake_alk_V01 dmi.board.vendor: TS_weibu dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: Primebook C11B dmi.product.sku: CFALKWW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1850681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
No idea. There's two ways to get to a locale through the chrome reg: - requested languages has that before en-US - there's no en-US chrome package registered for `messenger` How either of those two could happen for just a time-window on startup . no idea. I also don't think that anything changed there recently. To say something constructive, caching the folder names could be the actual problem. I'd suggest to invalidate that caching on intl:app- locales-changed, https://firefox-source- docs.mozilla.org/intl/locale.html#events. Not sure if there's a smooth way to make sure the UI updates. Even longer-term, if you could make the display string of those folders be Fluent and `data-l10n-id`, you shouldn't have these problems at all. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
Created attachment 9104179 1575512-follow-up-trunk.patch Easy tweak to finally get this working across the board. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
I have a Lenovo E585 w/ a Ryzen 5 2500U. I'm having the same issues, horizontal screen tears, parts of a window showing up where they shouldn't. It's mostly on Firefox, but happens when I view PDFs as well. I'm getting different problems on Steam, there it's small colored squares that flash on and off. I'm also having a problem where every time I wake from sleep I get a black screen, not sure if related but maybe it is? I'm happy to upload lspci and dmesg info if that would help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
I've played with it a bit more. It works OK as long as the offending language isn't listed in the "Alternatives". So removing Spanish from the alternatives brings the English folder names back. So I guess there's a bug in the Mozilla platform which we won't get fixed for TB 68. -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
So what are we doing here then? I've spent an extra-ordinary about of time on the niche feature which is clearly quite buggy in mozilla68. I'm not inclined to dedicate more time to it. So either I remove the patch again from TB 68 and you never get localised folder names, or we leave it "as is" with the "bad after-taste" of the previous language :-( - Could you check the new beta, TB 71. As far as I can see, it works there. Hi Axel, maybe you can help me here: If landed a patch https://hg.mozilla.org/comm-central/rev/8c7735bd0dc3 to re-initialise strings for folder names on final-ui-startup. We also suppress any processing creating folders with the wrong names before that point. The patch works on trunk and beta, but not on ESR. There, upon getting the strings again, we get strings from a language pack (which clearly is available at final-ui-startup) which isn't the chosen UI language. That looks like and M-C bug. Maybe I can fix the issue in TB 68 by backporting something what may have been fixed in the Mozilla platform at some stage. Do you know of any bugs in this area? -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847772]
(In reply to Jorg K (GMT+2) from comment #104) > Could you check the new beta, TB 71. As far as I can see, it works there. > I cannot test this in TB 71.0b1 since there are no language packs available for this version! -- 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/1847772 Title: E-mail folder names are not localized in thunderbird 68 Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850681] [NEW] Touchpad and touchsrceen not working
Public bug reported: touchpad not working, only usb-mouse is recognized. touchscreen functionality not working, but that would be rather less important. Everything else is perfectly fine. (18.04 LTS) TREKSTOR Primebook C11B Thanks :-) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 18:43:32 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2019-10-26 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TREKSTOR Primebook C11B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1.2 dmi.board.asset.tag: Default string dmi.board.name: Apollolake_alk_V01 dmi.board.vendor: TS_weibu dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: Primebook C11B dmi.product.sku: CFALKWW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1850681 Title: Touchpad and touchsrceen not working Status in xorg package in Ubuntu: New Bug description: touchpad not working, only usb-mouse is recognized. touchscreen functionality not working, but that would be rather less important. Everything else is perfectly fine. (18.04 LTS) TREKSTOR Primebook C11B Thanks :-) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 18:43:32 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2019-10-26 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TREKSTOR Primebook C11B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1.2 dmi.board.asset.tag: Default string dmi.board.name: Apollolake_alk_V01 dmi.board.vendor: TS_weibu dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: Primebook C11B dmi.product.sku: CFALKWW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: li
Re: [Desktop-packages] [Bug 1850214] Re: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_valu
On Wed, Oct 30, 2019 at 05:22:05PM -, Brian Murray wrote: > If this, 'gsettings abort when schemas/keys are missing', is a class of > crash which is not valuable can we prevent reporting them in the apport > package hook or in apport in general? It is valuable if it's pointing to a bug in the distribution, for example a missing dependency on a package providing a schema. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1850214 Title: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value() from g_settings_get_boolean() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2b1107a85955c863c2829d7fe9671b0d20868308 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850214] Re: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value()
If this, 'gsettings abort when schemas/keys are missing', is a class of crash which is not valuable can we prevent reporting them in the apport package hook or in apport in general? -- 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/1850214 Title: gnome-shell crashed with SIGTRAP in g_settings_schema_get_value() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get_value() from g_settings_get_boolean() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2b1107a85955c863c2829d7fe9671b0d20868308 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]
How do I record this bug as affecting Lubuntu, I think I was told to submit bugs to Lubuntu Packages Team (~lubuntu-packaging), I have no idea how to work launch pad :P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1757321 Title: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic] Status in udisks2 package in Ubuntu: Fix Released Bug description: after upgrading to bionic, attempts to mount an encrypted USB drive fail with the error "function bd_crypto_luks_open_blob called but not implemented" Installing libblockdev-crypto2 and libblockdev-crypto-dev and rebooting appears to have fixed it, but should that be necessary? or at least better documented? (https://www.distrowatch.com/weekly.php?issue=20171113 is the only reference I could find on the error) [Workaround] 1. Install libblockdev-crypto2 2. Restart udisks: $ systemctl restart udisks2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules Date: Tue Mar 20 20:28:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (942 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850673] [NEW] autofill and password sync does not work for snap version
Public bug reported: the autofill forms and passwords does not work anymore although one is logged into google account. opening the settings|passwords shows an empty list of username\passwords for sites. nevertheless, clicking on the link [sic] to the passwords in the google account shows they are all stored remotely, just the sync somehow fails to get them over and store them locally. might be $HOME access problem (again). ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1850673 Title: autofill and password sync does not work for snap version Status in chromium-browser package in Ubuntu: New Bug description: the autofill forms and passwords does not work anymore although one is logged into google account. opening the settings|passwords shows an empty list of username\passwords for sites. nevertheless, clicking on the link [sic] to the passwords in the google account shows they are all stored remotely, just the sync somehow fails to get them over and store them locally. might be $HOME access problem (again). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850563] Re: [snap] Google Search via Microphone says No Internet Connection
Interesting. Any work-rounds at the user-level? -- 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/1850563 Title: [snap] Google Search via Microphone says No Internet Connection Status in chromium-browser package in Ubuntu: Won't Fix Bug description: In Ubuntu 19.10, I have Chromium installed via this snap package: sudo snap install chromium With a working internet connect, if I attempt to search google, using the microphone-icon (on the right-side of the google search box), it says I do not have an internet connection. Video: https://youtu.be/pNDKydvUL74 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850664] Re: setting-window size overflow
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1850664 Title: setting-window size overflow Status in gnome-control-center package in Ubuntu: New Bug description: please refer to the screenshot. did you realize the window length is flowing below the visible screen area in my laptop? this is happening in my newly installed ubuntu 19.10 system unlike all earlier versions from 9.04 to 19.04. Is this according to the plan or just a mistake? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850664] [NEW] setting-window size overflow
You have been subscribed to a public bug: please refer to the screenshot. did you realize the window length is flowing below the visible screen area in my laptop? this is happening in my newly installed ubuntu 19.10 system unlike all earlier versions from 9.04 to 19.04. Is this according to the plan or just a mistake? ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- setting-window size overflow https://bugs.launchpad.net/bugs/1850664 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850563] Re: [snap] Google Search via Microphone says No Internet Connection
I suspect this is because the speech API isn't enabled for the API key used by chromium. The terms of service wouldn't allow us to enable it for anything but development purposes (https://console.developers.google.com/tos?id=speech). ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- 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/1850563 Title: [snap] Google Search via Microphone says No Internet Connection Status in chromium-browser package in Ubuntu: Won't Fix Bug description: In Ubuntu 19.10, I have Chromium installed via this snap package: sudo snap install chromium With a working internet connect, if I attempt to search google, using the microphone-icon (on the right-side of the google search box), it says I do not have an internet connection. Video: https://youtu.be/pNDKydvUL74 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847858] Re: No num lock upon starting Unity session
Confirmed on Ubuntu 19.10 with Unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1847858 Title: No num lock upon starting Unity session Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 fully dist-upgraded For a couple weeks now, there is no num lock upon starting the Unity session, as there should be. Behaviour confirmed on two separate Ubuntu 19.10 Unity stations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1847858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847858] Re: No num lock upon starting Unity session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1847858 Title: No num lock upon starting Unity session Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 fully dist-upgraded For a couple weeks now, there is no num lock upon starting the Unity session, as there should be. Behaviour confirmed on two separate Ubuntu 19.10 Unity stations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1847858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
This needs Regression Potential SRU information completed please. -- 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/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Incomplete Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1792932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850668] [NEW] No conozco el error
Public bug reported: NO se que le pasa ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CompositorRunning: None Date: Wed Oct 30 17:33:50 2019 DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed nvidia, 430.50, 5.3.0-19-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1261] InstallationDate: Installed on 2019-08-19 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire A717-72G ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux acpi_backlight=vendor quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charizard_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Aspire 7 dmi.product.name: Aspire A717-72G dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Oct 30 16:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4509 vendor AUO xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1850668 Title: No conozco el error Status in xorg package in Ubuntu: New Bug description: NO se que le pasa ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CompositorRunning: None Date: Wed Oct 30 17:33:50 2019 DistUpgraded: 2019-10-23 18:48:24,042 ERROR got er
[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
This, however, should fix the problem when the personal-files interface isn't connected: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=8799b7e8e5c6b8af9aa789df745b2dacb3652f02 -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: [Impact] * Shutdown and restart options don't work from the login screen, when the user is not logged in. [Test Case] * Start the system and don't log in, or log out in case the system is set up with autologin. * Restart, then shut down the system using the option in the upper right corner of the login screen. * Observe both operations working. [Regression Potential] * The fix is treating treating the greeter as user display sessions by cherry-picking upstream's change released in v243. The fix itself is very small, but there may be non-obvious security implications. [Original Bug Text] When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: [Impact] * Shutdown and restart options don't work from the login screen, when the user is not logged in. [Test Case] * Start the system and don't log in, or log out in case the system is set up with autologin. * Restart, then shut down the system using the option in the upper right corner of the login screen. * Observe both operations working. [Regression Potential] * The fix is treating treating the greeter as user display sessions by cherry-picking upstream's change released in v243. The fix itself is very small, but there may be non-obvious security implications. [Original Bug Text] When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Fixed in Focal, to be SRU-d to Eoan. ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- 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/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: [Impact] * Shutdown and restart options don't work from the login screen, when the user is not logged in. [Test Case] * Start the system and don't log in, or log out in case the system is set up with autologin. * Restart, then shut down the system using the option in the upper right corner of the login screen. * Observe both operations working. [Regression Potential] * The fix is treating treating the greeter as user display sessions by cherry-picking upstream's change released in v243. The fix itself is very small, but there may be non-obvious security implications. [Original Bug Text] When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
snap disconnect chromium:chromium-config snap connect chromium:chromium-config This is resolved my issue -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651] [NEW] Authentication constantly re-requested for Google
Public bug reported: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. + + I am using OAuth2 (so this ( https://support.mozilla.org/en- + US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: adam 3444 F pulseaudio - /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: adam 3444 F pulseaudio + /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: - default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 - 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown - 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown - 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 - 192.168.1.0/24 dev wlp3s0 proto kernel scope lin
[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
Well spotted! I wonder how the personal-files interface ended up in this semi-connected state for Alexey… In any case, Alexey to work around the problem I would suggest disconnecting and reconnecting the personal-files interface: snap disconnect chromium:chromium-config snap connect chromium:chromium-config And I'm going to add a " || true" as suggested by Jalon Funk. -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
In fact adding a " || true" statement doesn't cut it, chromium still fails to start with the same error. -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850563] Re: [snap] Google Search via Microphone says No Internet Connection
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1850563 Title: [snap] Google Search via Microphone says No Internet Connection Status in chromium-browser package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10, I have Chromium installed via this snap package: sudo snap install chromium With a working internet connect, if I attempt to search google, using the microphone-icon (on the right-side of the google search box), it says I do not have an internet connection. Video: https://youtu.be/pNDKydvUL74 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850650] Re: webkit-gtk crash on nvdia closed-source driver
Workaround: WEBKIT_DISABLE_COMPOSITING_MODE=1 surf https://google.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1850650 Title: webkit-gtk crash on nvdia closed-source driver Status in webkit2gtk package in Ubuntu: New Bug description: When I start "surf https://www.google.com"; surf reports a webkit crash: This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 264 error_code 2 request_code 152 (GLX) minor_code 34) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) web process terminated: crashed I have been able to reproduce this error on many other sites (not just google.com), but it doesn't crash on simple html sites (such as http://neverssl.com and https://isitfridayyet.com). Disabling images (-i option on surf), does not resolve the crash. I have been able to reproduce this crash on simple GTK webkit demo- applications, suggesting this is not caused by surf, but by webkit-gtk instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libwebkit2gtk-4.0-37 2.26.1-3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Oct 30 15:34:17 2019 InstallationDate: Installed on 2018-05-26 (521 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: webkit2gtk UpgradeStatus: Upgraded to eoan on 2019-10-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1850650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850650] [NEW] webkit-gtk crash on nvdia closed-source driver
Public bug reported: When I start "surf https://www.google.com"; surf reports a webkit crash: This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 264 error_code 2 request_code 152 (GLX) minor_code 34) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) web process terminated: crashed I have been able to reproduce this error on many other sites (not just google.com), but it doesn't crash on simple html sites (such as http://neverssl.com and https://isitfridayyet.com). Disabling images (-i option on surf), does not resolve the crash. I have been able to reproduce this crash on simple GTK webkit demo- applications, suggesting this is not caused by surf, but by webkit-gtk instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libwebkit2gtk-4.0-37 2.26.1-3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Oct 30 15:34:17 2019 InstallationDate: Installed on 2018-05-26 (521 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: webkit2gtk UpgradeStatus: Upgraded to eoan on 2019-10-24 (6 days ago) ** Affects: webkit2gtk (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 webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1850650 Title: webkit-gtk crash on nvdia closed-source driver Status in webkit2gtk package in Ubuntu: New Bug description: When I start "surf https://www.google.com"; surf reports a webkit crash: This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 264 error_code 2 request_code 152 (GLX) minor_code 34) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) web process terminated: crashed I have been able to reproduce this error on many other sites (not just google.com), but it doesn't crash on simple html sites (such as http://neverssl.com and https://isitfridayyet.com). Disabling images (-i option on surf), does not resolve the crash. I have been able to reproduce this crash on simple GTK webkit demo- applications, suggesting this is not caused by surf, but by webkit-gtk instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libwebkit2gtk-4.0-37 2.26.1-3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Oct 30 15:34:17 2019 InstallationDate: Installed on 2018-05-26 (521 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: webkit2gtk UpgradeStatus: Upgraded to eoan on 2019-10-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1850650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
There's another problem I'm not sure if is related: even if the icon is well handled, the opened window will not show as an individual one on taskbar - it will still recognized as a window of Chromium itself with a Chromium icon. On the deb version of Chromium is works correctly. -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Triaged Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths.  tracking:candidate installed: 62.0.3202.94 (123) 246MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850646] [NEW] Sound output device switched on DP/MST connect
Public bug reported: 1. Starting with sound output set to line-out with DP/MST/HDMI monitor connected. 2. Disconnect monitor. Sound output remains on line-out. Music continues playing etc. 3. Re-connect monitor. Music/sound stops being produced. Sound output device is switched to HDMI/Display Port 6 device. Sound output device should remain on user-selected device unless user interactively changes the output device. Or add configurable option for "sound output device auto switching". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.3.7-050307-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 10:14:02 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (329 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (7 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-01-08T10:59:11.363686 ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850646 Title: Sound output device switched on DP/MST connect Status in gnome-shell package in Ubuntu: New Bug description: 1. Starting with sound output set to line-out with DP/MST/HDMI monitor connected. 2. Disconnect monitor. Sound output remains on line-out. Music continues playing etc. 3. Re-connect monitor. Music/sound stops being produced. Sound output device is switched to HDMI/Display Port 6 device. Sound output device should remain on user-selected device unless user interactively changes the output device. Or add configurable option for "sound output device auto switching". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.3.7-050307-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 10:14:02 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (329 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (7 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-01-08T10:59:11.363686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
It also breaks games from Steam in full-screen mode. For example, Counter-Strike 1.6 fullscreen window become minimized after layout change. Ridiculous. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in GNOME Settings Daemon: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848841] Re: Chromium snap looks tiny in hidpi after gnome shell restart
Hi Olivier, sorry for the delay, I've installed Chrome from the official
deb and it also happens there so it seems like a non-snap specific,
upstream bug.
Do you have any idea what kind of "signal" could the app be receiving
when shell restarts? It's really weird that it somehow resets to 1x
scale.
** Summary changed:
- Chromium snap looks tiny in hidpi after gnome shell restart
+ Chromium/Chrome looks tiny in hidpi after gnome shell restart
--
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/1848841
Title:
Chromium/Chrome looks tiny in hidpi after gnome shell restart
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded
to 19.10 and chromium became a snap package. It launches at the right
scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to
1x (I believe) and everything becomes absurdly tiny. Restarting
chromium afterwards restores the right scaling factor.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBRmIgTACobAQSlHRR4Asr8pFZPnicOT1UBAQEBAQEBAQEBAQEBAQEBuJi4oLDQPnAwIDUAJcQQAAAaAAAY/gBUSUFOTUEgWE0g/wBUTDEzOUdEWFAwMQAAAF8=
modes: 3000x2000
Date: Sat Oct 19 05:11:37 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 331G 62G 255G 20% /
tmpfs tmpfs 7,8G 75M 7,7G 1% /dev/shm
/dev/nvme0n1p2 ext4 331G 62G 255G 20% /
InstallationDate: Installed on 2019-06-13 (127 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd
(Foxlink) HD Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HUAWEI MACH-WX9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic
root=UUID=08b323c0-f1a9-46a9-8d2c-694dff8193f6 ro quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion: Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2018
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.17
dmi.board.name: MACH-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M14
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M14
dmi.modalias:
dmi:bvnHUAWEI:bvr1.17:bd07/28/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
dmi.product.family: HUAWEI MateBook X
dmi.product.name: MACH-WX9
dmi.product.sku: C128
dmi.product.version: M14
dmi.sys.vendor: HUAWEI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848841/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837746] Re: [snap] wrapper script doesn't source ~/.chromium-browser.init
I can confirm that if "personal-files" slot isn't connected and "~/.chromium-browser.init" exist then chromium snap fails to start. The solution is to either connect "personal-files" slot or delete "~/.chromium-browser.init" (arguably it's pointless to have this file if access is blocked). @osomon you may also use something like: test -f $REALHOME/.chromium-browser.init && . $REALHOME/.chromium- browser.init || true which will ignore failure of sourcing ".chromium-browser.init" and let chromium start. -- 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/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850635] [NEW] Some applications don't redraw their windows correctly
Public bug reported: After updating from 19.04 to 19.10 I noted that some apps don't redraw their window(s) correctly. Affected apps include (it seems) all Qt- based apps (including KDE and VirtualBox), as well as firefox/thunderbird. Unaffected apps include emacs, chrome, xterm. The symptom is that an affected app will only redraw its window when another X window redraws its window. If there is no other window, then the app's window is not redrawn at all. This is best illustrated with a video, which shows the problem using konsole and kpat (both KDE apps) :- https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA I am using the intel graphics driver (no graphics card). Other info as requested below :- $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy xserver-xorg xserver-xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 30 11:50:09 2019 DistUpgraded: 2019-10-21 13:25:02,550 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000] InstallationDate: Installed on 2016-01-02 (1396 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=8af2cd02-0009-4ce5-9ec6-e6cdf44c9411 ro nopti SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-21 (8 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF2:bd07/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 #enabled=1 enabled=0 mtime.conffile..etc.default.apport: 2016-01-06T17:10:43.876145 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 eoan 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/1850635 Title: Some applications don't redraw their windows correctly Status in xorg package in Ubuntu: New Bug description: After updating from 19.04 to 19.10 I noted that some apps don't redraw their window(s) correctly. Affected apps include (it seems) all Qt- based apps (including KDE and VirtualBox), as well as firefox/thunderbird. Unaffected apps include emacs, chrome, xterm. The symptom is that an affected app will only redraw its window when another X window redraws its window. If there is no other window, then the app's window is not redrawn at all. This is best illustrated with a video, which shows the problem using konsole and kpat (both KDE apps) :- https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA I am using the intel graphics driver (no graphics card). Other info as requested below :- $ lsb_release -rd Descri
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
There is a systemd 243 build in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801 for Eoan, it may worth a shot to try it, but it looks like an issue with nvidia's drivers rather than a bug in systemd. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Unfortunately, I can't reproduce the problem on my system, running the 435 driver in 19.10. What I don't see on my system is the following error from logind: Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (EE) Error systemd-logind returned paused fd for drm node Compare this from Martin's journald log: Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) xfree86: Adding drm device (/dev/dri/card0) ... Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 1 Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (EE) Error systemd-logind returned paused fd for drm node Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) systemd-logind: releasing fd for 226:0 Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (--) PCI:*(1@0:0:0) 10de:1b06:1043:85e4 rev 161, Mem @ 0xde00/16777216, 0xc000/268435456, 0xd000/33554432, I/O @ 0xe000/128, BIOS @ 0x/131072 Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) LoadModule: "glx" With what happens on my system: ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (II) xfree86: Adding drm device (/dev/dri/card0) ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0 ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (--) PCI:*(1@0:0:0) 10de:1b80:10de:119e rev 161, Mem @ 0xf600/16777216, 0xe000/268435456, 0xf000/33554432, I/O @ 0xe000/128, ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (II) LoadModule: "glx" I could be an bug in logind. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassi
[Desktop-packages] [Bug 1850627] [NEW] Right click happens automatically, disturbs work
Public bug reported: Since the last 3-4 days, the right click happens all by itself. Sometimes replacing the left click, while working in Inkscape or handling files on desktop for a fully updated 18.04. It is so annoying and good enough to destroy the work we are doing. I manually cleaned my mouse just in case hardware is causing the issue I tried using Cinnamon DE. There was no such issue in it. It would be great if there could be a fix. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 16:35:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-12 (109 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850627 Title: Right click happens automatically, disturbs work Status in gnome-shell package in Ubuntu: New Bug description: Since the last 3-4 days, the right click happens all by itself. Sometimes replacing the left click, while working in Inkscape or handling files on desktop for a fully updated 18.04. It is so annoying and good enough to destroy the work we are doing. I manually cleaned my mouse just in case hardware is causing the issue I tried using Cinnamon DE. There was no such issue in it. It would be great if there could be a fix. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 16:35:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-12 (109 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850088] Re: permission denied when opening a mounted folder in save file dialog
The "proper fix" may never arrive because sandboxing is core feature of
snaps and blocking access to dotfiles is inherent part of sandbox. So
from snap perspective your workflow is invalid.
There are two solutions: adjust your workflow or abandon chromium snap.
It's up to you what you choose.
--
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/1850088
Title:
permission denied when opening a mounted folder in save file dialog
Status in chromium-browser package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu 19.10, when I tried to open a file into a
sshfs-mounted folder inside my home folder, it says permission denied.
This didn't happen at Ubuntu 19.04.
Steps to reproduce:
1. Use sshfs to mount a sftp folder on an empty folder inside my home drive
(e.g. ~/.server)
2. Create a soft link in the home folder to a folder inside the mounted sftp
file system (e.g. ~/server > .server/home/michael )
3. Open chromium
4. Download a file
5. Enter that folder in the file dialog
Expected result:
I can enter the folder
Actual result:
It says permission denied
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
DRM.card1-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card1-VGA-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBBDGbAJEYAAA8WAQNuMx14LspFpFZLnCUSUFS9SwDRwLMAlQCBgJUPAQEBAQEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxMjE1MDE3OTU2/ABQaGlsaXBzIDIzNENM/QA4TB5TEQAKICAgICAgAHs=
modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768
1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400
Date: Mon Oct 28 10:14:27 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/vg0-root ext4 230G 190G 29G 87% /
tmpfstmpfs 7.8G 165M 7.6G 3% /dev/shm
/dev/mapper/vg0-root ext4 230G 190G 29G 87% /
InstallationDate: Installed on 2016-10-03 (1119 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=/dev/mapper/vg0-root ro quiet splash resume=/dev/vg0/swap vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)
dmi.bios.date: 08/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd08/13/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850088/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850621] [NEW] zoom sets wrong window size in fullscreen mode
Public bug reported: Using eoan 19.10 and wayland and the following package versions * gnome-shell 3.34.1ubuntu1 * gnome-terminal 3.34.0-1ubuntu2 * mutter 3.34.1-1ubuntu1 * libmutter-5-0 3.34.1-1ubuntu1 How to reproduce: * I open up gnome-terminal and switch to fullscreen (F11). * Then I decrease font-size / zoom (CTRL+-). * The gnome-terminal window no longer fills the display. The window size is reduced proportionally to the reduction in font size. The same applies for zooming in / increasing font size. The window is then larger than the display and the cursor is outside of the viewport. What I expect: * No matter the font size, the gnome-terminal window should cover the whole display (not more, not less) as long as gnome-terminal is in fullscreen mode. As far as I remember, this was working before in Ubuntu 19.04 disco. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1850621 Title: zoom sets wrong window size in fullscreen mode Status in gnome-terminal package in Ubuntu: New Bug description: Using eoan 19.10 and wayland and the following package versions * gnome-shell 3.34.1ubuntu1 * gnome-terminal 3.34.0-1ubuntu2 * mutter 3.34.1-1ubuntu1 * libmutter-5-0 3.34.1-1ubuntu1 How to reproduce: * I open up gnome-terminal and switch to fullscreen (F11). * Then I decrease font-size / zoom (CTRL+-). * The gnome-terminal window no longer fills the display. The window size is reduced proportionally to the reduction in font size. The same applies for zooming in / increasing font size. The window is then larger than the display and the cursor is outside of the viewport. What I expect: * No matter the font size, the gnome-terminal window should cover the whole display (not more, not less) as long as gnome-terminal is in fullscreen mode. As far as I remember, this was working before in Ubuntu 19.04 disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850619] [NEW] evince crash on startup with segmentation fault
Public bug reported: I'm unable since a few weeks to open evince, since it crashes with a segmentation fault at launch. Ubuntu release: 18.04.3 LTS $ apt-cache policy evince evince: Installato: 3.28.4-0ubuntu1.2 Candidato: 3.28.4-0ubuntu1.2 Tabella versione: *** 3.28.4-0ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Repro: $ evince [1]25999 segmentation fault (core dumped) evince Attaching crash report. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_evince.1000.crash" https://bugs.launchpad.net/bugs/1850619/+attachment/5301367/+files/_usr_bin_evince.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1850619 Title: evince crash on startup with segmentation fault Status in evince package in Ubuntu: New Bug description: I'm unable since a few weeks to open evince, since it crashes with a segmentation fault at launch. Ubuntu release: 18.04.3 LTS $ apt-cache policy evince evince: Installato: 3.28.4-0ubuntu1.2 Candidato: 3.28.4-0ubuntu1.2 Tabella versione: *** 3.28.4-0ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Repro: $ evince [1]25999 segmentation fault (core dumped) evince Attaching crash report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1850619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850615] Re: gnome-shell hardlocks under load
This sounds suspicious: 5 Thread 0x7f7432336700 (LWP 26358) "gnome-s:disk$0" Separately, you seem to have a number of extensions installed: 'remmina-search-provi...@alexmurray.github.com' 'alt-tab-worksp...@kwalo.net' 'openweather-extens...@jenslody.de' 'un...@hardpixel.eu' 'gsconn...@andyholmes.github.io' 'cpuf...@zdyb.tk' 'cpufreq@konkor' 'cpupo...@mko-sl.de' 'drive-m...@gnome-shell-extensions.gcampax.github.com' Although I mostly suspect the last one, please uninstall all of them and see if that solves the problem. You will need to uninstall them all and not just disable them because extensions can still interfere when installed and disabled. We need to do this because so many bugs are caused by extensions. Eliminating them very often solves the problem. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850615 Title: gnome-shell hardlocks under load Status in gnome-shell package in Ubuntu: Incomplete Bug description: With the upgrade to eoan, my GNOME and Ubuntu sessions started locking up hard when under load (i.e. when I start my session and start a bunch of applications). I couldn't find anything special in gdb, whether it's stuck or not, the stack looks mostly the same: (gdb) info threads Id Target Id Frame * 1Thread 0x7f7439f6bcc0 (LWP 26352) "gnome-shell"0x7f743f7f5c2f in __GI___poll (fds=0x7ffc1a361ba8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 2Thread 0x7f7439f68700 (LWP 26354) "gmain" 0x7f743f7f5c2f in __GI___poll (fds=0x556aeb3369e0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7f7433fff700 (LWP 26356) "gdbus" 0x7f743f7f5c2f in __GI___poll (fds=0x7f73fc002070, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7f74337fe700 (LWP 26357) "dconf worker" 0x7f743f7f5c2f in __GI___poll (fds=0x556aeb377c50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 5Thread 0x7f7432336700 (LWP 26358) "gnome-s:disk$0" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb339d28) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 6Thread 0x7f74311a7700 (LWP 26384) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 7Thread 0x7f7430fa6700 (LWP 26385) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 8Thread 0x7f7430da5700 (LWP 26386) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 9Thread 0x7f7430ba4700 (LWP 26387) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb33446c) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 10 Thread 0x7f74082d4700 (LWP 26696) "threaded-ml"0x7f743f7f5c2f in __GI___poll (fds=0x7f73f4002910, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7f73d3fff700 (LWP 2290) "threaded-ml" 0x7f743f7f5c2f in __GI___poll (fds=0x7f73cc003130, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Wed Oct 30 10:46:53 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850615] [NEW] gnome-shell hardlocks under load
Public bug reported: With the upgrade to eoan, my GNOME and Ubuntu sessions started locking up hard when under load (i.e. when I start my session and start a bunch of applications). I couldn't find anything special in gdb, whether it's stuck or not, the stack looks mostly the same: (gdb) info threads Id Target Id Frame * 1Thread 0x7f7439f6bcc0 (LWP 26352) "gnome-shell"0x7f743f7f5c2f in __GI___poll (fds=0x7ffc1a361ba8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 2Thread 0x7f7439f68700 (LWP 26354) "gmain" 0x7f743f7f5c2f in __GI___poll (fds=0x556aeb3369e0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7f7433fff700 (LWP 26356) "gdbus" 0x7f743f7f5c2f in __GI___poll (fds=0x7f73fc002070, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7f74337fe700 (LWP 26357) "dconf worker" 0x7f743f7f5c2f in __GI___poll (fds=0x556aeb377c50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 5Thread 0x7f7432336700 (LWP 26358) "gnome-s:disk$0" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb339d28) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 6Thread 0x7f74311a7700 (LWP 26384) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 7Thread 0x7f7430fa6700 (LWP 26385) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 8Thread 0x7f7430da5700 (LWP 26386) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 9Thread 0x7f7430ba4700 (LWP 26387) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb33446c) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 10 Thread 0x7f74082d4700 (LWP 26696) "threaded-ml"0x7f743f7f5c2f in __GI___poll (fds=0x7f73f4002910, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7f73d3fff700 (LWP 2290) "threaded-ml" 0x7f743f7f5c2f in __GI___poll (fds=0x7f73cc003130, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Wed Oct 30 10:46:53 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-28 (1 days ago) ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850615 Title: gnome-shell hardlocks under load Status in gnome-shell package in Ubuntu: New Bug description: With the upgrade to eoan, my GNOME and Ubuntu sessions started locking up hard when under load (i.e. when I start my session and start a bunch of applications). I couldn't find anything special in gdb, whether it's stuck or not, the stack looks mostly the same: (gdb) info threads Id Target Id Frame * 1Thread 0x7f7439f6bcc0 (LWP 26352) "gnome-shell"0x7f743f7f5c2f in __GI___poll (fds=0x7ffc1a361ba8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 2Thread 0x7f7439f68700 (LWP 26354) "gmain" 0x7f743f7f5c2f in __GI___poll (fds=0x556aeb3369e0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7f7433fff700 (LWP 26356) "gdbus" 0x7f743f7f5c2f in __GI___poll (fds=0x7f73fc002070, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7f74337fe700 (LWP 26357) "dconf worker" 0x7f743f7f5c2f in __GI___poll (fds=0x556aeb377c50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 5Thread 0x7f7432336700 (LWP 26358) "gnome-s:disk$0" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb339d28) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 6Thread 0x7f74311a7700 (LWP 26384) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 7Thread 0x7f7430fa6700 (LWP 26385) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 8Thread 0x7f7430da5700 (LWP 26386) "JS Helper" futex_wait_cancelable (private=, expected=0, futex_word=0x556aeb334468) at ../sysdeps/unix/sysv/linux/futex-in
[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
Ubuntu 19.10, Gnome-Session, same problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install hplip-gui 3. Launch GNOME session. 4. Get error message window with header "HPLIP Status Service" and text "No system tray detected on this system. Unable to start, exiting." Expected results: hp-systray is compatible with modern GNOME Actual results: hp-systray is not compatible with modern GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 (dbus://) went away, retrying! CurrentDesktop: GNOME Date: Sat Sep 2 14:10:19 2017 InstallationDate: Installed on 2017-08-26 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. UX32A PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850052] Re: installing zsys breaks desktop login
This bug was fixed in the package zsys - 0.2.2+19.04 --- zsys (0.2.2+19.04) eoan; urgency=medium * Backward compatibility for org.zsys set on user datasets and transition to newer com.ubuntu.zsys (LP: #1850052) -- Didier Roche Mon, 28 Oct 2019 09:51:38 +0100 ** Changed in: zsys (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1850052 Title: installing zsys breaks desktop login Status in zsys package in Ubuntu: Fix Released Status in zsys source package in Eoan: Fix Released Bug description: [Impact] After installing zsys on 19.10, you can't log in in your desktop. Removing it won't fix the issue. [Test Case] Test A: (migrating broken people) 1. Install 19.10 using experimental ZFS disk partitioning and reboot on installed system. 2. sudo apt install zsys 3. Reboot 4. Attempt to login to the desktop -> you can't log in. 5. Go to a tty (ctrl + alt + F3) and log in as your user 6. Install zsys 0.2.3 from -proposed 7. Reboot -> you can now log in in GDM. Test B: (direct installation) 1. Install 19.10 using experimental ZFS disk partitioning and reboot on installed system. 2. Install zsys from proposed 3. Reboot -> you can log in in GDM. [Regression Potential] Due to a missing rename in the installer from "org.zsys" to "com.ubuntu.zsys", we added transitional code which can be dropped in 20.04 as soon as compatible ubiquity is installed. People in 19.10 up to date (with the SRU fix) will have the required compatible tag. Note that we only due to transition once, the first time we are able to set the current timestamp. This doesn't regress any existing tests. Note that as this is due to unsync behavior between installer and zsys, zsys is behaving as expecting (unfortunately to the user) and the transitional code being removed soon, we didn't add a special test which will be removed later on. - I installed zsys on an up to date 19.10 system and can now no longer login. Removing zsys from a tty does not solve the problem. The home partition is no longer available - I have "lost" all my files, which were there before I installed zsys and rebooted Steps to reproduce. 1. Install 19.10 using experimental ZFS disk partitioning. 2. Complete the first run wizard 3. Install all updates 4. sudo apt install zsys 5. reboot 6. Attempt to login to the desktop Actual outcome * GDM accepts user/password, clears screen, looks like desktop is about to start, then I get dropped back to GDM Expected outcome * Login successful. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zsys 0.2.2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 27 14:50:10 2019 InstallationDate: Installed on 2019-10-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1850052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
** Changed in: gnome-tweaks (Ubuntu) Status: Incomplete => New ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => New ** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-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/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825785] Re: lightdm: screen does not wake up on mouse/keyboard events
I think I have the same bug.
I use Xubuntu 19.10.
When the screen locks, mouse and keyboard events will lake me to the
unlock screen. Password is accepted, but screen never shows the
desktop. I can log out and log in again to restore the desktop, but of
course this closes all applications.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1825785
Title:
lightdm: screen does not wake up on mouse/keyboard events
Status in lightdm package in Ubuntu:
Confirmed
Status in xfce package in Ubuntu:
Confirmed
Status in lightdm package in openSUSE:
New
Bug description:
Description: When session is locked either using dm-tool or light-
locker, lightdm greeter is functional (you can type your password and
press Enter to unlock the session) but screen is not turned on, and
remains turned off even when you move the mouse or press any key.
Although, it doesn't occur when you close your session instead locking
it.
Additional info:
* xorg: 1:7.7+19ubuntu12
* lightdm 1.28.0-0ubuntu1
* xfce4-session: 4.12.1-6ubuntu1
From lsb_release:
Description: Ubuntu 19.04
Release: 19.04
* Reproducible on other distributions as well. See here:
https://bugs.archlinux.org/task/59750
* Reproducible on both Intel UHD Graphics and AMDGPU Graphics.
Steps to reproduce:
* Lock the running session using lightdm
* Screen is turned off, but it won't turn back on when you move the mouse or
use the keyboard
* You can type the password and press Enter to unlock the session. It the
password is correct, the screen will finally turn on and you will be at your
desktop.
Note: switching out and then switching back to tty7 restores
visibility of the lock screen.
On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
screen behave as expected.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Apr 22 02:06:42 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA
controller])
Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
Integrated Graphics Controller [1028:0725]
InstallationDate: Installed on 2019-04-22 (0 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 11-3162
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0NM68T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3162
dmi.product.sku: 0725
dmi.product.version: 2.4.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20180925-2
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/lightdm/+bug/1825785/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
yeah, i tried both the condition and yes the problem is equally persistent in both the cases. moreover what i realized is when the mouse hovers over one of the menus in gnome tweak box, it assumes it as the click input and keep dancing between the menu pressed and non pressed situation. a sort of misinterpreted mouse input scenario in that particular application. hope this be solved. -- 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/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-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/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Changed in: network-manager Importance: Undecided => Unknown ** Changed in: network-manager Status: New => Unknown ** Changed in: network-manager Remote watch: None => github.com/nm-l2tp/NetworkManager-l2tp/issues #112 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN Status in gnome-control-center: New Status in L2TP over IPsec VPN Manager: New Status in NetworkManager: Unknown Status in strongSwan: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. In case it matters, these additional packages were also required for my initial VPN setup: sudo apt-get install -y network-manager-l2tp network-manager-l2tp- gnome strongswan Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48
[Desktop-packages] [Bug 1850278] Re: Activities overview hot corner setting does not persist
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1850278 Title: Activities overview hot corner setting does not persist Status in gnome-shell package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Disable activities overview hot corner in GNOME tweaks 2. See that the hot corner is indeed disabled 3. Lock the screen 4. Unlock the screen 5. See that hot corner is active again (however GNOME tweaks still shows it as disabled) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 09:47:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-02 (421 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434986] Re: Not working network connection after boot
Forgot to mention that pc is connected directly through network cable. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434986] Re: Not working network connection after boot
Same here. I have Ubuntu Mate 18.04 64bit. After reboot network looks connected, but cannot open any web page and connect to it from outside. When i disconnect and connect back, everything works until next reboot. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Since Nautilus isn't used in newer Ubuntu versions this bug will probably not be fixed. ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: ubuntu-meta (Ubuntu) -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in nautilus package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard (in Wayland sessions only)
BTW, please log a new bug about the screen tearing in Xorg by: 1. Logging into 'Ubuntu' (Xorg) 2. Opening a Terminal and run: ubuntu-bug mutter -- 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/1849405 Title: Repeated keypresses from bluetooth keyboard (in Wayland sessions only) Status in mutter package in Ubuntu: New Bug description: I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g. around every 10-15mins) end up with repeated keypresses being made (e.g. apppt get update). This seems to happen when the machine is under slight stress, or when a new notification pops up in gnome, so it could be related to wayland possibly - but even if wayland or other processes are causing stress, I should imagine the bluetooth hid driver should not cause repeated key presses. Please let me know if you require further information about my environment, it's difficult to know where to begin with determining which process is the root cause of this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Oct 23 09:38:20 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude 7480 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:63:3F:E9:51:8C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0 TX bytes:605292 acl:98 sco:0 commands:2484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard
Yes, kind of. I do know mutter's occasional stutters and pauses do cause problems for libinput in Wayland, and libinput likes to log messages warning about it. It seems likely the problem is in Mutter. ** Tags added: wayland-session ** Summary changed: - Repeated keypresses from bluetooth keyboard + Repeated keypresses from bluetooth keyboard (in Wayland sessions only) ** No longer affects: bluez (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1849405 Title: Repeated keypresses from bluetooth keyboard (in Wayland sessions only) Status in mutter package in Ubuntu: New Bug description: I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g. around every 10-15mins) end up with repeated keypresses being made (e.g. apppt get update). This seems to happen when the machine is under slight stress, or when a new notification pops up in gnome, so it could be related to wayland possibly - but even if wayland or other processes are causing stress, I should imagine the bluetooth hid driver should not cause repeated key presses. Please let me know if you require further information about my environment, it's difficult to know where to begin with determining which process is the root cause of this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Oct 23 09:38:20 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude 7480 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:63:3F:E9:51:8C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0 TX bytes:605292 acl:98 sco:0 commands:2484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success
Can't explain better, but I found root cause. So, full steps to reproduce: 1) sudo service NetworkManager stop 2) sudo wpa_supplicant -c /etc/wpa_supplicant/wired.conf -i eth1 -D wired 3) sudo dhclient eth1 4) see in output "ls: cannot access '/run/systemd/resolved.conf.d/isc-dhcp-v6-***.conf': No such file or directory" 5) check ifconfig that only IPv4 address was received Work-around: Disable IPv6 for Ethernet ** Summary changed: - gnome-control-center reports Ethernet Connection Failure while Connection success + dhclient can't obtain IPv6 addr -- 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/1850159 Title: dhclient can't obtain IPv6 addr Status in network-manager package in Ubuntu: Incomplete Bug description: gnome-control-center reports Ethernet Connection Failure with TLS Authentication 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Show Connected for Wired Connection 4) Show Disconnected for Wired Connection ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 17:06:43 2019 InstallationDate: Installed on 2019-08-01 (88 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850278] Re: Activities overview hot corner setting does not persist
After restarting, it seems that the problem doesn't persist anymore. I think you can close this. Thanks -- 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/1850278 Title: Activities overview hot corner setting does not persist Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 1. Disable activities overview hot corner in GNOME tweaks 2. See that the hot corner is indeed disabled 3. Lock the screen 4. Unlock the screen 5. See that hot corner is active again (however GNOME tweaks still shows it as disabled) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 09:47:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-02 (421 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
