[Desktop-packages] [Bug 1998111] Re: Quectel EM05-G not being unlocked
Works fine for me with Ubuntu 23.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1998111 Title: Quectel EM05-G not being unlocked Status in modemmanager package in Ubuntu: Confirmed Bug description: Despite support being in fcc-unlock.d Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd. Quectel EM05-G the modem remains locked and enabling it fails: jak@jak-t14-g3:~:master$ mmcli -m any -e error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition' Doing something like # modprobe -r cdc_mbim # modprobe cdc_mbim # mbimcli --device-open-proxy --device="/dev/wwan0mbim0" --quectel-set-radio-state=on # systemctl RestartModemManager # mmcli -m any -e makes it work. Peculiar it seems that the mbim-proxy process that ModemManager started is hanging and causing the mbimcli command to time out (if I just run it manually). Further investigation warranted, tips welcome. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: modemmanager 1.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Nov 28 13:54:07 2022 InstallationDate: Installed on 2022-11-26 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1998111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
I think I had the same issue on 23.04 and changing the setting to Wayland fixed it for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 Status in mutter package in Ubuntu: Triaged Bug description: This morning, I upgraded gnome-shell and gnome-shell-common from 42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer renders properly. Notice the missing image header on the Ubuntu website and the garbled right click menu here: https://i.imgur.com/BPnqfVG.png I downgraded gnome-shell and gnome-shell-common version to 42.0-2ubuntu1, restarted gnome, and the rendering issues went away: https://i.imgur.com/CzEPgqY.png I upgraded gnome-shell and gnome-shell-common again to the latest and the rendering issues came back. Going to chrome://settings/system and disabling hardware acceleration fixes the rendering issues (but now I don't have hardware acceleration). I'm running the latest stable version of chrome which was released a few weeks ago: 114.0.5735.198 --- $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 (phased 40%) 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
I tried reporting my most recent crash but ubuntu-bug just exits immediately when I try to send the report with 'ubuntu-bug ' and pressing S afterwards. I'll continue trying to report it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
I upgraded to mutter to 44.3-0ubuntu1 but am still experiencing crashes after resume from lock screen. Log output: Jul 17 16:13:59 ThinkPad-T14-flb kernel: gnome-shell[4048]: segfault at ff48 ip 7f9efa316ebb sp 7ffd043ed2d8 error 5 in libmutter-clutter-12.so.0.0.0[7f9efa2b4000+8b000] likely on CPU 14 (core 7, socket 0) Jul 17 16:13:59 ThinkPad-T14-flb kernel: Code: 30 48 85 c0 74 09 c3 0f 1f 84 00 00 00 00 00 48 8b 47 68 48 85 c0 75 ee 48 8b 47 28 c3 66 90 f3 0f 1e fa 48 63 05 b5 e7 07 00 <48> 8b 44 38 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 Please let me know if and how I can assist in further debugging. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic package, but the linux-image-6.2.0-25-generic package has been available for some time. Package upgrades therefore insist on switching to nvidia- dkms, no matter what I try to do. So I'm still on 6.2.0-24. Is this just another aspect of this bug, or is the linux-objects- nvidia-* package discontinued and we are actually supposed to switch to dkms? -- 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/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
Is there a way to test the fix with Ubuntu Lunar? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
I'm using a ThinkPad T14 (AMD) Gen 1 connected to a 38" LG monitor via USB-C using DisplayPort alternate mode. I can quite reliably reproduce the crash, it happens a few times per day when resuming from a locked screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
If there is anything I can do to assist in getting this bug fixed, please let me know. Today I had two crashes on resume from the lock screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I just opened Evince from the command line ('evince' -> Enter) and am
seeing this error:
Entity: line 41: parser error : Extra content at the end of the document
endstream
It could be totally unrelated to this bug though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1969896
Title:
Evince Document Viewer(42.0) does not remember last page in 22.04 and
opens in a tiny window when launched
Status in evince package in Ubuntu:
Confirmed
Bug description:
Just switched from Ubuntu 20.04 to 22.04 and realized that Document
Viewer no longer open on the last viewed page and doesn't remember the
side pane preference even after using the "Save Current Settings as
Default" option. Kindly advise
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.1-3
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:58:50 2022
InstallationDate: Installed on 2022-03-19 (34 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I upgraded from 21.10 to 22.04. The issue happens when using a Wayland session or an Xorg session. My userdir is a local one. There is nothing special about my configuration. One thing that might be noteworthy is that before upgrading I was using the night mode of Evince and now it is stuck in night mode. I can disable night mode but this is not saved, meaning that when I close Evince and open it again it is back to night mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
One extra observation: when I use "xset dpms force off" to send the display to sleep, it stays in sleep indefinitely until the next user input, so apparently g-s-d never touches the power state. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
I'm using Xorg 2:21.1.3-2ubuntu2, with kms on "Intel Iris Plus Graphics (G7)". Xorg.0.log attached as well. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+attachment/5586349/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1971434/+attachment/5586348/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1971434/+attachment/5586347/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
apport information ** Tags added: apport-collected ** Description changed: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-07-04 (667 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + Package: gnome-settings-daemon 42.1-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + Tags: jammy + Uname: Linux 5.15.0-27-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1971434/+attachment/5586346/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
OK, have also reported this against gstreamer-vaapi as https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1971463 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] [NEW] Display powersave only blanks, but does not turn off
Public bug reported: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: New Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
One more datapoint, vlc seems to be using VAAPI on the same machine & distro without issues: ``` $ vlc big_buck_bunny_720p_surround.mp4 VLC media player 3.0.16 Vetinari (revision 3.0.13-8-g41878ff4f2) [55cebcc6f580] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [7f9b1c003e50] gl gl: Initialized libplacebo v4.192.1 (API v192) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7f9b39141220] avcodec decoder: Using Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 () for hardware decoding ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Update: can confirm that this issue can be worked around by uninstalling gstreamer1.0-vaapi package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
I'm pretty sure this is not a Totem issue, but rather a GStreamer issue. E.g. for the linked video, if I try to play it through playbin on Jammy (`gst-launch-1.0 playbin uri=file:///home/floe/Downloads/big_buck_bunny_720p_surround.mp4`), I get a black window with the audio track playing in the background. Same happens for any movie that also has the same issue with Totem. Running with GST_DEBUG=3 gives a lot of ``` 0:00:00.381581482 183712 0x7f5f6c05b640 ERROR vaapivideomemory gstvaapivideomemory.c:254:map_vaapi_memory: failed to make image current 0:00:00.381663666 183712 0x7f5f6c05b640 ERRORdefault video-frame.c:168:gst_video_frame_map_id: failed to map video frame plane 0 0:00:00.381711318 183712 0x7f5f6c05b640 WARN xvimagesink xvimagesink.c:1038:gst_xv_image_sink_show_frame: could not map image ``` so this may be VAAPI-related? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966637] Re: don't have good text copy method like on android / ios as using touch monitor, firefox snap
I cleanly installed Jammy Jellyfish today on my Thinkpad X1 Yoga 3rd Gen and can confirm, that with the snap version of firefox neither the gnome on screen keyboard is triggered nor can one scroll with touch. After removing the snap version and installing the deb version from the Mozilla Team PPA both issues work out of the box -- 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/1966637 Title: don't have good text copy method like on android / ios as using touch monitor, firefox snap Status in OEM Priority Project: New Status in firefox package in Ubuntu: Incomplete Bug description: don't have a good text copy method like on android/ios as using a touch monitor OS: jammy update @ 2022/03/28 firefox snap: 98.0.2-1 r1154 it's not good on URL entry or text entry box on the HTML page. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
I still see this error on Ubuntu 21.10 with speech-dispatcher 0.10.2-2build1 so the fix @linmanfu mentions unfortunately did not help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: Some (or all) desktop icons are missing
Hello, This issue is still on, and even if it's «low» issue, it's really disturbing because 20.04 is LTS. I planned to move dozens of computers from 18.04 to 20.04, but seeing how my users rely on desktop to keep many files, I can see how painful it will be to move on 20.04, even though alt F2 + r works fine. Is there anything, besides coding, that could be done to help taking down this issue ? Thanks, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
@jakoblell, I had hoped for the same solution, but it does _not_ work for me that way. Even when starting it manually, it will show its icon in the dock, and after a while, the same problem happens for me. -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
Hm, for me it's not intermittent at all. It happens as soon as I've sent a single message using Thunderbird; Gnome Shell simply becomes unable to keep track of Thunderbird windows, and the window switcher can't launch any more. -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
Can someone explain why this bug seems to be such low priority? It makes using the Gnome Shell nearly impossible for anyone who uses Thunderbird, as it stops any meaningful switching between windows, and massively interferes with even the most basic workflow. -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
Not sure whether the upstream issue, which is several months old, is the same. The present one seems to have kicked in for several users at the same time at the end of June 2021. It looks like it is somehow connected to Thunderbird. Also see this comment, for one way of reproducing it: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1934527/comments/4 I can also confirm that it does not seem to occur if Thunderbird isn't running at all. -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926075] [NEW] Dock hidden after unlocking screen with multiple monitors
Public bug reported: I'm running Ubuntu 20.04 with gnome-shell-extension-ubuntu-dock version 68ubuntu1~20.04.1. I have multiple monitors (three) connected to my Ubuntu machine, and I've set the middle screen as the "main" one (the one where the Dock and the top bar are displayed on). When I have an application running in Fullscreen (for example, Chromium) on the middle monitor where the dock is, everything is working as intended. I can lock the screen, unlock it again, and everything is like I left it. If I do the same thing (application in fullscreen) on the right monitor, everything works just fine, too. However, if I run a fullscreen application on the left monitor, then lock and unlock the screen, the dock on the middle monitor is gone. The top bar (the one that says "Activities", the application name, current date & time, ...) is still present, but the dock is gone. I either need to disable fullscreen in the application that's on the left screen, or I click on the "Activities" button to open the app drawer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 14:24:39 2021 InstallationDate: Installed on 2019-08-17 (617 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-05-09 (350 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1926075 Title: Dock hidden after unlocking screen with multiple monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 with gnome-shell-extension-ubuntu-dock version 68ubuntu1~20.04.1. I have multiple monitors (three) connected to my Ubuntu machine, and I've set the middle screen as the "main" one (the one where the Dock and the top bar are displayed on). When I have an application running in Fullscreen (for example, Chromium) on the middle monitor where the dock is, everything is working as intended. I can lock the screen, unlock it again, and everything is like I left it. If I do the same thing (application in fullscreen) on the right monitor, everything works just fine, too. However, if I run a fullscreen application on the left monitor, then lock and unlock the screen, the dock on the middle monitor is gone. The top bar (the one that says "Activities", the application name, current date & time, ...) is still present, but the dock is gone. I either need to disable fullscreen in the application that's on the left screen, or I click on the "Activities" button to open the app drawer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 14:24:39 2021 InstallationDate: Installed on 2019-08-17 (617 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-05-09 (350 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1926075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924861] [NEW] nvidia random crashes back to login screen
Public bug reported: sometimes, when I click on some application in the panel e.g discord/firefox/chrome Xorg crashes and takes me back to login screen dmesg error: [205084.240560] NVRM: Xid (PCI::01:00): 31, pid=1673, Ch 0009, intr 1000. MMU Fault: ENGINE CE0 HUBCLIENT_CE0 faulted @ 0x1_02764000. Fault is of type FAULT_PTE ACCESS_TYPE_READ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 17 17:12:48 2021 DistUpgraded: 2020-11-28 16:24:27,019 DEBUG entry '# deb http://ppa.launchpad.net/jeremysanders/ppa/ubuntu focal main # Bei Aktualisierung zu bionic deaktiviert Bei Aktualisierung zu focal deaktiviert' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-71-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3283] InstallationDate: Installed on 2016-09-09 (1681 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=21ee0900-9162-4298-bd0e-5dbd103514f0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-28 (139 days ago) dmi.bios.date: 01/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: Default string dmi.board.name: B150 PRO GAMING/AURA 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.:bvr0501:bd01/26/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150PROGAMING/AURA: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: sometimes, when I click on some application in the panel e.g discord/firefox/chrome Xorg crashes and takes me back to login screen + + dmesg error: + [205084.240560] NVRM: Xid (PCI::01:00): 31, pid=1673, Ch 0009, intr 1000. MMU Fault: ENGINE CE0 HUBCLIENT_CE0 faulted @ 0x1_02764000. Fault is of type FAULT_PTE ACCESS_TYPE_READ + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0'
[Desktop-packages] [Bug 1922187] [NEW] [snap] No menu on i3wm/xorg
Public bug reported: Description No menu is shown in applications when installed with snap. Startup of libreoffice is extremely slow. When installing with "apt install libreoffice" menus are shown and startup is very fast. Expected: Menu bar is shown Actual: Menu bar is not shown Setup Ubuntu server 20.04.2 LTS i3 4.17.1 sudo X -version gives: X.Org X Server 1.20.9 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.15.0-130-generic x86_64 Ubuntu Current Operating System: Linux dev 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=/dev/mapper/ubuntu--vg-lv--0 ro Build Date: 17 January 2021 09:13:31AM xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- 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/1922187 Title: [snap] No menu on i3wm/xorg Status in libreoffice package in Ubuntu: New Bug description: Description No menu is shown in applications when installed with snap. Startup of libreoffice is extremely slow. When installing with "apt install libreoffice" menus are shown and startup is very fast. Expected: Menu bar is shown Actual: Menu bar is not shown Setup Ubuntu server 20.04.2 LTS i3 4.17.1 sudo X -version gives: X.Org X Server 1.20.9 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.15.0-130-generic x86_64 Ubuntu Current Operating System: Linux dev 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic root=/dev/mapper/ubuntu--vg-lv--0 ro Build Date: 17 January 2021 09:13:31AM xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1922187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898389] Re: browser frequently crashing with trap int3
Getting those traps as well, don't know if it is because of the snap usage or chromium: [941728.747452] traps: chrome[1912045] trap int3 ip:559081754d9e sp:7ffe0c20d510 error:0 in chrome[55907cad+780d000] [941731.964290] traps: chrome[1912059] trap int3 ip:559081754d9e sp:7ffe0c213e40 error:0 in chrome[55907cad+780d000] -- 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/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Expired Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages *** 85.0.4183.83-0ubuntu0.16.04.2 100 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 18.0.1025.151~r130497-0ubuntu1 500 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages dmesg: [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 sp:7ffdfc31ca70 error:0 [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 sp:7ffd8fc04770 error:0 [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 sp:7ffdfc31b2c0 error:0 [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be sp:7ffdfc31bd40 error:0 [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 sp:7ffdfc31cab0 error:0 [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 sp:7ffdfc31b300 error:0 [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 sp:7ffdfc31c640 error:0 [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be sp:7ffdfc31a6a0 error:0 [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 sp:7fe1dcaf95e0 error:0 [519367.329864] traps: chromium-browse[24588] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.357674] traps: chromium-browse[24558] trap invalid opcode ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 sp:7ffdfc316260 error:0 [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 sp:7ffdfc31abd0 error:0 [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be sp:7ffdfc31bbb0 error:0 [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 sp:7ffdfc31d020 error:0 [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 sp:7ffdfc3165c0 error:0 [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 sp:7ffdfc3164c0 error:0 [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 sp:7ffdfc31c5b0 error:0 [519429.841404] traps: chromium-browse[24906] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
FYI, here's the corresponding bug in GNOME: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/108 And here's the workaround: https://wrgms.com/disable-mouse-battery-low- spam-notification/ ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #108 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/108 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
Follow-up to Comment #36: Although patching upower fixes the issue, gnome-settings-daemon is still broken, since disabling notifications won't disable all notifications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect
I have the same Problem with my LiDE 60 like Michael. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect Status in simple-scan package in Ubuntu: Triaged Bug description: Scanner: Canon, Inc. CanoScan N1240U/LiDE 30 Ubuntu 14.04, Simple Scan version 3.12.1. Adjusting the settings of brightness and contrast has no effect. With the default for scanning in "text" mode being too bright, this makes "Simple Scan" in text mode unusable for me. Brightness and contrast settings don't work in "foto" mode, too. But the default of the foto mode is usable. Brightness setting does work in program "Skanlite". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
@Hui Wang I installed your package and rebooted. It seems to fix the issue, audio is working as expected again. One thing I noticed is that when I mute the speakers or microphone via their media keys (F1 and F4) the LEDs on the keys don't light up. It may not be related to this issue though because when I activate the FnLock the LED on the Esc key also doesn't light up. -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE 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.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I use this small script based on Giuseppe's findings as a workaround: #!/bin/bash sudo modprobe -r snd_rn_pci_acp3x systemctl --user restart pulseaudio sudo modprobe snd_rn_pci_acp3x -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE 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.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902519] [NEW] KDE shows bad pixels after hibernate
Public bug reported: After hibernation to disk kde shows bad pixels on home screen (look at attached screenshot) sometimes there are also graphics related bugs in other applications when I logout and login again or I do a reboot it works like before maybe it has something to do with the nvidia graphics card? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Nov 2 13:03:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-52-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:850a] Subsystem: CLEVO/KAPOK Computer GP107M [GeForce GTX 1050 Mobile] [1558:850a] MachineType: XMG N85_N87,HJ,HJ1,HK1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=ef695d35-e2d0-422a-bb31-ef1dec2df0e0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.19 dmi.board.asset.tag: Tag 12345 dmi.board.name: N85_N87,HJ,HJ1,HK1 dmi.board.vendor: XMG dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: XMG dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.19:bd12/02/2017:svnXMG:pnN85_N87,HJ,HJ1,HK1:pvrNotApplicable:rvnXMG:rnN85_N87,HJ,HJ1,HK1:rvrNotApplicable:cvnXMG:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N85_N87,HJ,HJ1,HK1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: XMG version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 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.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal kubuntu third-party-packages ubuntu ** Attachment added: "This is a screenshot" https://bugs.launchpad.net/bugs/1902519/+attachment/5430234/+files/nvidia-bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902519 Title: KDE shows bad pixels after hibernate Status in xorg package in Ubuntu: New Bug description: After hibernation to disk kde shows bad pixels on home screen (look at attached screenshot) sometimes there are also graphics related bugs in other applications when I logout and login again or I do a reboot it works like before maybe it has something to do with the nvidia graphics card? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/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.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Nov 2 13:03:10 2020 DistUpgraded: Fresh
[Desktop-packages] [Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
OK, so deletion of pulse config helped. First deletion only temporarly and the weird behavior came back after some switching. But after the second one it seems to be permanently fixed and I can't reproduce the faulty behavior. So I assume it can be seen as fixed?! If it happens again and is reproducible, I'll report again. Thank you for your help! -- 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/1901538 Title: Output Device selection messed (Line Out <-> HDMI) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: [System] - Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled - pulseaudio 1:13.99.1-1ubuntu3.7 - NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450 - Monitor with build-in (stereo) speakers connected via HDMI to graphics card - External (stereo) speakers connected via audio jack to mainboard [Expected Behavior] 1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device" 2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" 3. The switching should enable the chosen output device. [Bug Description and Behavior] If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers. [Workaround] While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active. [Further comments] I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed. At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:15:41 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-26 (0 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/1901538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901538] [NEW] Output Device selection messed (Line Out <-> HDMI)
Public bug reported: [System] - Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled - pulseaudio 1:13.99.1-1ubuntu3.7 - NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450 - Monitor with build-in (stereo) speakers connected via HDMI to graphics card - External (stereo) speakers connected via audio jack to mainboard [Expected Behavior] 1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device" 2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" 3. The switching should enable the chosen output device. [Bug Description and Behavior] If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers. [Workaround] While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active. [Further comments] I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed. At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:15:41 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-26 (0 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 -- 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/1901538 Title: Output Device selection messed (Line Out <-> HDMI) Status in gnome-control-center package in Ubuntu: New Bug description: [System] - Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled - pulseaudio 1:13.99.1-1ubuntu3.7 - NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450 - Monitor with build-in (stereo) speakers connected via HDMI to graphics card - External (stereo) speakers connected via audio jack to mainboard [Expected Behavior] 1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device" 2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" 3. The switching should enable the chosen output device. [Bug Description and Behavior] If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers. [Workaround] While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active. [Further comments] I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed. At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:15:41 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
Clarification: this bug ist not about wrong battery Level measurements (Nobody reported that), it's about users being unable to disable notifications. The notification is shown even when in DND mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893729] Re: Keyboard shortcuts stop working
Hi, see https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1893737 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1893729 Title: Keyboard shortcuts stop working Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: On Groovy keyboard shortcuts and media keys stopped working. Reproducible on a fresh installation and an upgrade of an installed system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0 Uname: Linux 5.8.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 07:16:50 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-31 (92 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 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-settings-daemon/+bug/1893729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893737] [NEW] gnome-settings-daemon_3.37.0-1ubuntu1 breaks keyboard shortcuts, media keys and backlight controls
Public bug reported: groovy (devel branch) Affected version: gnome-settings-daemon_3.37.0-1ubuntu1 Not affected: gnome-settings-daemon_3.36.1-1ubuntu1 and older After upgrading to version gnome-settings-daemon_3.37.0-1ubuntu1, the following broke: - backlight controls (laptop) unresponsive - backlight slider in the top right menu does not change backlight - volume controls (laptop + usb keyboard w. media keys) unresposive - custom gnome-shell keyboard shortcut (ctrl+alt+t) stopped working - creating a new shortcut in gnome-shell (ctrl+alt+e for xeyes) does not start application reverting to gnome-settings-daemon_3.36.1-1ubuntu1 and rebooting fixed the issue. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Summary changed: - 3.37.0-1ubuntu1 breaks keyboard shortcuts + 3.37.0-1ubuntu1 breaks keyboard shortcuts, media keys and backlight controls ** Summary changed: - 3.37.0-1ubuntu1 breaks keyboard shortcuts, media keys and backlight controls + gnome-settings-daemon_3.37.0-1ubuntu1 breaks keyboard shortcuts, media keys and backlight controls ** Description changed: groovy (devel branch) - Affected version: gnome-settings-daemon-3.37.0-1ubuntu1 - Not affected: 3.36.1-1ubuntu1 and older + Affected version: gnome-settings-daemon_3.37.0-1ubuntu1 + Not affected: gnome-settings-daemon_3.36.1-1ubuntu1 and older - - After upgrading to version gnome-settings-daemon-3.37.0-1ubuntu1, the following broke: + After upgrading to version gnome-settings-daemon_3.37.0-1ubuntu1, the following broke: - backlight controls (laptop) unresponsive - backlight slider in the top right menu does not change backlight - volume controls (laptop + usb keyboard w. media keys) unresposive - custom gnome-shell keyboard shortcut (ctrl+alt+t) stopped working - creating a new shortcut in gnome-shell (ctrl+alt+e for xeyes) does not start application - reverting to gnome-settings-daemon-3.36.1-1ubuntu1 and rebooting fixed + reverting to gnome-settings-daemon_3.36.1-1ubuntu1 and rebooting fixed the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1893737 Title: gnome-settings-daemon_3.37.0-1ubuntu1 breaks keyboard shortcuts, media keys and backlight controls Status in gnome-settings-daemon package in Ubuntu: New Bug description: groovy (devel branch) Affected version: gnome-settings-daemon_3.37.0-1ubuntu1 Not affected: gnome-settings-daemon_3.36.1-1ubuntu1 and older After upgrading to version gnome-settings-daemon_3.37.0-1ubuntu1, the following broke: - backlight controls (laptop) unresponsive - backlight slider in the top right menu does not change backlight - volume controls (laptop + usb keyboard w. media keys) unresposive - custom gnome-shell keyboard shortcut (ctrl+alt+t) stopped working - creating a new shortcut in gnome-shell (ctrl+alt+e for xeyes) does not start application reverting to gnome-settings-daemon_3.36.1-1ubuntu1 and rebooting fixed the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1893737/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Issue is fixed for me with mutter 3.36.4. And yes, I got the scaling bug mentioned by Wallo013, too. Although mine isn't that heavy. I use 100 % and something is setting it below that (75 % - 90 %?). If I change scaling to 125 % and back to 100 %, everything is fine. After Relogin or Reboot, scaling is wrong again. But this bug is not linked to multiple screens at least for me, so maybe should get reported in another bug ticket. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
The problem isn't fixed (at least for me). My system: OS: Ubuntu 20.04 - Linux [...] 5.4.0-40-generic [...] x86_64 Graphics: GeForce GTX 650 Ti BOOST, nvidia-driver-440 Monitors: Primary monitor connected via HDMI, secondary rotated monitor connected via display port, staying left from my primary monitor. Before upgrading from 19.10 to 20.04 rotation with gnome-control-center settings worked quiet fine (I only had to configure this once). Now I have the same problem as described above. Each time I power on my secondary monitor I have to manually change orientation by using xrandr commands. Rotating via gnome-control-center results in weird unrotated overlapping display contents. Once configured manually via xrandr, after suspension and wake up the settings are still working. After reboot settings are lost again. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
Some background: rechargeable batteries have 1.2V nominal (compared to 1.5V nominal for regular battteries). Any mouse will report levels around 10%, although the batteries will run for *many* months. So users of rechargeable batteries will experience notifications about low levels basically after a few days of using a rechargeable battery. Although you might very wel argue that "it's a hardware problem", notifications about low mouse / keyboard battery should be optional, not forced upon the user. I have no way to disable the mouse / battery level alarm. (that is BUG #1) Furthermore, if i use DND (which i don't really want to use, but just assumed), the mouse/keyboard alarms are the ONLY alarms that OVERRIDE DND, to "using DND" is not a solution, and DND does in fact disturb in some cases, which is BUG #2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0 native-path: hidpp_battery_0 model:MX Keys Wireless Keyboard serial: 408a-9b-b6-52-57 power supply: no updated: Fr 12 Jun 2020 22:39:07 CEST (8 seconds ago) has history: yes has statistics: yes mouse present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' ** Attachment added: "Screenshot of the notification" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+attachment/5383373/+files/Bildschirmfoto%20von%202020-06-12%2022-38-51.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: Regression: MTP not working/very slow
I have the same Problem on Ubuntu 19.10 with a Samsung Galaxy S10 (SM- G973F) Kernel: 5.3.0-46-generic x86_64 Architecture: arm64 Desktop: Gnome 3.34.2 gvfs: amd64 1.42.1-1ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866721] Re: Unable to use microphone in chrome
Same error here. $ snap connections chromium | grep audio audio-playbackchromium:audio-playback:audio-playback - audio-record chromium:audio-record - - pulseaudiochromium:pulseaudio- - Workaround: $ snap connect chromium:audio-record :audio-record $ snap connections chromium | grep audio audio-playbackchromium:audio-playback:audio-playback - audio-record chromium:audio-record :audio-record manual pulseaudiochromium:pulseaudio- - -- 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/1866721 Title: Unable to use microphone in chrome Status in chromium-browser package in Ubuntu: Incomplete Bug description: Running Ubuntu 19.10 and the chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 package I am unable to use my microphone with sites that support it, such as discord. I can hear audio from websites like Youtube, but sites that want to use my microphone fail to do so, even though I give permission. I've tested with Hubs by Mozilla, Discord and https://www.onlinemictest.com/ All three properly prompt for permission, but then act as if I refused to give it when choose "allow". If I start chrome from the command line, when this happens I see this in the output [73233:73233:0309/165624.013771:ERROR:pulse_util.cc(300)] pa_operation is nullptr. The https://www.onlinemictest.com/ reports "Microphone not authorized. Please check your media permissions settings." My microphone works fine in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868408] [NEW] scanimage doesn't respect options (brightness, contrast, ...) with Canon CanoScan LIDE 35
Public bug reported: Device: Canon CanoScan LIDE 35 Options (--brightness and --contrast) are not respected. Reproduce the bug: Scan the same document with scanimage --brightness=0 > 0.pnm and scanimage --brightness=100 > 100.pnm The result will be the same. Changing the output format doesn't change anything. Graphical programs (simple-scan 3.36.0, skanlite 2.1.0.1) have the same problem. But with xsane-0.999 it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 22:39:23 2020 InstallationDate: Installed on 2020-01-05 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (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 sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1868408 Title: scanimage doesn't respect options (brightness, contrast, ...) with Canon CanoScan LIDE 35 Status in sane-backends package in Ubuntu: New Bug description: Device: Canon CanoScan LIDE 35 Options (--brightness and --contrast) are not respected. Reproduce the bug: Scan the same document with scanimage --brightness=0 > 0.pnm and scanimage --brightness=100 > 100.pnm The result will be the same. Changing the output format doesn't change anything. Graphical programs (simple-scan 3.36.0, skanlite 2.1.0.1) have the same problem. But with xsane-0.999 it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 22:39:23 2020 InstallationDate: Installed on 2020-01-05 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1868408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866929] [NEW] gnome-shell crashes when typing on lock screen
Public bug reported: When the screen is locked, typing anything on the keyboard doesn't lead to the password prompt. Instead, the desktop / open applications are shown for a few seconds, but the session is not unlocked, the gnome- shell crashes and the lock screen is back on. After that, the kernel log says: [ 1253.059365] traps: gnome-shell[15914] trap int3 ip:7fa53d1000d5 sp:7fffdf2bbc50 error:0 in libglib-2.0.so.0.6400.0[7fa53d0c4000+84000] If libreoffice is open during this procedure, it is killed. The kernel log says: [ 1753.463495] audit: type=1400 audit(1583883878.179:44): apparmor="ALLOWED" operation="signal" profile="libreoffice-oopslash" pid=18520 comm="oosplash" requested_mask="send" denied_mask="send" signal=kill peer="libreoffice-soffice" [ 1753.463502] audit: type=1400 audit(1583883878.179:45): apparmor="ALLOWED" operation="signal" profile="libreoffice-soffice" pid=18520 comm="oosplash" requested_mask="receive" denied_mask="receive" signal=kill peer="libreoffice-oopslash" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 00:31:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1866929 Title: gnome-shell crashes when typing on lock screen Status in gnome-shell package in Ubuntu: New Bug description: When the screen is locked, typing anything on the keyboard doesn't lead to the password prompt. Instead, the desktop / open applications are shown for a few seconds, but the session is not unlocked, the gnome-shell crashes and the lock screen is back on. After that, the kernel log says: [ 1253.059365] traps: gnome-shell[15914] trap int3 ip:7fa53d1000d5 sp:7fffdf2bbc50 error:0 in libglib-2.0.so.0.6400.0[7fa53d0c4000+84000] If libreoffice is open during this procedure, it is killed. The kernel log says: [ 1753.463495] audit: type=1400 audit(1583883878.179:44): apparmor="ALLOWED" operation="signal" profile="libreoffice-oopslash" pid=18520 comm="oosplash" requested_mask="send" denied_mask="send" signal=kill peer="libreoffice-soffice" [ 1753.463502] audit: type=1400 audit(1583883878.179:45): apparmor="ALLOWED" operation="signal" profile="libreoffice-soffice" pid=18520 comm="oosplash" requested_mask="receive" denied_mask="receive" signal=kill peer="libreoffice-oopslash" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 00:31:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
Correction: The crashes still happen. I probably was just lucky when testing. -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Committed Bug description: [ Description ] Intellij and other java apps can cause GNOME shell to crash [ Test case ] 1) Run this test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/956 2) Windows should appear and close correctly while Gnome shell must not crash [ Regression potential ] Parent-child relationship on some windows might be broken. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
Interesting. I tested that version as well, and all the (similar) crashing problems I had with the text editor Geany are gone, so the update at least seems to help in some cases. -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Committed Bug description: [ Description ] Intellij and other java apps can cause GNOME shell to crash [ Test case ] 1) Run this test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/956 2) Windows should appear and close correctly while Gnome shell must not crash [ Regression potential ] Parent-child relationship on some windows might be broken. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846423]
I am also struggling with this error - half of my calendars is not working anymore... No change, same behavior in recent Thunderbird 68.2.2 (64-bit) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: New Bug description: Cannot dismiss reminders for a recurrence with exceptions. Calendar entries like this are generated: BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:My recurrence TRIGGER;VALUE=DURATION:-PT120M X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame ter with an illegal type for property: VALUE=DURATION END:VALARM ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vectro 2004 F pulseaudio /dev/snd/controlC0: vectro 2004 F pulseaudio BuildID: 20190705212852 Channel: Unavailable CurrentDesktop: KDE Date: Wed Oct 2 17:50:39 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.43 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 640 G1 dmi.product.sku: T4M40UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Upstream fix is most likely https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/763
I have installed gnome-shell{,-common}
3.34.1+git20191024-1ubuntu1~19.10.1 from eoan-proposed and verified that
the "opening activities" delay goes down from ~4 seconds in
3.34.1-1ubuntu1 to <1 second in the -proposed package, while having a
total of 22 windows open.
I have not done any serious regression testing, so not changing the tag.
--
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/1848009
Title:
Delay launching application launcher gets longer the more apps are
open
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Eoan:
Fix Committed
Bug description:
[ Impact ]
On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD.
If I launch a bunch of applications - possibly a slightly unreasonable
number, but a lot anyway - with minimal CPU or memory in use, the button to
launch applications in the bottom left takes progressively longer to run.
Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ
[ Test case ]
- Launch lots of applications
- Click in the applications icon in the launcher (or press super+A)
- Animation should not be delayed (some delay is still expected depending
on the number of installed applications)
[ Regression potential ]
Windows in activities overview might have wrong positioning
This is uploaded under the GNOME MRE:
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
---
Steps to reproduce.
Open application launcher
Note a ~0.6s delay before the icons fly onto the screen
Open GNOME Software
Install all the editors picks
Launch a bunch of applications
Click the application launcher
Note a 4s delay before icons fly onto the screen.
Expectation
Honestly, no delay at all, but it should be at least consistent with when no
applications are running, so 0.6s delay as per the state when no apps are
launched.
ProblemType: BugDistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 13:02:04 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-10-13 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1SourcePackage:
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/1848009/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
I'd be interested in that as well. I'm using the text editor "Geany", and every time I use the search function, this exact same error happens for me. Hoping that the package in Ubuntu gets fixed soon. -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
Confirming what mangocats said here; this is still (or rather, again) present on 18.04.3. Block Caribou appears to be the only reliable workaround. -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: Won't Fix Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted
I see this in journalctl at approx. the time of this "giving up after 5 attempts", I also use sftp: (where XXX is my user name) Okt 25 17:51:09 XXX kernel: gvfsd-sftp[10782]: segfault at 55b30002 ip 7f0a424e63ae sp 7fffe1c32c00 error 4 in libc-2.30.so[7f0a4246e000+178000] Okt 25 17:51:09 XXX kernel: Code: 84 5c ff ff ff 0f 1f 80 00 00 00 00 48 8d 0c 58 0f b7 11 66 85 d2 0f 84 45 ff ff ff 48 8d 04 d8 83 ea 01 4c 8b 80 80 00 00 00 <49> 8b 30 48 89 b0 80 00 00 00 66 8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1600299 Title: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup package in Mandriva: New Bug description: I've got my system set up with off-site backup over sftp. This works fine but the problem is that while deja-dup is gathering files and calculating the backup delta the connection to the server times out. This means that it's not available when deja-dup actually tries to push files to the server and results in this error message: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted (16) By sitting in the file manager and jumping between folders the connection can be kept alive but that's rather annoying and requires my presence. Would really like to see deja-dup actually trying to set up the connection again instead. Using: Manjaro 16.06.1 deja-dup 34.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1600299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838181] Re: 3D Application cannot run anymore
For information the last update was: $ less /var/log/apt/history.log > Start-Date: 2019-07-28 08:23:57 > Commandline: aptdaemon role='role-commit-packages' sender=':1.107' > Install: xdg-desktop-portal-gtk:amd64 (1.0.2-0ubuntu1.1, automatic), > xdg-desktop-portal:amd64 (1.0.3-0ubuntu0.2, automatic) > Upgrade: language-pack-gnome-fr:amd64 (1:18.04+20190117, 1:18.04+20190718), > gir1.2-gtk-3.0:amd64 (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), > libegl1-mesa-dev:amd64 (18.2.8-0ubuntu0~18.04.2, 19.0.2-1ubuntu1.1~18.04.2), > sane-utils:amd64 (1.0.27-1~experimental3ubuntu2, > 1.0.27-1~experimental3ubuntu2.1), libegl-mesa0:amd64 > (18.2.8-0ubuntu0~18.04.2, 19.0.2-1ubuntu1.1~18.04.2), libgtk-3-common:amd64 > (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), libgtk-3-0:amd64 (3.22.30-1ubuntu3, > 3.22.30-1ubuntu4), libglapi-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libglapi-mesa:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), mesa-common-dev:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libxatracker2:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libegl1-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), language-pack-en:amd64 (1:18.04+20180712, > 1:18.04+20190718), language-pack-fr:amd64 (1:18.04+20190117, > 1:18.04+20190718), libgbm1:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libsane1:amd64 (1.0.27-1~experimental3ubuntu2, > 1.0.27-1~experimental3ubuntu2.1), libgtk-3-bin:amd64 (3.22.30-1ubuntu3, > 3.22.30-1ubuntu4), libwayland-egl1-mesa:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgail-3-0:amd64 (3.22.30-1ubuntu3, > 3.22.30-1ubuntu4), libgl1-mesa-dri:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-dri:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-glx:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libgl1-mesa-glx:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libsane-common:amd64 > (1.0.27-1~experimental3ubuntu2, 1.0.27-1~experimental3ubuntu2.1), > gtk-update-icon-cache:amd64 (3.22.30-1ubuntu3, 3.22.30-1ubuntu4), > mesa-vdpau-drivers:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), mesa-va-drivers:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libglx-mesa0:amd64 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2), libglx-mesa0:i386 (18.2.8-0ubuntu0~18.04.2, > 19.0.2-1ubuntu1.1~18.04.2) > End-Date: 2019-07-28 08:24:59 -- 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/1838181 Title: 3D Application cannot run anymore Status in xorg package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 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.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF dmi.product.version:
[Desktop-packages] [Bug 1838181] [NEW] 3D Application cannot run anymore
Public bug reported: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 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.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY Notebook dmi.product.sku: W6X73EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838181 Title: 3D Application cannot run anymore Status in xorg package in Ubuntu: New Bug description: Since a recent update (done today 2019-07-28) I cannot start application that requires 3D (openGL support). It start being slow with degraded graphics, then freeze and finally crash with the following message : > i965: Failed to submit batchbuffer: Input/output error It also happened to me when I updated from Bionic Beaver to Disco. The Workaround was to reinstall a Bionic Beaver version. Now it does not work on this version anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 08:58:45 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80df] InstallationDate: Installed on 2019-04-30 (89 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DF dmi.board.vendor: HP dmi.board.version: 87.72 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP
[Desktop-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Issue may get closed. Solved with upgrading to Ubuntu 19.04. Nevertheless thanks for your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in glib2.0 package in Ubuntu: Triaged Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
Quick workaround for those who want to enjoy the benefits right away: echo "MOZ_USE_XINPUT2=1" | sudo tee /etc/environment.d/90firefox-xinput2.conf -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
For completeness sake, here is the OpenSuse bug report talking about it: https://bugzilla.opensuse.org/show_bug.cgi?id=1032003 -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
It is indeed a common complaint/request as evidenced by the people talking about it in various places (blogs, reddit, etc.): https://www.rojtberg.net/1569/switching-back-from-chrome-to-firefox/ https://www.reddit.com/r/linux/comments/72mfv8/psa_for_firefox_users_set_moz_use_xinput21_to/ https://hackido.com/2019/02/01/2019-02-01-firefox-with-touch/ I paste here again the upstream bug report as the link changed slightly: https://bugzilla.mozilla.org/show_bug.cgi?id=1207700 Recent comments in it (a year old) are fairly positive: "I think we can enable the XInput2 for recent Gtk+ versions (say Gtk+ >= 3.20) as the related Gtk+ focus bugs was fixed but for XInput2 only. Also Fedora enables XInput2 by default and we don't have any user complains." However there is a list of possible issues that need to be checked before moving on this: https://bugzilla.mozilla.org/show_bug.cgi?id=1182700 (wheel scrolling issue when window not active) https://bugzilla.mozilla.org/show_bug.cgi?id=1390795 (wheel scrolling issue when window not active) https://bugzilla.mozilla.org/show_bug.cgi?id=1487882 (pdf zoom increments by 10%) https://bugzilla.mozilla.org/show_bug.cgi?id=1196777 (probably fixed) https://bugzilla.mozilla.org/show_bug.cgi?id=1170342 (fixed) Additionally, we need to check it works adequately when the synaptics driver is enabled (I'm not sure but perhaps it's enabled by default on Macbooks?). Finally, I tried a couple more tweaks in about:config to make the scrolling experience smoother with a touchpad: - disabling smooth scrolling: general.smoothScroll = false OR - enabling msdPhysics scrolling: general.smoothScroll.msdPhysics.enabled = true I'm not yet entirely convinced by either and still have to test it more, especially with a mouse. ** Bug watch added: Mozilla Bugzilla #1207700 https://bugzilla.mozilla.org/show_bug.cgi?id=1207700 ** Bug watch added: Mozilla Bugzilla #1182700 https://bugzilla.mozilla.org/show_bug.cgi?id=1182700 ** Bug watch added: Mozilla Bugzilla #1390795 https://bugzilla.mozilla.org/show_bug.cgi?id=1390795 ** Bug watch added: Mozilla Bugzilla #1487882 https://bugzilla.mozilla.org/show_bug.cgi?id=1487882 ** Bug watch added: Mozilla Bugzilla #1196777 https://bugzilla.mozilla.org/show_bug.cgi?id=1196777 ** Bug watch added: Mozilla Bugzilla #1170342 https://bugzilla.mozilla.org/show_bug.cgi?id=1170342 ** Bug watch added: bugzilla.opensuse.org/ #1032003 https://bugzilla.opensuse.org/show_bug.cgi?id=1032003 -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
** Summary changed: - Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable touch gestures + Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
If someone else has those issues with a USB-C Dock (Thunderbolt 3) I got rid of the issue by using the latest mainline Kernel: 5.1.0-050100-generic #201905052130 SMP Mon May 6 01:32:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux and the following Kernel config settings (/etc/default/grub): GRUB_CMDLINE_LINUX_DEFAULT=" quiet splash intel_idle.max_cstate=4 i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0 i915.enable_dp_mst=0" -- 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/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage
[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Since I'm also facing this bug I just want to confirm that the error also occurs on the latest mainline Kernel (5.1) and also on the current drm-tip kernel version (5.1.0.0994 from https://kernel.ubuntu.com /~kernel-ppa/mainline/drm-tip/2019-05-05/) I'm trying to use an additional monitor on my X380 Yoga using an USB-C Dock. During the boot process the error message appears: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO After the boot process the monitor is sometimes enabled, but only a couple of seconds. -- 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/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
Same bug here on two different laptop. Fresh install Ubuntu 18.04.2 nvidia-driver-418 4.18.0-18-generic First $vulkaninfo => OK Switch on Intel with NVIDIA X Server settings reboot Switch to NVIDIA with NVIDIA X Server settings reboot $vulkaninfo => VK_ERROR_INITIALIZATION_FAILED $sudo vulkaninfo => OK then vulkaninfo => OK So now before launch Steam to play games that use vulkan I always do sudo vulkaninfo -- 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/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem
Only Line Out works -- 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/1824205 Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: My card is detected and with ubuntu-bug all output is detected but on Sound Control only SPDIF Output is showed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 18:47:50 2019 InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B09 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem
Line Out it work but Headphone output doesn't appear. -- 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/1824205 Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: My card is detected and with ubuntu-bug all output is detected but on Sound Control only SPDIF Output is showed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 18:47:50 2019 InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B09 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824205] [NEW] [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem
Public bug reported: My card is detected and with ubuntu-bug all output is detected but on Sound Control only SPDIF Output is showed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 18:47:50 2019 InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B09 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1824205 Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: My card is detected and with ubuntu-bug all output is detected but on Sound Control only SPDIF Output is showed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 18:47:50 2019 InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B09 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824179] [NEW] Fingerprint Scanner of XIAOMI Mi notebook pro is not detected
*** This bug is a duplicate of bug 1641290 *** https://bugs.launchpad.net/bugs/1641290 Public bug reported: My fingerprint scanner is not detected. I have a XIAOMI Mi notebook pro. lsusb ``` Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0c1a Elan Microelectronics Corp. Bus 001 Device 003: ID 05c8:03b7 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` lshw ``` florian description: Ordinateur Bloc-notes produit: TM1707 (TM1707-18404) fabriquant: TIMI version: Mi Laptop Pro 15.6 numéro de série: 18404/1836 bits: 64 bits fonctionnalités: smbios-3.0 dmi-3.0 smp vsyscall32 configuration: boot=normal chassis=notebook family=TIMIBOOK sku=TM1707-18404 uuid=9D271ED7-B3CD-9944-A832-E1C327F26F99 *-core description: Carte mère produit: TM1707 fabriquant: TIMI identifiant matériel: 0 version: XMAKB5RRP0503 numéro de série: MMG5S018588LP0027 emplacement: Type2 - Board Chassis Location *-firmware description: BIOS fabriquant: TIMI identifiant matériel: 0 version: XMAKB5RRP0603 date: 07/28/2018 taille: 128KiB capacité: 8128KiB fonctionnalités: pci upgrade shadowing cdboot bootselect edd int9keyboard int10video acpi usb biosbootspecification uefi *-cpu description: CPU produit: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz fabriquant: Intel Corp. identifiant matériel: 4 information bus: cpu@0 version: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz numéro de série: To Be Filled By O.E.M. emplacement: U3E1 taille: 3211MHz capacité: 4005MHz bits: 64 bits horloge: 100MHz fonctionnalités: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp flush_l1d cpufreq configuration: cores=4 enabledcores=4 threads=8 *-cache:0 description: L1 cache identifiant matériel: 5 emplacement: L1 Cache taille: 256KiB capacité: 256KiB fonctionnalités: synchronous internal write-back unified configuration: level=1 *-cache:1 description: L2 cache identifiant matériel: 6 emplacement: L2 Cache taille: 1MiB capacité: 1MiB fonctionnalités: synchronous internal write-back unified configuration: level=2 *-cache:2 description: L3 cache identifiant matériel: 7 emplacement: L3 Cache taille: 8MiB capacité: 8MiB fonctionnalités: synchronous internal write-back unified configuration: level=3 *-memory description: Mémoire Système identifiant matériel: b emplacement: Carte mère taille: 16GiB *-bank:0 description: SODIMM DDR4 Synchrone Unbuffered (Unregistered) 2400 MHz (0,4 ns) produit: M471A1K43BB1-CRC fabriquant: Samsung identifiant matériel: 0 numéro de série: emplacement: ChannelA-DIMM0 taille: 8GiB bits: 64 bits horloge: 2400MHz (0.4ns) *-bank:1 description: SODIMM DDR4 Synchrone Unbuffered (Unregistered) 2400 MHz (0,4 ns) produit: M471A1K43BB1-CRC fabriquant: Samsung identifiant matériel: 1 numéro de série: emplacement: ChannelB-DIMM0 taille: 8GiB bits: 64 bits horloge: 2400MHz (0.4ns) *-pci description: Host bridge produit: Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers fabriquant: Intel Corporation identifiant matériel: 100 information bus: pci@:00:00.0 version: 08 bits: 32 bits
[Desktop-packages] [Bug 1756516] Re: update libvorbis to 1.3.6
libvorbis 1.3.6 is in cosmic and the CVEs were already fixed in bionic (and earlier through security updates, I believe) ** Changed in: libvorbis (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvorbis in Ubuntu. https://bugs.launchpad.net/bugs/1756516 Title: update libvorbis to 1.3.6 Status in libvorbis package in Ubuntu: Fix Released Bug description: libvorbis 1.3.6 (2018-03-16) -- "Xiph.Org libVorbis I 20180316 (Now 100% fewer shells)" * Fix CVE-2018-5146 - out-of-bounds write on codebook decoding. * Fix CVE-2017-14632 - free() on unitialized data * Fix CVE-2017-14633 - out-of-bounds read * Fix bitrate metadata parsing. * Fix out-of-bounds read in codebook parsing. * Fix residue vector size in Vorbis I spec. * Appveyor support * Travis CI support * Add secondary CMake build system. * Build system fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/1756516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
As you proposed: https://gitlab.gnome.org/GNOME/glib/issues/1688 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in glib2.0 package in Ubuntu: New Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
By the way, due to freezing issues with copying many small files last august, I was forced to change fstab. The cifs/smb version is now 2.0: //ip-address/home /mnt/cifs_nas_home cifs uid=florian,gid=florian,credentials=/home/florian/.smbcredentials,dir_mode=0700,vers=2.0 0 0 Restrictions to the .exe speed drop exception: If the .exe-file already exists in the destination, replacing is as slow as coping iso files (7 MB/s) Same behaviour with gio copy. Because of the replacement issue above I repeated the measurements with following approach: - test file size 8 GB - only upload - fast copies are repeated 3 times and averaged performance chosen (only if no freak value) - slow copies are repeated 3 times too but aborted after ca. 20 seconds Results Tool/CMDtypeending performance (in MB/s) nautiluscopyiso ~ 7 nautilusrepl. iso ~ 7 nautiluscopyexe ~ 110 nautilusrepl. exe ~ 7 gio copycopyiso ~ 7 gio copyrepl. iso ~ 7 gio copycopyexe ~ 110 gio copyrepl. exe ~ 7 cp copyiso ~ 75 cp repl. iso ~ 110 cp copyexe ~ 110 cp repl. exe ~ 110 Commands gio copy -pT /home/florian/testfile-upload-8gb.[iso/exe] /mnt/cifs_nas_media_flo/testfile-upload-8gb.[iso/exe] time cp -T /home/florian/testfile-upload-8gb.[iso/exe] /mnt/cifs_nas_media_flo/testfile-upload-8gb.[iso/exe] Annotation: Because "cp" has no progress function, the less accurate time command is used. Through comparing "gio copy -pT" and "time gio copy -pT", I translated "cp" time results to performance. Very first copy issue This part needs to be observed more closely. Resetting cifs mount (umount, mount) appears to help for a few 8 GB copies. But after a few it starts fast but drops hard down to 7 MB/s after 4 GB transmitted. After some more beginning and cancelling copies it stays at 7 MB/s permanently. Summary: - massive speed drop with upload copy is only observed with "nautilus" and "gio copy", not "cp", although the last one has also a weird behaviour, but that's probably another matter - the very first copy issue needs closer observation - speed drop is depending on file ending, ".iso" is always slow, ".exe" only if replacing existing file -- 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/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in nautilus package in Ubuntu: Incomplete Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Thank you for looking into this problem. What I observed additionally: * the very first upload copy with nautilus is normal maximum speed (~110 MB/s) * then every upload copy is about 7 MB/s * if I change the file ending to ".exe" and upload, I get maximum speed! Results to your requested data: 1st cp: time cp -T /home/florian/upload.iso /mnt/cifs_nas_media_flo/upload.iso real1m21,701s user0m0,054s sys 0m4,832s 2nd cp: time cp -T /home/florian/upload.iso /mnt/cifs_nas_media_flo/upload.iso real1m23,342s user0m0,059s sys 0m4,879s => so maximum speed (8GB need ca. 80 seconds) 1st gio copy: gio copy -pT /home/florian/upload.iso /mnt/cifs_nas_media_flo/upload.iso Transferred 114,8 MB out of 8,0 GB (6,8 MB/s)^C 2nd gio copy with ".exe" file ending: gio copy -pT /home/florian/upload.exe /mnt/cifs_nas_media_flo/upload.exe Transferred 8,0 GB out of 8,0 GB (115,0 MB/s) So all this speed drop is somehow linked to the file ending. What could interfere just because of different file endings? And why are only nautilus and gio copy affected and not all copy utilities? -- 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/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in nautilus package in Ubuntu: Incomplete Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
Tested with Ubuntu 18.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver Status in xf86-input-wacom package in Ubuntu: Confirmed Bug description: /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this: Section "InputClass" Identifier "Wacom touchscreen class" MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4" MatchDevicePath "/dev/input/event*" MatchIsTouchscreen "true" Driver "wacom" EndSection The result is that on my Yoga 920, in a plain X11 session (running openbox in my case), the touchscreen acts like a broken mouse: there is no multi-touch capability in Qt Quick applications, and clicking isn't quite right either. I also verified it with Peter Hutterer's old cairo-based mt-touch test program. I suspect we will get some users mistakenly writing up Qt bugs about this if you don't ship a fix. (Seems to me that already happened at least once, actually.) Yes, the touchscreen is made by Wacom, but wacom_drv.so has historically been only for Wacom tablets and in-screen stylus digitizers, and IMO that continues to be the case. libinput is a much better choice of driver for this hardware (so is evdev for that matter), so I changed it to Driver "libinput" and got it working. (Wayland uses libinput, so in a wayland session, touch already works fine in Qt apps on this hardware.) I'm one of the Qt Quick maintainers, most concerned with touch handling, and I've also written some of the Qt xcb code for dealing with XInput touch and tablet devices. So if you think that there's something wrong with Qt, such that it should still work anyway to use a wacom driver for a Wacom touchscreen, let me know. These AES devices are still new to me (that's why I got a Yoga, to try it out). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/70-wacom.conf] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 30 19:40:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB 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 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
The same issue happens on the Lenovo Thinkpad X1 Yoga 2nd gen. I think the rule above was simply a bit too much. Can somebody confirm a device where exactly the rules with the capability MatchIsTouchscreen "true" are really needed? Those devices seem to have a buggy HID descriptor. If not, Ubuntu, could you please remove (or at least comment) these annoying rules since they seem to break a lot (if not all) Lenovo Yoga convertible devices... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver Status in xf86-input-wacom package in Ubuntu: Confirmed Bug description: /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this: Section "InputClass" Identifier "Wacom touchscreen class" MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4" MatchDevicePath "/dev/input/event*" MatchIsTouchscreen "true" Driver "wacom" EndSection The result is that on my Yoga 920, in a plain X11 session (running openbox in my case), the touchscreen acts like a broken mouse: there is no multi-touch capability in Qt Quick applications, and clicking isn't quite right either. I also verified it with Peter Hutterer's old cairo-based mt-touch test program. I suspect we will get some users mistakenly writing up Qt bugs about this if you don't ship a fix. (Seems to me that already happened at least once, actually.) Yes, the touchscreen is made by Wacom, but wacom_drv.so has historically been only for Wacom tablets and in-screen stylus digitizers, and IMO that continues to be the case. libinput is a much better choice of driver for this hardware (so is evdev for that matter), so I changed it to Driver "libinput" and got it working. (Wayland uses libinput, so in a wayland session, touch already works fine in Qt apps on this hardware.) I'm one of the Qt Quick maintainers, most concerned with touch handling, and I've also written some of the Qt xcb code for dealing with XInput touch and tablet devices. So if you think that there's something wrong with Qt, such that it should still work anyway to use a wacom driver for a Wacom touchscreen, let me know. These AES devices are still new to me (that's why I got a Yoga, to try it out). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/70-wacom.conf] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 30 19:40:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB 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 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs Kruitbosch from comment #83) > Seems to me from comment 81 that this change should not be OS X - specific. So do you think we should remove the maybeCanonizeURL code altogether? I wasn't sure if we wanted to keep this behavior inherited from Internet Explorer on at least Windows, so I suggested making the minimal behavior change for a first patch (I was helping nox understand how this code works while we were waiting at the airport). -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs Kruitbosch from comment #86) > Also, if we're going to change this on only some platforms, given the > contention, the most straightforward thing would be to have a pref that we > default to different values on Windows - then Windows users who don't care > for the IE behaviour can flip it, or vice versa. A pref would make sense, especially if we want to be able to test both behaviors on all platforms. I didn't suggest it mostly because of comment 62, but that comment was arguably more about exposing the pref in the UI than about having a pref in the implementation. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gavin Sharp [email: ga...@gavinsharp.com] from comment #56) > Unfortunately fixing this at this point would be disastrous for muscle > memory/user habits, so it's just not feasible. This bug still seems to be annoying people. Philipp, do you agree that the current behavior of accel+enter (adding www. and .com, and loading in the current tab) has been here for so long that we can't fix it at this point? Or given that this behavior was introduced to mimic IE's behavior, would it be reasonable to implement "accel+enter opens in new tab" for OS X only, where no other browser has ever supported the www./.com completion behavior? -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788021] Re: changing keyborad brightness doesn't work
Using Mainline Kernel 4.19.0 or above, it works. So it's a bug in the Ubuntu 18.10 Kernel Version. Maybe it's this 4.19 patch. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61c4fc1eaf736344904767d201b0d4f7a2ebaf79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1788021 Title: changing keyborad brightness doesn't work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Checking 'journalctl' I get this error message: gsd-power[1924]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Running on an Asus UX490UA (7th-gen Intel CPU), and before upgrading to 18.10 everything worked fine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.29.90.1-1~ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 21:22:13 2018 InstallationDate: Installed on 2018-08-15 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to cosmic on 2018-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1788021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788021] Re: changing keyborad brightness doesn't work
Same problem on an Asus UX331U. In Ubuntu 18.04 setting kbd backlight worked, it's broken in Ubuntu 18.10. Oct 1 17:43:19 avis gsd-power[2143]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed i am able to manually control the backlight on the shell using sudo tee /sys/class/leds/asus\:\:kbd_backlight/brightness <<< 3 (replace 3 with [0..3] for brightness levels) --- rephlex@avis:[/proc]: ls /sys/class/leds/ asus::kbd_backlight asus::lightbar asus-wireless::airplane input4::capslock input4::numlock input4::scrolllock phy0-led --- root@avis:/sys/class/backlight# ls -la /sys/class/backlight/intel_backlight lrwxrwxrwx 1 root root 0 Okt 1 17:44 /sys/class/backlight/intel_backlight -> ../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/intel_backlight root@avis:/sys/class/backlight# ls -la /sys/class/backlight/ insgesamt 0 drwxr-xr-x 2 root root 0 Okt 1 17:44 . drwxr-xr-x 70 root root 0 Okt 1 17:40 .. lrwxrwxrwx 1 root root 0 Okt 1 17:44 intel_backlight -> ../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/intel_backlight -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1788021 Title: changing keyborad brightness doesn't work Status in gnome-settings-daemon package in Ubuntu: New Bug description: Checking 'journalctl' I get this error message: gsd-power[1924]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Running on an Asus UX490UA (7th-gen Intel CPU), and before upgrading to 18.10 everything worked fine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.29.90.1-1~ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 21:22:13 2018 InstallationDate: Installed on 2018-08-15 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to cosmic on 2018-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1788021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789104] [NEW] package tex-common 6.04ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: Crash recovered by brute-force restarting of the computer preceded the error message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 24 17:49:59 2018 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2014-11-03 (1392 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (630 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1789104 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in tex-common package in Ubuntu: New Bug description: Crash recovered by brute-force restarting of the computer preceded the error message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 24 17:49:59 2018 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2014-11-03 (1392 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (630 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1789104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Some additional performance measurements with dd... speed test with /dev/zero upload/write: dd if=/dev/zero of=/mnt/cifs_media/test.iso bs=10M count=400 400+0 records in 400+0 records out 4194304000 bytes (4,2 GB, 3,9 GiB) copied, 40,4893 s, 104 MB/s download/read: dd if=/mnt/cifs_media/test.iso of=/dev/zero bs=10M 400+0 records in 400+0 records out 4194304000 bytes (4,2 GB, 3,9 GiB) copied, 37,393 s, 112 MB/s More practical up- and download speeds upload: dd if=/home/me/file.iso of=/mnt/cifs_media/file.iso bs=10M 767+1 records in 767+1 records out 8048736256 bytes (8,0 GB, 7,5 GiB) copied, 93,209 s, 86,4 MB/s download: dd if=/mnt/cifs_media/file.iso of=/home/me/file2.iso bs=10M 767+1 records in 767+1 records out 8048736256 bytes (8,0 GB, 7,5 GiB) copied, 81,2462 s, 99,1 MB/s So cifs and other underlying systems and hardware seem to be capable to use maximum speed. But more important, if I lower bs, the speed drops down really hard. Upload with bs=... - Default (512) -> 830 kB/s - 4096 -> 6,2 MB/s So maybe the file managers and rsync or their underlying systems are using these small bs? -- 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/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in nautilus package in Ubuntu: New Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782535] [NEW] cifs - poor upload speed with nautilus compared to rsync
Public bug reported: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s - rsync command (upload): + rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ - fstab entry: + fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 - 3) What you expected to happen: At least same speed as rsync + 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above -- 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/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in nautilus package in Ubuntu: New Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782077] [NEW] network/wifi icon missing from top bar and user menu
Public bug reported: On 18.04, after a recent update, the top bar in gnome-shell does not show a wifi icon anymore. More importantly, the network menu entry is missing in the user menu. This appears to be already tracked in this upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 Here's the recent updates that may have cause this (apparently the switch from 3.28.1 to 3.28.2): gnome-shell-common:amd64 (3.28.1-0ubuntu2, 3.28.2-0ubuntu0.18.04.1) gnome-shell:amd64 (3.28.1-0ubuntu2, 3.28.2-0ubuntu0.18.04.1) gnome-desktop3-data:amd64 (3.28.1-1ubuntu1, 3.28.2-0ubuntu1) libgnome-desktop-3-17:amd64 (3.28.1-1ubuntu1, 3.28.2-0ubuntu1) c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 17 08:56:18 2018 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-12 (2103 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-06-14 (32 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "gnome-network.png" https://bugs.launchpad.net/bugs/1782077/+attachment/5164365/+files/gnome-network.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1782077 Title: network/wifi icon missing from top bar and user menu Status in gnome-shell package in Ubuntu: New Bug description: On 18.04, after a recent update, the top bar in gnome-shell does not show a wifi icon anymore. More importantly, the network menu entry is missing in the user menu. This appears to be already tracked in this upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 Here's the recent updates that may have cause this (apparently the switch from 3.28.1 to 3.28.2): gnome-shell-common:amd64 (3.28.1-0ubuntu2, 3.28.2-0ubuntu0.18.04.1) gnome-shell:amd64 (3.28.1-0ubuntu2, 3.28.2-0ubuntu0.18.04.1) gnome-desktop3-data:amd64 (3.28.1-1ubuntu1, 3.28.2-0ubuntu1) libgnome-desktop-3-17:amd64 (3.28.1-1ubuntu1, 3.28.2-0ubuntu1) c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 17 08:56:18 2018 DisplayManager: gdm3 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-12 (2103 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-06-14 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I'm also experiencing this bug on kubuntu 18.04. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744775] Re: "Operation was cancelled" when trying to use Transparency Unit in Canon 9000F Mark II
The use of the transparency unit in Canon 9000F Mark II requires to take the regular white background away from the covering lid, beneath with the actual backlight of the transparency unit resides. Any scanning attempt with the transparency unit as source while the backlight is hidden by the white background yields the error described above – which is, sadly, not very descriptly. After taking way the background the transparency unit works like a charm. @Jelle you might try whether this works for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1744775 Title: "Operation was cancelled" when trying to use Transparency Unit in Canon 9000F Mark II Status in sane-backends package in Ubuntu: Confirmed Bug description: I'm trying to scan foto negatives using this command (that used to work in previous Ubuntu versions): scanimage --device-name pixma:04A9190D --source "Transparency Unit" --resolution "2400" --format "tiff" --mode Color -l 76 -x 66 > test.tiff But I get this error: scanimage: sane_read: Operation was cancelled Note: scanning regular images (using the Flatbed source) works fine. My current ubuntu verison is Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Found this patch: https://github.com/manjaro/packages- community/tree/master/nautilus-typeahead Not sure if it works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
I can confirm that signon-ui-service (0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) and signon-ui-x11 (0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) allow me to get past the Google account error. The account shows up, but going online does not quite work yet (which I have seen before). -- 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/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault
Using artful, I updated these packages (everything that used to have version "17.2.2-0ubuntu1" on my system) to version "17.2.4-0ubuntu1~17.10.1" from -proposed: libegl1-mesa:amd64 libgbm1:amd64 libgl1-mesa-dev:amd64 libgl1-mesa-dri:amd64 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-glx:i386 libglapi-mesa:amd64 libglapi-mesa:i386 libgles2-mesa:amd64 libwayland-egl1-mesa:amd64 libxatracker2:amd64 mesa-common-dev:amd64 mesa-vdpau-drivers:amd64 mesa-vulkan-drivers:amd64 After a reboot, I can confirm Lawrence's observation that vulkan- smoketest segfaulted on the old version, but seems to work fine using the version from -proposed. Since Lawrence forgot to remove the verification-needed-artful tag, I'm going to remove it now. ** Tags removed: verification-needed-artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1720890 Title: vulkan-smoketest segfaults steam vulkan games segfault Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Installed: 17.2.1-0ubuntu1 Candidate: 17.2.1-0ubuntu1 Version table: *** 17.2.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install vulkan-utils Open a terminal type vulkan-smoketest instead of a glxgears type window it will segfault. message from kernel.log: Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in libvulkan_radeon.so[7fed619ab000+18b000] syslog: Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in libvulkan_radeon.so[7f627053b000+18b000] What should happen is a glxgears like window will open and render properly instead of segfaulting. It appears that the culprit is an old or broken libvulkan_radeon.so provided by mesa-vulkan-drivers. As a test I renamed the old lib and dropped in a newer version from oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad Max now work properly in Vulkan mode as well instead of segfaulting. This issue is also present on Zesty and fixed in both Oibaf's and Padoka's ppa's since April back when they were rolling 17.2 mesa. I have no idea if libvulkan_intel.so also needs updating no hardware to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184328] Re: xpdf crashes with SIGSEGV in GlobalParams::findFontFile()
attached PDF files display without crashing in xpdf 3.04-5, hence marking as "Fix Released" ** Changed in: xpdf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1184328 Title: xpdf crashes with SIGSEGV in GlobalParams::findFontFile() Status in Fontconfig: New Status in Poppler: New Status in xpdf-intl: New Status in fontconfig package in Ubuntu: Confirmed Status in poppler package in Ubuntu: Confirmed Status in xpdf package in Ubuntu: Fix Released Bug description: xpdf crashes with SIGSEGV when opening the public available document DOSB_Pruefungswegweiser_Komplett_web_11_12.pdf The document can be viewed with mupdf, but there are also issues (non- crash) with other viewers, see Bug 429. xpdf crashes with SIGSEGV when opening the public available document 033_avv.pdf That document can be viewed with mupdf and other viewers without any issues. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xpdf 3.02-21build1 ProcVersionSignature: Ubuntu 3.2.0-44.69-generic-pae 3.2.44 Uname: Linux 3.2.0-44-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 Date: Sun May 26 13:57:27 2013 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True SourcePackage: xpdf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1184328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726745] [NEW] gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1556601 *** https://bugs.launchpad.net/bugs/1556601 Public bug reported: 1) Description: Ubuntu 17.10 Release:17.10 2) gnome-shell: Installé : 3.26.1-0ubuntu4 Candidat : 3.26.1-0ubuntu4 Table de version : *** 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) When I open a new user session I've got this issue. I can use Ubuntu without trouble but I've got this error message. I had 3 packages outdated I updated them. 4) But I've always the same error when I start a session. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Oct 24 09:55:09 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-22 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful ** Information type changed from Private to Public -- 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/1726745 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: 1) Description: Ubuntu 17.10 Release: 17.10 2) gnome-shell: Installé : 3.26.1-0ubuntu4 Candidat : 3.26.1-0ubuntu4 Table de version : *** 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) When I open a new user session I've got this issue. I can use Ubuntu without trouble but I've got this error message. I had 3 packages outdated I updated them. 4) But I've always the same error when I start a session. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Oct 24 09:55:09 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-22 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
I filed a glibc bug: https://sourceware.org/bugzilla/show_bug.cgi?id=22273 However, I do not know if that bug is the root cause of the issue reported here. ** Bug watch added: Sourceware.org Bugzilla #22273 https://sourceware.org/bugzilla/show_bug.cgi?id=22273 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: New Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 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 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 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.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704752] Re: Xorg crashed with SIGABRT in OsAbort() - right after fresh boot and logging in
*** This bug is a duplicate of bug 1547267 *** https://bugs.launchpad.net/bugs/1547267 Bug 1547267 cannot be found, so this bug can't be a duplicate of it, right?. -- 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/1704752 Title: Xorg crashed with SIGABRT in OsAbort() - right after fresh boot and logging in Status in xorg-server package in Ubuntu: New Bug description: - booted the system - logged in - crash occured ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sat Jul 15 04:12:59 2017 DistUpgraded: 2017-07-06 16:01:25,517 DEBUG failed to SystemUnLock() (E:Nicht gesperrt) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.22, 4.10.0-26-generic, x86_64: installed virtualbox, 5.1.22, 4.11.0-10-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0841] Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0841] InstallationDate: Installed on 2017-02-19 (147 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Acer Aspire E1-771 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=UUID=ab215173-8176-498e-b4e3-a5548ed8f9ee ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () LockServer () OsInit () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to artful on 2017-07-06 (10 days ago) UserGroups: dmi.bios.date: 06/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.23:bd06/19/2013:svnAcer:pnAspireE1-771:pvrV2.23:rvnAcer:rnEA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-771 dmi.product.version: V2.23 dmi.sys.vendor: Acer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jul 17 10:31:49 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1704752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 661640] Re: no sound after resume from suspend [Conexant ID 2c06] PA test tone failed (alsa tone succeeded)
David, thanks for your reply. As you may have guessed from the date I opened the bug, that was seven years ago. I no longer have the machine that was affected by this problem. However, I do remember the sound working in later Ubuntu versions. So I guess... fix released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/661640 Title: no sound after resume from suspend [Conexant ID 2c06] PA test tone failed (alsa tone succeeded) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Binary package hint: pulseaudio Before suspending my laptop, sound sent to my external monitor via HDMI works perfectly. However, after waking from suspend, all I hear from my speakers is low frequency buzzing and sound playback has stopped working ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: florian 16250 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 47' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,10280242,0010 HDA:83847616,10280242,00100201' Controls : 31 Simple ctrls : 19 Date: Sat Oct 16 11:15:04 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: pulseaudio Symptom: audio Title: [Conexant ID 2c06] PA test tone failed (alsa tone succeeded) dmi.bios.date: 01/07/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WP007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/07/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0WP007:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/661640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 178442] Re: Pulseaudio fails to initialize ICE1712 chipsets
Unfortunately I must say I've moved on from using both Ubuntu and the affected card within the last 10 years. Maybe one of the several other affected people can provide some feedback. -- 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/178442 Title: Pulseaudio fails to initialize ICE1712 chipsets Status in alsa-lib package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-lib source package in Lucid: Won't Fix Status in pulseaudio source package in Lucid: Won't Fix Bug description: Binary package hint: pulseaudio I have a problem that makes pulseaudio unusable for me. I noticed the only device listed by pulseaudio is my webcam (as an input device obviously), so I tried starting pulseaudio from the command line to see what was happening. This resulted in: "ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ICE1712.pcm.surround71.0:CARD=0' ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM surround71:0 W: alsa-util.c: Device hw:0 doesn't support 2 channels, changed to 10. W: alsa-util.c: Device hw:0 doesn't support sample format s16le, changed to s32le. W: alsa-util.c: Cannot find fallback mixer control "PCM". E: module-alsa-sink.c: Failed to create sink object E: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_output.pci_1412_1712_sound_card_0_alsa_playback_0"): initialization failed.ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ICE1712.pcm.surround71.0:CARD=0' ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM surround71:0 W: alsa-util.c: Device hw:0 doesn't support 2 channels, changed to 12. W: alsa-util.c: Device hw:0 doesn't support sample format s16le, changed to s32le. W: alsa-util.c: Cannot find fallback mixer control "Mic". E: module-alsa-source.c: Failed to create source object E: module.c: Failed to load module "module-alsa-source" (argument: "device_id=0 source_name=alsa_input.pci_1412_1712_sound_card_0_alsa_capture_0"): initialization failed." This is an up to date Hardy installation. Soundcard is a M-Audio Audiophile 2496. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/178442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 443004] Fw: a piece of useful info
Hi, I found some interesting information that seems to be very useful, check it out here http://tekky.net/alive.php?7978 Speak to you later, gibking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/443004 Title: Buttons disappear or do not respond to mouse clicks in Eclipse Status in Azureus: Invalid Status in Eclipse: Fix Released Status in LibGTK: Fix Released Status in eclipse package in Ubuntu: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Bug description: After update from alpha 6 to beta Karmic Koala - Eclispe is no longer working correct. It seems to be a problem with GTK. Few buttons are not working - nothing happens when pressing the button or the expected dialog is not shown as expected. I also tested other eclispe package with same result. eclipse 3.5.1 downloaded directly from www.eclipse.org has this bug. Solution: Install eclipse 3.5.1-0ubuntu7 (or later) from the Ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/azureus/+bug/443004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
Seeing exactly the same behavior as described in comment #71, happy to test any change -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1665418] Re: package libcairo-perl 1.106-1build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
you're welcome :-) ** Changed in: libcairo-perl (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcairo-perl in Ubuntu. https://bugs.launchpad.net/bugs/1665418 Title: package libcairo-perl 1.106-1build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libcairo-perl package in Ubuntu: Fix Released Bug description: tried to update the package using ubuntu software updater Description: Ubuntu 16.04.1 LTS Release: 16.04 libcairo-perl: Installed: 1.106-1build1 Candidate: 1.106-1build1 Version table: *** 1.106-1build1 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcairo-perl 1.106-1build1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Feb 16 18:49:21 2017 DpkgHistoryLog: Start-Date: 2017-02-16 18:49:05 Commandline: aptdaemon role='role-commit-packages' sender=':1.64' Install: snap-confine:amd64 (2.21, automatic) Upgrade: ubuntu-core-launcher:amd64 (1.0.27.1, 2.21) DuplicateSignature: package:libcairo-perl:1.106-1build1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libcairo-perl (--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 2016-08-10 (190 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libcairo-perl Title: package libcairo-perl 1.106-1build1 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/libcairo-perl/+bug/1665418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
