[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I tried to install stock 20.04.1 ubuntu with 'Install third party pkgs (e.g. nvidia)' + enable login automatically. After a reboot because of installation completed, the system will stuck in GDM login screen and can't login even if typing correct password. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Desktop-packages] [Bug 1855350] Re: Will not logout or shutdown from guest-session
I don't have much to add other than to say I am also experiencing this issue or one similar to it. I am running xfce on ubuntu 20.04 in a kvm virtual machine. The system was configured to boot to a command prompt with “systemctl set-default multi-user.target”, so when I want to run xfce this is done with "startxfce4". (problem description) if you log in to xfce then immediately log out it will fail with one of these errors: session manager must be in idle state when requesting a shutdown gdbus.error:org.freedesktop.dbus.error.invalidargs: type of message, "(yb)", does not match expected type "(b)" - example scenarios: reach the desktop, wait 45 seconds or more, try to log out, it works normally reach the desktop, try to log out immediately, get an error, try a second time, sometimes it will work reach the desktop, try to log out immediately, get an error, sit there doing nothing for a few seconds, sometimes it will log out - I tried playing around with the file 50-guest-wrapper.conf as others had mentioned, but I did not notice any difference. I also have an identically-configured centos 8 vm and it does not have this issue. (uninformed guess) When reaching the desktop something related to lightdm or xfce is failing in the background, once a timeout is reached, things work as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown from guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
Also, do you experience the same problem if you log into 'Ubuntu on Wayland'? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
Please run the following commands immediately after attempting a resolution change: lspci -kv > lspci.txt xrandr --verbose > xrandr.txt journalctl -b0 > journal.txt and then attach the resulting text files here. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] [NEW] gnome-control-center cannot change resolution of external monitor
Public bug reported: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: New Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar
Same here. Connected to google account. No sync with gnome calendar. Ubuntu 20.04.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Sounds reasonable. Marco? -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892288] [NEW] Comet Lake PCH-H RAID not support on Ubuntu20.04
Public bug reported:
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in ubuntu-meta package in Ubuntu:
New
Bug description:
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
This bug was fixed in the package alsa-lib - 1.2.2-2.3ubuntu3 --- alsa-lib (1.2.2-2.3ubuntu3) groovy; urgency=medium * d/p/0001-conf-USB-Audio-Disable-IEC958-on-Lenovo-ThinkStation.patch - Disable IEC958 on Lenovo ThinkStation P620 (LP: #1891461) -- Kai-Heng Feng Thu, 13 Aug 2020 22:54:44 +0800 -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu10 --- pulseaudio (1:13.99.1-1ubuntu10) groovy; urgency=medium * d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch: - recognize USB jack mixer to support jack detection (LP: #1891461) * d/p/0002-module-alsa-card-Set-a-minimum-profile-priority-if-i.patch: - resolve an issue when headset gets unplugged, HDMI audio is chosen instead of internal speaker (LP: #1891461) -- Kai-Heng Feng Thu, 13 Aug 2020 16:58:42 +0800 ** Changed in: pulseaudio (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: alsa-lib (Ubuntu Groovy) Status: Fix Committed => 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Disco and Eoan are EOL though, and Focal looks like it already has upstream commit 19e0840 included. So isn't it your proposed Bionic upload that would be different? Why not look into making that the same as what is in Focal? Regardless, I'd like you to please at least consider the possibility that cherry-picking only 86a00b6 from upstream is an incomplete fix to this bug and look into further upstream changes to that file since that commit to see if 19e0840 or others are relevant. If after understanding the relevant changes you conclude that there is still a benefit to SRU this as-is, can explain the trade-off in not also taking the other relevant changes and can make the case for 19e0840 being correct on its own, then I'll consider that. As it stands it appears to me that 19e0840 contains an oversight that was since corrected upstream, but your SRU doesn't include the correction. Unless you change my mind, I don't consider this acceptable for SRU. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892276] Re: pdf images stretched on desktop 20.04 after previous bug fix release
Please: 1. Run this command to send us more information about the system: apport-collect 1892276 2. Report the bug to the developers at https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues and then tell us the new issue ID. ** Tags added: focal ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete -- 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/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892094] Re: Xrandr brightness and gamma settings not remembered on power resume
In that case please report the bug upstream at: https://gitlab.gnome.org/GNOME/mutter/issues and then tell us the new issue ID. -- 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/1892094 Title: Xrandr brightness and gamma settings not remembered on power resume Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Brightness Reset to Maximum on Nvidia GPU Desktop when setting on Blank Screen The Desktop LED Monitor brightness or Gamma level is not preserved and reset when I set gnome-control-center setting on Power to Blank Screen. I try to post as much details as possible. -I did a test by setting Nvidia X Server Color Correction and set any brightness and gamma.It get reset when Power Saving Blank Screen time active which I had set 10 minutes to save power by auto turning off the display. -The second test was by installing a Brightness Controller which use Xrandr but same result of getting reset when I set Blank Screen.I also manually set xrandr --output DVI-D-0 –brightness 0.5 --gamma 0.5:0.5:0.5 an value get reset after the trigger from blank screen. -Third test by selecting Nouveau open source but same result of getting reset when I set Blank Screen. -Forth test , manually turn off the monitor ‘xset dpms force off’ it doesn’t trigger the brightness reset. Since the system is using Desktop GPU , the folder on xblacklight is empty without config files. The flow > Set brightness > Power Saving Blank Screen time active > Brightness reset > External Monitor dim and Turn Off > Press any keyboard button to wakeup the display > Brightness Stay at reset value of Full 100% brightness. The details I had tested , I suspect gsd-power may have related to this issue.This is happen before which I had find a solution to other brightness reset happen when every restart , delete a files upon restart , open a web browser with and play a video stream, login and logout , suspend and Power Saving Blank Screen. All of this are affected by gsd-color.Which I had found a link a fix suggestion https://github.com/LordAmit/Brightness/issues/102#issuecomment-374253884 by disable /usr/lib/gnome-settings-daemon/gsd-color on startup. The only left is Power Saving Blank Screen still get reset when it get active.I am not too sure whether it is related to gsd-power , I did disable it but it also disable Power Saving Blank Screen together. It just goes to screensaver mode and did not turn off the monitor. I do not have any basic on gsd-power code https://gitlab.gnome.org/starnight/gnome-settings- daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power /gsd-power-manager.c Not knowing which line did it callback and get reset , presumably ‘GSD_POWER_IDLE_MODE_BLANK’ ? Fresh Install OS : Ubuntu 18.04.4 Architecture: amd64 Nvidia : GTX 1050 Driver : NVIDIA Driver Version: 440.100 uname : 5.4.0-42-generic DisplayManager: gdm3 Journalctl log when blank screen active. nvidia-settings[19556]: PRIME: is it supported? no nvidia-settings[19556]: PRIME: No offloading required. Abort nvidia-settings[19556]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Check that logind is properly installed and pam_systemd is getting used at login. gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login. gnome-screensav[1551]: Source ID 19140 was not found when attempting to remove it gnome-session-binary[1521]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login. gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login. Reading the log shows somewhere it trigger brightness reset.The Nvidia Setting prime message is show because I am using a desktop dedicated GPU without using nvidia prime for laptop check to switching between build in intel gpu and nvidia. In which way I could fix brightness reset when I need to set Blank Screen to turn off the monitor to save power ? I did another test by manually turn off the monitor ‘xset dpms force off’ it doesn’t trigger the brightness reset.It only happen when it is set with a timer at setting blank screen to 1-15 minutes and which it call for a PID which unknown and I assume gsd-power that trigger the reset. The most I can find is the gsd-power code https://gitlab.gnome.org/starnight/gnome-settings- daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power /gsd-power-manager.c .I am nor expert on daemon.service pin
[Desktop-packages] [Bug 1892249] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892249 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: System crashed and I needed to reboot. The screen turned in black and I couldn't do nothing. I attached files here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 22:32:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3752] InstallationDate: Installed on 2020-04-24 (117 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1892249/+subscriptions --
[Desktop-packages] [Bug 1892207] Re: Desktop wallpaper resolution reduces.
*** This bug is a duplicate of bug 1862308 *** https://bugs.launchpad.net/bugs/1862308 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1862308, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1862308 Desktop wallpaper is slightly blurry -- 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/1892207 Title: Desktop wallpaper resolution reduces. Status in gnome-shell package in Ubuntu: New Bug description: When an image is set as wallpaper the resolution of the image gets reduced. The original image is 3840*2160 pixels and is very clear when viewed in the Image Viewer Application. However when the same image is set as a wallpaper the resolution reduces and the image becomes blurred and is not as clear and sharp as when it is viewed in the Image Viewer Application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 19:55:35 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-23 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 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/1892207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Given the age of this bug I suggest it's most helpful to make each series' fix the same. If the symptoms, or similar symptoms persist then I would track that in a new bug so that we can make additional fixes the same in each series. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap
** Also affects: gnome-control-center (Ubuntu Groovy) Importance: Low Assignee: Bin Li (binli) Status: Fix Released ** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-control-center (Ubuntu Focal) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu Focal) Importance: Undecided => Low ** Tags added: fixed-in-3.36.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Status in gnome-control-center source package in Groovy: Fix Released Bug description: There is a display bug when you unplug the network cable on focal. Please see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892276] [NEW] pdf images stretched on desktop 20.04 after previous bug fix release
Public bug reported: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New -- 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/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681962] Re: gedit handles encodings inconsistently (and corrupts files)
I saw this assert too and reported it upstream https://gitlab.gnome.org/GNOME/gedit/-/issues/353#note_894322 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #353 https://gitlab.gnome.org/GNOME/gedit/-/issues/353 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1681962 Title: gedit handles encodings inconsistently (and corrupts files) Status in gedit package in Ubuntu: New Bug description: The handling of codepages by gedit is inconsistent and may corrupt files and/or cause loss of data: gedit 3.18.3 / Ubuntu 16.04 LTS If I use the command gedit --encoding ISO-8859-15 If, for some reason, the (new) input contains an UTF-8 character (e.g., by typing, or by pasting) then gedit does not save the file, but issues a warning: Could not save the file <..> using the "Western (ISO-8859-15)" character encoding. but does not show the incorrect character. Now there are two options: (1) If the file is saved using UTF-8 then also the "old" (unchanged) content is saved using UTF-8 (i.e., it corrupts the existing data) (2) Using "Save as ..." in order to avoid this does not work either: gedit acts as if it had obeyed this command, but after exit there is no such file (i.e., newly added material is lost), but the terminal shows the following error message: ** (gedit:20985): CRITICAL **: _gedit_tab_save_as_async: assertion 'tab->state == GEDIT_TAB_STATE_NORMAL || tab->state == GEDIT_TAB_STATE_EXTERNALLY_MODIFIED_NOTIFICATION || tab->state == GEDIT_TAB_STATE_SHOWING_PRINT_PREVIEW' failed I think that this behaviour counts as a (quite) serious bug. Moreover, I made some tests and noticed another quite curious behaviour: If a new file is opened with this command and then saved with text containing non-standard characters (like accented characters), these are saved using UTF-8 encoding. If this file is opened again they are shown "binary" as two characters while newly added characters are treated as the should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1681962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3
[Desktop-packages] [Bug 1892094] Re: Xrandr brightness and gamma settings not remembered on power resume
Someone had tested on 20.04 before and it did reset too. Similar issue. https://askubuntu.com/questions/1233030/nvidia-settings-reset-randomly https://askubuntu.com/questions/1241645/nvidia-settings-reset-when-playing-video There is possible gsd.power.manager check for blacklight but it was set by nvidia thus it get reset when value null. /* Fetch the current target brightness (not the actual display brightness) * and return if it is already lower than the idle percentage. */ gsd_backlight_get_brightness (manager->backlight, ); if (brightness < idle_percentage) https://gitlab.gnome.org/starnight/gnome-settings- daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power/gsd- power-manager.c Or there is possible conflict on gsd.power on wayland with x11. -- 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/1892094 Title: Xrandr brightness and gamma settings not remembered on power resume Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Brightness Reset to Maximum on Nvidia GPU Desktop when setting on Blank Screen The Desktop LED Monitor brightness or Gamma level is not preserved and reset when I set gnome-control-center setting on Power to Blank Screen. I try to post as much details as possible. -I did a test by setting Nvidia X Server Color Correction and set any brightness and gamma.It get reset when Power Saving Blank Screen time active which I had set 10 minutes to save power by auto turning off the display. -The second test was by installing a Brightness Controller which use Xrandr but same result of getting reset when I set Blank Screen.I also manually set xrandr --output DVI-D-0 –brightness 0.5 --gamma 0.5:0.5:0.5 an value get reset after the trigger from blank screen. -Third test by selecting Nouveau open source but same result of getting reset when I set Blank Screen. -Forth test , manually turn off the monitor ‘xset dpms force off’ it doesn’t trigger the brightness reset. Since the system is using Desktop GPU , the folder on xblacklight is empty without config files. The flow > Set brightness > Power Saving Blank Screen time active > Brightness reset > External Monitor dim and Turn Off > Press any keyboard button to wakeup the display > Brightness Stay at reset value of Full 100% brightness. The details I had tested , I suspect gsd-power may have related to this issue.This is happen before which I had find a solution to other brightness reset happen when every restart , delete a files upon restart , open a web browser with and play a video stream, login and logout , suspend and Power Saving Blank Screen. All of this are affected by gsd-color.Which I had found a link a fix suggestion https://github.com/LordAmit/Brightness/issues/102#issuecomment-374253884 by disable /usr/lib/gnome-settings-daemon/gsd-color on startup. The only left is Power Saving Blank Screen still get reset when it get active.I am not too sure whether it is related to gsd-power , I did disable it but it also disable Power Saving Blank Screen together. It just goes to screensaver mode and did not turn off the monitor. I do not have any basic on gsd-power code https://gitlab.gnome.org/starnight/gnome-settings- daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power /gsd-power-manager.c Not knowing which line did it callback and get reset , presumably ‘GSD_POWER_IDLE_MODE_BLANK’ ? Fresh Install OS : Ubuntu 18.04.4 Architecture: amd64 Nvidia : GTX 1050 Driver : NVIDIA Driver Version: 440.100 uname : 5.4.0-42-generic DisplayManager: gdm3 Journalctl log when blank screen active. nvidia-settings[19556]: PRIME: is it supported? no nvidia-settings[19556]: PRIME: No offloading required. Abort nvidia-settings[19556]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Check that logind is properly installed and pam_systemd is getting used at login. gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login. gnome-screensav[1551]: Source ID 19140 was not found when attempting to remove it gnome-session-binary[1521]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login. gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login. Reading the log shows somewhere it trigger brightness reset.The Nvidia Setting prime message is show because I am using a desktop dedicated GPU without using nvidia prime for laptop check to switching between build in
[Desktop-packages] [Bug 1892249] Re: Xorg crash
Another attach. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892249/+attachment/5402890/+files/prevboot.txt -- 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/1892249 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: System crashed and I needed to reboot. The screen turned in black and I couldn't do nothing. I attached files here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 22:32:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3752] InstallationDate: Installed on 2020-04-24 (117 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892249] [NEW] Xorg crash
Public bug reported: System crashed and I needed to reboot. The screen turned in black and I couldn't do nothing. I attached files here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 22:32:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3752] InstallationDate: Installed on 2020-04-24 (117 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 crash focal ubuntu ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/bugs/1892249/+attachment/5402869/+files/lspcik.txt -- 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/1892249 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: System crashed and I needed to reboot. The screen turned in black and I couldn't do nothing. I attached files here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for
[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Changed in: alsa-lib (Ubuntu Focal) Status: New => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => Fix Committed ** Changed in: pulseaudio (Ubuntu Focal) Status: New => Fix Committed -- 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/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Changed in: alsa-lib (Ubuntu Focal) Status: New => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => Fix Committed ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1892244] Re: Spaces not showing correctly with Chinese characters
** Attachment added: "Test PDF display in Adobe Reader" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892244/+attachment/5402861/+files/Adobe%20Reader.JPG -- 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/1892244 Title: Spaces not showing correctly with Chinese characters Status in evince package in Ubuntu: New Bug description: Package: evince Status: install ok installed Priority: optional Section: gnome Architecture: amd64 Version: 3.36.0-2 Ubuntu version- Description: Ubuntu 20.04 LTS Release: 20.04 I created a PDF file through python reportLab library, containing random Chinese alphabet. The spaces in between the Chinese letters are not showing up correctly in Evince. I have attached the PDF file - chinese_test.pdf, that did not behave correctly. I have also attached the screenshots of how the file is being displayed in Adobe Reader and Evince. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892244] Re: Spaces not showing correctly with Chinese characters
** Attachment added: "Test PDF display in Evince" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892244/+attachment/5402862/+files/evince.JPG -- 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/1892244 Title: Spaces not showing correctly with Chinese characters Status in evince package in Ubuntu: New Bug description: Package: evince Status: install ok installed Priority: optional Section: gnome Architecture: amd64 Version: 3.36.0-2 Ubuntu version- Description: Ubuntu 20.04 LTS Release: 20.04 I created a PDF file through python reportLab library, containing random Chinese alphabet. The spaces in between the Chinese letters are not showing up correctly in Evince. I have attached the PDF file - chinese_test.pdf, that did not behave correctly. I have also attached the screenshots of how the file is being displayed in Adobe Reader and Evince. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892244] [NEW] Spaces not showing correctly with Chinese characters
Public bug reported: Package: evince Status: install ok installed Priority: optional Section: gnome Architecture: amd64 Version: 3.36.0-2 Ubuntu version- Description: Ubuntu 20.04 LTS Release: 20.04 I created a PDF file through python reportLab library, containing random Chinese alphabet. The spaces in between the Chinese letters are not showing up correctly in Evince. I have attached the PDF file - chinese_test.pdf, that did not behave correctly. I have also attached the screenshots of how the file is being displayed in Adobe Reader and Evince. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Test PDF" https://bugs.launchpad.net/bugs/1892244/+attachment/5402860/+files/chinese_testing.pdf -- 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/1892244 Title: Spaces not showing correctly with Chinese characters Status in evince package in Ubuntu: New Bug description: Package: evince Status: install ok installed Priority: optional Section: gnome Architecture: amd64 Version: 3.36.0-2 Ubuntu version- Description: Ubuntu 20.04 LTS Release: 20.04 I created a PDF file through python reportLab library, containing random Chinese alphabet. The spaces in between the Chinese letters are not showing up correctly in Evince. I have attached the PDF file - chinese_test.pdf, that did not behave correctly. I have also attached the screenshots of how the file is being displayed in Adobe Reader and Evince. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705156] Re: gnome-shell interface shows up extremely scaled up
For the record, this just happened to me on a *fresh* install of Ubuntu 18.04. The first thing I did after system installed months ago was to install Unity from repositories (and set lightdm as the default greeter). Unity may not be the default anymore in 18.04 but it runs and looks great. Today I needed to test Gnome Shell. So I logged out, and in the greeter selected "Ubuntu" instead of pre-selected "Unity (Default)". And that *insane* zoom up happened. Same as described by OP. Logging out and back into Unity everything is OK. Also tried "Ubuntu on Wayland)" and same super super zoom. Super+Alt+8 fixes the zoom. -- 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/1705156 Title: gnome-shell interface shows up extremely scaled up Status in gnome-shell package in Ubuntu: Invalid Bug description: Trying the gnome session, the login process and gdm screen work perfectly, but then in gnome shell, I get a very scaled up interface that is completely unusable. Even the mouse cursor size is like 1/4 of the screen's size Instead, logging back to Unity, the interface shows up with the correct, usual scaling dimensions ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 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 CurrentDesktop: Unity:Unity7 Date: Wed Jul 19 09:23:06 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['chromium-browser.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'update-manager.desktop', 'skypeforlinux.desktop', 'slack.desktop', 'virtualbox.desktop', 'popcorn-time.desktop', 'chrome-hmjkmjkepdijhoojdojkdfohbdgmmhki-Profile_2.desktop', 'pcgarage_py.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2012-11-25 (1696 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) 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/1705156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705156] Re: gnome-shell interface shows up extremely scaled up
For the record, this just happened to me on a *fresh* install of Ubuntu 18.04. The first thing I did after system installed months ago was to install Unity from repositories (and set lightdm as the default greeter). Unity may not be the default anymore in 18.04 but it runs and looks great. Today I needed to test Gnome Shell. So I logged out, and in the greeter selected "Ubuntu (default)" instead of pre-selected "Ubuntu (Unity)". And that *insane* zoom up happened. Same as described by OP. Logging out and back into Unity everything is OK. Also tried "Ubuntu (default on Wayland)" and same super zoom -- 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/1705156 Title: gnome-shell interface shows up extremely scaled up Status in gnome-shell package in Ubuntu: Invalid Bug description: Trying the gnome session, the login process and gdm screen work perfectly, but then in gnome shell, I get a very scaled up interface that is completely unusable. Even the mouse cursor size is like 1/4 of the screen's size Instead, logging back to Unity, the interface shows up with the correct, usual scaling dimensions ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 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 CurrentDesktop: Unity:Unity7 Date: Wed Jul 19 09:23:06 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['chromium-browser.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'update-manager.desktop', 'skypeforlinux.desktop', 'slack.desktop', 'virtualbox.desktop', 'popcorn-time.desktop', 'chrome-hmjkmjkepdijhoojdojkdfohbdgmmhki-Profile_2.desktop', 'pcgarage_py.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2012-11-25 (1696 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) 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/1705156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 910272] Re: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it
Same problem for me. I have an old parallel-only printer. It has been working with a dedicated printer server, but the printer server died and the PC has no parallel port. So I connected a USB-to-LPT cable. As I attach the cable /var/log/syslog shows: parport0: fix this legacy no-device port driver! lp0: using parport0 (polling) There does not exist a /dev/usb/lp0. I still set "DeviceURI parallel:/dev/usb/lp0" since that is what the instructions still say (https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_-.3E_Parallel_adapter), and indeed that fails. I also tried "DeviceURI parallel:/dev/parport0" and CUPS rejected it. Then I tried "DeviceURI parallel:/dev/lp0". CUPS accepted it, I sent a test print, and it just sits on the job queue with the msg "Printer not connected; will retry in 30 seconds". # usb_printerid /dev/lp0 Error: Invalid argument: GET_DEVICE_ID on '/dev/lp0' # usb_printerid /dev/parport0 Error: Invalid argument: GET_DEVICE_ID on '/dev/parport0' At another moment, I got a different error: # usb_printerid /dev/lp0 Error: Device or resource busy: can't open '/dev/lp0' This is on Bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/910272 Title: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it Status in cups package in Ubuntu: Fix Released Status in cups source package in Oneiric: Won't Fix Bug description: Parallel port dot matrix printer Panasonic KX-P2124 connected via usb- parallel cable to HP6600 PC; running Ubuntu 11.10 system located on external hard drive attached by usb. Worked on Ubuntu version 8 using URI "parallel:/dev/usb/lp0". Understand that usblp has been deprecated; replace with ??? Cups reports printer not connected. CUPS version is (from UbuntuSoftwareCenter) - "cups 1.5.0-8ubuntu6". #Researched existing bugs - lots of info - no results. No "Help" menu found by selecting upper right located "Gear"/"Printers; could not find any "Wizard." Thank you for your assistance, nvsoar w8@w8-FJ463AAR-ABA-a6528p:~$ uname -a Linux w8-FJ463AAR-ABA-a6528p 3.0.0-15-generic #24-Ubuntu SMP Mon Dec 12 15:25:25 UTC 2011 i686 i686 i386 GNU/Linux w8@w8-FJ463AAR-ABA-a6528p:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 067b:3507 Prolific Technology, Inc. PL3507 ATAPI6 Bridge Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader Bus 002 Device 002: ID 050d:0002 Belkin Components #Device immediately above is usb to parallel cable w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep lp lp 17455 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep ppdev ppdev 12849 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep parport_pc parport_pc 32114 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/* ls: cannot access /dev/usb/lp*: No such file or directory crw-rw-r-- 1 root root 189, 0 2011-12-30 15:04 /dev/bus/usb/001/001 crw-rw-r-- 1 root root 189, 1 2011-12-30 15:04 /dev/bus/usb/001/002 crw-rw-r-- 1 root root 189, 3 2011-12-30 15:04 /dev/bus/usb/001/004 crw-rw-r-- 1 root root 189, 128 2011-12-30 15:04 /dev/bus/usb/002/001 crw-rw-r-- 1 root lp 189, 129 2011-12-30 15:25 /dev/bus/usb/002/002 w8@w8-FJ463AAR-ABA-a6528p:~$ dmesg | grep par [0.00] Booting paravirtualized kernel on bare hardware [0.00] vt handoff: transparent VT on vt#7 [0.210399] hpet0: 3 comparators, 32-bit 25.00 MHz counter [ 28.754567] uss720: protocols (eg. bitbang) over USS720 usb to parallel cables [ 28.893725] type=1400 audit(1325286282.534:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=705 comm="apparmor_parser" [ 28.893736] type=1400 audit(1325286282.534:3): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=755 comm="apparmor_parser" [ 28.894175] type=1400 audit(1325286282.534:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=755 comm="apparmor_parser" [ 28.894324] type=1400 audit(1325286282.534:5): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=705 comm="apparmor_parser" [ 28.894438] type=1400 audit(1325286282.534:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=755 comm="apparmor_parser" [ 28.894592] type=1400 audit(1325286282.534:7): apparmor="STATUS" operation="profile_replace"
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
This mess just goes on and on and on. Can somebody provide an update on: - What work is being done to get fractional scaling working on Ubuntu with nVidia cards? - How someone who wants to help fix this required basic functionality would do so? I don't think that read >170 posts just to scale a GUI is a good experience for users. It is unclear who is a user and who is actually an authority on the topic. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Christian: the bug occurred again today while using the small fix version: so that one didn't solve it for me. I will start using the big fix now and see how it goes through the next weeks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Incomplete Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878330] Re: wrong icon used in the about dialog
This bug was fixed in the package rhythmbox - 3.4.4-1ubuntu3 --- rhythmbox (3.4.4-1ubuntu3) groovy; urgency=medium * d/p/git_icons_fixes.patch: - Fix broken icon in about and notifications (lp: #1878330) -- Sebastien Bacher Wed, 19 Aug 2020 16:37:38 +0200 ** Changed in: rhythmbox (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1878330 Title: wrong icon used in the about dialog Status in rhythmbox package in Ubuntu: Fix Released Bug description: Broken image icon appears in the title bar, notifications, and in the about dialog These files are missing: /usr/share/icons/hicolor/ ├── 16x16 │ └── apps │ └── rhythmbox.png ├── 22x22 │ └── apps │ └── rhythmbox.png ├── 24x24 │ └── apps │ └── rhythmbox.png ├── 256x256 │ └── apps │ └── rhythmbox.png ├── 32x32 │ └── apps │ └── rhythmbox.png ├── 48x48 │ └── apps │ └── rhythmbox.png └── scalable └── apps └── rhythmbox-symbolic.svg Rhythmbox Plugins: Tray Icon, ReplyGain, Notification, MPRIS D-Bus interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed May 13 00:03:50 2020 InstallationDate: Installed on 2018-04-29 (744 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
I'm not sure this fix is complete. What about, for example: https://gitlab.gnome.org/GNOME/gnome- shell/-/commit/19e084036a1dc3c5da010c3e7a42ce67df317797? As far as I understand, it is exactly (and only) the fsync() call that we're trying to move off the main thread, and this commit suggests to me that the fix proposed in this SRU won't actually do that. Please could you take a look, and also for anything else relevant in upstream's branches? We risk regression every time we land an SRU, so if this commit or others need to go in also, then it'd be better for us to SRU a fix for this only once. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761216] Re: Backup fails if backup destination is not mounted
This bug was fixed in the package deja-dup - 42.2-1ubuntu1 --- deja-dup (42.2-1ubuntu1) groovy; urgency=medium * Resynchronize on Debian, remaining change * debian/control.in, debian/rules: - Suggests python3-pydrive, ideally that would be a recommends but the package needs to be promoted first - set -Dpydrive_pkgs=python3-pydrive this way deja-dup knows how to install the pydrive backend on demand via packagekit * debian/patches/disable-google-drive.patch: - remove the patch disabling google drive, python3-pydrive is available now in focal -- Sebastien Bacher Wed, 19 Aug 2020 16:50:27 +0200 ** Changed in: deja-dup (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1761216 Title: Backup fails if backup destination is not mounted Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Released Bug description: I have set my backup destination to a separate drive in the machine, but not at the default location. When the backup runs, it fails stating permission denied, as the destination drive is not mounted. When I enter the proper destination in the backup at the "storage location", the drive then mounts and is present on the desktop. Then the backup will run successfully. I then "unmount" the drive using the menu on the drive icon, and the mounted drive disappears from the desktop. I don't need a bunch of drives listed or shown on my desktop, as it detracts from the beauty of the screen. If I mount the drive before running the backup, it will succeed. My point with this is that I am not going to mount the drive every time I run backup, and when mounted, I don't need it listed or shown on my desktop. In unity, the drives appeared in the launcher or dock, and there was an option to "remove from launcher", which still left the drive mounted, but off the desktop and launcher. This was a nice way to fix this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1761216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu3 --- alsa-ucm-conf (1.2.2-1ubuntu3) groovy; urgency=medium * d/p/0001-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch Add proper stream and jack assignment to Lenovo ThinkStation P620 (LP: #1891461) -- Kai-Heng Feng Tue, 18 Aug 2020 17:39:15 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: Fix Committed => 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1891739] Re: 4. and 5. mouse-button on thumb does not react during save-dialogue in LO
Cherry DW5100 I would expect to geht back with one mouse-button for the thumb, if I was in the wrong folder, as I can do in Firefox, or Nautilus. ** Attachment added: "example" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1891739/+attachment/5402825/+files/Bildschirmfoto%20von%202020-08-19%2018-41-34.png -- 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/1891739 Title: 4. and 5. mouse-button on thumb does not react during save-dialogue in LO Status in libreoffice package in Ubuntu: New Bug description: While "saving" the mouse-buttons don't react to browse in the menu structure as usual e.g. in a filebrowser like nautilus. (But I'm not sure if it has something to do with the gnome-shell of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-core 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 09:37:11 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2020-05-23 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash LD_LIBRARY_PATH= SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1891739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866620] Re: deja-dup-monitor startup invalid path
Below is the contents of /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop. If this is the expected value, consider this bug fixed. I also confirm that Deja Dup starts correctly every day. My current Ubuntu version is Groovy Gorilla. # SPDX-License-Identifier: CC-BY-SA-4.0 # SPDX-FileCopyrightText: Michael Terry [Desktop Entry] Name=Backup Monitor Comment=Schedules backups at regular intervals X-Ubuntu-Gettext-Domain=deja-dup Icon=org.gnome.DejaDup Exec=/usr/libexec/deja-dup/deja-dup-monitor X-GNOME-Autostart-Delay=120 StartupNotify=false NoDisplay=true Type=Application Categories=Utility;Archiving; -- 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/1866620 Title: deja-dup-monitor startup invalid path Status in deja-dup package in Ubuntu: Incomplete Bug description: deja-dup-monitor has the following paths in the file /etc/xdg/autostart/deja-dup-monitor.desktop, which are invalid: TryExec=/usr/lib/deja-dup/deja-dup-monitor Exec=/usr/lib/deja-dup/deja-dup-monitor This prevents deja-dup from making automatic back-ups. To resolve the situation, I had to manually update the paths to: TryExec=/usr/libexec/deja-dup/deja-dup-monitor Exec=/usr/libexec/deja-dup/deja-dup-monitor 1. Distribution: Description: Ubuntu Focal Fossa (development branch) 2. Version: deja-dup 40.5-1 duplicity 0.8.11.1596-1 3. Settings: org.gnome.DejaDup exclude-list ['/home/wiktor/.local/share/Trash', '/home/wiktor/Downloads', '/home/wiktor/.android', '/home/wiktor/.android-sdk', '/home/wiktor/.programy', '/home/wiktor/.VirtualBoxVMs', '/home/wiktor/Music', '/home/wiktor/Videos', '/home/wiktor/.gradle', '/home/wiktor/.p2', '/home/wiktor/.package-manager', '/home/wiktor/.cache', '/home/wiktor/.pub-cache', '/home/wiktor/.local/share/Daedalus', '/home/wiktor/.daedalus'] org.gnome.DejaDup allow-metered false org.gnome.DejaDup root-prompt true org.gnome.DejaDup periodic-period 1 org.gnome.DejaDup include-list ['$HOME'] org.gnome.DejaDup prompt-check '2017-10-13T18:23:45.958383Z' org.gnome.DejaDup periodic true org.gnome.DejaDup delete-after 0 org.gnome.DejaDup last-restore '2020-02-16T11:22:29.255500Z' org.gnome.DejaDup last-run '2020-03-09T10:55:11+00' org.gnome.DejaDup full-backup-period 90 org.gnome.DejaDup last-backup '2020-03-09T10:55:11+00' org.gnome.DejaDup backend 'local' org.gnome.DejaDup nag-check '2020-01-26T01:18:25.016870Z' org.gnome.DejaDup.S3 folder 'wiktor' org.gnome.DejaDup.S3 bucket '' org.gnome.DejaDup.S3 id '' org.gnome.DejaDup.Rackspace container 'wiktor' org.gnome.DejaDup.Rackspace username '' org.gnome.DejaDup.OpenStack authurl '' org.gnome.DejaDup.OpenStack tenant '' org.gnome.DejaDup.OpenStack container 'wiktor' org.gnome.DejaDup.OpenStack username '' org.gnome.DejaDup.GCS folder 'wiktor' org.gnome.DejaDup.GCS bucket '' org.gnome.DejaDup.GCS id '' org.gnome.DejaDup.Local folder '/mnt/iza/deja-dup' org.gnome.DejaDup.Google folder 'wiktor' org.gnome.DejaDup.GOA folder 'wiktor' org.gnome.DejaDup.GOA id '' org.gnome.DejaDup.GOA type 'owncloud' org.gnome.DejaDup.GOA migrated false org.gnome.DejaDup.Drive folder 'wiktor' org.gnome.DejaDup.Drive uuid '' org.gnome.DejaDup.Drive name '' org.gnome.DejaDup.Drive icon '' org.gnome.DejaDup.File path '' org.gnome.DejaDup.File relpath @ay [] org.gnome.DejaDup.File name '' org.gnome.DejaDup.File migrated true org.gnome.DejaDup.File type 'normal' org.gnome.DejaDup.File uuid '' org.gnome.DejaDup.File short-name '' org.gnome.DejaDup.File icon '' org.gnome.DejaDup.Remote folder 'wiktor' org.gnome.DejaDup.Remote uri '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1866620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889322] Re: nvidia gforce
I'm not sure what the original problem is with this bug, but regarding the denial messages, that seems specific to the rocketchat-server snap. Those denial messages could be silenced if the rocketchat-server snap used (or had connected it the interface is disconnected) network- observe. I do not see that the snap currently uses network-observe, so perhaps the upstream of this snap should be contacted about that @ https://open.rocket.chat/channel/ubuntu-snap (from the snap info contact info) -- 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/1889322 Title: nvidia gforce Status in snapd package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: fonctionne a ne pas se connecter pour mise a jour ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/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: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Jul 28 19:52:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710] [19da:7326] InstallationDate: Installed on 2020-07-25 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=08d4bac1-d829-450c-ae55-3b06a793cd85 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/23/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-GR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 xserver.bootTime: Tue Jul 28 18:36:06 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputEee PC WMI hotkeys KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1889322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Changed in: pulseaudio (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: alsa-ucm-conf (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1891956] Re: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-m
Just remove any manually installed openoffice packages, like "openoffice-debian-menus". An upgrade path with such packages present is not supported. -- 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/1891956 Title: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 Status in libreoffice package in Ubuntu: New Bug description: not sure what exactly happened, I uninstalled it and it never totally went. So, when I tried reinstalling it, I was told it was broken ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Uname: Linux 5.4.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 17 18:32:07 2020 ErrorMessage: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 InstallationDate: Installed on 2020-08-12 (5 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1891956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Changed in: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: alsa-lib (Ubuntu Groovy) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: alsa-lib (Ubuntu Groovy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1891956] Re: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-m
Was this system installed as a 20.04 and then you just did an apt update and upgrade? It sounds like your system is in a funky state with these libreoffice packages so to workaround it, try remove all libreoffice debs and reinstalling them with: $ sudo apt-get remove --purge libreoffice* $ sudo apt install libreoffice -- 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/1891956 Title: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 Status in libreoffice package in Ubuntu: New Bug description: not sure what exactly happened, I uninstalled it and it never totally went. So, when I tried reinstalling it, I was told it was broken ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Uname: Linux 5.4.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 17 18:32:07 2020 ErrorMessage: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 InstallationDate: Installed on 2020-08-12 (5 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1891956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891739] Re: 4. and 5. mouse-button on thumb does not react during save-dialogue in LO
Can you tell me more? What model of mouse are you using? So you click save and while the save dialog is up, these mouse buttons don't do anything - what do you expect to happen? -- 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/1891739 Title: 4. and 5. mouse-button on thumb does not react during save-dialogue in LO Status in libreoffice package in Ubuntu: New Bug description: While "saving" the mouse-buttons don't react to browse in the menu structure as usual e.g. in a filebrowser like nautilus. (But I'm not sure if it has something to do with the gnome-shell of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-core 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 09:37:11 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2020-05-23 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash LD_LIBRARY_PATH= SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1891739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager
upstream asked for some log, could you provide the requested information? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1806334 Title: Thunderbolt 2 storage not auto mounted and show in file manager Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in OEM Priority Project focal series: New Status in udisks: New Status in udisks2 package in Ubuntu: Triaged Bug description: OS 18.04 & 20.04 Plug thunderbolt 2 storage device, can see the device in lsblk as /dev/sda (and /dev/sda1 is a ext4 partition) however I can't see it in file manager (check attachment, it say TBT3 in the picture, however I use TBT2 and I can reproduce it) public bug: https://github.com/storaged-project/udisks/issues/793 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1806334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887222] Re: Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught)
** Changed in: rhythmbox (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1887222 Title: Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught) Status in rhythmbox package in Ubuntu: Fix Committed Bug description: Plugins bundled with Rhythmbox including "Cover Art Search", "FM Radio", and "Python Console" still link to http://www.rhythmbox.org/. Although http://www.rhythmbox.org/ used to redirect to https://wiki.gnome.org/Apps/Rhythmbox (source: https://web.archive.org/web/20200122080148/http://www.rhythmbox.org/), it now redirects to https://www.dropcatch.com/domain/rhythmbox.org, a site that appears to be selling the domain. Note: This is my first bug report! I apologize for attaching files that aren't relevant -- I'm still figuring this out! Most relevant is the PNG attatchment, bugReport.png. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 02:02:53 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-03-24 (109 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2020-06-19 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1887222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892207] [NEW] Desktop wallpaper resolution reduces.
Public bug reported: When an image is set as wallpaper the resolution of the image gets reduced. The original image is 3840*2160 pixels and is very clear when viewed in the Image Viewer Application. However when the same image is set as a wallpaper the resolution reduces and the image becomes blurred and is not as clear and sharp as when it is viewed in the Image Viewer Application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 19:55:35 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-23 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892207 Title: Desktop wallpaper resolution reduces. Status in gnome-shell package in Ubuntu: New Bug description: When an image is set as wallpaper the resolution of the image gets reduced. The original image is 3840*2160 pixels and is very clear when viewed in the Image Viewer Application. However when the same image is set as a wallpaper the resolution reduces and the image becomes blurred and is not as clear and sharp as when it is viewed in the Image Viewer Application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 19:55:35 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-23 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 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/1892207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866620] Re: deja-dup-monitor startup invalid path
Thank you for your bug report, what is not working exactly? The file you are mentioning is a leftoever (we should clean it up on upgrades), the package nowadays installs /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop which has the correct paths. Could you check if you have this one, and if you do describe the difference with the one you edited? ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Low ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- 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/1866620 Title: deja-dup-monitor startup invalid path Status in deja-dup package in Ubuntu: Incomplete Bug description: deja-dup-monitor has the following paths in the file /etc/xdg/autostart/deja-dup-monitor.desktop, which are invalid: TryExec=/usr/lib/deja-dup/deja-dup-monitor Exec=/usr/lib/deja-dup/deja-dup-monitor This prevents deja-dup from making automatic back-ups. To resolve the situation, I had to manually update the paths to: TryExec=/usr/libexec/deja-dup/deja-dup-monitor Exec=/usr/libexec/deja-dup/deja-dup-monitor 1. Distribution: Description: Ubuntu Focal Fossa (development branch) 2. Version: deja-dup 40.5-1 duplicity 0.8.11.1596-1 3. Settings: org.gnome.DejaDup exclude-list ['/home/wiktor/.local/share/Trash', '/home/wiktor/Downloads', '/home/wiktor/.android', '/home/wiktor/.android-sdk', '/home/wiktor/.programy', '/home/wiktor/.VirtualBoxVMs', '/home/wiktor/Music', '/home/wiktor/Videos', '/home/wiktor/.gradle', '/home/wiktor/.p2', '/home/wiktor/.package-manager', '/home/wiktor/.cache', '/home/wiktor/.pub-cache', '/home/wiktor/.local/share/Daedalus', '/home/wiktor/.daedalus'] org.gnome.DejaDup allow-metered false org.gnome.DejaDup root-prompt true org.gnome.DejaDup periodic-period 1 org.gnome.DejaDup include-list ['$HOME'] org.gnome.DejaDup prompt-check '2017-10-13T18:23:45.958383Z' org.gnome.DejaDup periodic true org.gnome.DejaDup delete-after 0 org.gnome.DejaDup last-restore '2020-02-16T11:22:29.255500Z' org.gnome.DejaDup last-run '2020-03-09T10:55:11+00' org.gnome.DejaDup full-backup-period 90 org.gnome.DejaDup last-backup '2020-03-09T10:55:11+00' org.gnome.DejaDup backend 'local' org.gnome.DejaDup nag-check '2020-01-26T01:18:25.016870Z' org.gnome.DejaDup.S3 folder 'wiktor' org.gnome.DejaDup.S3 bucket '' org.gnome.DejaDup.S3 id '' org.gnome.DejaDup.Rackspace container 'wiktor' org.gnome.DejaDup.Rackspace username '' org.gnome.DejaDup.OpenStack authurl '' org.gnome.DejaDup.OpenStack tenant '' org.gnome.DejaDup.OpenStack container 'wiktor' org.gnome.DejaDup.OpenStack username '' org.gnome.DejaDup.GCS folder 'wiktor' org.gnome.DejaDup.GCS bucket '' org.gnome.DejaDup.GCS id '' org.gnome.DejaDup.Local folder '/mnt/iza/deja-dup' org.gnome.DejaDup.Google folder 'wiktor' org.gnome.DejaDup.GOA folder 'wiktor' org.gnome.DejaDup.GOA id '' org.gnome.DejaDup.GOA type 'owncloud' org.gnome.DejaDup.GOA migrated false org.gnome.DejaDup.Drive folder 'wiktor' org.gnome.DejaDup.Drive uuid '' org.gnome.DejaDup.Drive name '' org.gnome.DejaDup.Drive icon '' org.gnome.DejaDup.File path '' org.gnome.DejaDup.File relpath @ay [] org.gnome.DejaDup.File name '' org.gnome.DejaDup.File migrated true org.gnome.DejaDup.File type 'normal' org.gnome.DejaDup.File uuid '' org.gnome.DejaDup.File short-name '' org.gnome.DejaDup.File icon '' org.gnome.DejaDup.Remote folder 'wiktor' org.gnome.DejaDup.Remote uri '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1866620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station
** Tags added: ubuntu-certified -- 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/1872034 Title: [Focal] No HDMI output through thunderbolt docking station Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: I can find monitor in display list, but no output from it. Also, I can't switch to extend mode, it failed to apply the setting and switched back to mirror mode. [Steps] 1. Connect a thunderbolt docking station to thunderbolt port. 2. Connect HDMI monitor to HDMI port on the docking station. 3. Switch mode in display setting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:44:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Just deleted 240G syslog file after system stalled. Syslog.1 is 20G full of folowing: Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]: [7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825126] Re: Shell dialog shadows are clipped on the top and left edges
** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => In Progress ** Changed in: mutter (Ubuntu) Status: Won't Fix => In Progress ** Tags removed: disco ** Tags added: focal groovy ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low ** Changed in: mutter (Ubuntu) Importance: Medium => Low -- 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/1825126 Title: Shell dialog shadows are clipped on the top and left edges Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: Shell dialog shadows are clipped on the top and left edges. Although the shadow only seems to exist in the Yaru theme, not upstream, I can also fix the bug by removing: this._dialog.set_offscreen_redirect(Clutter.OffscreenRedirect.ALWAYS); from gnome-shell/js/ui/dialog.js ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Apr 17 16:21:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-04 (134 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Above workaround with older ibt* files does not work on Ubuntu 20.04.1 LTS on Elitebook 840 G6, Bluetooth devices: Samsung HM1350 Sony WH-CH700N -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue here, Ubuntu 20.04.1 LTS on Elitebook 840 G6, Bluetooth devices: Samsung HM1350 Sony WH-CH700N -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891157] Re: [MIR] ipp-usb
I have talked with the upstream maintainer of ipp-usb, Alexander Pevzner now and he will emove the dependency on ini.v1. ** Changed in: golang-github-openprinting-goipp (Ubuntu) Status: Incomplete => New ** Changed in: golang-gopkg-ini.v1 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ipp-usb in Ubuntu. https://bugs.launchpad.net/bugs/1891157 Title: [MIR] ipp-usb Status in golang-github-openprinting-goipp package in Ubuntu: New Status in golang-gopkg-ini.v1 package in Ubuntu: Invalid Status in ipp-usb package in Ubuntu: New Bug description: IPP-over-USB ipp-usb is the second implementation of the IPP-over-USB standard. This allows the PWG's Internet Printing Protocol (IPP) which is currently the most common communication protocol for network printers also to be used via USB, simply by a network printer being emulated on localhost. Advantages are: - IPP is a high-level bi-directional packet-based protocol for printing, scanning, and fax - Full device capabilities can be polled from the device, together with using standardized printing and scanning data format driverless printing and scanning is possible - Status, like loaded paper, toner levels, ... can get polled - Printing and scanning can be performed simultaneously and independently - The administration web interface can get accessed ipp-usb detects supported devices automatically and advertises their full functionality via DNS-SD on localhost, CUPS and the appropriate SANE backends discover the device automatically then and it is immediately available, no drivers needed, it just works. This makes thousands of printers, scanners, and multi-function devices work on USB, USB-only devices, like the scanner Canon Lide 400 get working for the first time. Why ipp-usb? There is ippusbxd already -- ippusbxd was the first implementation of IPP-over-USB, with the very same intentions, but it has problems which were not easily to be solved in C and so after a short discussion with me the author of the driverless scanning SANE backend sane-airscan (https://github.com/alexpevzner/sane-airscan) created a first draft of ipp-usb in Go within a few hours, which solved these problems. The project has matured with the time and seems to work perfectly. See also here: https://github.com/OpenPrinting/ippusbxd#before-you-begin-ippusbxd-or- ipp-usb See the original README for the rationale of ipp-usb: https://github.com/OpenPrinting/ipp-usb -- Unfortunately, the naive implementation, which simply relays a TCP connection to USB, does not work. It happens because closing the TCP connection on the client side has a useful side effect of discarding all data sent to this connection from the server side, but it does not happen with USB connections. In the case of USB, all data not received by the client will remain in the USB buffers, and the next time the client connects to the device, it will receive unexpected data, left from the previous abnormally completed request. Actually, it is an obvious flaw in the IPP-over-USB standard, but we have to live with it. So the implementation, once the HTTP request is sent, must read the entire HTTP response, which means that the implementation must understand the HTTP protocol, and effectively implement a HTTP reverse proxy, backed by the IPP-over-USB connection to the device. And this is what the ipp-usb program actually does. -- Many users reported this to work perfectly and I am using it since its creation in January 2020 on a daily basis without problems. Here are the issues of ippusbxd: https://github.com/OpenPrinting/ippusbxd/issues Especially https://github.com/OpenPrinting/ippusbxd/issues/15 shows that packets of canceled connections can get stuck in buffer and spilled out on next connection. Problems of ippusbxd's architecture and lack of useful C libraries to solve this is discussed here. https://github.com/OpenPrinting/ippusbxd/issues/14 The flakiness of the web admin interface is caused by above problems. Due to this most other Linux distributions are also migrating to ipp- usb. Chrome OS was the last system sticking with ippusbxd but they have introduced their own replacement, ippusb_bridge (https://github.com/dgreid/platform2/tree/master/ippusb_bridge) now. From the README.md of ippusb_bridge: -- The impetus for creating this was that ippusbxd has lost a lot of interest since the release of ipp-usb, a similar project written in Golang. Upstream provides only some oversight, and the code is pure C and has security bugs. -- With this the interest in ippusbxd has gone and ippusbxd can get considered deprecated. goipp - goipp (Debian/Ubuntu
[Desktop-packages] [Bug 1891767] Re: Nautilus does not show video thumbnails
** Summary changed: - Nautilus not showing video thumbnails + Nautilus does not show video thumbnails -- 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/1891767 Title: Nautilus does not show video thumbnails Status in nautilus package in Ubuntu: Incomplete Bug description: Using Ubuntu 20.10 (Groovy) Daily Live, GNOME session (gnome-session) on Wayland. Nautilus is no longer showing thumbnails (generated by Totem) for some video files, although the Totem thumbnail generator (totem-video-thumbnailer) is working. Nautilus is showing thumbnails for video files with (Ogg) Theora codec content (even if wrapped in a non-Ogg file format, such as mkv), but not for others, although I have installed all the required/usual libraries (libav*, gstreamer1*). Deleting the thumbnail fail cache (~/.cache/thumbnails/fail/) does not help. Installing ffmpegthumbnailer does not help either. This seems to be a regression, or maybe some libraries for video files in non-free codec formats have not been updated properly. Package versions are as follows:- Nautilus: 1:3.37.90-1ubuntu1 Totem: 3.34.1-2ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Aug 15 23:47:22 2020 InstallationDate: Installed on 2020-08-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200814) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892150] Re: can select but cannot drag multiple files on desktop only 1 file moves
*** This bug is a duplicate of bug 1886322 *** https://bugs.launchpad.net/bugs/1886322 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1886322, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** This bug has been marked a duplicate of bug 1886322 Unable to move all selected files on desktop -- 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/1892150 Title: can select but cannot drag multiple files on desktop only 1 file moves Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: here is a question on askubuntu.com facing the same problem: https://askubuntu.com/questions/1266068/i-cannot-move-multiple-files-by-drag-and-drop-method there is also a link to a video in the description of the question and I have also attatched my own screen recording. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 13:11:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-08 (163 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-08-09 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1892150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892150] [NEW] can select but cannot drag multiple files on desktop only 1 file moves
Public bug reported: here is a question on askubuntu.com facing the same problem: https://askubuntu.com/questions/1266068/i-cannot-move-multiple-files-by-drag-and-drop-method there is also a link to a video in the description of the question and I have also attatched my own screen recording. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 13:11:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-08 (163 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-08-09 (9 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "video of my own desktop. Cannot drag multiple files" https://bugs.launchpad.net/bugs/1892150/+attachment/5402710/+files/ubuntu-desktop_bug -- 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/1892150 Title: can select but cannot drag multiple files on desktop only 1 file moves Status in gnome-shell package in Ubuntu: New Bug description: here is a question on askubuntu.com facing the same problem: https://askubuntu.com/questions/1266068/i-cannot-move-multiple-files-by-drag-and-drop-method there is also a link to a video in the description of the question and I have also attatched my own screen recording. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 13:11:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-08 (163 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-08-09 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892146] [NEW] [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium
Public bug reported: Deleting the ~/snaps folder in ubuntu seems to permanently break gnome dash window tracking. Steps to reproduce: 1) Add chromium-browser.desktop to your dash / dock favourites. Chromium Windows get attributed to this favourite when created. 2) Delete the ~/snaps folder, quit all chromium processes and / or reboot 3) The ~/snaps folder gets recreated, but Chromium windows now get attributed to a new chromium-browser dash icon, ignoring the favourite created in step 1 I know I know, don't delete the ~/snaps folder then! Unfortunately, there are situations when this is beyond my control. These desktops are gonna get into the hands of normal users, like my dad and my colleagues. They will delete the folder by accident or because they don't know and don't care about snaps. Deleting it shouldn't permanently break window tracking. This is on a fully patched 20.04 system. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: Deleting the ~/snaps folder in ubuntu seems to permanently break gnome dash window tracking. Steps to reproduce: 1) Add chromium-browser.desktop to your dash / dock favourites. Chromium Windows get attributed to this favourite when created. 2) Delete the ~/snaps folder, quit all chromium processes and / or reboot 3) The ~/snaps folder gets recreated, but Chromium windows now get attributed to a new chromium-browser dash icon, ignoring the favourite created in step 1 I know I know, don't delete the ~/snaps folder then! Unfortunately, there are situations when this is beyond my control. These desktops are gonna get into the hands of normal users, like my dad and my colleagues. They will delete the folder by accident or because they don't know and don't care about snaps. Deleting it shouldn't permanently break window tracking. + + This is on a fully patched 20.04 system. -- 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/1892146 Title: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium Status in chromium-browser package in Ubuntu: New Bug description: Deleting the ~/snaps folder in ubuntu seems to permanently break gnome dash window tracking. Steps to reproduce: 1) Add chromium-browser.desktop to your dash / dock favourites. Chromium Windows get attributed to this favourite when created. 2) Delete the ~/snaps folder, quit all chromium processes and / or reboot 3) The ~/snaps folder gets recreated, but Chromium windows now get attributed to a new chromium-browser dash icon, ignoring the favourite created in step 1 I know I know, don't delete the ~/snaps folder then! Unfortunately, there are situations when this is beyond my control. These desktops are gonna get into the hands of normal users, like my dad and my colleagues. They will delete the folder by accident or because they don't know and don't care about snaps. Deleting it shouldn't permanently break window tracking. This is on a fully patched 20.04 system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892136] Re: reverse prime produces corrupted output on specific resolutions
Please note that 19.04 is no longer supported. It would be nice to know for sure if 20.04 is still a problem. ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Aleksander Miera (amiera) ** Tags added: bionic ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #889 https://gitlab.freedesktop.org/xorg/xserver/-/issues/889 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/889 Importance: Unknown Status: Unknown ** Changed in: xorg-server (Ubuntu) Status: New => In Progress -- 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/1892136 Title: reverse prime produces corrupted output on specific resolutions Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: In Progress Bug description: The issue has initially been discovered for resolution 1366x768 on a DisplayLink (evdi)-backed device, but applies also to UDL, as well as reverse prime setups (rendering on Intel, output through NVidia). The issue manifests with 1366x768 and several other resolutions only, due to the fact that the GPU seems to use 64-aligned framebuffer stride. This is "accidentally" fine with the most popular VGA resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the stride would be 1920*4 -> 7680, which is divisible by 64 w/o a remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to update the stride with the GPU-provided value instead of the Xorg- calculated one at the stage of sharing the pixmap between GPUs. Doing that at earlier stage would probably require distinguishing between allocation of a FB and a generic pixmap, which is the same for Xorg. Issue for sure was seen on 18.04 and 19.04, probably still there for 20.04. Upstream report: https://gitlab.freedesktop.org/xorg/xserver/-/issues/889 And posted (not yet integrated) fix: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1892136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
It is not a common issue, I tried to reproduce it on many machines, but so far can't reproduce the problem. It is not easy to debug without a physical machine to reproduce the problem. -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
and here's another new wrinkle... it looks like after my machine has been put to sleep and woken up a few times, it now creates a new dummy audio device each time, until my system is full of dummy audio devices. seriously what is up with sleep/wake and pulse in ubuntu 20.04?? -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891712] Re: nautilus takes ages to start up when not already running
ok well, this is exceptionally weird. I was seeing some issues with my wine install where the internal state was all messed up and it was just hanging starting apps and so I blew it away and rebuilt it, and now I can't reproduce this nautilus issue. Is there any connection between nautilus and wine? I can't think of why that would be, but here we are, and I'm very confused. -- 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/1891712 Title: nautilus takes ages to start up when not already running Status in nautilus package in Ubuntu: Incomplete Bug description: I'm filing this bug separately because it appears to be distinct from #1063282, but the root cause may be similar. when I start nautilus and it's not already running, it can take an extremely long time to start, up to even 2m before a file browser appears. as well, opening certainly locations (like the trash, or network shares) can also take another huge span of time before they complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44 Uname: Linux 5.4.0-42-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:21:04 2020 InstallationDate: Installed on 2020-07-15 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892136] [NEW] reverse prime produces corrupted output on specific resolutions
Public bug reported: The issue has initially been discovered for resolution 1366x768 on a DisplayLink (evdi)-backed device, but applies also to UDL, as well as reverse prime setups (rendering on Intel, output through NVidia). The issue manifests with 1366x768 and several other resolutions only, due to the fact that the GPU seems to use 64-aligned framebuffer stride. This is "accidentally" fine with the most popular VGA resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the stride would be 1920*4 -> 7680, which is divisible by 64 w/o a remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to update the stride with the GPU-provided value instead of the Xorg-calculated one at the stage of sharing the pixmap between GPUs. Doing that at earlier stage would probably require distinguishing between allocation of a FB and a generic pixmap, which is the same for Xorg. Issue for sure was seen on 18.04 and 19.04, probably still there for 20.04. Upstream report: https://gitlab.freedesktop.org/xorg/xserver/-/issues/889 And posted (not yet integrated) fix: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1892136 Title: reverse prime produces corrupted output on specific resolutions Status in xorg-server package in Ubuntu: New Bug description: The issue has initially been discovered for resolution 1366x768 on a DisplayLink (evdi)-backed device, but applies also to UDL, as well as reverse prime setups (rendering on Intel, output through NVidia). The issue manifests with 1366x768 and several other resolutions only, due to the fact that the GPU seems to use 64-aligned framebuffer stride. This is "accidentally" fine with the most popular VGA resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the stride would be 1920*4 -> 7680, which is divisible by 64 w/o a remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to update the stride with the GPU-provided value instead of the Xorg- calculated one at the stage of sharing the pixmap between GPUs. Doing that at earlier stage would probably require distinguishing between allocation of a FB and a generic pixmap, which is the same for Xorg. Issue for sure was seen on 18.04 and 19.04, probably still there for 20.04. Upstream report: https://gitlab.freedesktop.org/xorg/xserver/-/issues/889 And posted (not yet integrated) fix: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1892136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
