[Desktop-packages] [Bug 1882023] Re: Notifications are pointlessly truncated even on ultrawide monitors
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors Status in gnome-shell package in Ubuntu: Expired Bug description: I tried to use ubuntu-bug -w to identify the component for this bug by clicking on a notification, but it failed with "xprop failed to determine process ID of the window". Sorry. The bug is that notifications of adding/removing icons to Favorites in the taskbar, are truncated for no good reason. I have a dual monitor setup ridiculous amounts of horizontal space, yet the notification is fixed size - which is fine, if it wrapped the text inside it. But it doesn't. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (109 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893478] Re: Wireless mouse not working
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1893478 Title: Wireless mouse not working Status in xorg-server package in Ubuntu: Expired Bug description: This might be link to gdm3 Running Ubuntu 20.04.1 Wireless mouse stop working after fresh install of Ubuntu 20.04 and after upgrade to 20.04 on another computer. The usb dongle is detected according to lsusb Bus 001 Device 023: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse When booting if I select recovery mode and then choose resume, everything works fine for this session, but as soon as I reboot then mouse stop working again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 28 15:30:34 2020 InstallationDate: Installed on 2020-05-15 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2020-08-28T11:40:26.503109 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1893478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I would like to report back that on Ubuntu 20.04 with Intel AX200 network card (8087:0029), I resolved this issue by following @Hui Wang's instruction ibt-20-1-3.sfi and ibt-20-1-3.ddc from 20.10 driver HSP/HSF was greyed out before but is now available and functioning after powering off and on again. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
On 2020-10-30 02:29, Gunnar Hjalmarsson wrote: > Is that what we want to do? Probably not. https://gitlab.gnome.org/GNOME/pango/-/issues/483#note_949138 Matthias' gtk commits seem to fix it. -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Confirmed Bug description: trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551949] Re: Printing to PDF file loses URLs/links
** Changed in: thunderbird Importance: Medium => Unknown -- 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/1551949 Title: Printing to PDF file loses URLs/links Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. File -> Print... 2. Select "Print to File". 3. Enter the file name. 4. Enter the save-to folder. 5. Leave the output format as-is, or select PDF if it's not the default. 6. Hit the Print button. 7. Open the resulting PDF in any PDF viewer. Actual results: The URLs within the document are not actually hyperlinks. They are simply text, coloured blue and underlined. Expected results: Any clickable links on the original e-mail message should be retained when converting the document to PDF format. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: thunderbird 1:38.5.1+build2-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colan 2383 F pulseaudio /dev/snd/controlC0: colan 2383 F pulseaudio BuildID: 20160106101030 Channel: Unavailable CurrentDesktop: Unity Date: Tue Mar 1 15:53:53 2016 EcryptfsInUse: Yes ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.140 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-1abc004a-043e-4a15-bdc0-45ade2150908 Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/zsh Profiles: Profile0 (Default) - LastVersion=38.5.1/20160106101030 (In use) RelatedPackageVersions: google-talkplugin 5.41.0.0-1 rhythmbox-mozilla 3.2.1-1ubuntu3.1 adobe-flashplugin 1:20160209.1-0ubuntu0.15.10.1 RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-1abc004a-043e-4a15-bdc0-45ade2150908 bp-c8c94f9f-0c39-42d2-97ac-f2c7d2150713 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to wily on 2015-11-30 (92 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1551949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823616] Re: Incorrect date format for Australia
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3338 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3338 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3338 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low ** Tags removed: disco ** Tags added: focal ** Also affects: gnome-desktop (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/1823616 Title: Incorrect date format for Australia Status in GNOME Shell: Unknown Status in gnome-desktop3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: The calendar in the menu bar of gnome-shell is not adhering to the localisation settings for Australia. The issue is displayed both in the menu bar date and within the calendar popout as well. The localisation configuration in the Settings appears to display correctly whilst the calendar in the menu bar is showing US layout. This issue appears in a minimal install of the OS. I have not tested the behaviour in a full install. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 15:42:35 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) 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/1823616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823616] Re: Incorrect date format for Australia
** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu) ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Triaged ** Changed in: gnome-desktop3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1823616 Title: Incorrect date format for Australia Status in GNOME Shell: Unknown Status in gnome-desktop3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: The calendar in the menu bar of gnome-shell is not adhering to the localisation settings for Australia. The issue is displayed both in the menu bar date and within the calendar popout as well. The localisation configuration in the Settings appears to display correctly whilst the calendar in the menu bar is showing US layout. This issue appears in a minimal install of the OS. I have not tested the behaviour in a full install. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 15:42:35 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) 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/1823616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823616] Re: Incorrect date format for Australia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1823616 Title: Incorrect date format for Australia Status in GNOME Shell: Unknown Status in gnome-desktop3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: The calendar in the menu bar of gnome-shell is not adhering to the localisation settings for Australia. The issue is displayed both in the menu bar date and within the calendar popout as well. The localisation configuration in the Settings appears to display correctly whilst the calendar in the menu bar is showing US layout. This issue appears in a minimal install of the OS. I have not tested the behaviour in a full install. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 15:42:35 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) 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/1823616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902108] Re: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Please check that you don't have 'timidity' installed. If the problem continues then please try a higher kernel version like this one: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.2/amd64/ ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1902108 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since I upgraded from Ubuntu 18.04 to 20.04 any sound is played. The audio output is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dario 9759 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:55:36 2020 InstallationDate: Installed on 2019-08-09 (446 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-10-15 (14 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8257 dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8257:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1LZ10EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 939242] Re: gnome-control-center takes 100% CPU
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/939242 Title: gnome-control-center takes 100% CPU Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: Ubuntu 12.04 Alpha 2 unity 5.4.0 gnome-control-center 1:3.3.90-0ubuntu1 When I have the GNOME Control Center open, I have soaring CPU usage by it - constantly at 100% according to top, and my computer's fan runs wild when it's open. I'm not sure why, but I would assume that, if idle, it should not do anything and have near 0% CPU usage. Steps to reproduce: 1) Open Appearance settings 2) Open a terminal 3) run 'top' and see if gnome-control-center is taking tons of CPU ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.6-kroqernel+ x86_64 ApportVersion: 1.92-0ubuntu1 Architecture: amd64 CheckboxSubmission: 7f98738f6663bda1ae1c2900a3a1db71 CheckboxSystem: 577751a334467e78ed04da699e5debc9 Date: Wed Feb 22 22:44:42 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-02-11 (11 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.1-0ubuntu2 deja-dup21.2-0ubuntu4 gnome-bluetooth 3.2.2-0ubuntu1 indicator-datetime 0.3.90-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/939242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902094] Re: High Xorg and gnome-shell CPU usage while Sound Settings opened
Given gnome-shell is also affected it seems the problem is gnome- control-center doing some kind of constant, invisible rendering when in the Sound panel. ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1902094 Title: High Xorg and gnome-shell CPU usage while Sound Settings opened Status in gnome-control-center package in Ubuntu: Triaged Bug description: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:27:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824] InstallationDate: Installed on 2020-09-12 (47 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. G5 5587 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 03PVDF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0824 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 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.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902094] Re: High CPU usage while Sound Settings opened
Oddly, confirmed. Only when in Sound settings... PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1841 dan 20 0 1125668 168248 120056 S 12.9 1.0 103:17.70 Xorg 1984 dan 20 0 5481060 435396 90896 S 8.3 2.7 89:49.05 gnome-shell 346704 dan 20 0 1611480 120968 90512 S 6.0 0.7 0:06.76 gnome-control-c ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Summary changed: - High CPU usage while Sound Settings opened + High Xorg CPU usage while Sound Settings opened ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Summary changed: - High Xorg CPU usage while Sound Settings opened + High Xorg and gnome-shell CPU usage while Sound Settings opened ** No longer affects: xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1902094 Title: High Xorg and gnome-shell CPU usage while Sound Settings opened Status in gnome-control-center package in Ubuntu: Triaged Bug description: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:27:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824] InstallationDate: Installed on 2020-09-12 (47 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. G5 5587 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 03PVDF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0824 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 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.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1902018] Re: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version
The login GUI is gnome-shell... ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- 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/1902018 Title: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version Status in gnome-shell package in Ubuntu: New Bug description: OS: Ubuntu 20.10 version Test sequence: Fingeprint is enrolled Win+L: At login screen, earlier in 20.04 version, it used to display "scan your finger", it is not displayed in 20.10 version, but fingerprint identify is working fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-09-29 (29 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-control-center 1:3.38.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-27 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902086] Re: xorg on Ubuntu 20.04 fails to show correctly background image and icons
*** This bug is a duplicate of bug 1867668 *** https://bugs.launchpad.net/bugs/1867668 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1867668, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1867668 Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902086 Title: xorg on Ubuntu 20.04 fails to show correctly background image and icons Status in xorg package in Ubuntu: New Bug description: Hello I have PC with Xeon E processor and I am using integrated Intel graphics to drive a VGA display. I am using Ubuntu 20.04 Everything works fine. Then I add xorg.conf file, for other reasons, to /etc/X11 ( by default no xorg.conf file is present ) and I get the first screen after the log in is corrupted by yellow vertical lines and/or corrupted icons and eventually a block box is present at half height of the screen. See here below the incriminated xorg.conf : Section "ServerLayout" Identifier "layout" Screen 0 "intel" EndSection Section "Device" Identifier "intel" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection and photo of the corrupted screen is attached. If I open terminal or what else looks good but the first screen is always a bit corrupted. If I change the background image , the new background appears without vertical lines. If I go back to the original background image that is still corrupted with vertical lines. I am sure the corruption is because of the xorg.conf file but how can I fix the situation ? I need the xorg.conf file because I want xorg.conf to use only the internal integrated intel graphics and not other graphics cards/drivers that will be present. If I do exactly the same , adding the same xorg.conf file to on Ubuntu 18.04, same HW, same configuration, I don't see this problem. It happens only with Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900873] Re: dual display scaling broken at 4k
Thanks. I think xrandr.txt is the most important file there but it looks like you didn't have any scaling set at the time. Please enable fractional scaling, even if it is too big, and then run: xrandr --verbose > xrandr2.txt journalctl -b0 > journal2.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1900873 Title: dual display scaling broken at 4k Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have to 4k monitors. 15" on the dell xps 3840/2160/60 40" philips external BDM4065 3840/2160/30 Obviously i need different scale factors to use them properly. This feature DOES NOT WORK. It seems the scaling is not handled separately per monitor as the UI suggests. The fractional scaling also does not seem to work. any change to the scaling ends seems to be rounded to full. Which meens a compromise scale of 125% is effectively 200% on the large monitor. I havent found any config which would make this useful. So basically when I use the external 40" I cannot use the builtin anymore without an external fresnell magnifier lens (which I dont have ;) updated Ubuntu 20.04.1 LTS on DELL XPS 7590 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz 32GB SODIMM DDR4 Synchronous 2667 (0.4ns) PCI bridge: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] Hostbridge: Intel UHD Graphics 630 (Mobile) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 17:35:12 2020 InstallationDate: Installed on 2020-04-22 (181 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901808] Re: Laptop displays has lags and tearing
** This bug is no longer a duplicate of bug 1853094 [modeset] Screen tearing when using multiple monitors ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1901808 Title: Laptop displays has lags and tearing Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: I have laptop dell with intel i5-4100U, intel hd 4400 and geforce 820m on board. I added zotac gtx 960 and one monitor via rizer. gtx and monitor worked correctly. but laptop displays has lags and tearing. I tried install i915 i965-va-drivers intel config section Section "Device" Identifier "Device1" Driver "intel" VendorName "Intel Corporation" Option "TearFree" "true" Option "DRI" "2" EndSection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06: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 455.32.00 Wed Oct 14 22:46:18 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Deepin Date: Wed Oct 28 11:03:01 2020 DistUpgraded: 2020-08-20 21:43:47,424 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2378] Subsystem: Dell GeForce 820M [1028:0652] InstallationDate: Installed on 2020-07-16 (103 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=ab9e3a31-2ad4-4c5f-a786-92ff7dbde56d ro rootflags=subvol=@ nouveau.modeset=0 DEEPIN_GFXMODE= crashkernel=512M-:192M SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-20 (68 days ago) dmi.bios.date: 03/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0926J6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/28/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0652 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1901808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901946] Re: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1793640 *** https://bugs.launchpad.net/bugs/1793640 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1793640, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1793640 Pulseaudio fails to detect sound card, while timidity is installed -- 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/1901946 Title: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading distribution pulseaudio only sees dummy output and no input ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:16:37 2020 InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
As geez did above, I installed libmutter-7-0, mutter, and mutter-common from groovy-proposed. Zoom now opens and seems to run fine, which is the snap that, for me, previously did not open. There seems to be a draw issue that I have never had before though. When I close the application, the window closes, then the title bar and window outline reappear for a second or two, prior to closing for good. -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: In Progress Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
geez, That's a common mistake... When we ask people to test a mutter update we actually mean 'libmutter' that's used by gnome-shell. ** Also affects: mutter (Ubuntu Hirsute) Importance: High Status: In Progress ** Also affects: snapd (Ubuntu Hirsute) Importance: High Status: Won't Fix -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: In Progress Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
Now we know from the upstream pango issue which commit caused this bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/e5c0b4f5 I confirmed that reversing that commit fixes it: https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-terminal Is that what we want to do? -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Confirmed Bug description: trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10
ok, this is what happens in journalctl when an ISO successfully is mounted: ``` Oct 29 18:02:06 boxxy kernel: loop1: p1 p2 Oct 29 18:02:06 boxxy kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Oct 29 18:02:06 boxxy kernel: ISO 9660 Extensions: RRIP_1991A Oct 29 18:02:06 boxxy udisksd[2567]: Mounted /dev/loop1p1 at /media/tessa/Ubuntu 20.04.1 LTS amd64 on behalf of uid 1000 Oct 29 18:02:06 boxxy udisksd[2567]: Set up loop device /dev/loop1 (backed by /home/tessa/Downloads/ISOs/ubuntu-20.04.1-desktop-amd64.iso) Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0315 FuEngine ccgx failed to change udev device /sys/devices/virtual/block/loop1: cannot ensure ID: FuUdevDevice: Oct 29 18:02:07 boxxy fwupd[6497]: Unknown Device Oct 29 18:02:07 boxxy fwupd[6497]: Flags:none Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0319 FuEngine ccgx failed to change udev device /sys/devices/virtual/block/loop1/loop1p2: cannot ensure ID: FuUdevDevice: Oct 29 18:02:07 boxxy fwupd[6497]: Unknown Device Oct 29 18:02:07 boxxy fwupd[6497]: Flags:none Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0320 FuEngine ccgx failed to change udev device /sys/devices/virtual/block/loop1/loop1p1: cannot ensure ID: FuUdevDevice: Oct 29 18:02:07 boxxy fwupd[6497]: Unknown Device Oct 29 18:02:07 boxxy fwupd[6497]: Flags:none ``` but when I try to mount that virtio iso, it just times out, displays that error dialogue, and literally nothing goes to `journalctl`. is there a way to run it with debug logging? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1901286 Title: gnome-disk-image-mounter fails after upgrade to 20.10 Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: after upgrading to 20.10, mounting ISOs fails after a bit over 20s, with a GTK dialogue that reads: ``` Error attaching disk image: GDBus.Error:org.freedesktop.UDisks2.Error.Fails: Error waiting for loop object after creating '/dev/loop5': Timed out waiting for object (udisks-error-quark, 0) ``` note that the loop device named increases on every attempt, it doesn't appear to be freeing previously allocated devices. here's the only output when run from the shell: ``` $ time gnome-disk-image-mounter some.iso real 0m23.141s user 0m0.144s sys 0m0.019s ``` ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-disk-utility 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14 Uname: Linux 5.8.0-25-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 23 23:42:34 2020 InstallationDate: Installed on 2020-07-15 (101 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896919] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in gnome-control-center source package in Groovy: Fix Released Bug description: [Impact] After we plugging a hdmi/dp monitor with audio capability, we could select hdmi audio as output device in the g-c-c, but after we do that, the profile combo list will show up in the g-c-c and this combo list is empty, it should be stereo-hdmi by default according to 18.04 [Fix] Backport a fix from g-c-c upstream, after applying this patch, the combo list update signals will be recevied after the pa finishes the changing active profile. [Test Case] Plug the hdmi/dp monitor with audio capability, then choose hdmi audio as active output device from g-c-c, we will find the profile combo list has hdmi-steoreo as the default profile. This is same as 18.04. [Regression Risk] It is possible to make the output and input device can't work after applying this patch, that is because the active profile is not set as our expected. But this possibility is very low, I tested this patch on 2 lenovo and 2 dell laptops, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873378] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873378 Title: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact The user panel hits a segfault sometimes * Test case Check that reports stop on https://errors.ubuntu.com/problem/af55dc0f4cb3abb5f2c5632d1195450e44db98ca * Regression potential The change is in the user panel's user initial avatar generation, check that the default image for profiles without an avatar is still generated --- Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Package version: 1:3.36.1-1ubuntu4 The application was running in the background, with only Chrome running at the same time. It's a mid-2014 MacBook Pro, so some drivers are not very stable and can cause this kind of issues. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 23:41:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-10 (250 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f303176e6e4:movzbl (%r14),%r15d PC (0x7f303176e6e4) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%r15d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 generate_default_avatar () ?? () ?? () Title: gnome-control-center crashed with SIGSEGV in g_utf8_normalize() UpgradeStatus: Upgraded to focal on 2020-04-09 (7 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887707] Re: Disabling fractional scaling after selecting another integer scaling may unselect user choice
This bug was fixed in the package gnome-control-center - 1:3.36.4-0ubuntu2 --- gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium * debian/patches/git_useraccount_segfault.patch: - don't segfault trying to get the user initials when accountsservice is not responding (lp: #1873378) * debian/patches/git_row_collide.patch: - backport a fix for items of the connection details colliding (lp: #1873184) [ Hui Wang ] * d/p/0033-sound-update-the-profile-list-after-getting-the-sign.patch - signal to update profile combo list after the PA changes the active profile, this patch fixes the empty profile combo list issue after selecting the hdmi/dp audio in the g-c-c. (LP: #1896919) [ Marco Trevisan (Treviño) ] * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch: - Don't try to fetch monitors if the config manager is not ready yet (lp: #1887731) * d/p/0019-display-Support-UI-scaled-logical-monitor-mode.patch, d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - Don't disable fractional scaling immediately on integer changes (lp: #1887707) -- Sebastien Bacher Thu, 24 Sep 2020 17:03:01 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887707 Title: Disabling fractional scaling after selecting another integer scaling may unselect user choice Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Released Bug description: [ Impact ] If selecting another integer scaling after disabling fractional scaling [ Test case ] When running Ubuntu session under X11, in gnome-control-center, display panel: - Ensure 100% scaling is selected and applied - Enable fractional scaling - Select 200% scaling (or bigger integer scaling) - Green "Apply" button should be visible and clickable - Deactivate fractional scaling - Green "Apply" button stays and fractional scaling isn't disabled until applied Repeat with inverted scaling orders (applying 200% and then selecting 100%) Currently, once another integer value is selected, we just deselect the user choice and restore the previous one, deactivating the fractional scaling promtply. [ Regression potential ] - Displays are wrongly disposed and configured when fractional scaling is enabled - Configurations are not applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873184] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in gnome-control-center source package in Groovy: Fix Released Bug description: * Impact The details of the connection settings sometime overlap * Test case Connect the computer to a wired ethernet, go to settings and check the connection details, the items should be displayed separated and not overlapping * Regression potential Check that the connection details dialog is correctly displayed on different typo of connections, the change is in the layout of the elements so it could impact the layout in other cases To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887707] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887707 Title: Disabling fractional scaling after selecting another integer scaling may unselect user choice Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Released Bug description: [ Impact ] If selecting another integer scaling after disabling fractional scaling [ Test case ] When running Ubuntu session under X11, in gnome-control-center, display panel: - Ensure 100% scaling is selected and applied - Enable fractional scaling - Select 200% scaling (or bigger integer scaling) - Green "Apply" button should be visible and clickable - Deactivate fractional scaling - Green "Apply" button stays and fractional scaling isn't disabled until applied Repeat with inverted scaling orders (applying 200% and then selecting 100%) Currently, once another integer value is selected, we just deselect the user choice and restore the previous one, deactivating the fractional scaling promtply. [ Regression potential ] - Displays are wrongly disposed and configured when fractional scaling is enabled - Configurations are not applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873378] Re: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc()
This bug was fixed in the package gnome-control-center - 1:3.36.4-0ubuntu2 --- gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium * debian/patches/git_useraccount_segfault.patch: - don't segfault trying to get the user initials when accountsservice is not responding (lp: #1873378) * debian/patches/git_row_collide.patch: - backport a fix for items of the connection details colliding (lp: #1873184) [ Hui Wang ] * d/p/0033-sound-update-the-profile-list-after-getting-the-sign.patch - signal to update profile combo list after the PA changes the active profile, this patch fixes the empty profile combo list issue after selecting the hdmi/dp audio in the g-c-c. (LP: #1896919) [ Marco Trevisan (Treviño) ] * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch: - Don't try to fetch monitors if the config manager is not ready yet (lp: #1887731) * d/p/0019-display-Support-UI-scaled-logical-monitor-mode.patch, d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - Don't disable fractional scaling immediately on integer changes (lp: #1887707) -- Sebastien Bacher Thu, 24 Sep 2020 17:03:01 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873378 Title: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact The user panel hits a segfault sometimes * Test case Check that reports stop on https://errors.ubuntu.com/problem/af55dc0f4cb3abb5f2c5632d1195450e44db98ca * Regression potential The change is in the user panel's user initial avatar generation, check that the default image for profiles without an avatar is still generated --- Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Package version: 1:3.36.1-1ubuntu4 The application was running in the background, with only Chrome running at the same time. It's a mid-2014 MacBook Pro, so some drivers are not very stable and can cause this kind of issues. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 23:41:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-10 (250 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f303176e6e4:movzbl (%r14),%r15d PC (0x7f303176e6e4) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%r15d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 generate_default_avatar () ?? () ?? () Title: gnome-control-center crashed with SIGSEGV in g_utf8_normalize() UpgradeStatus: Upgraded to focal on 2020-04-09 (7 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887731] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887731 Title: gnome-control-center crashes in cc_display_config_manager_get_current -> get_valid_monitors -> get_dock_monitor -> update_dock_placement_combo_selection Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact The appearance settings hit a segfault sometime * Test case The error reports should stop on https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 * Regression potential Check that that appearance settings still work correctly, including configuring on which screen the dock should be displayed The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.4-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c
This bug was fixed in the package gnome-control-center - 1:3.36.4-0ubuntu2 --- gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium * debian/patches/git_useraccount_segfault.patch: - don't segfault trying to get the user initials when accountsservice is not responding (lp: #1873378) * debian/patches/git_row_collide.patch: - backport a fix for items of the connection details colliding (lp: #1873184) [ Hui Wang ] * d/p/0033-sound-update-the-profile-list-after-getting-the-sign.patch - signal to update profile combo list after the PA changes the active profile, this patch fixes the empty profile combo list issue after selecting the hdmi/dp audio in the g-c-c. (LP: #1896919) [ Marco Trevisan (Treviño) ] * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch: - Don't try to fetch monitors if the config manager is not ready yet (lp: #1887731) * d/p/0019-display-Support-UI-scaled-logical-monitor-mode.patch, d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - Don't disable fractional scaling immediately on integer changes (lp: #1887707) -- Sebastien Bacher Thu, 24 Sep 2020 17:03:01 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in gnome-control-center source package in Groovy: Fix Released Bug description: [Impact] After we plugging a hdmi/dp monitor with audio capability, we could select hdmi audio as output device in the g-c-c, but after we do that, the profile combo list will show up in the g-c-c and this combo list is empty, it should be stereo-hdmi by default according to 18.04 [Fix] Backport a fix from g-c-c upstream, after applying this patch, the combo list update signals will be recevied after the pa finishes the changing active profile. [Test Case] Plug the hdmi/dp monitor with audio capability, then choose hdmi audio as active output device from g-c-c, we will find the profile combo list has hdmi-steoreo as the default profile. This is same as 18.04. [Regression Risk] It is possible to make the output and input device can't work after applying this patch, that is because the active profile is not set as our expected. But this possibility is very low, I tested this patch on 2 lenovo and 2 dell laptops, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887731] Re: gnome-control-center crashes in cc_display_config_manager_get_current -> get_valid_monitors -> get_dock_monitor -> update_dock_placement_combo_selection
This bug was fixed in the package gnome-control-center - 1:3.36.4-0ubuntu2 --- gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium * debian/patches/git_useraccount_segfault.patch: - don't segfault trying to get the user initials when accountsservice is not responding (lp: #1873378) * debian/patches/git_row_collide.patch: - backport a fix for items of the connection details colliding (lp: #1873184) [ Hui Wang ] * d/p/0033-sound-update-the-profile-list-after-getting-the-sign.patch - signal to update profile combo list after the PA changes the active profile, this patch fixes the empty profile combo list issue after selecting the hdmi/dp audio in the g-c-c. (LP: #1896919) [ Marco Trevisan (Treviño) ] * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch: - Don't try to fetch monitors if the config manager is not ready yet (lp: #1887731) * d/p/0019-display-Support-UI-scaled-logical-monitor-mode.patch, d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - Don't disable fractional scaling immediately on integer changes (lp: #1887707) -- Sebastien Bacher Thu, 24 Sep 2020 17:03:01 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887731 Title: gnome-control-center crashes in cc_display_config_manager_get_current -> get_valid_monitors -> get_dock_monitor -> update_dock_placement_combo_selection Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact The appearance settings hit a segfault sometime * Test case The error reports should stop on https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 * Regression potential Check that that appearance settings still work correctly, including configuring on which screen the dock should be displayed The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.4-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap
This bug was fixed in the package gnome-control-center - 1:3.36.4-0ubuntu2 --- gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium * debian/patches/git_useraccount_segfault.patch: - don't segfault trying to get the user initials when accountsservice is not responding (lp: #1873378) * debian/patches/git_row_collide.patch: - backport a fix for items of the connection details colliding (lp: #1873184) [ Hui Wang ] * d/p/0033-sound-update-the-profile-list-after-getting-the-sign.patch - signal to update profile combo list after the PA changes the active profile, this patch fixes the empty profile combo list issue after selecting the hdmi/dp audio in the g-c-c. (LP: #1896919) [ Marco Trevisan (Treviño) ] * d/p/0008-Allow-tweaking-some-settings-for-Ubuntu-Dock.patch: - Don't try to fetch monitors if the config manager is not ready yet (lp: #1887731) * d/p/0019-display-Support-UI-scaled-logical-monitor-mode.patch, d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - Don't disable fractional scaling immediately on integer changes (lp: #1887707) -- Sebastien Bacher Thu, 24 Sep 2020 17:03:01 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in gnome-control-center source package in Groovy: Fix Released Bug description: * Impact The details of the connection settings sometime overlap * Test case Connect the computer to a wired ethernet, go to settings and check the connection details, the items should be displayed separated and not overlapping * Regression potential Check that the connection details dialog is correctly displayed on different typo of connections, the change is in the layout of the elements so it could impact the layout in other cases To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901318] Re: needs to depend on tcl (not just tcl8.6)
@digidietze you might have misunderstood the report. It's all working fine if the tcl package is installed, as that package includes the /usr/bin/tclsh symlink. But the usb-modeswitch package does not depend on the tcl package, it only depends on the tcl8.6 package (which doesn't contain a /usr/bin/tclsh symlink). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1901318 Title: needs to depend on tcl (not just tcl8.6) Status in usb-modeswitch package in Ubuntu: Fix Committed Bug description: * Impact the usb-modeswitch dispatcher script fails to start on the default installation because it uses tclsh unversioned while we depends on tcl8.6 * Test Case $ /usr/sbin/usb_modeswitch_dispatcher shouldn't bail out on an interpreter error (or better, test that plugging an usb modem is correctly handled) * Regression potential The script was bailing out due to a missing intepreter before so the code wasn't tested, it's possible that it triggers errors or could interact with the system in some way. The dispatcher reacts to udev events when an usb modem is connected, so try to use one of those and make sure that there is no negative effect (and if possible that the modem gets correctly handled) -- the package currently depends on tcl8.6, but /usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which isn't provided by tcl8.6, so it likely would need to depend on something like tcl (= 8.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902148] [NEW] [snap] launchers in app's dock menu do launch general LO
Public bug reported: LO 7.0.2 Ubuntu Focal 1) right-click on LO icon in dock (white LO icon which does launch the home page with apps and recent docs) 2) select e.g. Calc It does launch general LO (home page with apps and recent docs), not Calc. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1902148 Title: [snap] launchers in app's dock menu do launch general LO Status in libreoffice package in Ubuntu: New Bug description: LO 7.0.2 Ubuntu Focal 1) right-click on LO icon in dock (white LO icon which does launch the home page with apps and recent docs) 2) select e.g. Calc It does launch general LO (home page with apps and recent docs), not Calc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900445] Re: LibreOffice 7 Writer and Calc crash when creating new or opening documents
cf. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/comments/6 ** Attachment added: "journalctl -b for user 1000 (me)" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/+attachment/5429202/+files/journal.1000.txt -- 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/1900445 Title: LibreOffice 7 Writer and Calc crash when creating new or opening documents Status in libreoffice package in Ubuntu: New Bug description: I'm using LibreOffice under Ubuntu 20.04 LTS. I've always used LibreOffice PPA depot instead of Ubuntu's. Up to version 6.4, no issues. When 7.0 became available, LibreOffice got automatically upgraded. Since then, when ever I try to create a new Writer or Calc document or when I try to open such existing document, LibreOffice crashes immediately, then reopens and proposes to recover the document I tried to create/open. If I opt to recover, it crashes again. If I opt to discard, LibreOffice opens up but as soon as I try to either create new/open either a Writer or Calc document, it crashes again. I tried to open LibreOffice in safe-mode but to no avail, same behaviour. I also tried to reset my user profile but again to no avail. I finally tried to disable Java, but here again the crashes continued. Opening Impress or Math Formula does not cause issues. I haven't tried with Draw, nor Base. Attached the crash report I found in /var/crash Any help would be welcome. In awaiting I rolled back to Ubuntu's depot, thus back to LibreOffice 6.4.6.2 (as I'm writing these lines). Thanks in advance & kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900445] Re: LibreOffice 7 Writer and Calc crash when creating new or opening documents
@Sebastien Bacher: Hi, thanks for the suggestion. I gave it a try and well, with a new user and a "clean" profile, no problem. LibreOffice works ok. So I decided to logon back to my user account and wiped out the .config/libreoffice folder completely, wiping out all my preferences... well to no avail, when I restarted back LibreOffice and tried to create a new Writer doc or Calc spreadsheet LibreOffice crashed again... So one step forward and again one step back. The good: the problem with LibreOffice does not come from installed software or broken dependency. The bad: I suppose the issue does not only reside in LibreOffice's user settings, but probably also from some interference of other configuration settings in my own user account. I'm a bit reluctant to wipe it completely out as it would cost me hours to get it back to my needs/liking... I've also attached the results of journalctl -b on both user accounts (1000 = me; 1001 = the new user): journal.1000.txt and journal.1001.txt -- 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/1900445 Title: LibreOffice 7 Writer and Calc crash when creating new or opening documents Status in libreoffice package in Ubuntu: New Bug description: I'm using LibreOffice under Ubuntu 20.04 LTS. I've always used LibreOffice PPA depot instead of Ubuntu's. Up to version 6.4, no issues. When 7.0 became available, LibreOffice got automatically upgraded. Since then, when ever I try to create a new Writer or Calc document or when I try to open such existing document, LibreOffice crashes immediately, then reopens and proposes to recover the document I tried to create/open. If I opt to recover, it crashes again. If I opt to discard, LibreOffice opens up but as soon as I try to either create new/open either a Writer or Calc document, it crashes again. I tried to open LibreOffice in safe-mode but to no avail, same behaviour. I also tried to reset my user profile but again to no avail. I finally tried to disable Java, but here again the crashes continued. Opening Impress or Math Formula does not cause issues. I haven't tried with Draw, nor Base. Attached the crash report I found in /var/crash Any help would be welcome. In awaiting I rolled back to Ubuntu's depot, thus back to LibreOffice 6.4.6.2 (as I'm writing these lines). Thanks in advance & kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900445] Re: LibreOffice 7 Writer and Calc crash when creating new or opening documents
cf. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/comments/6 ** Attachment added: "journalctl -b for user 1001 (new test user, libreoffice works ok)" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/+attachment/5429203/+files/journal.1001.txt -- 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/1900445 Title: LibreOffice 7 Writer and Calc crash when creating new or opening documents Status in libreoffice package in Ubuntu: New Bug description: I'm using LibreOffice under Ubuntu 20.04 LTS. I've always used LibreOffice PPA depot instead of Ubuntu's. Up to version 6.4, no issues. When 7.0 became available, LibreOffice got automatically upgraded. Since then, when ever I try to create a new Writer or Calc document or when I try to open such existing document, LibreOffice crashes immediately, then reopens and proposes to recover the document I tried to create/open. If I opt to recover, it crashes again. If I opt to discard, LibreOffice opens up but as soon as I try to either create new/open either a Writer or Calc document, it crashes again. I tried to open LibreOffice in safe-mode but to no avail, same behaviour. I also tried to reset my user profile but again to no avail. I finally tried to disable Java, but here again the crashes continued. Opening Impress or Math Formula does not cause issues. I haven't tried with Draw, nor Base. Attached the crash report I found in /var/crash Any help would be welcome. In awaiting I rolled back to Ubuntu's depot, thus back to LibreOffice 6.4.6.2 (as I'm writing these lines). Thanks in advance & kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
Olivier, since I wrote comment #26, I actually got it working and since then it seems to be reliable. What I did was: 1. Stopped Thunderbird, which had been running in safe mode. 2. sudo apt remove thunderbird-locale* 3. sudo apt install thunderbird-locale-en-gb 4. Start Thunderbird normally. I've since stopped and started it about 5 times normally, and all seems to work correctly. -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901318] Re: needs to depend on tcl (not just tcl8.6)
ALL distributions that I'm familiar with are adding a symlink "/usr/bin/tclsh" to whatever specific version of the shell is included when tcl is installed. Update: just checked, and the symlink "tclsh" is included with the current tcl package of Debian Sid as well as with the package of Debian Stretch. @cmeerw, can you try to re-install the tcl package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1901318 Title: needs to depend on tcl (not just tcl8.6) Status in usb-modeswitch package in Ubuntu: Fix Committed Bug description: * Impact the usb-modeswitch dispatcher script fails to start on the default installation because it uses tclsh unversioned while we depends on tcl8.6 * Test Case $ /usr/sbin/usb_modeswitch_dispatcher shouldn't bail out on an interpreter error (or better, test that plugging an usb modem is correctly handled) * Regression potential The script was bailing out due to a missing intepreter before so the code wasn't tested, it's possible that it triggers errors or could interact with the system in some way. The dispatcher reacts to udev events when an usb modem is connected, so try to use one of those and make sure that there is no negative effect (and if possible that the modem gets correctly handled) -- the package currently depends on tcl8.6, but /usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which isn't provided by tcl8.6, so it likely would need to depend on something like tcl (= 8.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
Alistair: in comment #26 you mention that you only had langpack-en- g...@thunderbird.mozilla.org.xpi in your profile directory. The extensions.json you attached in comment #25 also lists other extensions (not langpacks), I wonder whether one of them could be causing this. This would widen the scope of the problem. Can you make a backup copy of your profile folder, and then try removing the .xpi files under /home/alistair/.thunderbird/gh0m9rq4.default/extensions/ one by one, launching thunderbird in between each removal, and let us know if/when it eventually starts successfully. It would be very useful to identify precisely which extension is causing the problem. 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
If anyone is able to reproduce the problem, please before deleting the
local langpacks from the profile directory, check its timestamp:
find ~/.thunderbird -name langpack*@thunderbird.mozilla.org.xpi
-exec ls -l {} \;
and compare it against the date/time you first launched thunderbird
after upgrading to 20.10.
--
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/1901829
Title:
thunderbird fails to open, xml parse error
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
launching thunderbird opens a small browser window displaying the
following error:
XML Parsing Error: undefined entity
Location: chrome://messenger/content/messenger.xhtml
Line Number 905, Column 3:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
I cannot confirm that hypothesis: I created a thunderbird profile in a focal VM, and imported it in a groovy VM. The application ran fine in the groovy VM after the simulated upgrade, several times in a row, and I didn't observe langpack extensions being automatically downloaded and installed in the profile directory. -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
In my case it ran ok for several days, so I think it's most likely an update to the language packs extension themselves. El 29/10/20 a las 15:48, Olivier Tilloy escribió: > It sounds like something in the upgrade from thunderbird 68.X (in focal) > to version 78.Y (in groovy) is possibly making thunderbird automatically > download language pack updates from the extensions site, that shadow the > ones that are installed system-wide. This would happen the first time > thunderbird is run after the update, which explains why it runs okay > once and fails afterwards. > > This is just an hypothesis that needs to be confirmed. > -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900873] Re: dual display scaling broken at 4k
here are the requested files. ** Attachment added: "bug1900873.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+attachment/5429161/+files/bug1900873.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1900873 Title: dual display scaling broken at 4k Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have to 4k monitors. 15" on the dell xps 3840/2160/60 40" philips external BDM4065 3840/2160/30 Obviously i need different scale factors to use them properly. This feature DOES NOT WORK. It seems the scaling is not handled separately per monitor as the UI suggests. The fractional scaling also does not seem to work. any change to the scaling ends seems to be rounded to full. Which meens a compromise scale of 125% is effectively 200% on the large monitor. I havent found any config which would make this useful. So basically when I use the external 40" I cannot use the builtin anymore without an external fresnell magnifier lens (which I dont have ;) updated Ubuntu 20.04.1 LTS on DELL XPS 7590 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz 32GB SODIMM DDR4 Synchronous 2667 (0.4ns) PCI bridge: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] Hostbridge: Intel UHD Graphics 630 (Mobile) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 17:35:12 2020 InstallationDate: Installed on 2020-04-22 (181 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
It sounds like something in the upgrade from thunderbird 68.X (in focal) to version 78.Y (in groovy) is possibly making thunderbird automatically download language pack updates from the extensions site, that shadow the ones that are installed system-wide. This would happen the first time thunderbird is run after the update, which explains why it runs okay once and fails afterwards. This is just an hypothesis that needs to be confirmed. -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** No longer affects: openjdk-7 (Ubuntu) -- 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/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Fix Released Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in Visual Studio Code: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in mc package in Ubuntu: Confirmed Status in terminator package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in mc source package in Xenial: Confirmed Status in terminator source package in Xenial: Confirmed Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Won't Fix Status in openoffice package in Fedora: Won't Fix Bug description: Keyboard shortcuts are key combinations like Alt+F (usually opens the File menu) and Ctrl+O (usually opens the File→Open... dialog box). There is an issue with non-latin keyboard layouts that the keys under F or O (for Alt+F and Ctrl+O respectively) would correspond to some other character. What should happen then? There is some smart functionality (at least in the GTK+ library) that when we press a shortcut, it will try to make Alt+F or Ctrl+O work, even if the active keyboard layout is not English. For this smart functionality to work, it requires us to have as first keyboard layout the English (en) layout. Then, GTK+ will be able to check whether the shortcut makes sense for English, and if so, will run it. All that even if the active layout is Greek or Russian or something else. This report has over 300 comments and these comments include all sort of corner cases that indeed shortcuts do not work. In general, shortcuts work, but in specific cases there are issues that need to be fixed. What we need to do, is collect those corner cases and create new separate reports. Here are the corner cases: 1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, Russian), but they do not work for Super+A/F/M/C/V. Report: 2. Java GUI applications on Linux do not support shortcuts in non-latin languages. This is an issue with Java and should be reported there. Java GUI apps are not included in any of the Ubuntu ISOs. Report: 3. Shortcuts that use Ctrl on LibreOffice work for several languages (like Greek, Russian), but has been reported not to work on Hebrew. This should be a separate bug report specific to Hebrew and other languages affected in the same way. Report: To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
The problem was more with sssd than gnome. Not sure of the exact source of the problem with SSSD, but applying the following worked as a workaround : - Run `sudo systemctl edit sssd.service` and add the following: [Service] RuntimeMaxSec=1800 Restart=on-failure - Restart SSSD: $ sudo systemctl restart sssd.service This will restart sssd.service every 30 minutes unless you manually stop it, in which case it'll stay stopped until you manually start it again. -- 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/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop Status in gnome-settings-daemon package in Ubuntu: New Bug description: A Lenovo P53 is installed with ubuntu 18.04.5 LTS. Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also installed but not used for main display. Laptop is domain joined. When logging to the local ubuntu user, there is no problem detected. Then, if we log out and try to login with a domain user, gnome crashes. From what I can see in the logs, the user is authenticated correctly, but then in the instantiation of the session, gnome.shell.desktop faces an unrecoverable failure. From auth.log ``` pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=u...@na.cie.com Oct 23 16:27:28 WLLNXPFX gdm-password]: pam_unix(gdm-password:session): session opened for user u...@na.cie.com by (uid=0) Oct 23 16:27:28 WLLNXPFX systemd-logind[1200]: New session 17 of user u...@na.cie.com. ``` From syslog ``` Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: after 21 requests (21 known processed) with 0 events remaining. ``` I will include the full syslog and auth.log to this bug. Please let me know if any other log could be useful to troubleshoot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902108] [NEW] [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: Since I upgraded from Ubuntu 18.04 to 20.04 any sound is played. The audio output is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dario 9759 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:55:36 2020 InstallationDate: Installed on 2019-08-09 (446 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-10-15 (14 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8257 dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8257:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1LZ10EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902108 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 18.04 to 20.04 any sound is played. The audio output is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dario 9759 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:55:36 2020 InstallationDate: Installed on 2019-08-09 (446 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-10-15 (14 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8257 dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8257:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1LZ10EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899326] Re: after install nvidia-340, unable to login with white screen with logout button only
Sorry, but I don't understand anything of that. I'm just a computer user not a nerd. -- 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/1899326 Title: after install nvidia-340, unable to login with white screen with logout button only Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I just installed and updated Ubuntu 20.10. During installation of Nvidia proprietry driver, the following error message was appeared (Everythings were fine with Ubuntu 20.04) nvidia-340 (340.108-0ubuntu5) 설정하는 중입니다 ... dpkg: 오류: version '-' has bad syntax: revision number is empty dpkg: 오류: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Adding system user `nvidia-persistenced' (UID 122) ... Adding new group `nvidia-persistenced' (GID 130) ... Adding new user `nvidia-persistenced' (UID 122) with group `nvidia-persistenced' ... Not creating home directory `/'. Loading new nvidia-340-340.108 DKMS files... Building for 5.8.0-20-generic 5.8.0-21-generic Building for architecture x86_64 Building initial module for 5.8.0-20-generic ERROR (dkms apport): kernel package linux-headers-5.8.0-20-generic is not supported Error! Bad return status for module build on kernel: 5.8.0-20-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subprocess returned error exit status 10 Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for desktop-file-utils (0.24-1ubuntu4) ... Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-21-generic 처리하는데 오류가 발생했습니다: nvidia-340 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13 Uname: Linux 5.8.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 11 16:31:40 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ko_KR.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1899326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899326] Re: after install nvidia-340, unable to login with white screen with logout button only
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1899326 Title: after install nvidia-340, unable to login with white screen with logout button only Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I just installed and updated Ubuntu 20.10. During installation of Nvidia proprietry driver, the following error message was appeared (Everythings were fine with Ubuntu 20.04) nvidia-340 (340.108-0ubuntu5) 설정하는 중입니다 ... dpkg: 오류: version '-' has bad syntax: revision number is empty dpkg: 오류: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Adding system user `nvidia-persistenced' (UID 122) ... Adding new group `nvidia-persistenced' (GID 130) ... Adding new user `nvidia-persistenced' (UID 122) with group `nvidia-persistenced' ... Not creating home directory `/'. Loading new nvidia-340-340.108 DKMS files... Building for 5.8.0-20-generic 5.8.0-21-generic Building for architecture x86_64 Building initial module for 5.8.0-20-generic ERROR (dkms apport): kernel package linux-headers-5.8.0-20-generic is not supported Error! Bad return status for module build on kernel: 5.8.0-20-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subprocess returned error exit status 10 Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for desktop-file-utils (0.24-1ubuntu4) ... Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-21-generic 처리하는데 오류가 발생했습니다: nvidia-340 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13 Uname: Linux 5.8.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 11 16:31:40 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ko_KR.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1899326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
I did the upgrade today and also found that it worked the first time I
started it but crashed every time after that. I ran the following, which
fixed the problem.
sudo apt remove thunderbird-locale*
rm .thunderbird/{profile
name}/extensions/langpack-en...@thunderbird.mozilla.org.xpi
sudo apt install thunderbird-locale-en
--
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/1901829
Title:
thunderbird fails to open, xml parse error
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
launching thunderbird opens a small browser window displaying the
following error:
XML Parsing Error: undefined entity
Location: chrome://messenger/content/messenger.xhtml
Line Number 905, Column 3:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
The bug affects me, too. I just installed the three above mentioned mutter packages (libmutter-7-0 mutter mutter-common) and now Chromium is working again. Thanks for the fix! -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
Launchpad has imported 1 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1674150. 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 2020-10-29T15:27:06+00:00 Olivier Tilloy wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36 Steps to reproduce: It's been reported several times on https://forum.snapcraft.io/ that when invoked from an application packaged as a classic snap¹ to open a hyperlink, firefox installed as a deb package (on Debian/Ubuntu) opens with the wrong profile by default. This issue was investigated in https://launchpad.net/bugs/1835024, and we found out that the culprit is nsToolkitProfileService::IsSnapEnvironment()². To reproduce the issue, ensure that a firefox window is open, then from a terminal run `SNAP_NAME=foobar firefox http://example.org`. ¹ https://snapcraft.io/docs/snap-confinement ² https://hg.mozilla.org/mozilla-central/file/tip/toolkit/profile/nsToolkitProfileService.cpp#l1838 Actual results: This opens the requested URL (http://example.org) in a separate firefox window, with a different profile than that of the already open firefox window. Expected results: This should have opened the requested URL in a new tab in the same window that was already open. Reply at: https://bugs.launchpad.net/snapd/+bug/1835024/comments/21 ** Changed in: firefox Status: Unknown => New -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: New Status in snapd: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir
do you still see the issue? ** Changed in: fontconfig (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1875019 Title: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir Status in fontconfig package in Ubuntu: Incomplete Bug description: 1) apt-src install fontconfig 2) cd fontconfig-2.13.1/ 3) debuild -us -uc -b gets to PASS: test-hash PASS: test-bz106632 FAIL: run-test.sh fontconfig 2.13.1: test/test-suite.log # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: run-test == Running: Basic check Running: With a subdir Running: Subdir with a cache file Running: Complicated directory structure Running: Subdir with an out-of-date cache file Running: Dir with an out-of-date cache file Running: Re-creating .uuid Running: Consistency between .uuid and cache name b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7 Running: Keep mtime of the font directory Running: Basic functionality with the bind-mounted cache dir *** Test failed: Basic functionality with the bind-mounted cache dir cache was updated. FAIL run-test.sh (exit status: 1) ubuntu: focal 20.04 LTS fontconfig1: fontconfig: Installed: 2.13.1-2ubuntu3 Candidate: 2.13.1-2ubuntu3 Version table: *** 2.13.1-2ubuntu3 500 500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages 500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fontconfig 2.13.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 25 13:15:14 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1875019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902094] [NEW] High CPU usage while Sound Settings opened
Public bug reported: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:27:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824] InstallationDate: Installed on 2020-09-12 (47 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. G5 5587 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 03PVDF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0824 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 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.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance ubuntu ** Attachment added: "top screenshot" https://bugs.launchpad.net/bugs/1902094/+attachment/5429064/+files/Screenshot%20from%202020-10-29%2018-11-53.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902094 Title: High CPU usage while Sound Settings opened Status in xorg package in Ubuntu: New Bug description: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg
[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** No longer affects: openjdk-7 (Ubuntu Xenial) -- 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/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Fix Released Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in Visual Studio Code: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in mc package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in terminator package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in mc source package in Xenial: Confirmed Status in terminator source package in Xenial: Confirmed Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Won't Fix Status in openoffice package in Fedora: Won't Fix Bug description: Keyboard shortcuts are key combinations like Alt+F (usually opens the File menu) and Ctrl+O (usually opens the File→Open... dialog box). There is an issue with non-latin keyboard layouts that the keys under F or O (for Alt+F and Ctrl+O respectively) would correspond to some other character. What should happen then? There is some smart functionality (at least in the GTK+ library) that when we press a shortcut, it will try to make Alt+F or Ctrl+O work, even if the active keyboard layout is not English. For this smart functionality to work, it requires us to have as first keyboard layout the English (en) layout. Then, GTK+ will be able to check whether the shortcut makes sense for English, and if so, will run it. All that even if the active layout is Greek or Russian or something else. This report has over 300 comments and these comments include all sort of corner cases that indeed shortcuts do not work. In general, shortcuts work, but in specific cases there are issues that need to be fixed. What we need to do, is collect those corner cases and create new separate reports. Here are the corner cases: 1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, Russian), but they do not work for Super+A/F/M/C/V. Report: 2. Java GUI applications on Linux do not support shortcuts in non-latin languages. This is an issue with Java and should be reported there. Java GUI apps are not included in any of the Ubuntu ISOs. Report: 3. Shortcuts that use Ctrl on LibreOffice work for several languages (like Greek, Russian), but has been reported not to work on Hebrew. This should be a separate bug report specific to Hebrew and other languages affected in the same way. Report: To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
Good catch Séb! I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1674150 to track the bug upstream. ** Bug watch added: Mozilla Bugzilla #1674150 https://bugzilla.mozilla.org/show_bug.cgi?id=1674150 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1674150 Importance: Unknown Status: Unknown -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Unknown Status in snapd: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: snapd Status: Confirmed => Invalid -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Unknown Status in snapd: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902092] [NEW] No Yaru theme on libreoffice snap
Public bug reported: There is no yaru icon theme on new Libreoffice snap. Since is available on Ubuntu 20.10 maybe it should be available on snap version ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1902092 Title: No Yaru theme on libreoffice snap Status in libreoffice package in Ubuntu: New Bug description: There is no yaru icon theme on new Libreoffice snap. Since is available on Ubuntu 20.10 maybe it should be available on snap version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
That's a firefox issue, the problem is there https://sources.debian.org/src/firefox/82.0-1/toolkit/profile/nsToolkitProfileService.cpp/?hl=1840#L1823 The classic snap call the default browser from the system but from the snap environment that has SNAP_NAME defined or firefox has code to disable profiles in such cases... The issue is easy to trigger using the deb, just do 'SNAP_NAME=bug firefox https://www.ubuntu.com' ** Summary changed: - Links triggered within most snap apps open in a separate browser session + firefox fails to use the default profile from classic snaps ** Package changed: xdg-utils (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: firefox fails to use the default profile from classic snaps Status in snapd: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
*** This bug is a duplicate of bug 1835024 *** https://bugs.launchpad.net/bugs/1835024 ** This bug has been marked a duplicate of bug 1835024 Links triggered within most snap apps open in a separate browser session -- 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/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile Status in firefox package in Ubuntu: Invalid Bug description: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
Uninstalled, cleared out old folders, re-installed. Working fine now. -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
so, only a few language versions are not fine ... is it so? On Thu, 29 Oct 2020 at 19:46, J-Paul BERARD <1901...@bugs.launchpad.net> wrote: > It works for me : > Removed the french language pack add-on > Then install in a terminal : thunderbird-locale-fr (it said : already > installed) > Then start normally Thunderbird : it works and in french ! > > -- > You received this bug notification because you are a member of Ubuntu > Bugs, which is subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1901829 > > Title: > thunderbird fails to open, xml parse error > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions > > -- > ubuntu-bugs mailing list > ubuntu-b...@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
I do not have tracker-miner-fs.service at all. My instance of gvfsd is started by either ibus-daemon, or "systemd --user". Please see the controversy at https://gitlab.gnome.org/GNOME/gvfs/-/issues/481#note_948506 -- 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/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902088] [NEW] u8_totitle() fails to handle "." as a word separator
Public bug reported:
u8_totitle() fails to handle "." as a word separator, though the dot is
commonly used without any space-character where initials precede a surname.
for example, the street address "Largo A.Gemelli"is rendered "Largo A.gemelli"
I find it necessary to include the dot (.), comma (,), opening and
closing parentheses [(,)], hyphen (-), single and double quotes (',"),
and the forward slash (/) as word separators; but the dot (.) is the
most common, after the correctly-handled space ( ).
I have libunistring 0.9.10-2
under Ubuntu 20.04 LTS
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
apt-cache policy libunistring2
libunistring2:
Installed: 0.9.10-2
Candidate: 0.9.10-2
Version table:
*** 0.9.10-2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: libunistring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libunistring in Ubuntu.
https://bugs.launchpad.net/bugs/1902088
Title:
u8_totitle() fails to handle "." as a word separator
Status in libunistring package in Ubuntu:
New
Bug description:
u8_totitle() fails to handle "." as a word separator, though the dot is
commonly used without any space-character where initials precede a surname.
for example, the street address "Largo A.Gemelli"is rendered "Largo A.gemelli"
I find it necessary to include the dot (.), comma (,), opening and
closing parentheses [(,)], hyphen (-), single and double quotes (',"),
and the forward slash (/) as word separators; but the dot (.) is the
most common, after the correctly-handled space ( ).
I have libunistring 0.9.10-2
under Ubuntu 20.04 LTS
lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
apt-cache policy libunistring2
libunistring2:
Installed: 0.9.10-2
Candidate: 0.9.10-2
Version table:
*** 0.9.10-2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1902088/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902086] [NEW] xorg on Ubuntu 20.04 fails to show correctly background image and icons
Public bug reported: Hello I have PC with Xeon E processor and I am using integrated Intel graphics to drive a VGA display. I am using Ubuntu 20.04 Everything works fine. Then I add xorg.conf file, for other reasons, to /etc/X11 ( by default no xorg.conf file is present ) and I get the first screen after the log in is corrupted by yellow vertical lines and/or corrupted icons and eventually a block box is present at half height of the screen. See here below the incriminated xorg.conf : Section "ServerLayout" Identifier "layout" Screen 0 "intel" EndSection Section "Device" Identifier "intel" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection and photo of the corrupted screen is attached. If I open terminal or what else looks good but the first screen is always a bit corrupted. If I change the background image , the new background appears without vertical lines. If I go back to the original background image that is still corrupted with vertical lines. I am sure the corruption is because of the xorg.conf file but how can I fix the situation ? I need the xorg.conf file because I want xorg.conf to use only the internal integrated intel graphics and not other graphics cards/drivers that will be present. If I do exactly the same , adding the same xorg.conf file to on Ubuntu 18.04, same HW, same configuration, I don't see this problem. It happens only with Ubuntu 20.04. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 xorg ** Attachment added: "1yYZU.jpg" https://bugs.launchpad.net/bugs/1902086/+attachment/5429027/+files/1yYZU.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902086 Title: xorg on Ubuntu 20.04 fails to show correctly background image and icons Status in xorg package in Ubuntu: New Bug description: Hello I have PC with Xeon E processor and I am using integrated Intel graphics to drive a VGA display. I am using Ubuntu 20.04 Everything works fine. Then I add xorg.conf file, for other reasons, to /etc/X11 ( by default no xorg.conf file is present ) and I get the first screen after the log in is corrupted by yellow vertical lines and/or corrupted icons and eventually a block box is present at half height of the screen. See here below the incriminated xorg.conf : Section "ServerLayout" Identifier "layout" Screen 0 "intel" EndSection Section "Device" Identifier "intel" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection and photo of the corrupted screen is attached. If I open terminal or what else looks good but the first screen is always a bit corrupted. If I change the background image , the new background appears without vertical lines. If I go back to the original background image that is still corrupted with vertical lines. I am sure the corruption is because of the xorg.conf file but how can I fix the situation ? I need the xorg.conf file because I want xorg.conf to use only the internal integrated intel graphics and not other graphics cards/drivers that will be present. If I do exactly the same , adding the same xorg.conf file to on Ubuntu 18.04, same HW, same configuration, I don't see this problem. It happens only with Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902084] [NEW] package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: -Nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 14:45:19 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (241 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-29 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1902084 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: -Nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 14:45:19 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (241 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1902084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902085] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1902084 *** https://bugs.launchpad.net/bugs/1902084 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 #1902084, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1902084 package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1902085 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: -Nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 14:45:19 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (241 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1902085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900908] Re: Mutter doesn't apply gsettings appropriately to Wacom tablet on Xorg, but Wayland works
If this is the same problem I'm having (https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1901279) Then a workaround that works for me is to set the display with `xsetwacom` using coords or HEAD-1 (VGA-1 and DP-3 type identifiers aren't working) $ xsetwacom --set "Wacom Intuos Pro S Pen stylus" MapToOutput 1920x1080+0+0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1900908 Title: Mutter doesn't apply gsettings appropriately to Wacom tablet on Xorg, but Wayland works Status in Mutter: Unknown Status in Xf86 Input Wacom: New Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-input-wacom package in Ubuntu: Confirmed Bug description: I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop + external). Under an up-to-date Ubuntu Focal running X, if I map the tablet to a single monitor it fails to map it more often than not. A reliable way of getting failure is first connecting the tablet via bluetooth and then via USB. The only way to revert to a correct behavior is reseting X (ALT+F2 r). This is necessary even after rebooting. I've noticed that, when not working well, the problem is that Mutter sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while it should be sending them to "Wacom Intuos BT M Pad stylus" (this is what it does when it works well). Under Wayland it works well (well, the tablet buttons don't work under Wayland but this is unrelated). PS I reported this bug against the Wacom X driver but was told it's really related to mutter (https://github.com/linuxwacom/xf86-input- wacom/issues/148). To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1900908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
It works for me : Removed the french language pack add-on Then install in a terminal : thunderbird-locale-fr (it said : already installed) Then start normally Thunderbird : it works and in french ! -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902084] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1902084 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: -Nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 14:45:19 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (241 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1902084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
It looks like this is a known issue: https://forum.snapcraft.io/t /default-browser-not-used-from-within-snap/4347. -- 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/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile Status in firefox package in Ubuntu: Invalid Bug description: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902085] [NEW] package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1902084 *** https://bugs.launchpad.net/bugs/1902084 Public bug reported: -Nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 14:45:19 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (241 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-29 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1902085 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: -Nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 14:45:19 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (241 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1902085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1044549] Re: The "Access Prompt" randomly pop up!
Forgot: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748729 ** Bug watch added: Debian Bug tracker #734908 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908 ** Bug watch added: Debian Bug tracker #748729 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748729 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1044549 Title: The "Access Prompt" randomly pop up! Status in gcr package in Ubuntu: Triaged Bug description: Access Prompt randomly pop up and prompt you for the password. Have you ever when opened Youtube, Facebook, Launchpad account!n And now opened a picture of the computer when pop up"Access Prompt" I use autologin. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gcr 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Fri Aug 31 22:33:44 2012 ExecutablePath: /usr/lib/gcr/gcr-prompter InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) SourcePackage: gcr UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not provided by any .service files (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: assertion `G_IS_SETTINGS (settings)' failed (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed (gnome-control-center:2016): Gtk-CRITICAL **: gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901946] Re: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card
Timidity deinstalled. The sound is back. thanks, Daniel. You can close the ticket. -- 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/1901946 Title: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading distribution pulseaudio only sees dummy output and no input ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:16:37 2020 InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
if someone has a good contact at Slack, please reach out to them about this issue. -- 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/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile Status in firefox package in Ubuntu: Invalid Bug description: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
help for gnome-screenshot 3.38.0-1ubuntu1 says -b, --include-border Include the window border with the screenshot. This option is deprecated and window border is always included -B, --remove-borderRemove the window border from the screenshot. This option is deprecated and window border is always included -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Triaged Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
I'm reporting that it opens the wrong profile. I'm not sure how Slack does this but I'm guessing Oliver is right, they call it directly with -profile or something Marking invalid since this is a FF/Slack issue. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile Status in firefox package in Ubuntu: Invalid Bug description: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900686] Re: Missing files in tex-common caus updmap to fail
Thank you for your bug report but /etc/texmf/web2c/updmap.cfg isn't a file provided by Ubuntu https://packages.ubuntu.com/search?searchon=contents=updmap.cfg=exactfilename=focal=any it seems a local configuration issue? ** Changed in: tex-common (Ubuntu) Importance: Undecided => Low ** Changed in: tex-common (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1900686 Title: Missing files in tex-common caus updmap to fail Status in tex-common package in Ubuntu: Incomplete Bug description: -- updmap output begin -- updmap will read the following updmap.cfg files (in precedence order): /etc/texmf/web2c/updmap.cfg /usr/share/texmf/web2c/updmap.cfg /usr/share/texlive/texmf-dist/web2c/updmap.cfg updmap may write changes to the following updmap.cfg file: /etc/texmf/web2c/updmap.cfg dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap" pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap" dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap" updmap [ERROR]: The following map file(s) couldn't be found: updmap [ERROR]: fontname.map (in /etc/texmf/web2c/updmap.cfg) updmap [ERROR]: Did you run mktexlsr? You can disable non-existent map entries using the option --syncwithtrees. -- ipdmap output end -- It looks like the map files are missing. This happened after upgrading from 20.04 -> 20.10 This is the installation log: -- log begin -- Setting up tex-common (6.15) ... Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in -- log end -- (see snippet above) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: tex-common 6.15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 20 11:32:19 2020 InstallationDate: Installed on 2020-03-22 (211 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) PackageArchitecture: all SourcePackage: tex-common UpgradeStatus: Upgraded to groovy on 2020-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1900686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
this is just going in circles. i don't understand the details but it seems that: * it's quite ok to have a monospace filter built into the gnome-terminal font selector * this job is really delegated to the pango lib, which uses the first fc result to determine the spacing for the *whole* family * for the ubuntu font the first fc result isn't the regular type, which has the spacing property, but some other variant which doesn't have it last point hints at the urgency that this is fixed in the fonts themselves. it's a great pity one cannot enjoy the ubuntu font in the gnome-terminal in the latest ubuntu distros. -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Confirmed Bug description: trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873378] Re: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc()
The update works fine and there is no report for >= 1:3.36.4-0ubuntu2 on e.u.c, marking as verified ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873378 Title: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Bug description: * Impact The user panel hits a segfault sometimes * Test case Check that reports stop on https://errors.ubuntu.com/problem/af55dc0f4cb3abb5f2c5632d1195450e44db98ca * Regression potential The change is in the user panel's user initial avatar generation, check that the default image for profiles without an avatar is still generated --- Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Package version: 1:3.36.1-1ubuntu4 The application was running in the background, with only Chrome running at the same time. It's a mid-2014 MacBook Pro, so some drivers are not very stable and can cause this kind of issues. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 23:41:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-10 (250 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f303176e6e4:movzbl (%r14),%r15d PC (0x7f303176e6e4) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%r15d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 generate_default_avatar () ?? () ?? () Title: gnome-control-center crashed with SIGSEGV in g_utf8_normalize() UpgradeStatus: Upgraded to focal on 2020-04-09 (7 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887731] Re: gnome-control-center crashes in cc_display_config_manager_get_current -> get_valid_monitors -> get_dock_monitor -> update_dock_placement_combo_selection
The update works fine and there is no report for >= 1:3.36.4-0ubuntu2 on e.u.c, marking as verified ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887731 Title: gnome-control-center crashes in cc_display_config_manager_get_current -> get_valid_monitors -> get_dock_monitor -> update_dock_placement_combo_selection Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Committed Bug description: * Impact The appearance settings hit a segfault sometime * Test case The error reports should stop on https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 * Regression potential Check that that appearance settings still work correctly, including configuring on which screen the dock should be displayed The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.4-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887707] Re: Disabling fractional scaling after selecting another integer scaling may unselect user choice
The 1:3.36.4-0ubuntu2 update works as documented ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887707 Title: Disabling fractional scaling after selecting another integer scaling may unselect user choice Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: Fix Committed Bug description: [ Impact ] If selecting another integer scaling after disabling fractional scaling [ Test case ] When running Ubuntu session under X11, in gnome-control-center, display panel: - Ensure 100% scaling is selected and applied - Enable fractional scaling - Select 200% scaling (or bigger integer scaling) - Green "Apply" button should be visible and clickable - Deactivate fractional scaling - Green "Apply" button stays and fractional scaling isn't disabled until applied Repeat with inverted scaling orders (applying 200% and then selecting 100%) Currently, once another integer value is selected, we just deselect the user choice and restore the previous one, deactivating the fractional scaling promtply. [ Regression potential ] - Displays are wrongly disposed and configured when fractional scaling is enabled - Configurations are not applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
Unsubscribing field high as desktop isn't covered under the Field SLA. -- 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/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop Status in gnome-settings-daemon package in Ubuntu: New Bug description: A Lenovo P53 is installed with ubuntu 18.04.5 LTS. Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also installed but not used for main display. Laptop is domain joined. When logging to the local ubuntu user, there is no problem detected. Then, if we log out and try to login with a domain user, gnome crashes. From what I can see in the logs, the user is authenticated correctly, but then in the instantiation of the session, gnome.shell.desktop faces an unrecoverable failure. From auth.log ``` pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=u...@na.cie.com Oct 23 16:27:28 WLLNXPFX gdm-password]: pam_unix(gdm-password:session): session opened for user u...@na.cie.com by (uid=0) Oct 23 16:27:28 WLLNXPFX systemd-logind[1200]: New session 17 of user u...@na.cie.com. ``` From syslog ``` Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: after 21 requests (21 known processed) with 0 events remaining. ``` I will include the full syslog and auth.log to this bug. Please let me know if any other log could be useful to troubleshoot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
To challenge the worked before the upgrade theory, I upgraded yesterday and installed Thunderbird today. It worked the first time I ran it, for ten minutes, but then failed to start the second time with the message above. Safe mode also does not work, same error message. -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
Seeing as the issue was solved for two other people, I had another go -
this time explicitly installing all mutter-related packages from
-proposed (and not just 'mutter'):
$ aptitude upgrade libmutter-7-0 mutter mutter-common
Lo and behold, the socket showed up:
$ sudo ss -xlp | grep Xwayland
u_str LISTEN 0 1 @/tmp/.X11-unix/X0 60747* 0
users:(("Xwayland",pid=2371,fd=4))
u_str LISTEN 0 1 @/tmp/.X11-unix/X1 60749* 0
users:(("Xwayland",pid=2371,fd=7))
u_str LISTEN 0 1/tmp/.X11-unix/X0 60748* 0
users:(("Xwayland",pid=2371,fd=5))
and I can confirm that my graphical snaps all work again. I suspect that
in my first try, not all packages were upgraded. I'm not sure, but
perhaps that points at a dependency issue with the packages in
-proposed.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done-groovy
--
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/1897224
Title:
Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
Status in Mutter:
Unknown
Status in snapd:
In Progress
Status in mutter package in Ubuntu:
In Progress
Status in snapd package in Ubuntu:
Won't Fix
Status in mutter source package in Groovy:
Fix Committed
Status in snapd source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users who select the Wayland session on Ubuntu 20.10 cannot run snap
confined X11 applications, due to gnome-shell no longer listening on an
abstract socket for connections.
* The fix, which has been accepted into upstream's gnome-3-38 branch
reverts the change removing the abstract socket, and fixes the bug that
prompted it's removal:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508
[Test Case]
* Start with a stock Ubuntu 20.10 desktop install.
* At the GDM login screen, after selecting your user account use the gear
icon to select the "Ubuntu on Wayland" session, and log in.
* Ensure Chromium is installed by running "sudo snap install
chromium".
* Try to run "chromium" from the terminal. Without the fix, it will fail
with the error "Unable to open X display". With the fix applied, it
will launch as normal.
[Regression Potential]
* The patch modifies the logic gnome-shell uses to launch Xwayland. So
there is a potential that the change could break X11 application
support on the Wayland session.
* The default configuration for gnome-shell is to launch Xwayland on
session start, so it should be immediately obvious if there are
problems.
* In addition to checking snapped X11 apps like Chromium, verify that a
few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).
[Other Info]
* Running "ss -xlp | grep Xwayland" should show that it is listening on
both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
"@/tmp/.X11-unix/X0" (the abstract socket).
---
I'm trying to run chromium installed via snap in Ubuntu 20.10 when running
Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
> chromium
[49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to
open X display.
I am able to run Firefox just fine (assuming that Firefox still runs
on xwayland) and also Intellij snap works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 25 09:45:16 2020
InstallationDate: Installed on 2016-09-05 (1480 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
Snap: chromium 85.0.4183.121 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902051] [NEW] Remmina frozen and whole Ubuntu not responsive
Public bug reported: I am working with Remmina for years, but today when I was on Remote Desktop using Windows suddenly Remmina has frozen - mouse pointer disappeared and no keyboard response. In Remmina I have set (CTRL+R) to send all keyboard keystrokes to Remmina. I have had music listening in the background, so Ubuntu has not frozen. The only way I could solved the problem was to hard press laptop power button to force poweroff machine. Remmina is very important program to me, now when I am working from home. Hope there is something in log files that can be traced and fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 13:15:30 2020 InstallationDate: Installed on 2019-10-23 (372 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (75 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1902051 Title: Remmina frozen and whole Ubuntu not responsive Status in remmina package in Ubuntu: New Bug description: I am working with Remmina for years, but today when I was on Remote Desktop using Windows suddenly Remmina has frozen - mouse pointer disappeared and no keyboard response. In Remmina I have set (CTRL+R) to send all keyboard keystrokes to Remmina. I have had music listening in the background, so Ubuntu has not frozen. The only way I could solved the problem was to hard press laptop power button to force poweroff machine. Remmina is very important program to me, now when I am working from home. Hope there is something in log files that can be traced and fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 13:15:30 2020 InstallationDate: Installed on 2019-10-23 (372 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (75 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1902051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898905] Re: Unfunctional plustek scanner in Ubuntu 20.10
** Changed in: sane-backends (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1898905 Title: Unfunctional plustek scanner in Ubuntu 20.10 Status in sane-backends package in Ubuntu: Fix Committed Status in sane-backends package in Debian: Unknown Bug description: There are multiple reports now of failing plustek backend in libsane 1.0.31-2 as shipped in Ubuntu 20.10 and Debian dev My report: https://gitlab.com/sane-project/backends/-/issues/363 Another report: https://gitlab.com/sane-project/backends/-/issues/360 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I was running libmutter-7-0 3.38.1-1ubuntu1. I could reproduce the
initial bug of not being able to launch Chromium from the snap. After
upgrading to 3.38.1-2ubuntu1, now I can launch it fine.
Additionally, ss shows that Xwayland is listening on the abstract socket
too.
laney@nightingale> ss -xlp | grep Xwayland
u_str LISTEN 0 1/tmp/.X11-unix/X0 71964
* 0 users:(("Xwayland",pid=3713,fd=5))
u_str LISTEN 0 1 @/tmp/.X11-unix/X0 71963
* 0 users:(("Xwayland",pid=3713,fd=4))
u_str LISTEN 0 1 @/tmp/.X11-unix/X1 71965
* 0 users:(("Xwayland",pid=3713,fd=7))
--
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/1897224
Title:
Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
Status in Mutter:
Unknown
Status in snapd:
In Progress
Status in mutter package in Ubuntu:
In Progress
Status in snapd package in Ubuntu:
Won't Fix
Status in mutter source package in Groovy:
Fix Committed
Status in snapd source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users who select the Wayland session on Ubuntu 20.10 cannot run snap
confined X11 applications, due to gnome-shell no longer listening on an
abstract socket for connections.
* The fix, which has been accepted into upstream's gnome-3-38 branch
reverts the change removing the abstract socket, and fixes the bug that
prompted it's removal:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508
[Test Case]
* Start with a stock Ubuntu 20.10 desktop install.
* At the GDM login screen, after selecting your user account use the gear
icon to select the "Ubuntu on Wayland" session, and log in.
* Ensure Chromium is installed by running "sudo snap install
chromium".
* Try to run "chromium" from the terminal. Without the fix, it will fail
with the error "Unable to open X display". With the fix applied, it
will launch as normal.
[Regression Potential]
* The patch modifies the logic gnome-shell uses to launch Xwayland. So
there is a potential that the change could break X11 application
support on the Wayland session.
* The default configuration for gnome-shell is to launch Xwayland on
session start, so it should be immediately obvious if there are
problems.
* In addition to checking snapped X11 apps like Chromium, verify that a
few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).
[Other Info]
* Running "ss -xlp | grep Xwayland" should show that it is listening on
both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
"@/tmp/.X11-unix/X0" (the abstract socket).
---
I'm trying to run chromium installed via snap in Ubuntu 20.10 when running
Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
> chromium
[49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to
open X display.
I am able to run Firefox just fine (assuming that Firefox still runs
on xwayland) and also Intellij snap works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 25 09:45:16 2020
InstallationDate: Installed on 2016-09-05 (1480 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
Snap: chromium 85.0.4183.121 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902050] Re: package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 failed to install/upgrade: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-da
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1902050 Title: package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 failed to install/upgrade: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 Status in ghostscript package in Ubuntu: New Bug description: Errors were encountered while processing: /var/cache/apt/archives/libgs9-common_9.26~dfsg+0-0ubuntu0.16.04.13_all.deb /var/cache/apt/archives/ghostscript_9.26~dfsg+0-0ubuntu0.16.04.13_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CupsErrorLog: Date: Thu Oct 29 16:45:50 2020 Dependencies: DpkgHistoryLog: Start-Date: 2020-10-29 16:45:47 Commandline: apt-get -f install Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.12, 9.26~dfsg+0-0ubuntu0.16.04.13), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.11, 9.26~dfsg+0-0ubuntu0.16.04.13), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.16.04.12, 9.26~dfsg+0-0ubuntu0.16.04.13), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.11, 9.26~dfsg+0-0ubuntu0.16.04.13) DuplicateSignature: package:libgs9-common:9.26~dfsg+0-0ubuntu0.16.04.11 Unpacking ghostscript (9.26~dfsg+0-0ubuntu0.16.04.13) over (9.26~dfsg+0-0ubuntu0.16.04.11) ... dpkg: error processing archive /var/cache/apt/archives/ghostscript_9.26~dfsg+0-0ubuntu0.16.04.13_amd64.deb (--unpack): trying to overwrite '/var/lib/ghostscript/CMap', which is also in package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 ErrorMessage: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 InstallationDate: Installed on 2019-05-09 (539 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: HP HP ProBook 440 G5 PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-177-generic root=UUID=0f6ccab4-4c2f-4be0-8bb6-ecf86dcc64f5 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.29ubuntu0.1 SourcePackage: ghostscript Title: package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 failed to install/upgrade: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.06.00 dmi.board.name: 837B dmi.board.vendor: HP dmi.board.version: KBC Version 02.32.00 dmi.chassis.asset.tag: 5CD9156H04 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.06.00:bd01/03/2019:svnHP:pnHPProBook440G5:pvr:rvnHP:rn837B:rvrKBCVersion02.32.00:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G5 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1902050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902050] [NEW] package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 failed to install/upgrade: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-
Public bug reported: Errors were encountered while processing: /var/cache/apt/archives/libgs9-common_9.26~dfsg+0-0ubuntu0.16.04.13_all.deb /var/cache/apt/archives/ghostscript_9.26~dfsg+0-0ubuntu0.16.04.13_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CupsErrorLog: Date: Thu Oct 29 16:45:50 2020 Dependencies: DpkgHistoryLog: Start-Date: 2020-10-29 16:45:47 Commandline: apt-get -f install Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.12, 9.26~dfsg+0-0ubuntu0.16.04.13), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.11, 9.26~dfsg+0-0ubuntu0.16.04.13), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.16.04.12, 9.26~dfsg+0-0ubuntu0.16.04.13), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.11, 9.26~dfsg+0-0ubuntu0.16.04.13) DuplicateSignature: package:libgs9-common:9.26~dfsg+0-0ubuntu0.16.04.11 Unpacking ghostscript (9.26~dfsg+0-0ubuntu0.16.04.13) over (9.26~dfsg+0-0ubuntu0.16.04.11) ... dpkg: error processing archive /var/cache/apt/archives/ghostscript_9.26~dfsg+0-0ubuntu0.16.04.13_amd64.deb (--unpack): trying to overwrite '/var/lib/ghostscript/CMap', which is also in package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 ErrorMessage: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 InstallationDate: Installed on 2019-05-09 (539 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: HP HP ProBook 440 G5 PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-177-generic root=UUID=0f6ccab4-4c2f-4be0-8bb6-ecf86dcc64f5 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.29ubuntu0.1 SourcePackage: ghostscript Title: package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 failed to install/upgrade: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.06.00 dmi.board.name: 837B dmi.board.vendor: HP dmi.board.version: KBC Version 02.32.00 dmi.chassis.asset.tag: 5CD9156H04 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.06.00:bd01/03/2019:svnHP:pnHPProBook440G5:pvr:rvnHP:rn837B:rvrKBCVersion02.32.00:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G5 dmi.sys.vendor: HP ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1902050 Title: package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 failed to install/upgrade: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 Status in ghostscript package in Ubuntu: New Bug description: Errors were encountered while processing: /var/cache/apt/archives/libgs9-common_9.26~dfsg+0-0ubuntu0.16.04.13_all.deb /var/cache/apt/archives/ghostscript_9.26~dfsg+0-0ubuntu0.16.04.13_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CupsErrorLog: Date: Thu Oct 29 16:45:50 2020 Dependencies: DpkgHistoryLog: Start-Date: 2020-10-29 16:45:47 Commandline: apt-get -f install Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.16.04.12, 9.26~dfsg+0-0ubuntu0.16.04.13), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.16.04.11, 9.26~dfsg+0-0ubuntu0.16.04.13), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.16.04.12, 9.26~dfsg+0-0ubuntu0.16.04.13), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.16.04.11, 9.26~dfsg+0-0ubuntu0.16.04.13) DuplicateSignature: package:libgs9-common:9.26~dfsg+0-0ubuntu0.16.04.11 Unpacking ghostscript (9.26~dfsg+0-0ubuntu0.16.04.13) over (9.26~dfsg+0-0ubuntu0.16.04.11) ... dpkg: error processing archive /var/cache/apt/archives/ghostscript_9.26~dfsg+0-0ubuntu0.16.04.13_amd64.deb (--unpack): trying to overwrite '/var/lib/ghostscript/CMap', which is also in package libgs9-common 9.26~dfsg+0-0ubuntu0.16.04.11 ErrorMessage: trying to overwrite '/var/lib/ghostscript/CMap', which is also in package poppler-data 0.4.7-7 InstallationDate: Installed on 2019-05-09 (539 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial
[Desktop-packages] [Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
I wonder how slack requests opening links. Does it explicitly invoke the firefox binary with a "-profile" parameter, instead of calling e.g. xdg- open ? -- 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/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile Status in firefox package in Ubuntu: New Bug description: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
The upstream bug got reopened now, could you try disabling the tracker service and see if it resolves the issue for you? -- 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/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902044] [NEW] SRU the current 42.5 stable update
Public bug reported: * Impact That's the current stable update, including some fixes and translation updates https://gitlab.gnome.org/World/deja-dup/-/releases/42.5 The update should help with bug #1901340 and backup on removable drives * Test case Check that local and remote backups and restore are working. * Regression potential The update has some fixes for backup on removable and encrypted media so that's probably something to give some testing to ** Affects: deja-dup (Ubuntu) Importance: Low Status: Fix Released ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Low ** Changed in: deja-dup (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1902044 Title: SRU the current 42.5 stable update Status in deja-dup package in Ubuntu: Fix Released Bug description: * Impact That's the current stable update, including some fixes and translation updates https://gitlab.gnome.org/World/deja-dup/-/releases/42.5 The update should help with bug #1901340 and backup on removable drives * Test case Check that local and remote backups and restore are working. * Regression potential The update has some fixes for backup on removable and encrypted media so that's probably something to give some testing to To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1902044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1901808] Re: Laptop displays has lags and tearing
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 Can i close bug. It was mistake. i just switch driver from intel to modesetting. it worked great. ср, 28 окт. 2020 г., 13:11 Daniel van Vugt <1901...@bugs.launchpad.net>: > *** This bug is a duplicate of bug 1853094 *** > https://bugs.launchpad.net/bugs/1853094 > > If you are using the modeset driver and have HDMI connected and that > HDMI port is connected to the Intel GPU then this is bug 1853094. If you > are using the old intel driver you can avoid that by using 'TearFree' > but your XorgLogOld.txt shows TearFree was still disabled. > > If you experience tearing in fullscreen windows on the laptop screen, > then this is bug 1754284. > > If you experience tearing in accelerated windows powered by the Nvidia > GPU then this is bug 1881909. > > It's unclear which of those bugs this is, but it seems likely it's > already covered by those. > > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > ** This bug has been marked a duplicate of bug 1853094 >[modeset] Screen tearing when using multiple monitors > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1901808 > > Title: > Laptop displays has lags and tearing > > Status in xorg-server package in Ubuntu: > New > > Bug description: > I have laptop dell with intel i5-4100U, intel hd 4400 and geforce 820m > on board. > I added zotac gtx 960 and one monitor via rizer. > gtx and monitor worked correctly. > but laptop displays has lags and tearing. > I tried install > i915 > i965-va-drivers > > > intel config section > Section "Device" > Identifier "Device1" > Driver "intel" > VendorName "Intel Corporation" > Option "TearFree" "true" > Option "DRI" "2" > EndSection > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 > Uname: Linux 5.4.0-52-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/capabilities/gpu0' > .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/capabilities/mig' > .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:06: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 455.32.00 Wed Oct 14 > 22:46:18 UTC 2020 >GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) > ApportVersion: 2.20.11-0ubuntu27.10 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: Deepin > Date: Wed Oct 28 11:03:01 2020 > DistUpgraded: 2020-08-20 21:43:47,424 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: No > GraphicsCard: >Intel Corporation Haswell-ULT Integrated Graphics Controller > [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) > Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652] >NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] > [19da:2378] > Subsystem: Dell GeForce 820M [1028:0652] > InstallationDate: Installed on 2020-07-16 (103 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > MachineType: Dell Inc. Inspiron 3542 > ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic > root=UUID=ab9e3a31-2ad4-4c5f-a786-92ff7dbde56d ro rootflags=subvol=@ > nouveau.modeset=0 DEEPIN_GFXMODE= crashkernel=512M-:192M > SourcePackage: xorg > UpgradeStatus: Upgraded to focal on 2020-08-20 (68 days ago) > dmi.bios.date: 03/28/2014 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A01 > dmi.board.name: 0926J6 > dmi.board.vendor: Dell Inc. > dmi.board.version: A01 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: Not Specified > dmi.modalias: > dmi:bvnDellInc.:bvrA01:bd03/28/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: > dmi.product.name: Inspiron 3542 > dmi.product.sku: 0652 > dmi.product.version: Not Specified > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx:
[Desktop-packages] [Bug 543183] Re: Updating system certificates requires rebuild
What is the status of the error at the moment? In Fedora 31/32 add sefl-
signed cert to system store allow Firefox to trust self-signed cert on
sites.
I use Ubuntu 18.04 in my enterprise and it's big problem, that I can not
add self-signed root cert in computers. Our users use different
browsers, different workplace. And when user first login on computer, he
must add self-signed cert to a browser.
--
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/543183
Title:
Updating system certificates requires rebuild
Status in Mozilla Firefox:
Won't Fix
Status in firefox package in Ubuntu:
Triaged
Status in firefox package in Fedora:
Won't Fix
Bug description:
Binary package hint: firefox
Hi,
Updating the list of trusted root certificate authorities across all users of
a system seems requires rebuilding a library. Non-root certificates may
similarly be impacted.
update-ca-certificates could be a mechanism to update the root
certificates used by firefox.
On a corporate install of firefox, currently the only options to adding an
internal root certificate authority are to:
* Hack it into the user creation script to extract a pre-created profile,
and update all the existing users profile directory. This bypasses the random
profile directory creation.
* Re-compile the shared library (.so) containing the root certificate
authorities (extra maintenance for dealing with ubuntu package updates).
* Have every user of the system go through a manual process of adding the
root certificate (most users don't know how).
* Use a plugin extension for firefox (do any exist?) that is automatically
used by all users (can this be done?)
* Have the root certificate signed at great expense by an external root
certificate authority already included. CaCert integration would lower the cost
but that seems far away, and is still an external authority. These root
certificates also might be limited to a single domain (wildcard certificate?)
or have other limitations ("low" expiry?, contractual restrictions...).
It seems unlikely that Mozilla will move away from having the root
certificates stored in the shared library as it would take some
control away from them. The shared libary method makes it harder for
malicious changes to be made, but only by adding the barier of
recompilation and installation of a shared library.
Thanks,
Drew Daniels
Resume: http://www.boxheap.net/ddaniels/resume.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/543183/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899025] Re: snap translations issue during 1st launch after update
Ok I found how to recover these snap-native langpacks. Config editor, search "lang" and reset the adequate values, see attachment. If I do that, the version is up-to-date and I still get "Inbox" not translated at first launch after langpack activation. Maybe a TB related bug, not snap. Are Groovy TB 78 users seeing the same issue? ** Attachment added: "Capture d’écran de 2020-10-29 11-12-48.png" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899025/+attachment/5428939/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-10-29%2011-12-48.png -- 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/1899025 Title: snap translations issue during 1st launch after update Status in thunderbird package in Ubuntu: New Bug description: When I updated today from 78.3.1 to 78.3.2, after the first launch of the updated 78.3.2, I got some untranslated strings (Inbox in mailboxes folder list, e.g.). After the 2nd launch, all became normal. AFAICR, it was the case during previous updates too. Not a big deal, though... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899025] Re: snap translations issue during 1st launch after update
Yes initially langpacks were listed in extensions list. I removed some of them (in TB UI), somewhat looks strange to me I could do that since they are bundled. Well, I obviously, until yesterday, kept snap-native FR langpack. The version displayed in TB UI of this langpack did not match the latest available version (present in /snap/thunderbird xpi bundled file). No update was displayed when I manually did update my addons through normal TB UI. So I now have uninstalled the snap-native FR langpack, installed the TB addon from TB addons website. I'll see if I experience any first launch issue when 78.4.1 will be available. Please note that I actually don't know how to recover all the snap- native langpacks since I have deleted them through TB UI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1899025 Title: snap translations issue during 1st launch after update Status in thunderbird package in Ubuntu: New Bug description: When I updated today from 78.3.1 to 78.3.2, after the first launch of the updated 78.3.2, I got some untranslated strings (Inbox in mailboxes folder list, e.g.). After the 2nd launch, all became normal. AFAICR, it was the case during previous updates too. Not a big deal, though... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
Thank you for your bug report, is slack explicitly asking for the profile 'default'? Or are you just reporting that it opens the wrong profile? The profile naming changed recently upstream, see https://support.mozilla.org/gl/questions/1264072 If the issue is the wrong profile it sounds similar to bug #1835024 -- 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/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile Status in firefox package in Ubuntu: New Bug description: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902018] Re: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version
Thank you for your bug report, could you take a photo showing the issue and add the 'journalctl -b 0' log after triggering the problem? ** Package changed: gnome-control-center (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1902018 Title: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version Status in gdm3 package in Ubuntu: New Bug description: OS: Ubuntu 20.10 version Test sequence: Fingeprint is enrolled Win+L: At login screen, earlier in 20.04 version, it used to display "scan your finger", it is not displayed in 20.10 version, but fingerprint identify is working fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-09-29 (29 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-control-center 1:3.38.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-27 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1902018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901908] Re: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1901908 Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume keys of my keyboard not working since the last ubuntu update release. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lumantar 3208 F pulseaudio /dev/snd/controlC0: lumantar 3208 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 10:01:27 2020 InstallationDate: Installed on 2018-09-14 (775 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: oct 28 09:15:18 lumantar dbus-daemon[776]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=120 pid=1243 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") oct 28 09:15:23 lumantar pulseaudio[1243]: No UCM verb is valid for hw:0 oct 28 09:15:26 lumantar pulseaudio[1243]: No UCM verb is valid for hw:2 oct 28 09:19:41 lumantar systemd[1199]: pulseaudio.service: Succeeded. oct 28 09:19:51 lumantar systemd[1199]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-21 (7 days ago) dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN31WW:bd04/20/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
