[Desktop-packages] [Bug 1866222] Re: GNOME Shell crashed with signal 11
Stéphane, please subscribe to bug 1866368 for your issue. Based on the information in comment #8. -- 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/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744544] Re: I don't know
Please describe the kind of problem you are, or were, experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1744544 Title: I don't know Status in Ubuntu: Incomplete Bug description: I don't know ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 21 11:06:23 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GTX 660M] [17aa:3977] InstallationDate: Installed on 2017-08-05 (168 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2099 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=13938ffd-9af8-467d-bb58-79084d5812e4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5DCN40WW(V2.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Product Name dmi.board.vendor: LENOVO dmi.board.version: Mainboard version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y580 dmi.modalias: dmi:bvnLENOVO:bvr5DCN40WW(V2.07):bd10/10/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadY580: dmi.product.family: IDEAPAD dmi.product.name: 2099 dmi.product.version: Lenovo IdeaPad Y580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jan 21 10:54:21 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1744544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752239] Re: Xorg crash
[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/1752239 Title: Xorg crash Status in xorg-server package in Ubuntu: Expired Bug description: lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Feb 28 12:42:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated Graphics Controller [1025:0926] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 860M] [1025:0926] InstallationDate: Installed on 2017-03-04 (361 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Acer Aspire VN7-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=0ae70f36-4706-49d1-af92-2bff72c1bae9 ro i8042.reset quiet splash acpi_backlight=vendor vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-591G dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd08/06/2015:svnAcer:pnAspireVN7-591G:pvrV1.15:rvnAcer:rnAspireVN7-591G:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.family: HSW dmi.product.name: Aspire VN7-591G dmi.product.version: V1.15 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 28 12:37:38 2018 xserver.configfile: default xserver.errors: Failed to load module "intel" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1752239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860244] Re: Gdm3 - infinite login
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1860244 Title: Gdm3 - infinite login Status in gdm3 package in Ubuntu: Expired Bug description: This is a strange issue that only appeared to happen after a failed resume from suspend state. Now each time I log in the is a flash of activity and I'm presented with the login screen again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 19 10:54:08 2020 InstallationDate: Installed on 2018-05-06 (622 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-10-27 (83 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-01-19T10:19:08.087127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1860244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860115] Re: normal usage then all apps stopped working
[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/1860115 Title: normal usage then all apps stopped working Status in gnome-shell package in Ubuntu: Expired Bug description: I was browsing on chrome and firefox then I saw chrome extensions crashed then firefox crashed then 2 other background apps crashed desktop still functioned I ran apport-bug gnome-shell and now I'm here. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 13:48:11 2020 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1607 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868155] Re: Banner text and user list functionality seem broken
I'm not familiar with this feature but do know the GUI is provided by the gnome-shell process so the bug should be reported there. Please report the issue upstream at: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new bug ID. ** 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/1868155 Title: Banner text and user list functionality seem broken Status in gnome-shell package in Ubuntu: New Bug description: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 14:33:30 2020 InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted
** This bug is no longer a duplicate of bug 1310121 headphones working while speakers not working ** Summary changed: - Integrated speakers always muted + [Toshiba NB250] Integrated speakers always muted -- 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/1868131 Title: [Toshiba NB250] Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868128] Re: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in Ubuntu: Incomplete Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868128] Re: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Firstly, not related to this bug but I notice your system will be running very slow because it's logging every single screen refresh to the kernel log. To stop that you should remove the kernel parameter: drm.debug=0xe -- 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/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in Ubuntu: Incomplete Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868083] Re: gnome-shell process "estabilished"
For some of us we may just need: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1100 and don't necessarily need to wait for: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1099 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - gnome-shell process "estabilished" + gnome-shell establishes https connections to extensions.gnome.org ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1868083 Title: gnome-shell establishes https connections to extensions.gnome.org Status in gnome-shell package in Ubuntu: Triaged Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867758] Re: Gnome shell froze completely
If a crash has been uploaded then please tell us the resulting new bug ID. If you don't know it then try uploading using something like this command: apport-cli YOURFILE.crash And if that doesn't work then please delete /var/crash/* and wait for it to happen again. -- 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/1867758 Title: Gnome shell froze completely Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome shell froze completely and would not respond to any mouse clicks or keyboard action. The mouse did move, but that's about it. It stayed this way for ~15mins before I reset it and lost all my work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 11:51:50 2020 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1126 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
Error report links are public unless you feel something particularly
personal has been shown on that page. So please paste the link here. And
if you prefer you can change this bug page to Private using the setting
at the top right of this page.
--
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/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
The kernel 5.3.0-43 is in the -proposed, please use this kernel instead of -42 kernel. -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860425] Re: Manually installed deb package cannot be uninstalled
Upstream gnome-software issue: https://gitlab.gnome.org/GNOME/gnome- software/issues/912 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #912 https://gitlab.gnome.org/GNOME/gnome-software/issues/912 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1860425 Title: Manually installed deb package cannot be uninstalled Status in snap-store: New Status in gnome-software package in Ubuntu: New Bug description: This happens on the latest GNOME Software 3.34.2 on Ubuntu Focal. Manually installed deb package (that does not contain any AppData), for example Steam from Valve (https://store.steampowered.com/about/), cannot be uninstalled using Ubuntu Software. The manually installed package appears under Add-ons section on the Installed tab, but it is gone after Ubuntu Software is restarted. When right clicking the Steam icon in GNOME Shell Overview mode and selecting "Show Details", details page with Ubuntu repository version of steam-launcher is displayed instead. The only way to remove the deb package using GUI is downloading it again, clicking "Install", then clicking "Remove" before closing the app details page. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1860425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal
Also seems to happen in Snap Store. ** Also affects: snap-store Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in snap-store: New Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1864307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1865536 Title: OBS consumes all memory, fixed in upstream Mesa Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1865536 Title: OBS consumes all memory, fixed in upstream Mesa Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867970] Re: Gnome WiFi Settings Freeze
Reported upstream at: https://gitlab.gnome.org/GNOME/gnome-control- center/issues/928 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #928 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/928 -- 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/1867970 Title: Gnome WiFi Settings Freeze Status in gnome-control-center package in Ubuntu: New Bug description: 1) Release: Ubuntu 19.10 2) Package Version: gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status 3) Expected Behavior: Open WiFi Settings then back out to full Gnome Settings and browse normally. 4) Actual Behavior: (Video Attached) Wifi Settings Banner freezes and flashes along with window management buttons in the top right. Freezing and flashing occurs when Wifi settings are opened directly or when they are accessed from the rest of the Gnome Settings. Because Wifi is the first menu option, freezing occurs when Settings is selected and Gnome Control Center is opened directly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 12:39:02 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-16 (214 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-20 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868083] Re: gnome-shell process "estabilished"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: Confirmed Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867970] Re: Gnome WiFi Settings Freeze
Thank you for your bug report, could you report the issue upstream as well on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ? ** 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/1867970 Title: Gnome WiFi Settings Freeze Status in gnome-control-center package in Ubuntu: New Bug description: 1) Release: Ubuntu 19.10 2) Package Version: gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status 3) Expected Behavior: Open WiFi Settings then back out to full Gnome Settings and browse normally. 4) Actual Behavior: (Video Attached) Wifi Settings Banner freezes and flashes along with window management buttons in the top right. Freezing and flashing occurs when Wifi settings are opened directly or when they are accessed from the rest of the Gnome Settings. Because Wifi is the first menu option, freezing occurs when Settings is selected and Gnome Control Center is opened directly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 12:39:02 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-16 (214 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-20 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
you also made your opinion clear on the other bug, the place to argue/contribute to that discussion is upstream, the Ubuntu team doesn't have the resources nor plan to invest engineering going against upstream choices there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Won't Fix Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
sorry but I'm not going to deal with bugs not respecting the code of conducts, also that bug is a duplicate as you knew when opening it, the fact that the issue has been wontfixed is not a reason to create extra work for others by registered a new ticket ** Changed in: nautilus (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Won't Fix Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868179] [NEW] Typing in virtualbox during installation does not work
Public bug reported: I tried to install Ubuntu 19.10, 20.04 and 18.04.4LTS in virtualbox 6.1 on MacOS Catalina. The installating packages starts, the mouse works, so I can navigate all the way through to the user account creation screen. However, I cannot input anything using the keyboard. I can drag the dialogue text into the text fields but not delete/add by typing into the field. All keyboard input is ignored. I use the standards laptop keyboard of the mac which otherwise works fine. Since it fails in all versions specified above it is likely to be related to the combination of VirtualBox, MacOS and the ubuntu installe package. ** Affects: virtualbox Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** No longer affects: alsa-driver (Ubuntu) ** Package changed: ubiquity (Ubuntu) => virtualbox ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- 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/1868179 Title: Typing in virtualbox during installation does not work Status in Virtualbox: New Status in ubiquity package in Ubuntu: New Bug description: I tried to install Ubuntu 19.10, 20.04 and 18.04.4LTS in virtualbox 6.1 on MacOS Catalina. The installating packages starts, the mouse works, so I can navigate all the way through to the user account creation screen. However, I cannot input anything using the keyboard. I can drag the dialogue text into the text fields but not delete/add by typing into the field. All keyboard input is ignored. I use the standards laptop keyboard of the mac which otherwise works fine. Since it fails in all versions specified above it is likely to be related to the combination of VirtualBox, MacOS and the ubuntu installe package. To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1868179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
There is an error report link, how should that be communicated?
--
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/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868083] Re: gnome-shell process "estabilished"
Seems like they eventually want to add one on/off control over checking for these updates? I hope so and thank you for taking the time on this. -- 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/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: New Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860425] Re: Manually installed deb package cannot be uninstalled
I have also added snap-store to this ticket, but it seems that deb packages cannot be opened in Snap Store (see #1867610). However, when installing a deb package manually using apt or non-Snap gnome-software, the same issue happens as with non-Snap gnome-software: The package is not displayed on the "Installed" tab of Snap Store. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1860425 Title: Manually installed deb package cannot be uninstalled Status in snap-store: New Status in gnome-software package in Ubuntu: New Bug description: This happens on the latest GNOME Software 3.34.2 on Ubuntu Focal. Manually installed deb package (that does not contain any AppData), for example Steam from Valve (https://store.steampowered.com/about/), cannot be uninstalled using Ubuntu Software. The manually installed package appears under Add-ons section on the Installed tab, but it is gone after Ubuntu Software is restarted. When right clicking the Steam icon in GNOME Shell Overview mode and selecting "Show Details", details page with Ubuntu repository version of steam-launcher is displayed instead. The only way to remove the deb package using GUI is downloading it again, clicking "Install", then clicking "Remove" before closing the app details page. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1860425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694367] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1694367 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1694367 Title: Screen tearing in 16.10 onwards Status in Mesa: Unknown Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: In 16.10 onwards my laptop has always shown screen tearing globally, additionally GL applications will not v-sync despite attempting to, they appear to sync slightly off from the [integrated] display. This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not entirely sure if it's a bug with either or a default miss- configuration in ubuntu... ubuntu-bug also appears to be broken... To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1694367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
* wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Confirmed Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
Correction for the patch, please use this one. ** Patch added: "69-libmtp.rules.patch" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339060/+files/69-libmtp.rules.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
Ok, however, that's not a reason for marking this as "opinion". The issue had already been addressed so there's no question that the behavior is wrong and has to be fixed. That debate has been settled ages ago. Also the importance shouldn't be "whichlist". This makes Nautilus unusable. ** Changed in: nautilus (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Confirmed Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1694367 Title: Screen tearing in 16.10 onwards Status in Mesa: Unknown Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: In 16.10 onwards my laptop has always shown screen tearing globally, additionally GL applications will not v-sync despite attempting to, they appear to sync slightly off from the [integrated] display. This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not entirely sure if it's a bug with either or a default miss- configuration in ubuntu... ubuntu-bug also appears to be broken... To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1694367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868083] Re: gnome-shell process "estabilished"
Looks like gnome-shell is checking for updates to extensions on startup. https://gitlab.gnome.org/GNOME/gnome- shell/commit/db9ef11f2893eae0905b091be361ff5417156beb?merge_request_iid=945 There is an upstream PR to add an option to turn this behavior off. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1099 -- 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/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: New Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
Thank you for your bug report. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about- ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Wishlist ** Changed in: nautilus (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Opinion Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
The attached patch would fix this bug. It adds two rules to skip printers. The second skips all kinds of printers by checking whether the standard interface of a printer is present in the USB device. The first skips HP printers, it is the same rule as HPLIP uses. I have added it because it covers a second interface, which is probably of some weird proprietary HP printer devices. For my printer the bug goes away with this patch, also with any one of the two rules commented out. I think one can assume that there is no printer available which doubles as a media player. ** Patch added: "69-libmtp.rules.patch" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339056/+files/69-libmtp.rules.patch ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
There was already a measure against wrongly identifying HP printers as media players, but it is a rather dirty workaround which does not work any more (therefore this bug). The rule in the end of 69-libmtp.rules checks the absence of the env variable libsane_matched and this variable is set for all HP printers by HPLIP. First, this rule fails miserably if HPLIP is not installed, and I cannot imagine that the libmtp package depends on HPLIP only to identify unsupported devices. Also the libmtp rules are applied for both "add" and "bind" actions, whereas the rules of HPLIP (56-hpmud.rules) are only applied for "add" and so the bug happens on a "bind" action, here the HPLIP rules do not set said env variable and so the libmtp rules probe the HP printers. One can theoretically work around this problem by mucking with the UDEV rules of HPLIP, but this is a REALLY DIRTY workaround, so please DO NOT add an hplip task to this bug report. In addition, HPLIP will not be installed by default any more in the not too far future, as prnting and scanning will get snapped. Also we want printer driver Snaps (Printer Applications) not to run as root if possible, so we need to be sure that USB printer device files always belong to the group "lp" for all printer manufacturers and without HPLIP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867529] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) with PCA
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867529
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) with PCA
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
New
Bug description:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/86/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867529/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867444] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) using PCA backend
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867444
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) using PCA backend
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
New
Bug description:
Sorry but after last fix, I have another error.
I am using duplicity 0.8.11.1606 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200314T160021Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(source_path.name))
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/84/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867444/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867435] Re: TypeError: must be str, not bytes using PCA backend
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1867435 Title: TypeError: must be str, not bytes using PCA backend Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: New Bug description: I am using duplicity 0.8.11.1604 from snap edge channel. I am trying to use multi backend with one of them being the OVH PCA. It fails when trying to write to the PCA with the following error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200314T135032Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backends/pcabackend.py", line 153, in _put self.conn.put_object(self.container, self.prefix + remote_filename, TypeError: must be str, not bytes To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1867435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867742] Re: TypeError: fsdecode() takes 1 positional argument but 2 were given with PCA backend
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1867742 Title: TypeError: fsdecode() takes 1 positional argument but 2 were given with PCA backend Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: New Bug description: I am using 0.8.11-0ubuntu1ppa1609~ubuntu18.04.1 package and trying to use PCA backend. Here is the error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200317T082259Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/usr/lib/python3/dist-packages/duplicity/backends/pcabackend.py", line 154, in _put open(util.fsdecode(source_path.name, u'rb'))) TypeError: fsdecode() takes 1 positional argument but 2 were given To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1867742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867955] Re: My entire DE flashes when trying to install an app and the application doesn't install
log attached ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867955/+attachment/5339030/+files/log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867955 Title: My entire DE flashes when trying to install an app and the application doesn't install Status in gnome-software package in Ubuntu: Incomplete Bug description: When I try to install an app both with gnome-software and snap-store my DE flashes and it doesn't install anything. tried both with snap and deb. At at least we deb a got an error message "Permission denied" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 18:48:22 2020 InstallationDate: Installed on 2019-12-24 (85 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InstalledPlugins: gnome-software-plugin-flatpak 3.35.91-0ubuntu1 gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-03-15 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867955] Re: My entire DE flashes when trying to install an app and the application doesn't install
It was related to gnome shell;I had opened another issue or gnome-shell (#1867735) and the workaround was to enable animation and it seems to have solved the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867955 Title: My entire DE flashes when trying to install an app and the application doesn't install Status in gnome-software package in Ubuntu: Incomplete Bug description: When I try to install an app both with gnome-software and snap-store my DE flashes and it doesn't install anything. tried both with snap and deb. At at least we deb a got an error message "Permission denied" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 18:48:22 2020 InstallationDate: Installed on 2019-12-24 (85 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InstalledPlugins: gnome-software-plugin-flatpak 3.35.91-0ubuntu1 gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-03-15 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 Increasing the headphones volume in alsamixer, speakers start to sound. If I plug the headphones, it works. When unplug the headphones, alsamixer Headphones volume goes to zero and it affects speaker, because headphones volume in alsamixer control both speaker and headphones. ** Attachment added: "With volume un Headphone section in alsamixer thre're sound" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339031/+files/sound.png -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 Just after boot, no sound. It can't be activated using pavucontrol. Only with alsamixer. ** Attachment added: "State of alsamixer and pavucontrol on boot" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339029/+files/boot.png -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868162] [NEW] snap chromium does not respect the dpi setting of xfce
Public bug reported:
on a 4k monitor the default 96dpi setting is typically too small to work
with. setting it to eg 120dpi the guis become more readable.
unfortunately, chromium browser from the snap package on ubuntu 19.04
does still comes with ultra tiny font for the url text window.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CurrentDesktop: XFCE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd3LF0AAAwdAQS1PCJ4nj4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QA4PR6HOAAKICAgICAg/ABMRyBIRFIgNEsKICAgAdoCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1600x900
1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480
720x480 640x480 640x480 640x480
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
Date: Thu Mar 19 20:06:13 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 149G 18G 123G 13% /
tmpfs tmpfs 3.9G 157M 3.7G 4% /dev/shm
/dev/sda2 ext4 149G 18G 123G 13% /
InstallationDate: Installed on 2020-03-18 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. CML-U PRO Cubi 5 (MS-B183)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic
root=UUID=55264ebb-0214-408c-9b11-5009818e9ad4 ro pti=off spectre_v2=off
l1tf=off nospec_store_bypass_disable no_stf_barrier quiet
Snap.Changes:
ID Status Spawn Ready Summary
3Done2020-03-18T21:46:44+01:00 2020-03-18T21:47:20+01:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.132
(fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974})
Snap.ChromiumVersion:
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Chromium 80.0.3987.132 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8.20
dmi.board.asset.tag: Default string
dmi.board.name: MS-B1831
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8.20:bd11/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnCML-UPROCubi5(MS-B183):pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-B1831:rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Desktop
dmi.product.name: CML-U PRO Cubi 5 (MS-B183)
dmi.product.sku: B183.8
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1868162
Title:
snap chromium does not respect the dpi setting of xfce
Status in chromium-browser package in Ubuntu:
New
Bug description:
on a 4k monitor the default 96dpi setting is typically too small to
work with. setting it to eg 120dpi the guis become more readable.
unfortunately, chromium browser from the snap package on ubuntu 19.04
does still comes with ultra tiny font for the url text window.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CurrentDesktop: XFCE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd3LF0AAAwdAQS1PCJ4nj4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QA4PR6HOAAKICAgICAg/ABMRyBIRFIgNEsKICAgAdoCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1600x900
1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480
720x480 640x480 640x480 640x480
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV
Aftering leaving my computer turned on while Dropbox was uploading 2000 files... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Incomplete Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868160] [NEW] vino does not receive Shift+Function key events correctly
Public bug reported: If I connect to vino (using UltraVNC client from Windows), any Shift+Function key press is received as the plain function key (no shift). This breaks my application which uses separate actions for F12 vs Shift+F12. I experimented with xev, and it prints a KeyRelease event for the shift key before the KeyPress for the function key. All function keys F1 through F12 are affected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vino 3.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-137.163~14.04.1-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: mtxservmanager mtxmemmanager ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 14:45:58 2020 ExecutablePath: /usr/lib/vino/vino-server InstallationDate: Installed on 2016-01-11 (1528 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1868160 Title: vino does not receive Shift+Function key events correctly Status in vino package in Ubuntu: New Bug description: If I connect to vino (using UltraVNC client from Windows), any Shift+Function key press is received as the plain function key (no shift). This breaks my application which uses separate actions for F12 vs Shift+F12. I experimented with xev, and it prints a KeyRelease event for the shift key before the KeyPress for the function key. All function keys F1 through F12 are affected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vino 3.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-137.163~14.04.1-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: mtxservmanager mtxmemmanager ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 14:45:58 2020 ExecutablePath: /usr/lib/vino/vino-server InstallationDate: Installed on 2016-01-11 (1528 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1868160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] [NEW] Reopen issue 1666681
Public bug reported: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream - developers defend) demonstrates that it's maintained by a bunch of - idiots. + developers defend) proves that Nautilus maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' - b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" - b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' + b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" + b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream - developers defend) proves that Nautilus maintained by a bunch of idiots. + developers defend) demonstrates that it's maintained by a bunch of + idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. + + Anyway, in the shorter term, it seems that there are working patches + available to mitigate this disgrace. + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state'
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Why the fuck was this closed??? See also the discussion on 1164016 after this idiocy resurfaced. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868155] [NEW] Banner text and user list functionality seem broken
Public bug reported: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 14:33:30 2020 InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1868155 Title: Banner text and user list functionality seem broken Status in gdm3 package in Ubuntu: New Bug description: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion:
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
Now I tried to investigate from which UDEV rule the wrong setting comes
from. First I searched all UDEV rules for the word "audio":
till@till-x1yoga:~$ grep -l '\baudio\b' /*/udev/rules.d/*.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-v4l.rules
/lib/udev/rules.d/69-libmtp.rules
/lib/udev/rules.d/70-uaccess.rules
/lib/udev/rules.d/90-pulseaudio.rules
till@till-x1yoga:~$
So I expect only one of these can be the culprit. Actually a 'GROUP="audio"'
setting exists only in
/lib/udev/rules.d/50-udev-default.rules
and
/lib/udev/rules.d/69-libmtp.rules
The former is probably no problem as it assigns this group only to
devices of 'SUBSYSTEM=="sound"" where the latter seems to be actually
the culprit.
First it includes some devices explicitly and then it lists thousands of
supported devices. In the end there is some rule for passing a wide
range of devices through an auto-probing:
-
# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1",
ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{ID_GPHOTO}!="1",
ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff",
PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1",
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1",
ENV{ID_MEDIA_PLAYER}="1"
-
And this auto-probing tests positive on my printer:
till@till-x1yoga:~$ /lib/udev/mtp-probe
/sys/devices/pci:00/:00:14.0/usb1/1-1 001 012
1
till@till-x1yoga:~$
The device path of the printer I have taken from the blob in the udevadm
output (attached to previous comment) which also contains
"ID_MEDIA_PLAYER=1". So mtp-probe identifies my printer as a media
player and assigns the device file to the "audio" group.
I assume that this happens to most or even all HP printers, so an
exclusion of only my device via Vendor and Product ID would not be the
correct solution.
Either mtp-probe needs to get fixed or before said rule in the end of
the 69-libmtp.rules file and after the lines explicitly identifying
media players from HP, there should be placed a line to exclude further
HP devices, like
--
...
# Exclude any further, not explicitly specified HP devices
ATTR{idVendor}=="03f0", GOTO="libmtp_rules_end"
# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1",
ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{ID_GPHOTO}!="1",
ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff",
PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1",
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1",
ENV{ID_MEDIA_PLAYER}="1"
LABEL="libmtp_rules_end"
--
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: libmtp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1863239
Title:
/dev/bus/usb/*/* device file of HP multi-function printer assigned to
"audio" group
Status in libmtp package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Status in udev package in Ubuntu:
Invalid
Bug description:
When testing HPLIP I found out that CUPS backends can access my
printer only when they are running as root, when they are running as
the special user lp, as it is usually the case, they cannot access the
printer.
So I tried to find out why and saw that the /dev/bus/usb/*/* device
file for the printer has group ownership "audio" and not "lp":
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll
/dev/bus/usb/*/*
crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001
crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003
crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004
crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005
crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006
crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063
crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$
The printer is the device /dev/bus/usb/001/063:
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit
Ethernet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc.
Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated
Camera
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
Bus 001
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
Attached is the output of sudo udevadm monitor -e Output of lsusb: till@till-x1yoga:~$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 012: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~$ Device is on Bus 001, Device 012, the HP OfficeJet Pro 8730 Here one sees that it is assigned to the "audio" group: till@till-x1yoga:~$ ls -l /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Mar 17 11:45 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Mar 17 11:45 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Mar 17 11:45 /dev/bus/usb/001/004 crw-rw 1 root plugdev 189, 4 Mar 18 14:04 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Mar 17 11:45 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 11 Mar 19 18:55 /dev/bus/usb/001/012 crw-rw-r-- 1 root root189, 128 Mar 17 11:45 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Mar 17 11:45 /dev/bus/usb/002/003 till@till-x1yoga:~$ ** Attachment added: "udevadm-monitor-e-plug-hp-officejet-pro-8730-20200319-log.txt" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5338953/+files/udevadm-monitor-e-plug-hp-officejet-pro-8730-20200319-log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1865379/+attachment/5338950/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] ShellJournal.txt
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1865379/+attachment/5338951/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the screen
is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes just
fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu18
+ Architecture: armhf
+ CurrentDesktop: XFCE
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ GsettingsChanges:
+ b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
+ b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
+ Package: gnome-shell 3.35.91-1ubuntu2
+ PackageArchitecture: armhf
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
+ RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
+ Tags: focal uec-images third-party-packages
+ Uname: Linux 5.4.0-1001-raspi2 armv7l
+ UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
+ UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1865379/+attachment/5338949/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867955] Re: My entire DE flashes when trying to install an app and the application doesn't install
Thank you for your bug report, could you add the log from that command after triggering the issue? $ journalctl -b 0 > log ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867955 Title: My entire DE flashes when trying to install an app and the application doesn't install Status in gnome-software package in Ubuntu: Incomplete Bug description: When I try to install an app both with gnome-software and snap-store my DE flashes and it doesn't install anything. tried both with snap and deb. At at least we deb a got an error message "Permission denied" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 18:48:22 2020 InstallationDate: Installed on 2019-12-24 (85 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InstalledPlugins: gnome-software-plugin-flatpak 3.35.91-0ubuntu1 gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-03-15 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867943] Re: Nautilus “Open Other Application” problem
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1867943 Title: Nautilus “Open Other Application” problem Status in gtk+3.0 package in Ubuntu: New Bug description: When using Nautilus and I right click on an image file I get a drop down menu, the first two items are “Open With *Default application*” and “Open With Other Application”. I use Mirage as my default application for image files. On one account when I right click on an image file and choose “Open With Other Application”, Mirage is the preselected application not “Image Viewer” which is my usual second choice. On another account Mirage isn’t preselected, “Image Viewer” is. This is the expected behavior. I used the "Properties"->"Open With" to select “Image Viewer” and set it as the default. But that didn't work, it went back to Mirage as the default. I tried setting other programs as the default the same way and none stuck, it always returned to Mirage. I went to Settings->Details->Default Applications and changed the “Photos” from Mirage to “Image Viewer”. That worked and when right clicking and selecting “Other Application” Mirage is preselected. As expected. When I changed Settings->Details->Default Applications->“Photos” back to Mirage the problem returned. Mirage is the default and the preselected “Other Application”. “Right click on an image file and select : 'Open With Other Application' Then right click on the application that you do not want to be on that menu. Click on 'Forget association'”. Worked on other programs but not on Mirage. Description: Ubuntu 18.04 LTS (beaver-osha X84) Release: 18.04 Nautilus 1:3.26.4-0~ubuntu18.04.5 (from Software center) I expected Image Viewer to be the preselected Other Application. I got Mirage as the default application and the preselected “Other Application” I expected Mirage to be removed from the list when I clicked on “Forget association” What I got was Mirage would not go gently into the night I expected Mirage to accept not being the default application when using "Properties"->"Open With" to chose another application as the default. What I got was Mirage remaining the default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 11:21:53 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osha+X84 InstallationDate: Installed on 2019-11-28 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1867943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868140] [NEW] package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I think some configuration file for TeX needs to be completely replaced; maybe the post-processing script could offer that option instead of just complaining and exiting. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic i686 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: i386 Date: Thu Mar 19 12:49:14 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-03-18 (2557 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-02-09 (404 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1868140 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: I think some configuration file for TeX needs to be completely replaced; maybe the post-processing script could offer that option instead of just complaining and exiting. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic i686 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: i386 Date: Thu Mar 19 12:49:14 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-03-18 (2557 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-02-09 (404 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1868140/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868140] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script 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/1868140 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: I think some configuration file for TeX needs to be completely replaced; maybe the post-processing script could offer that option instead of just complaining and exiting. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic i686 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: i386 Date: Thu Mar 19 12:49:14 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-03-18 (2557 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-02-09 (404 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1868140/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832606] Re: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side
Can confirm that this exact thing happened to me as well, I believe after upgrading to 19.10. -- 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/1832606 Title: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: When setting window control layout to the left hand side rather than the right, GNOME Disks (gnome-disk-utility) does not show the 'Close' button, however the 'Minimize' and 'Maximize' buttons are still present. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 08:44:30 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1832606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868132] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1858414 *** https://bugs.launchpad.net/bugs/1858414 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 #1858414, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1868132/+attachment/5338926/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1868132/+attachment/5338928/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1868132/+attachment/5338932/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1868132/+attachment/5338933/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1868132/+attachment/5338934/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1868132/+attachment/5338936/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1868132/+attachment/5338937/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1858414 gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1868132 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: I was executing the opening of 'Compiz Fusion' icon after having just installed it. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 16:05:25 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 It is a duplicate of bug #1310121, unsolved from 2014, but administrators closed it. Daniel van Vugt (vanvugt) wrote 10 hours ago: #9 Everyone please report your own new bugs by running: ubuntu-bug pulseaudio This bug is closed. -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868131] [NEW] Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 Public bug reported: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa- mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "analog-output-headphones.conf" https://bugs.launchpad.net/bugs/1868131/+attachment/5338919/+files/analog-output-headphones.conf ** This bug has been marked a duplicate of bug 1310121 headphones working while speakers not working -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
[Desktop-packages] [Bug 1868128] [NEW] (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Public bug reported: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in xorg package in Ubuntu: New Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
I installed kernel 5.3.0-050300 and sound and microphone works fine: Linux G3-3590 5.3.0-050300-generic #201909152230 SMP Sun Sep 15 22:32:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I'm using Ubuntu 18.04.04 on Dell G3 3590-A20P. -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
I am also having this issue on Fedora 31, Gnome 3.34.4 with a Radeon RX 590 using amdgpu on Wayland. Video attached. Unsure how to replicate other than after locking. (I appreciate this is an Ubuntu bug tracker, but it's the same issue.) ** Attachment added: "stuckcursor.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+attachment/5338885/+files/stuckcursor.mp4 -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
I have the same problem with Dell G3-3590-A20P after upgraded kernel to 5.3.0-42. Does anyone have updates about this? -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868108] Re: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure
Don't froce/badtest that one, webkit2gtk is busted for real on ppc64el and the test did catch a valid regression, try starting MiniBrowser from webkgit and it fails to load any webpage ** Package changed: ruby-gnome (Ubuntu Focal) => webkit2gtk (Ubuntu Focal) ** Changed in: webkit2gtk (Ubuntu Focal) Importance: Undecided => High ** Changed in: webkit2gtk (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: webkit2gtk (Ubuntu Focal) Assignee: Lucas Kanashiro (lucaskanashiro) => Sebastien Bacher (seb128) ** Bug watch added: bugs.webkit.org/ #209236 https://bugs.webkit.org/show_bug.cgi?id=209236 ** Also affects: webkit via https://bugs.webkit.org/show_bug.cgi?id=209236 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1868108 Title: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure Status in Webkit: Unknown Status in webkit2gtk package in Ubuntu: In Progress Status in webkit2gtk source package in Focal: In Progress Bug description: ruby-gnome/3.4.1-2* package fails with: 2020-03-19T13:29:50+00:00: Running test for /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk Loaded suite test Started (run-test.rb:9142): dbind-WARNING **: 13:29:51.769: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ..[2020-03-19 13:29:52] INFO WEBrick 1.6.0 [2020-03-19 13:29:52] INFO ruby 2.7.0 (2019-12-25) [powerpc64le-linux-gnu] [2020-03-19 13:29:52] INFO WEBrick::HTTPServer#start: pid=9142 port=37651 (WebKitWebProcess:9153): dbind-WARNING **: 13:29:52.607: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files F === Failure: test: #load_uri(TestWebKit2GtkWebView::#load_uri): expected but was /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk/test/test-webkit2-gtk-web-view.rb:106:in `block (2 levels) in ' 103: @view.load_uri(http_url) 104: loop.run 105: => 106: assert_true(loaded) 107: end 108: end 109: end ===[2020-03-19 13:30:22] INFO going to shutdown ... [2020-03-19 13:30:22] INFO WEBrick::HTTPServer#start done. .. Finished in 30.95292437 seconds. --- 9 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 88.8889% passed --- 0.29 tests/s, 0.29 assertions/s Failed to run test: webkit2-gtk Failed targets: webkit2-gtk Gdk-Message: 13:30:22.622: WebKitWebProcess: Fatal IO error 2 (No such file or directory) on X server :99. autopkgtest [13:30:22]: test run-test: ---] run-test FAIL non-zero exit status 1 autopkgtest [13:30:23]: test run-test: - - - - - - - - - - results - - - - - - - - - - autopkgtest [13:30:23]: summary run-test FAIL non-zero exit status 1 Exit request sent. When running in ppc64el. This is likely due a timeout in glib main loop for that architecture but can't know for sure. I'm opening this bug so I can blacklist that particular test. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1868108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868117] [NEW] Adapt chromium user agent to avoid "not supported browser"
Public bug reported: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1868117 Title: Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: New Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868108] [NEW] [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure
You have been subscribed to a public bug: ruby-gnome/3.4.1-2* package fails with: 2020-03-19T13:29:50+00:00: Running test for /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk Loaded suite test Started (run-test.rb:9142): dbind-WARNING **: 13:29:51.769: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ..[2020-03-19 13:29:52] INFO WEBrick 1.6.0 [2020-03-19 13:29:52] INFO ruby 2.7.0 (2019-12-25) [powerpc64le-linux-gnu] [2020-03-19 13:29:52] INFO WEBrick::HTTPServer#start: pid=9142 port=37651 (WebKitWebProcess:9153): dbind-WARNING **: 13:29:52.607: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files F === Failure: test: #load_uri(TestWebKit2GtkWebView::#load_uri): expected but was /tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk/test/test-webkit2-gtk-web-view.rb:106:in `block (2 levels) in ' 103: @view.load_uri(http_url) 104: loop.run 105: => 106: assert_true(loaded) 107: end 108: end 109: end ===[2020-03-19 13:30:22] INFO going to shutdown ... [2020-03-19 13:30:22] INFO WEBrick::HTTPServer#start done. .. Finished in 30.95292437 seconds. --- 9 tests, 9 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 88.8889% passed --- 0.29 tests/s, 0.29 assertions/s Failed to run test: webkit2-gtk Failed targets: webkit2-gtk Gdk-Message: 13:30:22.622: WebKitWebProcess: Fatal IO error 2 (No such file or directory) on X server :99. autopkgtest [13:30:22]: test run-test: ---] run-test FAIL non-zero exit status 1 autopkgtest [13:30:23]: test run-test: - - - - - - - - - - results - - - - - - - - - - autopkgtest [13:30:23]: summary run-test FAIL non-zero exit status 1 Exit request sent. When running in ppc64el. This is likely due a timeout in glib main loop for that architecture but can't know for sure. I'm opening this bug so I can blacklist that particular test. ** Affects: webkit2gtk (Ubuntu) Importance: High Assignee: Sebastien Bacher (seb128) Status: In Progress ** Affects: webkit2gtk (Ubuntu Focal) Importance: High Assignee: Sebastien Bacher (seb128) Status: In Progress -- [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure https://bugs.launchpad.net/bugs/1868108 You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867480] Re: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1867480 Title: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl() Status in system-config-printer package in Ubuntu: Confirmed Bug description: not sure what it is I just saw there was n bug - I am new to Linux ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: system-config-printer-common 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 15 02:22:17 2020 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) InterpreterPath: /usr/bin/python3.8 Lpstat: device for L365: dnssd://EPSON%20L365%20Series._pdl-datastream._tcp.local/ MachineType: Universal Exports Group Limited ITL 1403-I3 128 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/L365.ppd'] failed with exit code 2: grep: /etc/cups/ppd/L365.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=464449a8-03b3-4536-9504-744640ef4b27 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SegvAnalysis: Segfault happened at: 0x506f57: mov%rcx,(%rdx) PC (0x00506f57) ok source "%rcx" ok destination "(%rdx)" (0x0004) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: system-config-printer StacktraceTop: ?? () ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so __nptl_deallocate_tsd () at pthread_create.c:301 __nptl_deallocate_tsd () at pthread_create.c:256 start_thread (arg=) at pthread_create.c:488 Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 04/29/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 0429 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Default dmi.board.vendor: Default dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr0429:bd04/29/2019:svnUniversalExportsGroupLimited:pnITL1403-I3128:pvrTBDbyOEM:rvnDefault:rnDefault:rvrType2-BoardVersion:cvnChassisManufacture:ct10:cvrChassisVersion: dmi.product.family: Notepad dmi.product.name: ITL 1403-I3 128 dmi.product.sku: ITL 1403-I3 128 dmi.product.version: TBD by OEM dmi.sys.vendor: Universal Exports Group Limited separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1867480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796437] Re: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()
*** This bug is a duplicate of bug 1745345 *** https://bugs.launchpad.net/bugs/1745345 This is still happening in Ubuntu Budgie 20.04 on virt-maneger VM on latest daily. -- 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/1796437 Title: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1796437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
@laney: Shouldn't udisks2 prefer in-kernel filesystem support if available, then fallback to a fuse driver? We also have a fuseext2 package, but if I have that installed I would still expect an ext2 formatted thumb drive to be mounted using the kernel's driver when I insert it rather than the fuse driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868089] Re: CUPS Fails to connect to printer
~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ~$ uname -a Linux Fueno 5.3.0-7629-generic #31~1581628854~18.04~2db8a7a~dev-Ubuntu SMP Fri Feb 14 19:57:43 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1868089 Title: CUPS Fails to connect to printer Status in cups package in Ubuntu: New Bug description: Printing is OK for a week, or, so. Then, with no changes, CUPS reports an error HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes, or so. I can ping the printer and connect to it with a browser. After pausing the printer and resume the printer, and connect with a browser, it starts to print. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CupsErrorLog: Date: Thu Mar 19 06:02:42 2020 Lpstat: device for HP_OfficeJet_Pro_9020_series: dnssd://HP%20OfficeJet%20Pro%209020%20series%20%5BCFE4C8%5D._ipp._tcp.local/?uuid=a58de112-16bc-5ad1-8887-1d919817cb03 device for HP_OfficeJet_Pro_9020_series_CFE4C8_: ipps://HPC46516CFE4C8.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 24f0:0105 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7i7BNH Papersize: letter PpdFiles: HP_OfficeJet_Pro_9020_series_CFE4C8_: OfficeJet Pro 9020 series HP_OfficeJet_Pro_9020_series: HP OfficeJet Pro 9020 series, driverless, cups-filters 1.20.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=e495b330-7204-41f9-bfb7-a2a47e56fffd ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-313 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i7BNH:pvrJ31153-314:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-313:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i7BNH dmi.product.version: J31153-314 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1868089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868089] [NEW] CUPS Fails to connect to printer
Public bug reported: Printing is OK for a week, or, so. Then, with no changes, CUPS reports an error HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes, or so. I can ping the printer and connect to it with a browser. After pausing the printer and resume the printer, and connect with a browser, it starts to print. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CupsErrorLog: Date: Thu Mar 19 06:02:42 2020 Lpstat: device for HP_OfficeJet_Pro_9020_series: dnssd://HP%20OfficeJet%20Pro%209020%20series%20%5BCFE4C8%5D._ipp._tcp.local/?uuid=a58de112-16bc-5ad1-8887-1d919817cb03 device for HP_OfficeJet_Pro_9020_series_CFE4C8_: ipps://HPC46516CFE4C8.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 24f0:0105 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7i7BNH Papersize: letter PpdFiles: HP_OfficeJet_Pro_9020_series_CFE4C8_: OfficeJet Pro 9020 series HP_OfficeJet_Pro_9020_series: HP OfficeJet Pro 9020 series, driverless, cups-filters 1.20.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=e495b330-7204-41f9-bfb7-a2a47e56fffd ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-313 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i7BNH:pvrJ31153-314:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-313:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i7BNH dmi.product.version: J31153-314 dmi.sys.vendor: Intel(R) Client Systems ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1868089 Title: CUPS Fails to connect to printer Status in cups package in Ubuntu: New Bug description: Printing is OK for a week, or, so. Then, with no changes, CUPS reports an error HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes, or so. I can ping the printer and connect to it with a browser. After pausing the printer and resume the printer, and connect with a browser, it starts to print. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CupsErrorLog: Date: Thu Mar 19 06:02:42 2020 Lpstat: device for HP_OfficeJet_Pro_9020_series: dnssd://HP%20OfficeJet%20Pro%209020%20series%20%5BCFE4C8%5D._ipp._tcp.local/?uuid=a58de112-16bc-5ad1-8887-1d919817cb03 device for HP_OfficeJet_Pro_9020_series_CFE4C8_: ipps://HPC46516CFE4C8.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 24f0:0105 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7i7BNH Papersize: letter PpdFiles: HP_OfficeJet_Pro_9020_series_CFE4C8_: OfficeJet Pro 9020 series HP_OfficeJet_Pro_9020_series: HP OfficeJet Pro 9020 series, driverless, cups-filters 1.20.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=e495b330-7204-41f9-bfb7-a2a47e56fffd ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-313 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i7BNH:pvrJ31153-314:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-313:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i7BNH
[Desktop-packages] [Bug 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
5.3.0-43 is in -proposed now, please test -43 kernel. -- 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/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: New Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD arecord: device_list:270: no soundcards
[Desktop-packages] [Bug 1868085] [NEW] Bug related to the new kernel version 5.3.0-42-generic
Public bug reported: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status 15 /sys/bus/acpi/devices/IFX0785:00/status 15 /sys/bus/acpi/devices/INT3400:00/status 15 /sys/bus/acpi/devices/INT3403:00/status 15 /sys/bus/acpi/devices/INT3403:01/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT34BB:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0B00:00/status 15 /sys/bus/acpi/devices/PNP0C02:00/status 3 /sys/bus/acpi/devices/PNP0C02:01/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C09:00/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status 15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD arecord: device_list:270: no soundcards found... !!Amixer output !!- !!Alsactl output !!-- --startcollapse-- --endcollapse-- !!All Loaded Modules !!-- ac97_bus acpi_pad acpi_thermal_rel aes_x86_64 aesni_intel amd_iommu_v2 amdgpu autofs4 bluetooth bnep btbcm btintel btrtl btusb ccm cfg80211 cmac coretemp crc32_pclmul crct10dif_pclmul cros_ec_core cros_ec_ishtp cryptd crypto_simd drm drm_kms_helper e1000e ecc ecdh_generic fb_sys_fops ghash_clmulni_intel glue_helper gpu_sched hid hid_generic hid_multitouch hid_sensor_als hid_sensor_hub
[Desktop-packages] [Bug 1868083] [NEW] gnome-shell process "estabilished"
Public bug reported: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: New Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
Before we switch any software to using p11-kit-trust.so, we need to fix our ca-certificates package to properly handle untrusted or blacklisted certificates. At the moment, I believe they are simply skipped when generating the contents of /usr/share/ca-certificates. -- 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/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868049] Re: Sound icon missing from tray
*** This bug is a duplicate of bug 1865169 *** https://bugs.launchpad.net/bugs/1865169 ** Package changed: 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/1868049 Title: Sound icon missing from tray Status in gnome-shell package in Ubuntu: New Bug description: The sound icon is missing from the Ubuntu focal tray (see attached ubuntu.jiff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868049] Re: Sound icon missing from tray
*** This bug is a duplicate of bug 1865169 *** https://bugs.launchpad.net/bugs/1865169 ** This bug has been marked a duplicate of bug 1865169 volume and light not working in Gnome Shell 3.35 -- 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/1868049 Title: Sound icon missing from tray Status in gnome-shell package in Ubuntu: New Bug description: The sound icon is missing from the Ubuntu focal tray (see attached ubuntu.jiff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868049/+subscriptions -- Mailing list: https://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 1647285] Re: SSL trust not system-wide
On Thu, 2020-03-19 at 09:44 +, Olivier Tilloy wrote: > It looks like symlinking firefox and thunderbird's own copies of > libnssckbi.so to the system-wide p11-kit-trust.so is the proper way to > fix this bug, as far as Mozilla's products are concerned. > > Before I proceed to doing this, I'd welcome comments from the security > team on this approach though, as I suspect I don't understand all the > implications. > > (an alternative would be building firefox/thunderbird against the > system-wide nss, but firefox currently requires 3.50, which isn't yet in > focal, and I suspect that requirement is being bumped often, so that > wouldn't really work with our distribution model) Right, don't bother trying to replace NSS just for this (although really, having a single version of NSS on the system *would* be nice). The interface to libnssckbi.so is a standard PKCS#11 library, and it's perfectly reasonable to replace that in each of firefox/thunderbird/chromium individually. -- 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/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868049] [NEW] Sound icon missing from tray
You have been subscribed to a public bug: The sound icon is missing from the Ubuntu focal tray (see attached ubuntu.jiff) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- Sound icon missing from tray https://bugs.launchpad.net/bugs/1868049 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867758] Re: Gnome shell froze completely
1. _usr_bin_gnome-screensaver crashed on the 16th, which is a day before this report. That crash was uploaded. _usr_bin_gnome-shell.1000 also crashes on the 11th, that was uploaded as well. 2. I've uninstalled everything I could, will see if it happens again. I just had the freeze happen now while extensions were still installed. ** Attachment added: "Screenshot_2020-03-19 Installed Extensions - GNOME Shell Extensions.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+attachment/5338729/+files/Screenshot_2020-03-19%20Installed%20Extensions%20-%20GNOME%20Shell%20Extensions.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867758 Title: Gnome shell froze completely Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome shell froze completely and would not respond to any mouse clicks or keyboard action. The mouse did move, but that's about it. It stayed this way for ~15mins before I reset it and lost all my work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 11:51:50 2020 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1126 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712122] Re: Desktop keyboard shortcuts autorepeat (probably shouldn't)
Fix Released some time ago I assume. ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1712122 Title: Desktop keyboard shortcuts autorepeat (probably shouldn't) Status in gnome-shell package in Ubuntu: Fix Released Bug description: "Please hold down CTRL+ALT and press T" sometimes results in (novice) users holding down all three keys at once. Desired behaviour:- One terminal opens, keyboard combination does not repeat. Actual behaviour:- Bazillions of terminals launch On my Ubuntu 16.04 system running Unity, the keyboard shortcut does not repeat. On 17.10 GNOME Shell it does. I believe it should not. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 18:12:51 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-control-center', 'bin/telegram', '~/bin/Telegram', '~/bin/telegram', '/home/alan/bin/telegram', '/home/alan/bin/Telegram', 'brackets', '/snap/bin/brackets']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load
** Tags added: fixed-in-3.35.92 -- 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/1866146 Title: GNOME Shell 3.35.91 extension's preferences doesn't load Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Using Ubuntu Focal Fossa development with gnome-shell 3.35.91 and preferences for extensions doesn't load. Tried opening using the browser, gnome-tweaks, or the new extensions app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 12:36:15 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-03 (518 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-10 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802680] Re: Adding keyboard layout broken without logout
** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1802680 Title: Adding keyboard layout broken without logout Status in gnome-shell package in Ubuntu: Fix Released Bug description: On my system, the default keyboard layout is English (Colemak). I have English (US) as a secondary keyboard layout. I attempted to add Russian, which worked. However, when I switched to it using Super+Space, input was really done in QWERTY. Both Russian and English (US) were effectively QWERTY options until I logged out and back in. - Steps from a duplicate bug affecting Bionic: 1. Open 'Language and Region' in Settings 2. Add Arabic as a new input source 3. Change to Arabic in the top panel, or press super+space 4. Write in Gedit or LibreOffice 5. The written text is still Latin (German is my first input source) The new input source (Arabic) is not recognized unless after restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866275] Re: Password overlay dialogue breaks during screen lock while overlay present
All comments will be in the upstream bug to avoid duplication: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2321 ** Changed in: gnome-shell (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866275 Title: Password overlay dialogue breaks during screen lock while overlay present Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Focal: In Progress Bug description: If you have a password overlay dialogue box present on your screen, for example, trying to mount an encrypted disk image from gnome-disks, or trying to unlock an ssh key, if the lock screen appears while the dialogue is in place, after unlocking the screen, you can still enter your password into the dialogue and the action still happens (mounting the disk image, unlocking the ssh key), but the dialogue box gets stuck and does not disappear. Steps for reproducing: 1) In gnome-disks, make a small 10mb disk image, select ext4 and luks. Set a trivial password. 2) Attempt to mount the encrypted disk image 3) When the password unlock dialogue appears, lock your screen (super + L) 4) Wake the screen up, unlock computer 5) Enter password into existing dialogue 6) The dialogue now cannot be dismissed. Logs: Mar 06 12:46:36 ubuntu0 udisksd[749]: Set up loop device /dev/loop5 (backed by /home/ubuntu/Documents/diskimage.img) Mar 06 12:46:37 ubuntu0 systemd[1]: fprintd.service: Succeeded. Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.307' (uid=1000 pid=1506 comm="> Mar 06 12:46:40 ubuntu0 systemd[1]: Starting Fingerprint Authentication Daemon... Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Successfully activated service 'net.reactivated.Fprint' Mar 06 12:46:40 ubuntu0 systemd[1]: Started Fingerprint Authentication Daemon. Mar 06 12:46:40 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory Mar 06 12:46:43 ubuntu0 gnome-shell[1506]: JS WARNING: [resource:///org/gnome/shell/gdm/authPrompt.js 316]: reference to undefined property "_defaultButtonWellActor" Mar 06 12:46:43 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory Mar 06 12:46:43 ubuntu0 gdm-password][1921]: gkr-pam: unlocked login keyring Mar 06 12:46:43 ubuntu0 NetworkManager[706]: [1583452003.9911] agent-manager: agent[69f92bd444c1b400,:1.307/org.gnome.Shell.NetworkAgent/1000]: agent registered Mar 06 12:46:43 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] Activating service name='org.freedesktop.FileManager1' requested by ':1.50' (uid=1000 pid=1506 comm="/usr/bin/gn> Mar 06 12:46:44 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] Activating service name='org.gnome.Nautilus' requested by ':1.50' (uid=1000 pid=1506 comm="/usr/bin/gnome-shell > Mar 06 12:46:44 ubuntu0 gnome-shell[1506]: Unable to mount volume 10.0 MB Encrypted: Gio.IOErrorEnum: An operation is already pending Mar 06 12:46:51 ubuntu0 udisksd[749]: Unlocked device /dev/loop5 as /dev/dm-3 Mar 06 12:46:51 ubuntu0 kernel: EXT4-fs (dm-3): mounted filesystem without journal. Opts: (null) Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS WARNING: [resource:///org/gnome/shell/ui/unlockDialog.js 762]: reference to undefined property "_authPrompt" Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS ERROR: TypeError: this._authPrompt is undefined _escape@resource:///org/gnome/shell/ui/unlockDialog.js:762:13 Version info: - Ubuntu 20.04 - gnome-shell 3.35.91-1ubuntu2 Attached is a screencast demonstrating each of the steps for reproducing. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
It looks like symlinking firefox and thunderbird's own copies of libnssckbi.so to the system-wide p11-kit-trust.so is the proper way to fix this bug, as far as Mozilla's products are concerned. Before I proceed to doing this, I'd welcome comments from the security team on this approach though, as I suspect I don't understand all the implications. (an alternative would be building firefox/thunderbird against the system-wide nss, but firefox currently requires 3.50, which isn't yet in focal, and I suspect that requirement is being bumped often, so that wouldn't really work with our distribution model) ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
according to #4 nss should still symlink libnssckbi.so to p11-kit- trust.so ** Changed in: nss (Ubuntu) Status: Fix Released => 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/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: New Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
** Description changed: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. + + I was previously using 19.04 and 19.10 on this device and never + experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. -- 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/1866194 Title: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate:
[Desktop-packages] [Bug 1868057] Re: screen flickering some small parts in user interface not right
Please open a Terminal window and type the command: apport-collect 1868057 Please also attach a new image or video when the problem returns. If the problem does not return then you don't need to do anything, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868057 Title: screen flickering some small parts in user interface not right Status in gnome-shell package in Ubuntu: Incomplete Bug description: just flickering but rare and little bits of colour problems in text. Don't really know what I'm doing now but it's an error report. Hopefully for graphics issues. lol ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 09:52:59 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1944] InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP ProBook 440 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=f6a4f0fe-5dac-4579-a54d-22600c546092 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.49 dmi.board.name: 1944 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.49:bd08/29/2019:svnHewlett-Packard:pnHPProBook440G1:pvrA3008DD10B03:rvnHewlett-Packard:rn1944:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 440 G1 dmi.product.sku: C7N87AV#AB5 dmi.product.version: A3008DD10B03 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Released -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Fix Released Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ Only pulseaudio is a regular file; other ones are symbolic links, so it is enough to modify the first one. gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1866146 Title: GNOME Shell 3.35.91 extension's preferences doesn't load Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Using Ubuntu Focal Fossa development with gnome-shell 3.35.91 and preferences for extensions doesn't load. Tried opening using the browser, gnome-tweaks, or the new extensions app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 12:36:15 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-03 (518 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-10 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828697] Re: Volume and brightness OSD make full-screen video flicker once they disappear
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed -- 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/1828697 Title: Volume and brightness OSD make full-screen video flicker once they disappear Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: Steps: 1. Open a video in Totem, MPV or YouTube 2. Make the video full-screen 3. Press the keyboard keys to change volume or brightness to show an OSD 4. Notice the video flicker ONCE the OSD disappears (as if it destroys the graphics behind it for a second) 5. Keep trying to show an OSD, changing volume or brightness, until you see the bug because sometimes it doesn't happen the first time and not consistently ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 00:14:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (163 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1828697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725180] Re: Shell animations are not smooth
** Changed in: gjs (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1725180 Title: Shell animations are not smooth Status in gjs: Fix Released Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Upstream fixes required to make all the overview/window/icon animations much smoother (at least halving render times): https://gitlab.gnome.org/GNOME/gjs/merge_requests/390 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/948 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1002 __ +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ xwayland: Installed: 2:1.19.5-0ubuntu2 Candidate: 2:1.19.5-0ubuntu2 Version table: *** 2:1.19.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630. Currently using Intel HD Graphics 630 as Nvidia seems to have no support for xwayland. The window/dock/launcher animations are lagging/shaky (not smooth). __ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:09:27 2017 DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-05-24 (149 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1725180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed -- 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/1819890 Title: Restarting gnome-shell displays images of applications running on other workspaces Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: Restarting gnome-shell with 'Alt-F2,r and enter' displays images of applications running on other workspaces which are not clickable. Steps to reproduce: 1) Enable multiple workspaces 2) Start an application on each workspace 3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter' Expected outcome: As with Ubuntu 18.04, each application is displayed only the workspace on which it was started. Actual outcome: All applications are displayed on the current workspace. The applications running on other workspaces are displayed as images, i.e. they cannot be 'clicked' but he 'wanted' application, the dock, top bar etc all function correctly. Workaround: To remove the unwanted images move to another workspace and return. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 10:15:45 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-20 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1819890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866044] Re: gnome-shell crashed with signal 5 in clutter_box_layout_allocate() ("ClutterBoxLayout child Gjs_ui_shellEntry_CapsLockWarning natural height: 0.000000 < minimum 24
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
--
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/1866044
Title:
gnome-shell crashed with signal 5 in clutter_box_layout_allocate()
("ClutterBoxLayout child Gjs_ui_shellEntry_CapsLockWarning natural
height: 0.00 < minimum 24.00 for width ...") when enable-
animations=false
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Bug description:
Starting this morning after updating my focal system, some GPG/SSH key
prompts will cause the entire shell to instantly crash. I also had a
similar shell crash happen when trying to unlock my laptop after
having it locked for a little while (but not suspended).
This unfortunately isn't easy reproduced on demand, but I've had 5
gnome-shell crashes over the past 4 hours when I have had none of the
3 months prior, so something feels quite wrong and makes getting any
work done quite difficult.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 4 08:45:46 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
LocalLibraries:
/home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
() at /usr/lib/gnome-shell/libst-1.0.so
() at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
() at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
clutter_actor_allocate () at
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: Upgraded to focal on 2018-12-17 (443 days ago)
UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner
sudo video
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1866044/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
I'll unassign myself since I have no way to reproduce this right now. We may yet group similar bugs with this one in future but generally it's more helpful to deter people from doing that too soon. Otherwise when a bug is declared fixed someone will pipe up and say it's not, when really they've just subscribed to the wrong bug. ** Changed in: pulseaudio (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1866194 Title: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848951] Re: High CPU when just moving the mouse
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed -- 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/1848951 Title: High CPU when just moving the mouse Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around for 18.04 version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1848951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
