[Desktop-packages] [Bug 1877829] [NEW] Won't reconnect to shared headphones
Public bug reported: In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my laptop running Ubuntu, and my Android smartphone. The headphones would pair with both, and I could simply re-enable the connection in Ubuntu or Android to connect to the headphones if the other device had been using the headphones last. In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my Android phone was using the headphones last. I have to manually unpair the headphones and re-pair them again. This is very inconvenient. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 15:44:22 2020 InstallationDate: Installed on 2017-08-16 (997 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET57W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:20456 acl:96 sco:0 events:2692 errors:0 TX bytes:604938 acl:84 sco:0 commands:2573 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T23:41:27.085337 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1877829 Title: Won't reconnect to shared headphones Status in bluez package in Ubuntu: New Bug description: In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my laptop running Ubuntu, and my Android smartphone. The headphones would pair with both, and I could simply re-enable the connection in Ubuntu or Android to connect to the headphones if the other device had been using the headphones last. In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my Android phone was using the headphones last. I have to manually unpair the headphones and re-pair them again. This is very inconvenient. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 15:44:22 2020 InstallationDate: Installed on 2017-08-16 (997 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET57W (1.36 )
[Desktop-packages] [Bug 1854676] Re: [snap] Web Midi API doesn't work
Olivier, it's not the webaudio that does not work. It's the webmidi. As in the 2 last examples on the demo list: https://ryoyakawai.github.io/smfplayer/ http://webaudiodemos.appspot.com/MIDIDrums/index.html In my testing the drum machine doesn't ask for permission to use midi. So that might be a bug on the websites part. But when smfplayer loads, this comes up in the teminal: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ hw Might be usefull :) -- 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/1854676 Title: [snap] Web Midi API doesn't work Status in chromium-browser package in Ubuntu: Confirmed Bug description: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Hi, I don't know if this is going to help, but I was experience a similar problem in Popos 20.04. In my case, the misbehaving app turned out to be Mega from mega.nz which I use for cloud sync. Their ubuntu 20.04 deb package causes noticeable stuttering. After disabling the app the desktop becomes smooth again. After enabling it again the computer becomes fast and smooth. This problem did not exist in 19.10 using mega's deb for 19.10. The stuttering happens across the board, in every activity randomly. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857182] Re: Unable to Google Online Account in Kubuntu 19.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon-ui (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1857182 Title: Unable to Google Online Account in Kubuntu 19.10 Status in signon-ui package in Ubuntu: Confirmed Bug description: Adding Google Online account in Kubuntu, i am able to enter my google username and password after that a message is received: Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu1 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 CurrentDesktop: KDE Date: Sat Dec 21 01:17:36 2019 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2019-12-20 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: signon-ui UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (pcmanfm:9039): Gtk-WARNING **: 23:27:13.685: Unable to locate theme engine in module_path: "adwaita", (pcmanfm:9039): Gtk-WARNING **: 23:27:13.691: Unable to locate theme engine in module_path: "adwaita", To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1857182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps
** Tags added: focal -- 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/938751 Title: Images are washed out or colors are skewed in some apps Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
This also affects me! Ubuntu Focal Fossa updated until right now; Dell Inspiron 15 5590 Laptop; Intel® Core™ i7-10510U CPU. I just use a simple P2 headphone. When plugged, audio doesn't sound out and mic doesn't capture in until I go to Gnome Control Center > Sound and change to the other input device created besides the default one. Look this out happening at https://youtu.be/uLwrqPwByNk -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). 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. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+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 1847829] Re: Three finger tap to middle click stopped working
Hi Rip, > Three fingers results in a right-click now for whatever > reason. I have the appropriate settings enabled in KDE > (I haven't changed them). > > Middle click works sometimes after restarting the device > via xinput, but this is very rare. If your three-finger taps are inconsistent (sometimes registered as left clicks, sometimes as right clicks, sometimes as middle clicks), it could be related to the following upstream issues: https://gitlab.freedesktop.org/libinput/libinput/-/issues/361 https://gitlab.freedesktop.org/libinput/libinput/-/issues/473 I am also affected by inconsistent three-finger taps (most often registered as right clicks) on a "SynPS/2 Synaptics TouchPad". ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #361 https://gitlab.freedesktop.org/libinput/libinput/-/issues/361 ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #473 https://gitlab.freedesktop.org/libinput/libinput/-/issues/473 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1847829 Title: Three finger tap to middle click stopped working Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I haven't expereinced this before, though a google search shows complaints from at least 2016. Three fingers results in a right-click now for whatever reason. I have the appropriate settings enabled in KDE (I haven't changed them). Middle click works sometimes after restarting the device via xinput, but this is very rare. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Sat Oct 12 03:40:48 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (330 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-31-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (167 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 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/xserver-xorg-input-libinput/+bug/1847829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877798] [NEW] The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
Public bug reported: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1877798/+attachment/5369253/+files/devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876847] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1876847 Title: HP-Spectre 2019 Intel wireless driver is detected incorrectly. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Output of lsb_release -rd, Description: Ubuntu 20.04 LTS Release: 20.04 Issue: I have Intel AX-201 for wireless but when i do "lspci -k", the driver is detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows that the wireless driver detected is "Intel AX-201". Output of lspci -k, 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 Subsystem: Intel Corporation Wireless-AC 9462 Kernel driver in use: iwlwifi Kernel modules: iwlwifi Output of journalctl -k | grep iwlwifi, May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002) May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0 May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 7c:b2:7d:d0:d5:95 May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - re-configuring In the additional drivers module, it shows that module Intel-9462 no longer works. My bluetooth is also not detected and doesn't work. I came across this but no else responded yet. So decided to report a bug here. https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems Please let me know if any more information is required. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srikar 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Spectre x360 Convertible 15-df1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df1xxx dmi.product.sku: 7UT64UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-package
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list-props 13" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369255/+files/xinput--list-props13.txt ** Description changed: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. - * "fingers": single-finger tap for a click, two-finger tap for a right click, - three-finger tap for a middle click - * "areas": tap in the lower right corner for a right click, tap in the upper - right corner for a middle click + * "fingers": single-finger tap for a click, two-finger tap for a right + click, three-finger tap for a middle click + * "areas": tap in the lower right corner for a right click, tap in the + upper right corner for a middle click After running the following command: - gsettings set org.gnome.desktop.peripherals.touchpad click-method - "'areas'" + gsettings set org.gnome.desktop.peripherals.touchpad click-method \ + "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: - cat /proc/bus/input/devices - xinput --list - xinput --list-props 13 # where 13 is the touchpad's ID + cat /proc/bus/input/devices + xinput --list + xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369254/+files/xinput--list.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.
Hi Seth, Functional issues, -> Wifi connection being spotty. -> No bluetooth functionality. I have mentioned a link in the description, if you can please check that, the wifi connection is dropping under load and wifi is just dropping. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1876847 Title: HP-Spectre 2019 Intel wireless driver is detected incorrectly. Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Output of lsb_release -rd, Description: Ubuntu 20.04 LTS Release: 20.04 Issue: I have Intel AX-201 for wireless but when i do "lspci -k", the driver is detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows that the wireless driver detected is "Intel AX-201". Output of lspci -k, 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 Subsystem: Intel Corporation Wireless-AC 9462 Kernel driver in use: iwlwifi Kernel modules: iwlwifi Output of journalctl -k | grep iwlwifi, May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002) May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0 May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 7c:b2:7d:d0:d5:95 May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - re-configuring In the additional drivers module, it shows that module Intel-9462 no longer works. My bluetooth is also not detected and doesn't work. I came across this but no else responded yet. So decided to report a bug here. https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems Please let me know if any more information is required. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srikar 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Spectre x360 Convertible 15-df1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df1xxx dmi.product.sku: 7UT64UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+s
[Desktop-packages] [Bug 1765832] Re: Two finger scrolling not working after suspend
*** This bug is a duplicate of bug 1722478 *** https://bugs.launchpad.net/bugs/1722478 thrantir's solution works for me in 20.04, is there a way to make this automatic on wake? -- 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/1765832 Title: Two finger scrolling not working after suspend Status in xorg package in Ubuntu: Confirmed Bug description: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718850] Re: Gnome Tweaks: Extensions appear off by default and can't be toggled or configured
Leaving the system and coming back, it was fine and the extensions worked again. Possibly a side effect of bug 1876641 (high memory usage?) -- 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/1718850 Title: Gnome Tweaks: Extensions appear off by default and can't be toggled or configured Status in Release Notes for Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-tweaks package in Ubuntu: Triaged Bug description: Go to the Extensions panel in Tweaks. System extensions (dock and appindicators) appear off by default, where they are obviously not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-tweak-tool 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 08:02:59 2017 ExecutablePath: /usr/bin/gnome-tweak-tool InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2 SourcePackage: gnome-tweak-tool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877182] Re: Screen turns off after 1 minute regardless of the configured timeout
After the update, the problem was solved. ** Changed in: gnome-shell (Ubuntu) Status: New => 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/1877182 Title: Screen turns off after 1 minute regardless of the configured timeout Status in gnome-shell package in Ubuntu: Fix Released Bug description: It just does not work if I set it to never or to 15 MIN it does not work it is stuck at one min ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 6 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d3d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d3d] InstallationDate: Installed on 2020-05-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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:b3fd Chicony Electronics Co., Ltd HD WebCam (Asus N-series) Bus 001 Device 005: ID 0b05:17ac ASUSTek Computer, Inc. ASUS Laser GAMING MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G551VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7fb860e1-6845-4a22-9fde-4c8435d52aba ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G551VW.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G551VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551VW.209:bd02/19/2016:svnASUSTeKCOMPUTERINC.:pnG551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G551VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1877182] Re: Screen turns off after 1 minute regardless of the configured timeout
Hello, After updating gnome-shell from 3.36.1-5ubuntu1 to 3.36.1-5ubuntu2 gnome-shell-common from 3.36.1-5ubuntu1 to 3.36.1-5ubuntu2 I guess It's ok now to close this bug. Thanks for your support. -- 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/1877182 Title: Screen turns off after 1 minute regardless of the configured timeout Status in gnome-shell package in Ubuntu: Fix Released Bug description: It just does not work if I set it to never or to 15 MIN it does not work it is stuck at one min ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 6 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d3d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d3d] InstallationDate: Installed on 2020-05-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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:b3fd Chicony Electronics Co., Ltd HD WebCam (Asus N-series) Bus 001 Device 005: ID 0b05:17ac ASUSTek Computer, Inc. ASUS Laser GAMING MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G551VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7fb860e1-6845-4a22-9fde-4c8435d52aba ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G551VW.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G551VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551VW.209:bd02/19/2016:svnASUSTeKCOMPUTERINC.:pnG551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G551VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877182/+subscriptions -- Mailing list: https://launchpa
[Desktop-packages] [Bug 1877795] [NEW] After failed attempt, can not type password for a few seconds
Public bug reported: On the login screen, after entering an incorrect password, the box shakes and the error "Sorry, that didn't work please try again." is displayed. In previous Ubuntu versions you could immediately begin entering your password again. In 20.04 there is a delay of about 2-3 seconds before the password entry filled is auto selected. Eventually the orange border appears and text input is filled. This process can be quickened by clicking on the password field with the mouse pointer. lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 gdm3: Installed: 3.34.1-1ubuntu1 Full desktop install, everything up to date as of 5/9/20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 12:26:07 2020 InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1877795 Title: After failed attempt, can not type password for a few seconds Status in gdm3 package in Ubuntu: New Bug description: On the login screen, after entering an incorrect password, the box shakes and the error "Sorry, that didn't work please try again." is displayed. In previous Ubuntu versions you could immediately begin entering your password again. In 20.04 there is a delay of about 2-3 seconds before the password entry filled is auto selected. Eventually the orange border appears and text input is filled. This process can be quickened by clicking on the password field with the mouse pointer. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 gdm3: Installed: 3.34.1-1ubuntu1 Full desktop install, everything up to date as of 5/9/20 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 12:26:07 2020 InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/gdm3/+bug/1877795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718850] Re: Gnome Tweaks: Extensions appear off by default and can't be toggled or configured
My system is currently in a state where changes in gnome-shell- extension-prefs also aren't sticking.The toggle toggles, but extension isn't activated. Not sure if this is a different bug or the same one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718850 Title: Gnome Tweaks: Extensions appear off by default and can't be toggled or configured Status in Release Notes for Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-tweaks package in Ubuntu: Triaged Bug description: Go to the Extensions panel in Tweaks. System extensions (dock and appindicators) appear off by default, where they are obviously not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-tweak-tool 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 08:02:59 2017 ExecutablePath: /usr/bin/gnome-tweak-tool InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2 SourcePackage: gnome-tweak-tool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877793] [NEW] [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all
Public bug reported: Is a duplicate of bug 1877766 On installation 16.04 LTS there is sound. Also sound in windows. But as soon as Ubuntu updates, no sound. Tried 18 LTS no sound Tried 20 LTS - sound comes back But I want to stick with 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1556 F pulseaudio CurrentDesktop: Unity Date: Sat May 9 22:26:24 2020 InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1556 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 05C3PP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd05/10/2019:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn05C3PP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 13-5378 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1877793 Title: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Is a duplicate of bug 1877766 On installation 16.04 LTS there is sound. Also sound in windows. But as soon as Ubuntu updates, no sound. Tried 18 LTS no sound Tried 20 LTS - sound comes back But I want to stick with 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1556 F pulseaudio CurrentDesktop: Unity Date: Sat May 9 22:26:24 2020 InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1556 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 05C3PP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd05/10/2019:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn05C3PP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 13-5378 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877789] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1857539 *** https://bugs.launchpad.net/bugs/1857539 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 #1857539, 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/1877789/+attachment/5369222/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1877789/+attachment/5369224/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1877789/+attachment/5369228/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1877789/+attachment/5369229/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1877789/+attachment/5369230/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1877789/+attachment/5369231/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1877789/+attachment/5369232/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1857539 nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?) ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1877789 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.37.1.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu May 7 15:40:35 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (524 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7fb39cdedac2:mov0x380(%rax),%rax PC (0x7fb39cdedac2) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1877789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)
** Tags added: groovy -- 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 in widget_needs_widget_path (shutdown?) 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 1877787] Re: incorrect "permissions & access" slider position
I guess this bug is related? https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1867598 -- 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/1877787 Title: incorrect "permissions & access" slider position Status in gnome-control-center package in Ubuntu: New Bug description: Steps to reproduce: 1. open Settings (gnome-control-center) 2. go to the applications tab 3. select application with long permission name (probably a snap package like discord or minecraft) Expected results: all sliders are aligned Actual results: slider is misaligned ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 9 23:08:50 2020 InstallationDate: Installed on 2020-05-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877787] [NEW] incorrect "permissions & access" slider position
Public bug reported: Steps to reproduce: 1. open Settings (gnome-control-center) 2. go to the applications tab 3. select application with long permission name (probably a snap package like discord or minecraft) Expected results: all sliders are aligned Actual results: slider is misaligned ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 9 23:08:50 2020 InstallationDate: Installed on 2020-05-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "example" https://bugs.launchpad.net/bugs/1877787/+attachment/5369218/+files/Screenshot%20from%202020-05-09%2023-06-50.png -- 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/1877787 Title: incorrect "permissions & access" slider position Status in gnome-control-center package in Ubuntu: New Bug description: Steps to reproduce: 1. open Settings (gnome-control-center) 2. go to the applications tab 3. select application with long permission name (probably a snap package like discord or minecraft) Expected results: all sliders are aligned Actual results: slider is misaligned ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 9 23:08:50 2020 InstallationDate: Installed on 2020-05-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap
Yeah, it's easier to install the deb on 20.04 now than it was when I made the 'experiment'. The explanation is the package python-is-python2 which was added to 20.04 right before the release. But they should still port atom to python3 - python2 is obsolete and will soon disappear from the Ubuntu archive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1867090 Title: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap Status in ibus package in Ubuntu: Confirmed Bug description: OS: Ubuntu 19.10 IBus version: 1.5.21 Atom version: 1.45.0 When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0 (snap version), it simply doesn't work. When I type the letters into the window, it shall bring up the candidate list for me to pick words. But instead, the letters are directly typed into the window, but not Chinese characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877784] Re: libreoffice help does not work
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1869561, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1869561 Libreoffice Help does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877784 Title: libreoffice help does not work Status in libreoffice package in Ubuntu: New Bug description: New installation of Ubuntu 20.04. LibreOffice Calc seems to work fine, but when I click on Help, I get the message: Object not accessible. The object cannot be accessed due to insufficient user rights. Ubuntu 20.04 LTC Release 20.04 LibreOffice Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877784] [NEW] libreoffice help does not work
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 Public bug reported: New installation of Ubuntu 20.04. LibreOffice Calc seems to work fine, but when I click on Help, I get the message: Object not accessible. The object cannot be accessed due to insufficient user rights. Ubuntu 20.04 LTC Release 20.04 LibreOffice Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877784 Title: libreoffice help does not work Status in libreoffice package in Ubuntu: New Bug description: New installation of Ubuntu 20.04. LibreOffice Calc seems to work fine, but when I click on Help, I get the message: Object not accessible. The object cannot be accessed due to insufficient user rights. Ubuntu 20.04 LTC Release 20.04 LibreOffice Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877783] Re: package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1877783 Title: package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libssh package in Ubuntu: New Bug description: the package is in a state of critical inconsistency: it is recommended install it again before attempting configuration. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 9 21:08:23 2020 DuplicateSignature: package:libssh-gcrypt-4:amd64:0.9.0-1ubuntu1.4 Unpacking openssl (1.1.1g-1+ubuntu19.10.1+deb.sury.org+1) over (1.1.1c-1ubuntu4) ... dpkg: error processing package libssh-gcrypt-4:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-04-02 (37 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: libssh Title: package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1877783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877783] [NEW] package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Public bug reported: the package is in a state of critical inconsistency: it is recommended install it again before attempting configuration. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 9 21:08:23 2020 DuplicateSignature: package:libssh-gcrypt-4:amd64:0.9.0-1ubuntu1.4 Unpacking openssl (1.1.1g-1+ubuntu19.10.1+deb.sury.org+1) over (1.1.1c-1ubuntu4) ... dpkg: error processing package libssh-gcrypt-4:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-04-02 (37 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: libssh Title: package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1877783 Title: package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libssh package in Ubuntu: New Bug description: the package is in a state of critical inconsistency: it is recommended install it again before attempting configuration. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 9 21:08:23 2020 DuplicateSignature: package:libssh-gcrypt-4:amd64:0.9.0-1ubuntu1.4 Unpacking openssl (1.1.1g-1+ubuntu19.10.1+deb.sury.org+1) over (1.1.1c-1ubuntu4) ... dpkg: error processing package libssh-gcrypt-4:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-04-02 (37 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: libssh Title: package libssh-gcrypt-4:amd64 0.9.0-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1877783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
Dammit! I cant believe this level of lack of security could happen in this project. WHAT A SHAME! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Fix Committed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://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 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)
I got the same answer, I lack memory. Le ven. 8 mai 2020 à 04:35, Daniel van Vugt a écrit : > Please try using 'apport-cli' instead of 'ubuntu-bug'. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877269 > > Title: > Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: > snd_pcm_delay() returned a value that is exceptionally large) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > Description: Ubuntu 18.04.4 LTS > Release: 18.04 > > pulseaudio: > Installé : 1:11.1-1ubuntu7.5 > Candidat : 1:11.1-1ubuntu7.5 >Table de version : >*** 1:11.1-1ubuntu7.5 500 > 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main > amd64 Packages > 100 /var/lib/dpkg/status >1:11.1-1ubuntu7 500 > 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 > Packages > > > The OS freezes when using in normal conditions, usually VS Code, Discord > app and Spotify in browser. > When it does, I need to hard reboot by holding power button. > > I checked journalctl to confirm it was due to pulseaudio. > > alsa-util.c: snd_pcm_delay() returned a value that is exceptionally > large > > The above line is always the last to prompt in the boot journal. > It does not freeze instantly, it progressively freezes down, but > sometime Mozilla Firefox crashes and it freezes no more. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7.5 > Uname: Linux 5.1.15-surface-linux-surface x86_64 > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: saravanane 2071 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Thu May 7 11:00:37 2020 > InstallationDate: Installed on 2019-10-01 (218 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > SourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/18/2019 > dmi.bios.vendor: Microsoft Corporation > dmi.bios.version: 108.2706.768 > dmi.board.name: Surface Pro 4 > dmi.board.vendor: Microsoft Corporation > dmi.chassis.type: 9 > dmi.chassis.vendor: Microsoft Corporation > dmi.modalias: > dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: > dmi.product.family: Surface > dmi.product.name: Surface Pro 4 > dmi.product.sku: Surface_Pro_4 > dmi.product.version: D:0B:09F:1C:03P:38 > dmi.sys.vendor: Microsoft Corporation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877269/+subscriptions > -- 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/1877269 Title: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installé : 1:11.1-1ubuntu7.5 Candidat : 1:11.1-1ubuntu7.5 Table de version : *** 1:11.1-1ubuntu7.5 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The OS freezes when using in normal conditions, usually VS Code, Discord app and Spotify in browser. When it does, I need to hard reboot by holding power button. I checked journalctl to confirm it was due to pulseaudio. alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large The above line is always the last to prompt in the boot journal. It does not freeze instantly, it progressively freezes down, but sometime Mozilla Firefox crashes and it freezes no more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 Uname: Linux 5.1.15-surface-linux-surface x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanane 2071 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 7 11:00:37 2020 InstallationDate: Installed on 2019-10-01 (218 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: puls
[Desktop-packages] [Bug 1867090] Re: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap
Upgraded Ubuntu to 20.04, and Atom snap to 1.46.0. Chinese input is attempted without success. I followed the instructions on https://flight-manual.atom.io/getting- started/sections/installing-atom/ and installed the deb version instead. Chinese input can work under this version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1867090 Title: IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0 as snap Status in ibus package in Ubuntu: Confirmed Bug description: OS: Ubuntu 19.10 IBus version: 1.5.21 Atom version: 1.45.0 When I switch to Chinese input mode (Intelligent Pinyin) and try to type Chinese into Atom 1.45.0 (snap version), it simply doesn't work. When I type the letters into the window, it shall bring up the candidate list for me to pick words. But instead, the letters are directly typed into the window, but not Chinese characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877776] [NEW] Ubuntu-Software app is not launching after upgrade to 20
Public bug reported: Ubuntu-Software app is not launching after 19.10 to 20 upgrade. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 13:19:53 2020 InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 PackageArchitecture: all 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-05-09 (0 days ago) ** Affects: gnome-software (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-software in Ubuntu. https://bugs.launchpad.net/bugs/186 Title: Ubuntu-Software app is not launching after upgrade to 20 Status in gnome-software package in Ubuntu: New Bug description: Ubuntu-Software app is not launching after 19.10 to 20 upgrade. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 13:19:53 2020 InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 PackageArchitecture: all 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-05-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877775] Re: Chromium browser not launching after Ubuntu 20 upgrade
BTW, "Ubuntu Software" app is not launching either. -- 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/185 Title: Chromium browser not launching after Ubuntu 20 upgrade Status in chromium-browser package in Ubuntu: New Bug description: After successful upgrade from Ubuntu 19.10 to 20 Chromium browser is not launching. Removing re-installing doesn't help. Installing via apt tells that Chromium browser snap exists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 12:50:45 2020 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda4 ext4 164G 2.9G 153G 2% /home tmpfs tmpfs 7.8G 226M 7.6G 3% /dev/shm /dev/sda4 ext4 164G 2.9G 153G 2% /home InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1058:25e2 Western Digital Technologies, Inc. My Passport (WD40NMZW) Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 0bc2:ac41 Seagate RSS LLC BUP Portable Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05511df3-f98b-4a65-be14-d202da25b6ee ro quiet splash vt.handoff=7 Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] failed with exit code 1: error: no changes found Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks: Operation not permitted Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks: Operation not permitted SourcePackage: chromium-browser UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14b dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14b:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877775] [NEW] Chromium browser not launching after Ubuntu 20 upgrade
Public bug reported: After successful upgrade from Ubuntu 19.10 to 20 Chromium browser is not launching. Removing re-installing doesn't help. Installing via apt tells that Chromium browser snap exists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 12:50:45 2020 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda4 ext4 164G 2.9G 153G 2% /home tmpfs tmpfs 7.8G 226M 7.6G 3% /dev/shm /dev/sda4 ext4 164G 2.9G 153G 2% /home InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1058:25e2 Western Digital Technologies, Inc. My Passport (WD40NMZW) Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 0bc2:ac41 Seagate RSS LLC BUP Portable Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05511df3-f98b-4a65-be14-d202da25b6ee ro quiet splash vt.handoff=7 Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] failed with exit code 1: error: no changes found Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks: Operation not permitted Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks: Operation not permitted SourcePackage: chromium-browser UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14b dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14b:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/185 Title: Chromium browser not launching after Ubuntu 20 upgrade Status in chromium-browser package in Ubuntu: New Bug description: After successful upgrade from Ubuntu 19.10 to 20 Chromium browser is not launching. Removing re-installing doesn't help. Installing via apt tells that Chromium browser snap exists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 12:50:45 2020 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda4 ext4 164G 2.9G 153G 2% /home tmpfs tmpfs 7.8G 226M 7.6G 3% /dev/shm /dev/sda4 ext4 164G 2.9G 153G 2% /home InstallationDate: Installed on 2020-04-08 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1058:25e2 Western Digital Technologies, Inc. My Passport (WD40NMZW) Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 0bc2:ac41 Seagate RSS LLC BUP Portable Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.
[Desktop-packages] [Bug 1877154] Re: [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF
Done: https://bugzilla.kernel.org/show_bug.cgi?id=207663 ** Bug watch added: Linux Kernel Bug Tracker #207663 https://bugzilla.kernel.org/show_bug.cgi?id=207663 -- 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/1877154 Title: [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF Status in alsa-driver package in Ubuntu: New Bug description: After suspend to RAM sound device changes from default HDMI to S/PDIF. After changing it again to HDMI right speaker stops to respond. I can hear only the sound from left speaker during sound test from the settings menu. After the first wake from suspend you can find in messages from dmesg: [ 68.362807] pcieport :00:01.3: PME: Spurious native interrupt! [ 68.527845] nvme nvme0: 15/0/0 default/read/poll queues [ 68.533836] snd_hda_intel :0a:00.1: spurious response 0x8000:0x0, last cmd=0x6f2f03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaroslaw 2972 F pulseaudio /dev/snd/controlC1: jaroslaw 2972 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 18:32:10 2020 InstallationDate: Installed on 2020-05-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [AB350N-Gaming WIFI, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877767] [NEW] unset pipewire dependency in cheese
Public bug reported: After installing Cheese via apt and trying to run it, cheese complains of a missing dependency and segfaults: leecy@Mia:~/projects$ cheese can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared object file: No such file or directory Segmentation fault (core dumped) Upon further inspection this is a library provided by pipewire, which is not referenced by cheese's dependencies. Manually installing pipewire using sudo apt install pipewire solves the issue. ** Affects: cheese (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1877767 Title: unset pipewire dependency in cheese Status in cheese package in Ubuntu: New Bug description: After installing Cheese via apt and trying to run it, cheese complains of a missing dependency and segfaults: leecy@Mia:~/projects$ cheese can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared object file: No such file or directory Segmentation fault (core dumped) Upon further inspection this is a library provided by pipewire, which is not referenced by cheese's dependencies. Manually installing pipewire using sudo apt install pipewire solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1877767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854386] Re: Stuck on show applications overlay (can't close it)
Sorry again there was a problem with gnome-shell extension (Temperature) -- 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/1854386 Title: Stuck on show applications overlay (can't close it) Status in gnome-shell package in Ubuntu: Invalid Bug description: Hello, I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across this very annoying bug. Whenever I click on 'show applications' or press win key (shortcut), the menu with the applications show, but it's empty - you can search through it and it works fine (applications show, one can trigger application launch), but then after you select an application, the menu doesn't disappear at all. It doesn't go away when pressing any application on the dash panel, nor when clicking esc key, it only goes away after you click on the dash icon again, BUT... It doesn't really go away - it just becomes invisible, but still it overlaps all the items that are launched (with exception of dash panel, because it's not being overlapped), and you can't do anything on any launched application. Sometimes when you try to move some windows, you can see them getting transformed into a miniature, as if the system wanted to insert application into the suggestions on the 'show applications'. The only thing that worked for me was restarting my computer. Here is a movie of this happening: https://photos.google.com/share/AF1QipNA94MOXY4iH8rm01coSkZcH6ILYas9n2oXNs9Swxo16ijABFqz71VaRpO59tGpPg/photo/AF1QipOqVIZXLZW-Z_7zCIy8eeBGQgJQkPLY-OKfgy0Y?key=MTJBa2pRUl9VU2lmMXdEZGxYX3ZiSDRSTjJxWjdn I couldn't record screen because apparently the hotkeys were also intercepted and I couldn't save the video. It makes programming right now super dangerous, as if you press the 'win' button then it's basically 'adios'. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.3 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 18:00:54 2019 InstallationDate: Installed on 2018-11-09 (383 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854386] Re: Stuck on show applications overlay (can't close it)
Bug continues on GNOME Shell 3.36.1 -- 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/1854386 Title: Stuck on show applications overlay (can't close it) Status in gnome-shell package in Ubuntu: Invalid Bug description: Hello, I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across this very annoying bug. Whenever I click on 'show applications' or press win key (shortcut), the menu with the applications show, but it's empty - you can search through it and it works fine (applications show, one can trigger application launch), but then after you select an application, the menu doesn't disappear at all. It doesn't go away when pressing any application on the dash panel, nor when clicking esc key, it only goes away after you click on the dash icon again, BUT... It doesn't really go away - it just becomes invisible, but still it overlaps all the items that are launched (with exception of dash panel, because it's not being overlapped), and you can't do anything on any launched application. Sometimes when you try to move some windows, you can see them getting transformed into a miniature, as if the system wanted to insert application into the suggestions on the 'show applications'. The only thing that worked for me was restarting my computer. Here is a movie of this happening: https://photos.google.com/share/AF1QipNA94MOXY4iH8rm01coSkZcH6ILYas9n2oXNs9Swxo16ijABFqz71VaRpO59tGpPg/photo/AF1QipOqVIZXLZW-Z_7zCIy8eeBGQgJQkPLY-OKfgy0Y?key=MTJBa2pRUl9VU2lmMXdEZGxYX3ZiSDRSTjJxWjdn I couldn't record screen because apparently the hotkeys were also intercepted and I couldn't save the video. It makes programming right now super dangerous, as if you press the 'win' button then it's basically 'adios'. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.3 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 18:00:54 2019 InstallationDate: Installed on 2018-11-09 (383 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877754] [NEW] GTKFileChooser: deselect highlighted directory
Public bug reported: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him /her-self with no entry highlighted. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: gtkfilechooser ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Description changed: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted - automatically (when it is not the first time you save a file). So the - user may click on another entry to change the selection, but clicking on - the background *does not cause* a deselection to take place. In my - opinion that would be an expected usage pattern as it is the case on - common other platforms. + automatically which may be a folder (especially when it is not the first + time you save a file). So the user may click on another entry to change + the selection, but clicking on the background *does not cause* a + deselection to take place. In my opinion that would be an expected usage + pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the - working directory and not a particular file. The only valid (and nasty) + current working directory and not a particular folder/file (he doesn't + want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him /her-self with no entry highlighted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877754 Title: GTKFileChooser: deselect highlighted directory Status in Ubuntu: New Bug description: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him/her-self with no entry highlighted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
** Description changed: - Please see https://askubuntu.com/posts/1236257 for most background. + Please see https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: nils 90077 F pulseaudio - /dev/snd/controlC0: nils 90077 F pulseaudio - /dev/snd/controlC1: nils 90077 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: nils 90077 F pulseaudio + /dev/snd/controlC0: nils 90077 F pulseaudio + /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: nils 90077 F pulseaudio - /dev/snd/controlC0: nils 90077 F pulseaudio - /dev/snd/controlC1: nils 90077 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: nils 90077 F pulseaudio + /dev/snd/controlC0: nils 90077 F pulseaudio + /dev/snd/controlC1: nils 90077 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for some users but not for others Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all users UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 10/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5222 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x: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 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704 -- 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/1877726 Title: [HD
[Desktop-packages] [Bug 1877748] [NEW] Fractional scaling does not work properly
Public bug reported: When I use 125% scaling, turning off fractional scaling does not work properly - all interface elements look very small. #define "normal scaling" "100% scaling in non-fractional (discrete) mode" 1. Set normal scaling (100% non-fractional). 2. Turn fractional mode on. 3. Press 125% and confirm. 4. Turn off fractional mode. Result: interface looks very small. I use AMDGPU driver, Xorg mode, no major tweaks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 19:46:19 2020 InstallationDate: Installed on 2020-05-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Bildschirmfoto von 2020-05-09 19-59-00.png" https://bugs.launchpad.net/bugs/1877748/+attachment/5369050/+files/Bildschirmfoto%20von%202020-05-09%2019-59-00.png -- 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/1877748 Title: Fractional scaling does not work properly Status in gnome-control-center package in Ubuntu: New Bug description: When I use 125% scaling, turning off fractional scaling does not work properly - all interface elements look very small. #define "normal scaling" "100% scaling in non-fractional (discrete) mode" 1. Set normal scaling (100% non-fractional). 2. Turn fractional mode on. 3. Press 125% and confirm. 4. Turn off fractional mode. Result: interface looks very small. I use AMDGPU driver, Xorg mode, no major tweaks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 19:46:19 2020 InstallationDate: Installed on 2020-05-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877093] Re: [SRU] New stable release 2.34.2
autopkgtest [15:02:47]: test tests: ---] autopkgtest [15:02:48]: test tests: - - - - - - - - - - results - - - - - - - - - - testsPASS autopkgtest [15:02:49]: summary testsPASS Successfully signed dsc, buildinfo, changes files Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1.dsc Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1.debian.tar.xz Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1_source.buildinfo Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1_source.changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1877093 Title: [SRU] New stable release 2.34.2 Status in at-spi2-atk package in Ubuntu: Fix Released Status in at-spi2-atk source package in Focal: In Progress Bug description: [ Description ] GNOME upstream have released a new stable version of at-spi2-atk. Changes: What's new in at-spi2-atk 2.34.2: * Meson: don't hard-code shared_library (!19). * Mitigate missing window events at startup. * Set C standard to gnu99 (#10). * Tests: include sys/time.h (#14). [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Install the desktop and exercise the screen reader in a variety of situations. Optionally, but ideally, test the installer too. [ Regression potential ] If this update is busted the screen reader might not work. This changes the C standard too, which should be fine, but make sure to do some QA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876797] Re: Numerous issues
That would be great, but even ubuntu-bug is having problems. It will sit for hours not doing anything. -- 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/1876797 Title: Numerous issues Status in xorg-server package in Ubuntu: Incomplete Bug description: I upgraded from 18.04 -> 20.04. After upgrade, it will not remember my display configuration if I reboot. Settings can be saved (forced) into Xconfig, but for some reason it ignores them. I have a 1080p monitor vertical on my left, and a 1440p monitor on my right. Also, the system still believes I'm on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 4 13:54:32 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (673 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1876797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I am using Ubuntu 20.04. Here is the output of snap info: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/candidate/vaapi refresh-date: 2020-05-09T15:52:01+02:00 channels: latest/stable:81.0.4044.138 2020-05-06T18:11:18Z (1143) 161MB - latest/candidate: 81.0.4044.138 2020-05-06T14:20:15Z (1143) 161MB - latest/beta: 83.0.4103.44 2020-05-08T01:02:43Z (1144) 163MB - latest/edge: 84.0.4128.3 2020-04-29T05:50:21Z (1136) 164MB - installed: 81.0.4044.113 (1117) 165MB - -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877725] [NEW] Displays aberrant percentages for disks belonging to btrfs RAID volume
Public bug reported: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (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-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in gnome-disk-utility package in Ubuntu: New Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 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/1877725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
In this example /dev/sde is part of a 5-disks RAID5 volume. ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1877725/+attachment/5368860/+files/Screenshot_20200506_125603.png -- 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/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in gnome-disk-utility package in Ubuntu: New Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 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/1877725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877093] Re: [SRU] New stable release 2.34.2
Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1877093 Title: [SRU] New stable release 2.34.2 Status in at-spi2-atk package in Ubuntu: Fix Released Status in at-spi2-atk source package in Focal: In Progress Bug description: [ Description ] GNOME upstream have released a new stable version of at-spi2-atk. Changes: What's new in at-spi2-atk 2.34.2: * Meson: don't hard-code shared_library (!19). * Mitigate missing window events at startup. * Set C standard to gnu99 (#10). * Tests: include sys/time.h (#14). [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Install the desktop and exercise the screen reader in a variety of situations. Optionally, but ideally, test the installer too. [ Regression potential ] If this update is busted the screen reader might not work. This changes the C standard too, which should be fine, but make sure to do some QA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
i said on feb 4: "dbus_method_call messages still appear in logs, while saving. i do not know why they are not reported by aa-notify." i made this report on apparmor site on march 7: https://gitlab.com/apparmor/apparmor/-/issues/81 "aa-notify does not show messages about dbus" ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #81 https://gitlab.com/apparmor/apparmor/-/issues/81 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1861408 Title: firefox apparmor messages Status in apparmor package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint 19.3. i see there is newer ubuntu version in https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for apparmor. i have not found a page for firefox bugs in linux mint sites, so i belive i should report here. but i have also asked about that in linux mint's irc and then github. i have enabled apparmor for firefox and see these types of messages in syslog: Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000 pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined") Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5525.077960] audit: type=1400 audit(1580226276.440:27): apparmor="DENIED" operation="capable" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948 comm="firefox" capability=21 capname="sys_admin" Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon" member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/Private/RemoteVolumeMonitor" interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported" mask="send" name=":1.35" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="ListMounts2" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="LookupMount" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000 pid=15948 comm="/usr/lib/firefox/firefox " label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)") Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.120" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177 peer_label="unconfined" Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer" member="Change" mask="send" name="ca.desrt.dconf" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370 peer_label="unconfined" Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel: [10131.880788] audit: type=1400 audit(1580237490.777:123):
[Desktop-packages] [Bug 1877666] Re: Python syntax warning in LayoutLoaderSVG.py
Also seen during upgrade from 18.04 to 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1877666 Title: Python syntax warning in LayoutLoaderSVG.py Status in onboard package in Ubuntu: New Bug description: This concerns onboard 1.4.1-2ubuntu7 in Ubuntu focal. Seen during package installation: [...] Setting up onboard (1.4.1-2ubuntu7) ... /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma? raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \ [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1877666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
i changed /usr/bin/python3.[0-6] mr, to /usr/bin/python3.[0-7] mr, and the python message disappeared while starting firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1861408 Title: firefox apparmor messages Status in apparmor package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint 19.3. i see there is newer ubuntu version in https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for apparmor. i have not found a page for firefox bugs in linux mint sites, so i belive i should report here. but i have also asked about that in linux mint's irc and then github. i have enabled apparmor for firefox and see these types of messages in syslog: Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000 pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined") Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5525.077960] audit: type=1400 audit(1580226276.440:27): apparmor="DENIED" operation="capable" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948 comm="firefox" capability=21 capname="sys_admin" Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon" member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/Private/RemoteVolumeMonitor" interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported" mask="send" name=":1.35" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="ListMounts2" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="LookupMount" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000 pid=15948 comm="/usr/lib/firefox/firefox " label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)") Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.120" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177 peer_label="unconfined" Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer" member="Change" mask="send" name="ca.desrt.dconf" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370 peer_label="unconfined" Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel: [10131.880788] audit: type=1400 audit(1580237490.777:123): apparmor="DENIED" operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720 comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000 these appeared while saving a file:
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
appeared when opening a file from a manually mounted partition: May 6 14:59:12 dinar-comp kernel: [544099.237323] audit: type=1400 audit(1588766352.217:3081): apparmor="DENIED" operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/run/user/1000/ICEauthority" pid=6886 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 linux and firefox were upgraded, firefox profile file was changed, i copied new changes to my file. appeared when starting firefox after system upgrade and reboot: except dbus messages: May 9 15:00:47 dinar-comp kernel: [ 227.464788] audit: type=1400 audit(1589025647.896:44): apparmor="DENIED" operation="open" profile="firefox" name="/run/user/1000/ICEauthority" pid=2086 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 May 9 15:00:49 dinar-comp kernel: [ 229.423946] audit: type=1400 audit(1589025649.856:45): apparmor="DENIED" operation="file_mmap" profile="firefox//lsb_release" name="/usr/bin/python3.7" pid=2115 comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 i have a local file pinned, and tabs are restored after restart, the "/run/user/1000/ICEauthority" may be because of it. (as in the may 6 message above). appear when pressing ctrl+o: May 9 15:23:33 dinar-comp kernel: [ 1592.754371] audit: type=1400 audit(1589027013.231:63): apparmor="DENIED" operation="open" profile="firefox" name="/home/dinar/.xsession-errors" pid=2086 comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 May 9 15:23:36 dinar-comp kernel: [ 1596.437062] audit: type=1400 audit(1589027016.916:65): apparmor="DENIED" operation="open" profile="firefox" name="/run/mount/utab" pid=2086 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1861408 Title: firefox apparmor messages Status in apparmor package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint 19.3. i see there is newer ubuntu version in https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for apparmor. i have not found a page for firefox bugs in linux mint sites, so i belive i should report here. but i have also asked about that in linux mint's irc and then github. i have enabled apparmor for firefox and see these types of messages in syslog: Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000 pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined") Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5525.077960] audit: type=1400 audit(1580226276.440:27): apparmor="DENIED" operation="capable" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948 comm="firefox" capability=21 capname="sys_admin" Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon" member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/Private/RemoteVolumeMonitor" interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported" mask="send" name=":1.35" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="ListMounts2" mask="send" name=":1.10" pid=15948 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262 peer_label="unconfined" Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="LookupM
[Desktop-packages] [Bug 1876606] Re: colord erros in varlog which causes display to fail
Logs from var/log directory ** Attachment added: "varLogTraces.tgz" https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1876606/+attachment/5368983/+files/varLogTraces.tgz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1876606 Title: colord erros in varlog which causes display to fail Status in colord package in Ubuntu: Incomplete Bug description: Sometime I experience that I'm not able to login my Virutal Ubuntu Machine. Couldn't see any error pop-up. In varlog I see below errors at similar timings: 1049 May 3 18:53:10 KUMAR-PC colord[1135]: failed to get edid data: EDID length is too small 1054 May 3 18:53:11 KUMAR-PC gsd-color[1067]: failed to get edid: unable to get EDID for output 1055 May 3 18:53:11 KUMAR-PC gnome-shell[975]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation 1056 May 3 18:53:12 KUMAR-PC gsd-color[1067]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output Let me know if more info is needed. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: colord 1.3.3-2build1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 3 19:25:47 2020 InstallationDate: Installed on 2020-04-07 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1876606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877735] Re: Video playback is choppy
** Package changed: ubuntu => xorg (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/1877735 Title: Video playback is choppy Status in xorg package in Ubuntu: New Bug description: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Nov 9 16:56:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877735] [NEW] Video playback is choppy
You have been subscribed to a public bug: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Nov 9 16:56:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance third-party-packages ubuntu -- Video playback is choppy https://bugs.launchpad.net/bugs/1877735 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1876606] Re: colord erros in varlog which causes display to fail
I'm trying to reproduce it again but couldn't find exact same error behavior is quite same. I was facing this problem when, I was trying to connection my Ubuntu machine via xrdp which is installed on VirtualBox on Windows 10 host. I can see that XRDP login is successful, but rather than landing on Desktop screen I'm landing on a login screen, which says "Authentication is required to create a color managed device". And when I provide credential then it blinks and I see same screen again. This time I got different error traces than before in /var/syslog. Below are traces: Some errors related to XRDP: May 9 13:19:20 KUMAR-PC xrdp[1918]: (1918)(140104060426048)[ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied May 9 13:19:27 KUMAR-PC xrdp-sesman[1869]: (1869)(139642876421440)[ERROR] g_tcp_bind(9, 6010) failed bind IPv6 (errno=98) and IPv4 (errno=22). Then some segfault in X11 library: May 9 13:19:29 KUMAR-PC kernel: [ 610.613426] VBoxClient[2010]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] And finally different set of errors related to gsd-sharing: May 9 13:19:35 KUMAR-PC gsd-sharing[2190]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded. May 9 13:19:35 KUMAR-PC gsd-sharing[2190]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. May 9 13:19:35 KUMAR-PC gsd-sharing[2190]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. May 9 13:19:35 KUMAR-PC gsd-sharing[2190]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded. May 9 13:19:35 KUMAR-PC gsd-media-keys[2231]: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied Similar gsd-color, related error as before: May 9 13:19:36 KUMAR-PC gsd-color[2223]: failed to get edid: unable to get EDID for output Then continuous crashes in X11 and some errors in gsd-color: May 9 13:19:41 KUMAR-PC kernel: [ 622.713229] VBoxClient[2400]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:19:46 KUMAR-PC kernel: [ 628.066421] VBoxClient[2407]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:19:51 KUMAR-PC kernel: [ 633.369511] VBoxClient[2415]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:19:57 KUMAR-PC kernel: [ 638.761881] VBoxClient[2423]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:01 KUMAR-PC gsd-color[2223]: failed to create device: Timeout was reached May 9 13:20:01 KUMAR-PC gsd-color[2223]: failed to get devices: Timeout was reached May 9 13:20:02 KUMAR-PC kernel: [ 644.128581] VBoxClient[2430]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:08 KUMAR-PC kernel: [ 649.471082] VBoxClient[2441]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:13 KUMAR-PC kernel: [ 654.786431] VBoxClient[2451]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:18 KUMAR-PC kernel: [ 660.122171] VBoxClient[2458]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:24 KUMAR-PC kernel: [ 665.466061] VBoxClient[2465]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:29 KUMAR-PC kernel: [ 670.779317] VBoxClient[2472]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:34 KUMAR-PC kernel: [ 676.085570] VBoxClient[2479]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:40 KUMAR-PC kernel: [ 681.400352] VBoxClient[2507]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] And blah blah: May 9 13:20:45 KUMAR-PC colord[1297]: failed to get seat for session c2 [pid 2223]: No data available May 9 13:20:45 KUMAR-PC gsd-color[1232]: no xrandr-rdp0 device found: Failed to find output xrandr-rdp0 May 9 13:20:45 KUMAR-PC kernel: [ 686.878261] VBoxClient[2551]: segfault at 968 ip 7f7c21a8c6ad sp 7fff970e0a20 error 4 in libX11.so.6.3.0[7f7c21a58000+133000] May 9 13:20:45 KUMAR-PC kernel: [ 687.028638] traps: gsd-color[2223] trap divide error ip:55dd2458194a sp:7ffe88a63da0 error:0 in gsd-color[55dd24578000+12000] May 9 13:20:52 KUMAR-PC gsd-xs
[Desktop-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
askubuntu link was wrong... correct link: https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb- soundcard/1236257#1236257 -- 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/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: New Bug description: Please see https://askubuntu.com/posts/1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for some users but not for others Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all users UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 10/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5222 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x: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 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877726] [NEW] [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
Public bug reported: Please see https://askubuntu.com/posts/1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for some users but not for others Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all users UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 10/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5222 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x: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 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "alsa-info.txt.eWNOZAwySG" https://bugs.launchpad.net/bugs/1877726/+attachment/5368861/+files/alsa-info.txt.eWNOZAwySG -- 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/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: New Bug description: Please see https://askubuntu.com/posts/1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog]
[Desktop-packages] [Bug 1877727] [NEW] Nvidia dGPU active despite prime-select set to Intel card
Public bug reported: After fresh installation of Ubuntu 20.04 I changed used card to Intel GPU with command "sudo prime-select intel". After reboot Intel card is used to display, but dGPU is still active (more heat and power consumption, this laptop also has led that indicate dGPU activation). In Ubuntu 19.04 which I used till today, after change to iGPU, laptop use iGPU and dGPU is in inactive state. I have MSI PE70 7RD laptop with Intel 7700HQ processor and NVIDIA 1050 GPU. I found similar problem on net, but without solution. https://askubuntu.com/questions/1232461/ubuntu-20-04-dgpu-is-always-on Workaround that I found is use "powertop" and in Tunables card activate power saving for dGPU card "Runtime PM for PCI Device NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile]", but I think it should work without such changes every reboot. Description:Ubuntu 20.04 LTS Release:20.04 nvidia-prime: Installed: 0.8.14 Candidate: 0.8.14 Version table: *** 0.8.14 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 11:38:41 2020 Dependencies: InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (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 nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card Status in nvidia-prime package in Ubuntu: New Bug description: After fresh installation of Ubuntu 20.04 I changed used card to Intel GPU with command "sudo prime-select intel". After reboot Intel card is used to display, but dGPU is still active (more heat and power consumption, this laptop also has led that indicate dGPU activation). In Ubuntu 19.04 which I used till today, after change to iGPU, laptop use iGPU and dGPU is in inactive state. I have MSI PE70 7RD laptop with Intel 7700HQ processor and NVIDIA 1050 GPU. I found similar problem on net, but without solution. https://askubuntu.com/questions/1232461/ubuntu-20-04-dgpu-is-always-on Workaround that I found is use "powertop" and in Tunables card activate power saving for dGPU card "Runtime PM for PCI Device NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile]", but I think it should work without such changes every reboot. Description: Ubuntu 20.04 LTS Release: 20.04 nvidia-prime: Installed: 0.8.14 Candidate: 0.8.14 Version table: *** 0.8.14 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 11:38:41 2020 Dependencies: InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696594] Re: gnome-font-viewer crashed with SIGSEGV
I appreciate some considerable time has passed since this bug was reported. Does it still occur with newer versions of the font viewer? Was there (if you recall) a particular font file which triggered this? ** Changed in: gnome-font-viewer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1696594 Title: gnome-font-viewer crashed with SIGSEGV Status in gnome-font-viewer package in Ubuntu: Incomplete Bug description: The viewer crashes immediately after trying to open a font file from the file manager. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-font-viewer 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jun 7 17:29:50 2017 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2017-01-29 (129 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170118) ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SegvAnalysis: Segfault happened at: 0x7fc08bd7f6ea:mov0x50(%r12),%rdi PC (0x7fc08bd7f6ea) ok source "0x50(%r12)" (0x00f0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-font-viewer StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-font-viewer crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-06-04 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1696594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662440] Re: Unable to import FNMT certificates in chromium or chrome
In reply to comment #13. After Olivier reported a clean fresh install showed no such issues, tried the closest to that I could do on my existing install, which was moving out the way my current user Chromium .cache/chromium and .config/chromium directories. Started Chromium and it worked as expected regarding the certificates in this Bug report. With still using Spanish as the system , environment and browser language. So whatever the problem is, seems to only affect users with : - Non-clean Chromium installs - Running on Spanish (or otherwise non default system language) - And only for some certificates, such as some of the ones used in the public administration in Spain (works for the root CA but fails for intermediate CA) So anyone hitting this would probably good with moving away the user's $HOME/.cache/chromium/ and $HOME/.config/chromium/ directories, and starting Chromium again. -- 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/1662440 Title: Unable to import FNMT certificates in chromium or chrome Status in chromium-browser package in Ubuntu: Incomplete Bug description: Hi, there's an "unknown error" when you try to import certificates from the FNMT on Chrome or derivatives. There's an error when you try to import the personal certificate, but also when you try to import the CA certificates from the FNMT. Here you can download the AC certificates: https://www.sede.fnmt.gob.es/descargas/certificados-raiz-de-la-fnmt (spanish) Direct links: https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM_SHA256.cer 2nd class: https://www.sede.fnmt.gob.es/documents/10445900/10526749/FNMTClase2CA.cer ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 Uname: Linux 4.8.8-040808-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA4o0pnAQEBAQ0TAQOgLx54Kg61qlE3qyUUUFS/74CBwIFAgYCLwJUAkECzAHFPITmQMGIaJ0AYsDZA2igRAAAc/QA4Sx9TEQAKICAgICAg/ABQMjIxVwogICAgICAg/wA5MzEwMDk0NE5CCiAgASECAxtiIwl/B4MBAABnAwwAIACALUMBEATiAA8AADYAQOhjAAAaGh0AgFHQHCBAgDUAQIRjAAAclQ== modes: 1680x1050 1920x1080 1920x1080 1400x1050 1280x1024 1280x1024 1440x900 1280x960 1360x768 1152x864 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-eDP-1: enabled: disabled dpms: Off status: connected edid-base64: AP///wAGr50hAAAVAQSQJhV4AsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBFDeAwHA4IEAwZDYAfdYQAAAYuCSAwHA4IEAwZDYAfdYQAAAYAgAMM/kKPGQfFCJuICAgAMs= modes: 1920x1080 1920x1080 Date: Tue Feb 7 08:12:37 2017 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2016-08-01 (189 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Load-Avg-1min: 1.07 Load-Processes-Running-Percent: 0.1% MachineType: Hewlett-Packard HP ENVY 17 Notebook PC SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1966 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.49 dmi.chassis.asset.tag: 5CG35023TQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd10/03/2013:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088410305B0620100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088410305B0620100 dmi.sys.vendor: Hewlett-Packard gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sou
[Desktop-packages] [Bug 1877717] [NEW] Sound stop working after wakeup
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 I don't know how to reproduce this bug. Sometimes after notebook wakup sound stop working. pulseaudio -k fixes this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1925 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 15:43:32 2020 InstallationDate: Installed on 2018-04-03 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83C9 dmi.board.vendor: HP dmi.board.version: 32.59 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV NOTEBOOK dmi.product.name: HP Envy dmi.product.sku: 2PQ29EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877717 Title: Sound stop working after wakeup Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I don't know how to reproduce this bug. Sometimes after notebook wakup sound stop working. pulseaudio -k fixes this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1925 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 15:43:32 2020 InstallationDate: Installed on 2018-04-03 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83C9 dmi.board.vendor: HP dmi.board.version: 32.59 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV NOTEBOOK dmi.product.name: HP Envy dmi.product.sku: 2PQ29EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I can confirm this is still an issue. The odd part is, however, that I did not have this issue on 19.10 with the nvidia drivers from the ppa. Upgrading to 20.04 introduced this issue to me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https:/
[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect
I have the latest Ubuntu 20.04 and it also seems to have this bug. There are workarounds, but I think it should work out of the box like it does on Windows. It is weird to have this kind of bug as Xbox One controller might just be the most popular controller and these kinds of issues prevent people from gaming on Linux. -- 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/1750146 Title: Xbox (One) Wireless Controller won't connect Status in gnome-control-center: Confirmed Status in Linux: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center. Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode. This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB). Please fix. See the attached system information below. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 09:26:14 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
v13.99.1 fix also works for me, but I also need to remove "~/.config/pulse" and "sudo alsa force-reload". 1. Upgrade pulse; Doesn't work 2. Upgrade + Reload; Doesn't work 3. Upgrade + Remove config + Reload; Works -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877711] [NEW] Libreoffice can read but not save files over SSH
Public bug reported: With Ubuntu 20.04 libreoffice can not anymore save files over SSH share. When trying to save, it says: Error saving the document. General Error. General input/output error. In addition, starting from Ubuntu 20.04 libreoffice has become very slow to start. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877711 Title: Libreoffice can read but not save files over SSH Status in libreoffice package in Ubuntu: New Bug description: With Ubuntu 20.04 libreoffice can not anymore save files over SSH share. When trying to save, it says: Error saving the document. General Error. General input/output error. In addition, starting from Ubuntu 20.04 libreoffice has become very slow to start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877712] Re: Severe performance degradation in Gnome Shell after upgrade to 20.04
The log file is absolutely flooded with errors like: May 9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on MetaDisplay 0x555ad20ba000. May 9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on MetaDisplay 0x555ad20ba000. May 9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on MetaDisplay 0x555ad20ba000. May 9 08:53:48 volga gnome-shell[3395]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 9 08:53:48 volga gnome-shell[3395]: The offending signal was notify on MetaDisplay 0x555ad20ba000. -- 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/1877712 Title: Severe performance degradation in Gnome Shell after upgrade to 20.04 Status in gnome-shell package in Ubuntu: New Bug description: Severe performance degradation in Gnome Shell after upgrade to 20.04 - everything is slow, even moving the mouse through a right-click menu has a severely delayed selection animation. Video displaying the problem: https://drive.google.com/open?id=1rAKN- ZKks6o9d37hQMbnMgNeAOy8VZyp ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 08:57:02 2020 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1178 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877712] [NEW] Severe performance degradation in Gnome Shell after upgrade to 20.04
Public bug reported: Severe performance degradation in Gnome Shell after upgrade to 20.04 - everything is slow, even moving the mouse through a right-click menu has a severely delayed selection animation. Video displaying the problem: https://drive.google.com/open?id=1rAKN- ZKks6o9d37hQMbnMgNeAOy8VZyp ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 08:57:02 2020 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1178 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago) ** 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/1877712 Title: Severe performance degradation in Gnome Shell after upgrade to 20.04 Status in gnome-shell package in Ubuntu: New Bug description: Severe performance degradation in Gnome Shell after upgrade to 20.04 - everything is slow, even moving the mouse through a right-click menu has a severely delayed selection animation. Video displaying the problem: https://drive.google.com/open?id=1rAKN- ZKks6o9d37hQMbnMgNeAOy8VZyp ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 08:57:02 2020 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1178 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp