[Desktop-packages] [Bug 1724876]
It might be a dup of tdf#121963 which has just been fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=e8720057aa0f4e612000d68f6de682f3afb8a1ea It should be present in daily build in 24/48h, to retest. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1724876 Title: libreoffice soffice.bin using 100% cpu Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1724876/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724876]
Thank you for reporting the bug. Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1724876 Title: libreoffice soffice.bin using 100% cpu Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1724876/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 526482]
Possibly related is that nsPrintSettingsService::GetGlobalPrintSettings and nsPrintSettingsService::GetNewPrintSettings essentially do the same thing: https://searchfox.org/mozilla- central/rev/8b7aa8af652f87d39349067a5bc9c0256bf6dedc/widget/nsPrintSettingsService.cpp#927 That's probably not the whole story though. -- 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/526482 Title: Firefox don't save print settings Status in Mozilla Firefox: New Status in Mozilla Thunderbird: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Environment: OS: Ubuntu 9.10 (Karmic Koala) Package: firefox-3.5 (3.5.8+build1+nobinonly-0ubuntu0.9.10.1) Problem: I print from firefox and change print settings, like select destination printer, margins, header, footer and so on. In about:config option 'print.save_print_settings' is set to true. Finally do print. Immediately after previous print I do print again and I suspect to get same settings (destination printer, margins, header, footer ...) that I set for last print, but unfortunately I get default print settings (destination printer, margins, header, footer ...). All this is happen in same browser session. Problem also reflect on our extension that we developed for Firefox (jsPrintSetup https://addons.mozilla.org/en-US/firefox/addon/8966). The extension using nsIPrintSettings interface to manage print settings also encounter problem with select destination printer. Independently from selected nsIPrintSettings.printerName Firefox always print to default for operating system printer. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/526482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
So I just upgraded to 19.10 and I am _STILL_ having this issue. I have had this issue now through two whole major releases! SMB1 being turned off _SHOULD NOT BREAK THIS_. SMB1 is a _MAJOR_ security threat, and this really needs to get fixed! I've been reporting this failure since April of 2019 :/ (started in another bug report) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
And as a reminder, my "solution" is to: 1. trigger the error by trying to browse to an SMB share with SMB1 disabled on the server-side 2. "pidof gvfsd-smb-browse" 3. "kill $PID" from above (regular kill, not -9) It then works, I can actually get to shares. I have to do this after _every_ reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
Happens to me as well after upgrade from 19.04 to 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
**Workaround:**
I found that disabling the indeterminate progress progress bar is not
enough; the spinning throbber in the tab is also responsible for CPU
usage.
I'm using the below in my Thunderbird profile folder's
`chrome/userChrome.css` to disable both, resulting in the 15-20% CPU
usage disappearing:
@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";);
/* nh2: Progress bar CPU usage fix. */
/* For some stupid reason we can't match the html:progress that's the first
child of this container.
See https://bugzilla.mozilla.org/show_bug.cgi?id=562977#c61
So we can't style the progress bar so that it does doesn't get shown
only when
indeterminate (which takes the most CPU), or style it to render faster.
So for now we hide the entire parent container, thus getting rid of the
progress bar entirely.
*/
#statusbar-progresspanel {
display: none;
}
/* nh2: Tab throbber animations also take a lot of CPU; hide them.
Unfortunately I didn't find a way to replace them by a static image.
*/
.tab-throbber[busy] {
display: none !important;
}
.tab-throbber[progress] {
display: none !important;
}
--
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/109943
Title:
Thunderbird: high CPU usage from progress bars
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Binary package hint: mozilla-thunderbird
When sending a simple and short email with Thunderbird via SMTP the
CPU is used intensively. This seems not to be necessary. If the
sending failed and an corresponding error message dialog appears, the
CPU is still being used. When pressing ok to close the error dialog
the CPU is fine. This suggests it might be related specifically to the
progress bar. Such behavior is especially annoying on a laptop where
you can hear the CPU usage because of a starting fan.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
This user chrome is a real battery saver! Thanks! ...and the throbber in the mouse pointer still tells me if thunderbird is busy. --- If I understand this right we now have 2 things that are rendered in the same thread and that use 100% of one CPU (indicated as 50% of the CPU power of a 2-CPU-System, 20% of the CPU power of a 5-cpu-system and 12,5% of the CPU power of an 8-cpu one) if they get the chance of doing so. ...or was the progress meter a Red Herring and it was only the throbber all along? 100% of one CPU normally doesn't indicate that something is amiss: The CPU could be asleep 99% of the time and be busy 1% of the remaining time. But the battery drain throbber+progress meter and generate seems to indicate that the CPU won't sleep while there is indeterminate progress... -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
Thunderbird 68.2.1 on Linux, I can confirm that this issue still exists, with createElementNS() as given above, and the SMTP sending progress bar from bug 742697, and the IMAP loading progress bar in the status bar when switching between folders. 15-20% CPU usage. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
Yes, `list-style-image: none !important;` also fixes it. > Strange that both together use the same CPU like when only one is active. I don't find that strange: Using either progress bar or animated PNG throbber, the screen now has to be drawn at many frames per second. Once you have to redraw, redrawing a bit more doesn't make a big difference. Separetely: Also useful to know for posterity, the upgrade from Thunderbird 60 to 68 made the indeterminate progress bar a lot more jumpy (it looks like around 10 FPS while the original was much smoother) - but to my surprise that increased jumpiness still didn't reduce CPU usage a lot. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
How can you match the generated tag with userChrome.css ? I'd like to style it differently to check how the performance behaves, or hide it, but I don't know how to match it, only its parent `#statusbar-progresspanel`. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
Gunter, you could only apply the rule for #statusbar-progresspanel and check how the CPU usage is with only the throbber spinning. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
(In reply to Niklas Hambüchen from comment #65)
> I have already tested that.
>
> * Only throbber: ~15-20% CPU usage
> * Only progress bar: ~15-20% CPU usage
> * Both throbber and progress bar: ~15-20% CPU usage
> * Both disabled: no CPU usage
Strange that both together use the same CPU like when only one is
active.
Please could you try
```
.tab-throbber[busy] {
list-style-image: none !important;
}
```
Then I can see if the animated PNG is the cause of the CPU usage.
--
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/109943
Title:
Thunderbird: high CPU usage from progress bars
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Binary package hint: mozilla-thunderbird
When sending a simple and short email with Thunderbird via SMTP the
CPU is used intensively. This seems not to be necessary. If the
sending failed and an corresponding error message dialog appears, the
CPU is still being used. When pressing ok to close the error dialog
the CPU is fine. This suggests it might be related specifically to the
progress bar. Such behavior is especially annoying on a laptop where
you can hear the CPU usage because of a starting fan.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
I have already tested that. * Only throbber: ~15-20% CPU usage * Only progress bar: ~15-20% CPU usage * Both throbber and progress bar: ~15-20% CPU usage * Both disabled: no CPU usage @Gunter: I measured CPU usage on Linux with `htop`, where the percentage is always relative to 1 core. 15% means 15% of 1 core. Using full 2 cores would show up as 200%. > 100% of one CPU normally doesn't indicate that something is amiss: The CPU could be asleep 99% of the time and be busy 1% of the remaining time. I don't understand this sentence. If the CPU is asleep 99% of the time, CPU usage in `htop` should show up as roughly 1%, not 100%. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843698] Re: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
** Changed in: gnome-software Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1843698 Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-software/issues/792 --- I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 PC (0x7f565aa3fcc4) ok source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! destination "%ymm5" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1843698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 525507]
What is the progress on fixing this bug? Why Thunderbird is updated to new versions without this bug ever fixed? Any reasonable person will say that 10 years is enough to fix this bug! -- 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/525507 Title: Empty All Trash for Smart Folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Add the possibility of emptying all trash by right click on the trash roots To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/525507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 525507]
So after 10 years of doing nothing, updating it from Bug to Enhancement is expected to do what - extend the timeline for another 10 years? Isn't it obvious, its a bug as how you can possibly have a Trash folder without Empty Trash option? Its not logical, these features come only in pairs, therefore its a bug. Missing mandatory option is not the same as "nice to have" feature request. Its like having a car without wheels, and then claiming adding wheels is an enhancement, and likely won't come any time soon. And saying "severity is minor" is wrong. If there was such option, but it didn't work, would you mark severity as minor, despite it directly affects privacy and security? Same applies to Junk folder, but the RMC option should be "Move Junk to Trash" rather than "Empty Junk". Do you have any mandatory completion deadlines for "enhancements" with "minor" severity? -- 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/525507 Title: Empty All Trash for Smart Folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Add the possibility of emptying all trash by right click on the trash roots To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/525507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 525507]
I will update this to an enhancement request as that ios what it is. -- 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/525507 Title: Empty All Trash for Smart Folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Add the possibility of emptying all trash by right click on the trash roots To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/525507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 525507]
@zamarac: (On a meta level:) People have different interests and priorities. People are free [not] to work on something. If you really want something to be implemented, feel free to provide a software patch and getting it reviewed or to convince someone else to write that software patch. "What have you done in the last 10 years to fix this problem?", basically. Also see https://www.mozilla.org/en- US/about/governance/policies/participation/ - thanks! :) -- 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/525507 Title: Empty All Trash for Smart Folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Add the possibility of emptying all trash by right click on the trash roots To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/525507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 525507]
I agree that it is rather an enhancement request than a bug, but I still believe it makes a lot of sense to implement it (and the functionality of the unified folders is diminished by not having this). It should be an integral part of the unified folders. Either support them - and include this - or remove them. (I hope this can be added). -- 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/525507 Title: Empty All Trash for Smart Folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Add the possibility of emptying all trash by right click on the trash roots To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/525507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I just had it locked up a number of times with all the extensions disabled. Trace looked basically the same. It seems to be launching Thunderbird (it takes a while due to calendars…) that's triggering this most often. -- 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) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True 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] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850615/+attachment/5303380/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True 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] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1850615/+attachment/5303381/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True 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] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1850615/+attachment/5303382/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True 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] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1850615/+attachment/5303378/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True 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] Re: gnome-shell hardlocks under load
apport information ** Tags added: apport-collected ** Description changed: 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) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.10 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-shell 3.34.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 + RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 + Tags: eoan + Uname: Linux 5.3.0-19-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) + UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850615/+attachment/5303377/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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=
[Desktop-packages] [Bug 1850615] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850615/+attachment/5303379/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-28 (9 days ago) UserGroups: adm cdrom dialout dip docker kvm libvirt lp lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True 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 1849135] Re: Clicking Activities in the corner doesn't work
I experience this bug, too. What is interesting is that even if: 1. I hide the top bar of gnome shell with extension, 2. Disable dash-to-dock and 3. Bring a window so it occupies the most top-left corner (or maximize it), the windows does not react if I click the corner. In this case the expected behavior is to grab and drag the window. -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
So this is actually happening now every time I lock my computer, no power change whatsoever (no standby, no suspend to RAM, no power off/reboot). So this is now becoming very frustrating to work with as I have to change my default audio device every time I use my computer now so that my volume controls (up/down) actually work. Can we PLEASE get this at least started to be looked at? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850912] Re: ALSA audio not working any more (with snap package)
Apologies, this issue might be unrelated after all. I do not have the exact same errors from chromium: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ hw -- 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/1850912 Title: ALSA audio not working any more (with snap package) Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu 19.04 to Ubuntu 19.10, audio in chromium browser stopped working, presumably this is related to chromium now being a snap package: Description: Ubuntu 19.10 Release: 19.10 Package: chromium-browser Architecture: amd64 Version: 77.0.3865.120-0ubuntu1~snap1 Note that I don't use pulseaudio or any other audio server on my system, it's supposed to use ALSA directly. In .xsession-errors I see: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [2536:2536:1031/194827.989956:ERROR:alsa_util.cc(204)] PcmOpen: default,No such file or directory ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM plug:default [2536:2536:1031/194827.990132:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850912] Re: ALSA audio not working any more (with snap package)
Apologies, this issue might be unrelated after all. I do not have the same errors from chromium: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ hw -- 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/1850912 Title: ALSA audio not working any more (with snap package) Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu 19.04 to Ubuntu 19.10, audio in chromium browser stopped working, presumably this is related to chromium now being a snap package: Description: Ubuntu 19.10 Release: 19.10 Package: chromium-browser Architecture: amd64 Version: 77.0.3865.120-0ubuntu1~snap1 Note that I don't use pulseaudio or any other audio server on my system, it's supposed to use ALSA directly. In .xsession-errors I see: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [2536:2536:1031/194827.989956:ERROR:alsa_util.cc(204)] PcmOpen: default,No such file or directory ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM plug:default [2536:2536:1031/194827.990132:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
@seb128 Sebastien, are you referring to this page? https://bugs.launchpad.net/ubuntu/+source/gnome-shell The specific issue is that the "dock" is exposed and it doesn't feel fullscreen. System info: Intel Integrated Graphics 530 (NO GPU, just processor) I've tried default 19.10 input device modesetting as well as specifying with an intel-20 xorg config to use Device driver "intel" (rather than modesetting) Sebastien this is what I'm trying to launch, it uses OpenGL and is coded in C. It always worked fine launching in fullscreen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851211] Re: [snap] SoloKeys not supported by u2f-devices interface
I've added it to my trello card for 2.43 policy updates.
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
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/1851211
Title:
[snap] SoloKeys not supported by u2f-devices interface
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Triaged
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.boar
[Desktop-packages] [Bug 1850912] Re: ALSA audio not working any more (with snap package)
I have the same issue: nov. 06 22:38:00 MASKED audit[1430]: USER_AVC pid=1430 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=4265 label="snap.chromium.chromium" nov. 06 22:38:00 MASKED kernel: audit: type=1107 audit(1573076280.807:71): pid=1430 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=4265 label="snap.chromium.chromium" -- 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/1850912 Title: ALSA audio not working any more (with snap package) Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu 19.04 to Ubuntu 19.10, audio in chromium browser stopped working, presumably this is related to chromium now being a snap package: Description: Ubuntu 19.10 Release: 19.10 Package: chromium-browser Architecture: amd64 Version: 77.0.3865.120-0ubuntu1~snap1 Note that I don't use pulseaudio or any other audio server on my system, it's supposed to use ALSA directly. In .xsession-errors I see: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [2536:2536:1031/194827.989956:ERROR:alsa_util.cc(204)] PcmOpen: default,No such file or directory ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM plug:default [2536:2536:1031/194827.990132:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 540751] Re: Unable to use dead keys with java and ibus
Re-opening the ibus task for now. @Johny: This is a very old bug report, and a lot has been changed since it was originally filed. Any chance you can provide some details about how to reproduce the bug on 19.10? ** Changed in: ibus (Ubuntu) Status: Invalid => New ** Tags removed: lucid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/540751 Title: Unable to use dead keys with java and ibus Status in ibus package in Ubuntu: New Status in openjdk-6 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Invalid Bug description: Using latest Lucid packages, I am unable to use ^ key to generate ê french character in every Java programs (jEdit, Netbeans, etc.). Typing ^ + e give just the e character. Typing ^ + Space and nothing appears. I've tried with Sun JDK (6u18, 6u20, 7) and the bug is still present. I've tried to remove ibus and everything works again (I've just unset XMODIFIERS and GTK_IM_MODULE). I don't know if it's an ibus bug or openjdk one. ProblemType: Bug Architecture: amd64 Date: Thu Mar 18 09:03:11 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java InstallationMedia: Error: [Errno 13] Permission non accordée: '/var/log/installer/media-info' NonfreeKernelModules: nvidia Package: openjdk-6-jre-headless 6b18~pre2-1ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.utf8 ProcVersionSignature: Ubuntu 2.6.32-16.25-genUser Name SourcePackage: openjdk-6 Uname: Linux 2.6.32-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/540751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851211] Re: U2F not working in current build
Thanks for the info. The u2f-devices interfaces doesn't support the SoloKeys yet, it will need updating. Relevant commits: https://github.com/Yubico/libu2f-host/commit/bdb4ca33a9ec7683d6f2016cf61f5c8e28d37379 https://github.com/Yubico/libu2f-host/commit/8d593512998a7df962d6dd0a7c4e641e5fe8b567 ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - U2F not working in current build + [snap] U2F SoloKeys not supported by u2f-devices interface ** Summary changed: - [snap] U2F SoloKeys not supported by u2f-devices interface + [snap] SoloKeys not supported by u2f-devices interface ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- 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/1851211 Title: [snap] SoloKeys not supported by u2f-devices interface Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: This affects the current build of the snap version of Chromium. Although it was marked as fixed in the ticket here: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1738164 it is still open. No chance to use such a key in the browser. dmesg output is: My dmesg out put shows a lot of DENIED: audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=20568 label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=?' [ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor" pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Suggested solutions in the other tickets do not work System is Ubuntu 19.10 on an Asus UX330 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg== modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 DRM.card0-eDP-1: enabled: disabled dpms: Off status: connected edid-base64: AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII= modes: 1920x1080 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda6 ext4 184G 35G 140G 20% /home tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm /dev/sda6 ext4 184G 35G 140G 20% /home DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2017-09-30 (766 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX330UAK Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinu
[Desktop-packages] [Bug 1851211] Re: [snap] SoloKeys not supported by u2f-devices interface
@Jamie, I'm tentatively assigning this to you, feel free to assign back
to me if you'd rather I contributed the changes (I don't have the
hardware to test with, though).
--
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/1851211
Title:
[snap] SoloKeys not supported by u2f-devices interface
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
New
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends
[Desktop-packages] [Bug 1851490] Re: [snap] Favourite entry for chromium disappears with every update
This should be addressed in Unity. I have already talked to Treviño (3v1n0 on launchpad) about it, and we agreed that increasing the timeout to 1min is an easy band-aid that should mitigate the problem most of the time, so I'll submit a merge request to do that. ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: New => Triaged -- 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/1851490 Title: [snap] Favourite entry for chromium disappears with every update Status in chromium-browser package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Bug description: $ snap version snap2.42 snapd 2.42 series 16 ubuntu 16.04 kernel 4.15.0-15-generic $ snap list chromium Name Version Rev Tracking Publisher Notes chromium 78.0.3904.70 920 stablecanonical✓ - After every upgrade which happens automatically with snap (which is great) launcher icon disappears and needed to be locked again after starting chromium after upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
>What webbrowser do you use? Chrome >Did you try to install from gnome-software instead? It doesn't work in gnome-software either. Additional behaviors observed in gnome-software: 1) When I try to _uninstall_ the extension from inside gnome-software, it says it can't uninstall it, but it actually does uninstall it, but it still thinks it's installed, until I log out and log back in again, at which point it no longer thinks it's installed. 2) If I open extension settings from gnome-software after installing it, the toggle switch for the extension is off (like on the web site) and it won't even let me toggle it on. I also tried creating the extension directory in ~/.local/share/gnome- shell/extensions by hand and downloading and unzipping the extension manually there and then logging out and logging back in again, at which point I'm back in the state described above: the shell thinks the extension is installed but won't let me turn it on. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] [NEW] monitor configuration restored incorrectly upon Wayland login
Public bug reported: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in gnome-shell package in Ubuntu: New Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844026] Re: nautilus crashed with SIGSEGV
** Tags added: bionic -- 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/1844026 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Confirmed Bug description: after restart gnome-shell with "alt + F2 and type 'r' in command" ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 15 05:26:31 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(892, 544)' InstallationDate: Installed on 2019-07-14 (62 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7eff95c1a8e2:mov0x380(%rax),%rax PC (0x7eff95c1a8e2) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1844026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851561] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1844026 *** https://bugs.launchpad.net/bugs/1844026 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1844026, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1851561/+attachment/5303338/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1851561/+attachment/5303340/+files/Disassembly.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1851561/+attachment/5303346/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1851561/+attachment/5303347/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1851561/+attachment/5303348/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1844026 nautilus crashed with SIGSEGV ** Tags removed: need-amd64-retrace -- 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/1851561 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: Crashed with Xorg crashed when resume the system from suspend when using dual screen with nvidia-driver ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Mon Nov 4 23:50:06 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (31 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: nautilus --new-window /home/mhizzani/Downloads/Videos/Silicon.Valley.S06E02.1080p.WEB.h264-TBS[TGx] ProcEnviron: Error: [Errno 13] Permission denied: 'environ' SegvAnalysis: Segfault happened at: 0x7efc1581b4a4:mov0x380(%rax),%rax PC (0x7efc1581b4a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1851561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Oh no the bug happens again with the desktop icons properly set, so it is not the root cause, pfff I'm setting up at work and home the same Linux setup, at home this is the focus bug fest, at work the bug never happened a single time ! Every click success and I do not have the problems I have at home The only difference I have from home and work in my setups are - At work I'm under a proxy, at home direct - At work the display are 1 graphic card intel and using Mesa if I remember, while at home i'm on nvidia latest drivers and 2 graphic cards - At work I'm on two displays, at home a gsync single display - I don't much extensions than what is installed by default on pacman -S gnome gdm cinnamon nemo I suspect this bug to be driver related, maybe driver and icon rendering problem, but understand that fixing bugs without any relevant log is like searching for a needle in a haystack :/ If I could help feel free to ask cause I believe I could find the root cause with 2 similar setup on 2 different hardware acting differently ! -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
Thank you for your bug report. What webbrowser do you use? Did you try to install from gnome-software instead? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: Incomplete Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
@user user, could you open a new bug report using 'ubuntu-bug gnome- shell'? Having the system info would be useful, especially the video card/driver in use. Also what game are you trying and what input device do you use? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851564] [NEW] Daily Limit Exceeded messages for google calendars
Public bug reported: This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have logs going back to mid august. The message is repeated for each calendar at various times. Nov 06 13:49:13 dipper gnome-calendar[8681]: source_credentials_required_cb: Failed to authenticate 'Kai Groner': Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:07:56 2019 InstallationDate: Installed on 2019-06-18 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1851564 Title: Daily Limit Exceeded messages for google calendars Status in gnome-calendar package in Ubuntu: New Bug description: This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have logs going back to mid august. The message is repeated for each calendar at various times. Nov 06 13:49:13 dipper gnome-calendar[8681]: source_credentials_required_cb: Failed to authenticate 'Kai Groner': Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:07:56 2019 InstallationDate: Installed on 2019-06-18 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1851564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851561] [NEW] nautilus crashed with SIGSEGV
Public bug reported: Crashed with Xorg crashed when resume the system from suspend when using dual screen with nvidia-driver ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Mon Nov 4 23:50:06 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (31 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: nautilus --new-window /home/mhizzani/Downloads/Videos/Silicon.Valley.S06E02.1080p.WEB.h264-TBS[TGx] ProcEnviron: Error: [Errno 13] Permission denied: 'environ' SegvAnalysis: Segfault happened at: 0x7efc1581b4a4: mov0x380(%rax),%rax PC (0x7efc1581b4a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- 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/1851561 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: Crashed with Xorg crashed when resume the system from suspend when using dual screen with nvidia-driver ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Mon Nov 4 23:50:06 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-10-06 (31 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: nautilus --new-window /home/mhizzani/Downloads/Videos/Silicon.Valley.S06E02.1080p.WEB.h264-TBS[TGx] ProcEnviron: Error: [Errno 13] Permission denied: 'environ' SegvAnalysis: Segfault happened at: 0x7efc1581b4a4:mov0x380(%rax),%rax PC (0x7efc1581b4a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1851561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Fixed by bios upgrade. -kernel: DMI: HP HP Laptop 15-db0xxx/84AE, BIOS F.02 04/06/2018 +kernel: DMI: HP HP Laptop 15-db0xxx/84AE, BIOS F.20 05/15/2019 also interesting -kernel: amdgpu :04:00.0: VRAM: 256M 0x00F4 - 0x00F40FFF (256M used) +kernel: amdgpu :04:00.0: VRAM: 1024M 0x00F4 - 0x00F43FFF (1024M used) -kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table -kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table -kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found -kernel: AMD-Vi: Disabling interrupt remapping and other changes with previous bios kernel 5.4 did not load (black screen at boot). with current bios it is loaded now : Linux 5.4.0-050400rc5-generic #201910271430 -- 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/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x8
[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.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Incomplete Status in gnome-session source package in Eoan: Incomplete Status in gnome-shell source package in Eoan: Incomplete 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 1179834] Re: baobab hangs at startup
This bug (or similar) also keeps happening on newer ubuntus, I am on
18.04. I am attaching a screenshot. Happy to provide more info if
needed.
** Attachment added: "strace baobab / screenshot"
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1179834/+attachment/5303313/+files/Baobab2019-11-06%2019-38-10.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to baobab in Ubuntu.
https://bugs.launchpad.net/bugs/1179834
Title:
baobab hangs at startup
Status in baobab package in Ubuntu:
Confirmed
Bug description:
When I run baobab nothing happens - I don't get a window or when
started from a console any messages, even after waiting for several
minutes. strace has this at the end with the hanging:
geteuid() = 1000
getegid() = 1000
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11,
revents=POLLOUT}])
sendmsg(11, {msg_name(0)=NULL, msg_iov(1)=[{"\0", 1}], msg_controllen=32,
{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=13565,
uid=1000, gid=1000}}, msg_flags=0}, MSG_NOSIGNAL) = 1
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11,
revents=POLLOUT}])
sendto(11, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
recvfrom(11, "REJECTED EXTERNAL DBUS_COOKIE_SH"..., 4096, 0, NULL, NULL) = 36
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11,
revents=POLLOUT}])
sendto(11, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
recvfrom(11, "OK 41b3c3c0a40c65fd7d45c7c85191f"..., 4096, 0, NULL, NULL) = 37
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11,
revents=POLLOUT}])
sendto(11, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
recvfrom(11, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11,
revents=POLLOUT}])
sendto(11, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
write(8, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x14a0250, FUTEX_WAKE_PRIVATE, 1) = 1
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 13
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=13, events=POLLIN}], 1, 0)= 1 ([{fd=13, revents=POLLIN}])
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
close(13) = 0
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 13
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
write(8, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x14a0250, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x1618400, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x16183d0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=13, events=POLLIN}], 1, 4294967295) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 4294967295) = 1 ([{fd=13, revents=POLLIN}])
read(13, "\1\0\0\0\0\0\0\0", 16)= 8
poll([{fd=13, events=POLLIN}], 1, 4294967295^C
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: baobab 3.6.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue May 14 01:27:58 2013
MarkForUpload: True
SourcePackage: baobab
UpgradeStatus: Upgraded to raring on 2013-04-28 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1179834/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-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
It's not possible to install non-classic snap (like chromium) with
--classic switch.
You can get access to /media/$USER/ through removable-media
interface which you have to manually connect to chromium snap.
https://snapcraft.io/docs/removable-media-interface
--
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:
Incomplete
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 1850088] Re: permission denied when opening a mounted folder in save file dialog
Another fairly simple path to hit this issue is when I mount a drive
from the File Browser. It gets mounted automatically under
/media/$USER/ and isn't accessible in the Snap by default.
I guess installing the snap with --classic would resolve it?
--
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:
Incomplete
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 1851554] Re: can't install gnome shell extensions
The extension won't turn on in Wayland either. -- 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] [NEW] can't install gnome shell extensions
Public bug reported: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share /gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable-drive- menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 ** 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. 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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47
[Desktop-packages] [Bug 1721988] Re: Ubuntu before 18.04 full disk encryption + Nvidia drivers not booting
** Summary changed: - Ubuntu 17.10 full disk encryption + Nvidia drivers not booting + Ubuntu before 18.04 full disk encryption + Nvidia drivers not booting ** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1721988 Title: Ubuntu before 18.04 full disk encryption + Nvidia drivers not booting Status in nvidia-graphics-drivers-304 package in Ubuntu: New Status in nvidia-graphics-drivers-304-updates package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in plymouth package in Ubuntu: Confirmed Bug description: I've installed ubuntu 17.10 with full disk encryption and then installed the nvidia drivers (v 384). when I boot the computer I will get the graphics interface to enter the encryption key but the system will stop to work, like it has hang. Basically I'm not able to enter the password! I've to restart in safe mode to be able to enter the password for the encryption, after that I can just resume the boot and all works. There seems to be some issues with the initial boot screen and nvidia drivers... I'm not able to press any combination of Control+Alt+Fx key to get any extra info about what is going on (not able to get any text mode). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-384 384.90-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 7 20:07:29 2017 InstallationDate: Installed on 2017-09-25 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: nvidia-graphics-drivers-384 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1721988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851490] Re: [snap] Favourite entry for chromium disappears with every update
Do you think this should be dealt from Unity side or from Snap side? According to that answer i will try to move this issue to them. -- 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/1851490 Title: [snap] Favourite entry for chromium disappears with every update Status in chromium-browser package in Ubuntu: Confirmed Status in unity package in Ubuntu: New Bug description: $ snap version snap2.42 snapd 2.42 series 16 ubuntu 16.04 kernel 4.15.0-15-generic $ snap list chromium Name Version Rev Tracking Publisher Notes chromium 78.0.3904.70 920 stablecanonical✓ - After every upgrade which happens automatically with snap (which is great) launcher icon disappears and needed to be locked again after starting chromium after upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Issue is still in Ubuntu 19.10 with vmware workstation player 15.5. One workaround I found is to use gnome-tweaks to select the wallpaper (under Appearance), and select an Adjustment option of "Wallpaper". Any other adjustment option causes the white background. Works best with a tile-able background, or a very large image that would not automatically tile (like a 4k image). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: Confirmed Bug description: As soon as I set my display to scaled (any percentage) via Settings -> Displays -> Scale, the background image disappears and become all white. When I choose a different background image via Settings -> Background initially nothing happens. As soon as I switch back to 100% scaling, the image I choose before now appears. This problem started right after updating to 19.04. No such issues with either 18.04 or 18.10. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:35:49 2019 DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-03-01 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, 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/mutter/+bug/1825842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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]
FYI: The issue is solved for me with TB 68.2.1. Works pretty well with the new multilingual UI. Thank you! -- 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 1851322] Re: VPN auto-connect is not working
I would rather not getting involved into too many bugtrackers, and as a Ubuntu user, remain on Launchpad and provide the required information to let you investigate. Also, as you are a member of Ubuntu teams, you have more authority/credibility than me, so that bug can be taken seriously by Gnome-shell teams. Thanks Sebastien. -- 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/1851322 Title: VPN auto-connect is not working Status in gnome-shell package in Ubuntu: New Bug description: Hi, This is a duplicate of bug: https://bugs.launchpad.net/network-manager/+bug/1718931 It is marked as fixed, but the feature is still broken for me. I configured my Wifi connection to automatically connect to a VPN, but it only works if I manually connect to the Wifi via NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 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: ubuntu:GNOME Date: Tue Nov 5 04:07:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851551] [NEW] man page does not mention that -e is deprecated
Public bug reported: gnome-terminal -e 'command...' emits a warning: # Option “-e” is deprecated and might be removed in a later version of gnome-terminal. # Use “-- ” to terminate the options and put the command line to execute after it. However this is contrary to the man page, which says nothing about -e being deprecated, and does not mention anything about the new method being possible (-- followed by command and options). Please update the documentation STEPS TO REPRODUCE: 1. man gnome-terminal 2. gnome-terminal -e "sh -c 'ls -l; sleep 3'" RESULTS: The documented method of specifying a command causes a deprecation warning. EXPECTED RESULTS: Documentation should say how to do the right thing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-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: Wed Nov 6 10:20:44 2019 InstallationDate: Installed on 2019-02-06 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1851551 Title: man page does not mention that -e is deprecated Status in gnome-terminal package in Ubuntu: New Bug description: gnome-terminal -e 'command...' emits a warning: # Option “-e” is deprecated and might be removed in a later version of gnome-terminal. # Use “-- ” to terminate the options and put the command line to execute after it. However this is contrary to the man page, which says nothing about -e being deprecated, and does not mention anything about the new method being possible (-- followed by command and options). Please update the documentation STEPS TO REPRODUCE: 1. man gnome-terminal 2. gnome-terminal -e "sh -c 'ls -l; sleep 3'" RESULTS: The documented method of specifying a command causes a deprecation warning. EXPECTED RESULTS: Documentation should say how to do the right thing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-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: Wed Nov 6 10:20:44 2019 InstallationDate: Installed on 2019-02-06 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1851551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
What do I need to do to have this looked at more closely? I can send a screenshot of the game in question. The input lag is so absurdly high with 19.10 and this bug among other things makes 19.10 feel like a huge regression for me. I am using 19.04 now and everything runs faster and I don't get this bug where the dock is infront of the the fullscreen application. I tried wayland, with modesetting, without modesetting - nothing works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851546] [NEW] Debug spew to stderr at startup
Public bug reported: gnome-terminal writes debug messages to stderr every time it starts up: # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) This pollutes the terminal when a script explicitly invokes gnome- terminal to open another window. STEPS TO REPRODUCE: 1. Open a terminal and type "gnome-terminal" RESULTS: Debug messages appear on the first terminal EXPECTED RESULTS: Nothing should appear on stderr or stdout of gnome- terminal itself, unless there is an actual error. P.S. Presumably a debug build escaped and was released. To prevent this from happening, it would be a good idea to add a test which checks that gnome-terminal writes nothing to std* in normal (non-error) cases. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-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: Wed Nov 6 10:03:24 2019 InstallationDate: Installed on 2019-02-06 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1851546 Title: Debug spew to stderr at startup Status in gnome-terminal package in Ubuntu: New Bug description: gnome-terminal writes debug messages to stderr every time it starts up: # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) This pollutes the terminal when a script explicitly invokes gnome- terminal to open another window. STEPS TO REPRODUCE: 1. Open a terminal and type "gnome-terminal" RESULTS: Debug messages appear on the first terminal EXPECTED RESULTS: Nothing should appear on stderr or stdout of gnome- terminal itself, unless there is an actual error. P.S. Presumably a debug build escaped and was released. To prevent this from happening, it would be a good idea to add a test which checks that gnome-terminal writes nothing to std* in normal (non- error) cases. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-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: Wed Nov 6 10:03:24 2019 InstallationDate: Installed on 2019-02-06 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1851546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851305] Re: ssh links, tg links, magnet links doesn't work in snap chromium
*** This bug is a duplicate of bug 1776873 *** https://bugs.launchpad.net/bugs/1776873 Sorry question of snap hardcoded white list is one issue (and could be viewed as wishlist). But question of degradation/break of previously working widely used functionality of Chromium in new Ubuntu version is quite different beast. Currently only possible workaround is build standalone (not snap) chromium from source, which is really bad/complicated way to deal with this problem for 99% of users/enterprises. -- 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/1851305 Title: ssh links, tg links, magnet links doesn't work in snap chromium Status in chromium-browser package in Ubuntu: New Bug description: It seems that chromium snap transition broken all possible custom URL scheme support. And I not manage found any workaround because snap use hardcoded white list of allowed URI schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851539] [NEW] Adwaita-Dark has black text on black background for auto-complete fields
Public bug reported: I'm using Adwaita-Dark with the gnome-themes-extra package that comes available to Ubuntu 19.10. When I go to a login form, github search, or other text field that has auto-complete options, the presented auto-complete options are black text on black background, and are completely illegible. Naturally when I use a light theme it's black font on white background and completely legible. We need to have a light/white font on black background for Adwaita-Dark and other Dark themes too, as this breaks accessibility of the environment (visual impairments, etc). ** Affects: gnome-themes-extra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1851539 Title: Adwaita-Dark has black text on black background for auto-complete fields Status in gnome-themes-extra package in Ubuntu: New Bug description: I'm using Adwaita-Dark with the gnome-themes-extra package that comes available to Ubuntu 19.10. When I go to a login form, github search, or other text field that has auto-complete options, the presented auto-complete options are black text on black background, and are completely illegible. Naturally when I use a light theme it's black font on white background and completely legible. We need to have a light/white font on black background for Adwaita- Dark and other Dark themes too, as this breaks accessibility of the environment (visual impairments, etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-themes-extra/+bug/1851539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851211] Snap.Info.core18.txt
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303298/+files/Snap.Info.core18.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN123456789012
[Desktop-packages] [Bug 1851211] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303291/+files/ProcCpuinfoMinimal.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678
[Desktop-packages] [Bug 1851211] Snap.Info.gtk-common-themes.txt
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303299/+files/Snap.Info.gtk-common-themes.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asse
[Desktop-packages] [Bug 1851211] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303288/+files/Dependencies.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678901234567
[Desktop-packages] [Bug 1851211] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303293/+files/ProcModules.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678901234567
dm
[Desktop-packages] [Bug 1851211] Snap.Connections.txt
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303295/+files/Snap.Connections.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN123456789012
[Desktop-packages] [Bug 1851211] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303300/+files/UdevDb.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.nam
[Desktop-packages] [Bug 1851211] Snap.Info.core.txt
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303297/+files/Snap.Info.core.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN1234567890123456
[Desktop-packages] [Bug 1851211] Snap.Info.chromium.txt
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303296/+files/Snap.Info.chromium.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678
[Desktop-packages] [Bug 1851211] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303290/+files/ProcCpuinfo.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678901234567
dm
[Desktop-packages] [Bug 1851211] Snap.ChromiumPrefs.txt
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303294/+files/Snap.ChromiumPrefs.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678
[Desktop-packages] [Bug 1851211] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303289/+files/Lspci.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name:
[Desktop-packages] [Bug 1851211] Re: U2F not working in current build
Hi Olivier thanks for your answer.
I executed the command you asked for. Hope you received all necessary
information. If not please don't hesitate to contact me.
No it is a SoloKeys (https://solokeys.com):
lsusb: Bus 001 Device 005: ID 0483:a2ca STMicroelectronics Solo 2.5.3
It works perfectly in Firefox or Vivalid-Browser which are not installed
as snaps
Thanks again! Cheers
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dia
[Desktop-packages] [Bug 1851211] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1851211/+attachment/5303292/+files/ProcInterrupts.txt
--
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/1851211
Title:
U2F not working in current build
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda6 ext4 184G 35G 140G 20% /home
tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
/dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN1234567890123456
[Desktop-packages] [Bug 1851211] Re: U2F not working in current build
apport information
** Tags added: apport-collected eoan snap
** Description changed:
This affects the current build of the snap version of Chromium.
Although it was marked as fixed in the ticket here:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164
it is still open. No chance to use such a key in the browser.
dmesg output is:
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Suggested solutions in the other tickets do not work
System is Ubuntu 19.10 on an Asus UX330
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DRM.card0-HDMI-A-1:
+ enabled: enabled
+ dpms: On
+ status: connected
+ edid-base64:
AP///wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAe/QA4PR5TDwAKICAgICAg/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAJg==
+ modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480
640x480 640x480 640x480
+ DRM.card0-eDP-1:
+ enabled: disabled
+ dpms: Off
+ status: connected
+ edid-base64:
AP///wAGry0nABAZAQSVHRF4ArwFolVMmiUOUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAY/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDIuNyAKAII=
+ modes: 1920x1080
+ DiskUsage:
+ Filesystem Type Size Used Avail Use% Mounted on
+ /dev/sda6 ext4 184G 35G 140G 20% /home
+ tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
+ /dev/sda6 ext4 184G 35G 140G 20% /home
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2017-09-30 (766 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ Lsusb:
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 004: ID 8087:0a2b Intel Corp.
+ Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
+ Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX330UAK
+ Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=de_DE.UTF-8
+ SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
+ Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
+ Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
+ Tags: eoan snap
+ Uname: Linux 5.3.0-19-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
+ UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev
sambashare sudo www-data
+ _MarkForUpload: True
+ dmi.bios.date: 04/19/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX330UAK.315
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX330UAK
+ 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.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASU
[Desktop-packages] [Bug 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend
If it's any bit of helpful information, I occasionally have this issue (on 18.04) and it is fixed by a proper shutdown and boot. It seems to happen for me when one of the servers that I sshfs to crashes/becomes unavailable (or something else server side) and the issue persists past the time in which the server is back and functional. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1702368 Title: Mounted sshfs filesystems sometimes prevent suspend Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in sshfs-fuse package in Ubuntu: Confirmed Bug description: Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30 and sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against a file on an sshfs filesystem. Sometimes when I suspend I get: Jul 4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ... done. Jul 4 20:59:08 xps kernel: [46684.613278] PM: Preparing system for sleep (mem) Jul 4 20:59:08 xps kernel: [46684.613788] Freezing user space processes ... Jul 4 20:59:08 xps kernel: [46704.620140] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): Jul 4 20:59:08 xps kernel: [46704.620534] gvimD0 11155 1336 0x0004 Jul 4 20:59:08 xps kernel: [46704.620541] Call Trace: Jul 4 20:59:08 xps kernel: [46704.620556] __schedule+0x233/0x6f0 ... Jul 4 20:59:08 xps kernel: [46704.620679] entry_SYSCALL_64_fastpath+0x1e/0xad ... Jul 4 20:59:08 xps kernel: [46704.620711] Restarting tasks ... done. ...and the system fails to suspend. AFAICT, this is https://bugzilla.redhat.com/show_bug.cgi?id=656992 and https://lists.debian.org/debian-kernel/2011/10/msg00412.html has an extensive explanation. The corresponding Debian bug was closed long ago due to inactivity. It isn't exactly bug 388419 though since that is about behaviour after resume, rather than failure to suspend. This affects sshfs-fuse, but it sounds like a full fix would be in the kernel. I wonder if it's possible to work around in userspace packaging in sshfs-fuse, though, by arranging some action in userspace before suspend? It seems unlikely that this will be addressed any time soon, but it'd be nice to keep a bug open in Launchpad so that users can have a single rallying point. --- ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 1519 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: sshfs-fuse ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 Tags: artful Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1702368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
At the risk of repeating myself: the firefox-next PPA is not intended
for production use, only for preview testing of the upcoming version of
firefox. Use at your own risk, or don't use it at all. This is not the
regular Ubuntu archive.
--
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",
Throttleable: 1
UptimeTS: 98.30915265
Vendor: Mozilla
Versi
[Desktop-packages] [Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1870 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1870 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870 -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault Status in gnome-shell package in Ubuntu: New Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
The JS traceback points to this line: https://gitlab.gnome.org/GNOME/gnome-shell/blob/3913fa5044b2cd1d5abadc9b4254d06215491458/js/ui/windowManager.js#L1771 (GitLab commit doesn't match gnome-shell from Ubuntu 19.10, sorry! I didn't have the time to go hunt for the exact commit that corresponds to the package, instead I extracted the source file with gresource extract /usr/lib/gnome-shell/libgnome-shell.so /org/gnome/shell/ui/windowManager.js, looked up the line, then found the same code in the same function in the current gitlab tree.) The column points to the `binding.get_name()` call. -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault Status in gnome-shell package in Ubuntu: New Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace
/var/crash/_usr_bin_gnome-shell.1000.crash
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Toks failas ar aplankas
neegzistuoja.
[Current thread is 1 (Thread 0x7f5c91796cc0 (LWP 3417))]
(gdb) bt
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x56068ef0852a in dump_gjs_stack_on_signal_handler ()
#2
#3 0x5606b18aca40 in ?? ()
#4 0x7f5c971a9f11 in invoke_handler (binding=0x56069dc351c0,
event=0x5606b4c878c0, window=0x56069dc351c0, handler=,
display=0x5606900e0020) at ../src/core/keybindings.c:1921
#5 process_event (display=display@entry=0x5606900e0020,
window=window@entry=0x56069e5ad220, event=event@entry=0x5606b4c878c0)
at ../src/core/keybindings.c:2005
#6 0x7f5c971ab83e in process_special_modifier_key
(display=display@entry=0x5606900e0020, event=event@entry=0x5606b4c878c0,
window=window@entry=0x56069e5ad220,
modifier_press_only=modifier_press_only@entry=0x5606900e01a8,
resolved_key_combo=resolved_key_combo@entry=0x5606900e0198,
trigger_callback=0x7f5c971a5100 )
at ../src/core/keybindings.c:2051
#7 0x7f5c971ac976 in process_overlay_key (window=0x56069e5ad220,
event=0x5606b4c878c0, display=0x5606900e0020)
at ../src/core/keybindings.c:2151
#8 process_key_event (event=0x5606b4c878c0, window=0x56069e5ad220,
display=0x5606900e0020) at ../src/core/keybindings.c:2228
#9 meta_keybindings_process_event (display=display@entry=0x5606900e0020,
window=window@entry=0x56069e5ad220,
event=event@entry=0x5606b4c878c0) at ../src/core/keybindings.c:2326
#10 0x7f5c971a801c in meta_display_handle_event (event=0x5606b4c878c0,
display=0x5606900e0020) at ../src/core/events.c:358
#11 event_callback (event=0x5606b4c878c0, data=0x5606900e0020) at
../src/core/events.c:479
#12 0x7f5c97368235 in _clutter_event_process_filters ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#13 0x7f5c9737e585 in emit_keyboard_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#14 0x7f5c9721c0e0 in meta_input_device_native_process_kbd_a11y_event
(event=0x5606b4c878c0, device=0x56068fd782b0,
emit_event_func=0x7f5c9737e570 ) at
../src/backends/native/meta-input-device-native.c:1195
#15 0x7f5c9737fa36 in _clutter_process_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#16 0x7f5c97399d08 in _clutter_stage_queue_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#17 0x7f5c9721901c in meta_event_dispatch (g_source=,
callback=, user_data=)
at ../src/backends/native/meta-device-manager-native.c:686
#18 0x7f5c97cf984d in g_main_context_dispatch () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#19 0x7f5c97cf9ad0 in g_main_context_iterate.isra () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#20 0x7f5c97cf9dc3 in g_main_loop_run () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#21 0x7f5c971aefe0 in meta_run () at ../src/core/main.c:676
#22 0x56068ef07d85 in main ()
(gdb) frame 4
#4 0x7f5c971a9f11 in invoke_handler (binding=0x56069dc351c0,
event=0x5606b4c878c0, window=0x56069dc351c0, handler=,
display=0x5606900e0020) at ../src/core/keybindings.c:1921
1921../src/core/keybindings.c: Toks failas ar aplankas neegzistuoja.
(gdb) print *binding->handler
$1 = {name = 0x5606b49e5e80 "", func = 0x5606b18aca40, default_func =
0x7f5c5b333f10, data = 0, flags = 0, user_data = 0x5606b10c4e30,
user_data_free_func = 0x7f5c97487c60}
(gdb) print *binding
$2 = {name = 0x5606b49d15d0 "\220T\241\234\006V", combo = {keysym = 50, keycode
= 0, modifiers = META_VIRTUAL_SUPER_MASK},
resolved_combo = {keycodes = 0x5606a0c44d70, len = 1, mask = 64}, flags = 0,
handler = 0x5606b37830b0}
#gnome-shell reactions on IRC:
18:34 looks suspicious
18:35 its as if the looked up binding was freed already and now just
contains garbage
--
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/1851528
Title:
JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
and segfault
Status in gnome-shell package in Ubuntu:
New
Bug description:
I was trying to bring my Firefox window to front by pressing Super+2
(it's my second pinned launcher), and gnome-shell crashed.
journalctl shows this:
lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed
UTF-8 character sequence at offset 0
_filterKeybinding@resource:///org/
[Desktop-packages] [Bug 540751] Re: Unable to use dead keys with java and ibus
This bug is now on Ubuntu 19.10 with openjdk-11... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/540751 Title: Unable to use dead keys with java and ibus Status in ibus package in Ubuntu: Invalid Status in openjdk-6 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Invalid Bug description: Using latest Lucid packages, I am unable to use ^ key to generate ê french character in every Java programs (jEdit, Netbeans, etc.). Typing ^ + e give just the e character. Typing ^ + Space and nothing appears. I've tried with Sun JDK (6u18, 6u20, 7) and the bug is still present. I've tried to remove ibus and everything works again (I've just unset XMODIFIERS and GTK_IM_MODULE). I don't know if it's an ibus bug or openjdk one. ProblemType: Bug Architecture: amd64 Date: Thu Mar 18 09:03:11 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java InstallationMedia: Error: [Errno 13] Permission non accordée: '/var/log/installer/media-info' NonfreeKernelModules: nvidia Package: openjdk-6-jre-headless 6b18~pre2-1ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.utf8 ProcVersionSignature: Ubuntu 2.6.32-16.25-genUser Name SourcePackage: openjdk-6 Uname: Linux 2.6.32-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/540751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 interesting idea - especially if you need data from extensions
(which I miss too and I didn't try to recover). Also +1 for
blocking/removing this build from download sources. It's too dangerous
for now ;).
--
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",
Throttleable: 1
UptimeTS: 98.30915265
Vendor: Mozilla
Version: 71.0
useragent_local
[Desktop-packages] [Bug 1851528] [NEW] JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
Public bug reported: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. ** 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault Status in gnome-shell package in Ubuntu: New Bug description: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850803] Re: Wrong wrap length when composing emails
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=159.
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 2019-11-06T15:20:40+00:00 Bugzilla-7 wrote:
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0)
Gecko/20100101 Firefox/70.0
Steps to reproduce:
After upgrading to Thunderbird 68.1.2 as part of upgrading to Ubuntu
19.10, Thunderbird seems to use the wrong wrap length when composing
emails. I have mail.wrap_long_lines set to true, and mailnews.wraplength
set to 72, but when composing emails, lines are wrapped at a shorter
length. It appears to be about 55 characters. Emails that I have sent
are displayed correctly, so the problem only happens when composing.
This bug report has been opened at the request of Oliver Tilloy on the
Ubuntu bug tracker:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850803
Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850803/comments/3
** Changed in: thunderbird
Status: Unknown => New
** Changed in: thunderbird
Importance: Unknown => Medium
--
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/1850803
Title:
Wrong wrap length when composing emails
Status in Mozilla Thunderbird:
New
Status in thunderbird package in Ubuntu:
Incomplete
Bug description:
After upgrading to Ubuntu 19.10, Thunderbird seems to use the wrong
wrap length when composing emails. I have mail.wrap_long_lines set to
true, and mailnews.wraplength set to 72, but when composing emails,
lines are wrapped at a shorter length. It appears to be about 55
characters. Emails that I have sent are displayed correctly, so the
problem only happens when composing.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: thunderbird 1:68.1.2+build1-0ubuntu1
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
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 30823 F pulseaudio
BuildID: 20191010144232
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 31 10:47:12 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
dns-search integrics.com
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-08-16 (805 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
default via 172.20.64.1 dev wlp58s0 proto dhcp metric 600
169.254.0.0/16 dev wlp58s0 scope link metric 1000
172.20.64.0/19 dev wlp58s0 proto kernel scope link src 172.20.71.127 metric
600
MostRecentCrashID: bp-f7ee5fe5-1543-4438-9493-dbd8f0170707
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
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: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1850803/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
The same bug! ** Also affects: pulseaudio Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => datch (s-ogorodnick) ** No longer affects: pulseaudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848185] Re: segfault in __strcasestr
This bug was fixed in the package network-manager-applet - 1.8.10-2ubuntu3 --- network-manager-applet (1.8.10-2ubuntu3) bionic; urgency=medium * debian/patches/git_error_handling.patch: - don't segfault when gnome-keyring is missing (lp: #1806269) * debian/patches/git_editor_segfault.patch: - backport a segfault fix for the editor (lp: #1848185) * debian/patches/git_label_warning.patch: - backport fix for parsing error warnings being displayed when connecting to an ap with special chars (lp: #1848186) -- Sebastien Bacher Tue, 15 Oct 2019 10:50:14 +0200 ** Changed in: network-manager-applet (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1848185 Title: segfault in __strcasestr Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Released Bug description: * Impact The connection editor sometime segfaults * Test case no specific to trigger the issue but check that error reports stop with the new version https://errors.ubuntu.com/problem/22f059991e427d58a003539ecedff7be196a7e35 * Regression potential the change is smaller and in newer serie, it should create issues but check that the editor keeps working fine without segfaultsb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1848185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848186] Re: label escaping warnings
This bug was fixed in the package network-manager-applet - 1.8.10-2ubuntu3 --- network-manager-applet (1.8.10-2ubuntu3) bionic; urgency=medium * debian/patches/git_error_handling.patch: - don't segfault when gnome-keyring is missing (lp: #1806269) * debian/patches/git_editor_segfault.patch: - backport a segfault fix for the editor (lp: #1848185) * debian/patches/git_label_warning.patch: - backport fix for parsing error warnings being displayed when connecting to an ap with special chars (lp: #1848186) -- Sebastien Bacher Tue, 15 Oct 2019 10:50:14 +0200 ** Changed in: network-manager-applet (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1848186 Title: label escaping warnings Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Released Bug description: * Impact When connecting to some access points warnings are printed in the log due to incorrect handling of special chars * Test case Connect to an AP with a '&' in its name, no warning should be displayed * Regression potential The code changes is the one building the label of APs, check that those are properly named in the applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1848186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806269] Re: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed
This bug was fixed in the package network-manager-applet - 1.8.10-2ubuntu3 --- network-manager-applet (1.8.10-2ubuntu3) bionic; urgency=medium * debian/patches/git_error_handling.patch: - don't segfault when gnome-keyring is missing (lp: #1806269) * debian/patches/git_editor_segfault.patch: - backport a segfault fix for the editor (lp: #1848185) * debian/patches/git_label_warning.patch: - backport fix for parsing error warnings being displayed when connecting to an ap with special chars (lp: #1848186) -- Sebastien Bacher Tue, 15 Oct 2019 10:50:14 +0200 ** Changed in: network-manager-applet (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1806269 Title: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed Status in Network Manager Applet: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Released Status in network-manager-applet package in Debian: Fix Released Bug description: * Impact the connection editor segfault when using without gnome-keyring * Test case uninstall gnome-keyring and try to edit a connection, it shouldn't segfault * Regression potential the fix changes an error handling case, it shouldn't impact normal use Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault. 0x77ba6b53 in modules_initialized (object=, res=0x56048a40, user_data=) at src/libnma/nma-cert-chooser-button.c:98 98 src/libnma/nma-cert-chooser-button.c: No such file or directory. This occurs when the package "gnome-keyring" is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1806269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey
Nevermind, I hadn't realized you had filed bug #1851211 already. Let's continue the discussion there. -- 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/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Won't Fix Bug description: [Impact] Installing a snap that requires the u2f-devices interface doesn't show a UI element to enable/disable this in GNOME Software. Initially Chromium didn't have this enabled by default, and thus the feature wouldn't work without going to the command line. It now is enabled by default. [Test Case] 1. Open GNOME Software 2. Install the Chromium snap 3. Click "Permissions" Expected result: A switch is shown to control "Read/write access to U2F devices exposed". Clicking it connects/disconnects the u2f-devices interface. Observed result: No switch is shown for this interface. [Regression Potential] A string for this interface was added to GNOME Software, low risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851305] Re: ssh links, tg links, magnet links doesn't work in snap chromium
*** This bug is a duplicate of bug 1776873 *** https://bugs.launchpad.net/bugs/1776873 ** This bug has been marked a duplicate of bug 1776873 Whitelisted allowedURLschemes breaks some desktop apps -- 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/1851305 Title: ssh links, tg links, magnet links doesn't work in snap chromium Status in chromium-browser package in Ubuntu: New Bug description: It seems that chromium snap transition broken all possible custom URL scheme support. And I not manage found any workaround because snap use hardcoded white list of allowed URI schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851211] Re: U2F not working in current build
The relevant denial seems to be: [ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c- ELAN1200:00/0018:04F3:3022.0001/report_descriptor" pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Christoph, is your device a Yubikey? Can you please attach additional debug information to this bug by running the following command in a terminal? apport-collect 1851211 ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851211 Title: U2F not working in current build Status in chromium-browser package in Ubuntu: Incomplete Bug description: This affects the current build of the snap version of Chromium. Although it was marked as fixed in the ticket here: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1738164 it is still open. No chance to use such a key in the browser. dmesg output is: My dmesg out put shows a lot of DENIED: audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=20568 label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=?' [ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor" pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Suggested solutions in the other tickets do not work System is Ubuntu 19.10 on an Asus UX330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806269] Update Released
The verification of the Stable Release Update for network-manager-applet has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1806269 Title: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed Status in Network Manager Applet: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Released Status in network-manager-applet package in Debian: Fix Released Bug description: * Impact the connection editor segfault when using without gnome-keyring * Test case uninstall gnome-keyring and try to edit a connection, it shouldn't segfault * Regression potential the fix changes an error handling case, it shouldn't impact normal use Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault. 0x77ba6b53 in modules_initialized (object=, res=0x56048a40, user_data=) at src/libnma/nma-cert-chooser-button.c:98 98 src/libnma/nma-cert-chooser-button.c: No such file or directory. This occurs when the package "gnome-keyring" is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1806269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848186] Update Released
The verification of the Stable Release Update for network-manager-applet has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1848186 Title: label escaping warnings Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Released Bug description: * Impact When connecting to some access points warnings are printed in the log due to incorrect handling of special chars * Test case Connect to an AP with a '&' in its name, no warning should be displayed * Regression potential The code changes is the one building the label of APs, check that those are properly named in the applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1848186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848185] Update Released
The verification of the Stable Release Update for network-manager-applet has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1848185 Title: segfault in __strcasestr Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Released Bug description: * Impact The connection editor sometime segfaults * Test case no specific to trigger the issue but check that error reports stop with the new version https://errors.ubuntu.com/problem/22f059991e427d58a003539ecedff7be196a7e35 * Regression potential the change is smaller and in newer serie, it should create issues but check that the editor keeps working fine without segfaultsb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1848185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
Thanks, that's useful. I'm not familiar with SPNEGO/GSSAPI/kerberos, could you maybe come up with easy steps to reproduce the problem on a clean system? That would allow me to dig further into the problem. -- 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/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in chromium-browser package in Ubuntu: Confirmed Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851522] [NEW] Ubuntu 18.04 cann't click for popup window
Public bug reported: 1) I use SecureCRT (Session Manager) and this program have float windows "Session Manager" It will dissapper when lost focus for this windows and not showing by click on button in program. 2) Same in wine with MSO2007 (popup menu for office is dissappear after first click) On pictures in attach (button not open float windows) On Wayland session all is OK. On 16.04 all is OK. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Снимок экрана от 2019-11-06 20-49-13.png" https://bugs.launchpad.net/bugs/1851522/+attachment/5303269/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-11-06%2020-49-13.png -- 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/1851522 Title: Ubuntu 18.04 cann't click for popup window Status in mutter package in Ubuntu: New Bug description: 1) I use SecureCRT (Session Manager) and this program have float windows "Session Manager" It will dissapper when lost focus for this windows and not showing by click on button in program. 2) Same in wine with MSO2007 (popup menu for office is dissappear after first click) On pictures in attach (button not open float windows) On Wayland session all is OK. On 16.04 all is OK. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1851522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
