[Desktop-packages] [Bug 1917974] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1917974 Title: Xorg freeze Status in xorg-server package in Ubuntu: New Bug description: I had been using the recommended nvidia driver (nvidia-driver-460). I recently changed to xserver-xorg-video-nouveau for the following reasons: 1) The resolution configuration was not saved. It is, every power off and power on the resolution restarted to low resolution. 2) The syslog file in /var/log/ constantly was filled with logs (may be with a rate of 1 GB per hour), then, I was enforced to install busybox-syslogd to stop the logging and continue with activities. 3) When using xserver-xorg-video-nouveau, in contrast with nvidia- driver-460, i didn't had to reset the resolution configuration, which was great, but now the screen is constantly freezing and i had to use alt+SysRq+REISUB two times in a day ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 22:59:16 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP108 [GeForce GT 1030] [1458:375c] InstallationDate: Installed on 2021-02-27 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=28228923-7b88-4688-b9fd-157d9ebc22df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2020 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: X99-k9 dmi.board.vendor: MACHINIST dmi.board.version: V1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd06/03/2020:br5.11:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnMACHINIST:rnX99-k9:rvrV1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/1917974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917806] Re: [amdgpu] Freezes after submitting the login password
** Attachment added: "prevboot log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+attachment/5473726/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1917806 Title: [amdgpu] Freezes after submitting the login password Status in gnome-shell package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Freezes after submitting the login password. If I shutdown the system it usually works afterwards on the first boot, but not subsequent reboots. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-lowlatency 5.4.86 Uname: Linux 5.4.0-66-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 06:39:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314] InstallationDate: Installed on 2020-12-07 (87 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-lowlatency root=UUID=d8850dd9-0462-4a0b-a22c-24c0df1551a7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/01/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3405:bd02/01/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917974] [NEW] Xorg freeze
Public bug reported: I had been using the recommended nvidia driver (nvidia-driver-460). I recently changed to xserver-xorg-video-nouveau for the following reasons: 1) The resolution configuration was not saved. It is, every power off and power on the resolution restarted to low resolution. 2) The syslog file in /var/log/ constantly was filled with logs (may be with a rate of 1 GB per hour), then, I was enforced to install busybox- syslogd to stop the logging and continue with activities. 3) When using xserver-xorg-video-nouveau, in contrast with nvidia- driver-460, i didn't had to reset the resolution configuration, which was great, but now the screen is constantly freezing and i had to use alt+SysRq+REISUB two times in a day ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 22:59:16 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Today GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP108 [GeForce GT 1030] [1458:375c] InstallationDate: Installed on 2021-02-27 (7 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=28228923-7b88-4688-b9fd-157d9ebc22df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2020 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: X99-k9 dmi.board.vendor: MACHINIST dmi.board.version: V1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd06/03/2020:br5.11:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnMACHINIST:rnX99-k9:rvrV1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917974 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I had been using the recommended nvidia driver (nvidia-driver-460). I recently changed to xserver-xorg-video-nouveau for the following reasons: 1) The resolution configuration was not saved. It is, every power off and power on the resolution restarted to low resolution. 2) The syslog file in /var/log/ constantly was filled with logs (may be with a rate of 1 GB per hour), then, I was enforced to install busybox-syslogd to stop the logging and continue with activities. 3) When using xserver-xorg-video-nouveau, in contrast with nvidia- driver-460, i didn't had to reset the resolution configuration, which was great, but now the screen is constantly freezing and i had to use alt+SysRq+REISUB two times in a day ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 22:59:16 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly
[Desktop-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
i have the same issue Description: Ubuntu 20.04.2 LTS Release: 20.04 CurrentDesktop: LXQt Architecture: amd64 Uname: Linux 5.8.17-050817-generic x86_64 in attach gdb glxinfo ** Attachment added: "gdb_glxinfo.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1915870/+attachment/5473703/+files/gdb_glxinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
Here's some output that perhaps is helpful # Normal orientation with tearing: $ xrandr Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1366x768 60.06*+ 40.04 1280x720 60.06 1024x768 60.06 800x600 60.06 640x480 60.06 HDMI-A-0 disconnected (normal left inverted right x axis y axis) # Workaround configuration $ xrandr Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP connected primary 1366x768+0+0 inverted X and Y axis (normal left inverted right x axis y axis) 344mm x 193mm 1366x768 60.06*+ 40.04 1280x720 60.06 1024x768 60.06 800x600 60.06 640x480 60.06 HDMI-A-0 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
A little investigation and the following implements johnnyl33-k's workaround from the command line. $ xrandr --output eDP --reflect xy --rotate inverted --mode 1366x768 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908535] Re: Xorg crash after clean Ubuntu 20.10 install on Intel system
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1908535 Title: Xorg crash after clean Ubuntu 20.10 install on Intel system Status in xorg-server package in Ubuntu: Expired Bug description: Intel Core i5/8GB/256GB. Each time a minute or so after I boot into the system, I get a system error, but there are no useful details. The only thing I found is a crash log: https://pastebin.com/W54KDMGE Since there does not seem to be much readible stuff in there for a common person, I cannot determine whether or not this bug has been reported already. How can I prevent this bug from happening? I also tried to run sudo ubuntu-bug xorg. That did not work: $ sudo ubuntu-bug xorg cat: /var/log/lightdm/x-0-greeter.log: No such file or directory cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908608] Re: Crash to login screen when plugging in/out external monitor
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908608 Title: Crash to login screen when plugging in/out external monitor Status in gnome-shell package in Ubuntu: Expired Bug description: This matches the title of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I don't want to assume it is the same considering that was allegedly fixed three years ago. journal: dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8 dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 10 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 7 dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6 - bcm5974: client bug: event processing lagging behind by 42ms, your system is too slow dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 8 dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, fd 15 dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine nitrokey failed to change udev device /sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice: dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device dec 17 23:12:53 computer-name fwupd[3384]: Flags:none dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1 dec 17 23:12:53 computer-name gnome-shell[2891]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed dec 17 23:12:53 computer-name gnome-shell[2891]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with signal 11 dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 0x55db60db91a0 == dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The Wayland connection broke. Did the Wayland compositor die? dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.82, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) (disconnected from bus) dec 17 23:13:06 computer-name unknown[3020]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3031]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3030]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name unknown[3064]: Error reading events from display: Brutet rör dec 17 23:13:06 computer-name systemd[2728]:
[Desktop-packages] [Bug 1909006] Re: Split screen
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1909006 Title: Split screen Status in xorg-server package in Ubuntu: Expired Bug description: My screen is split in 4 and forums have directed me to try and update my video graphics drivers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 14:52:26 2020 DistUpgraded: 2020-08-03 22:59:11,316 DEBUG inhibit gnome-session idle DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fb30] InstallationDate: Installed on 2020-02-09 (316 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TOSHIBA Satellite C850-F74T ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=ed9c77f9-c96b-4904-8ba9-1576f2c3a198 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-03 (140 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PLCSF8 dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.00:bd08/31/2012:svnTOSHIBA:pnSatelliteC850-F74T:pvrPSCBWF-011004F3:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite C850-F74T dmi.product.sku: PSCBWF dmi.product.version: PSCBWF-011004F3 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1909006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909152] Re: color calibration fails when using gnome gui on 20.10
[Expired for colord (Ubuntu) because there has been no activity for 60 days.] ** Changed in: colord (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1909152 Title: color calibration fails when using gnome gui on 20.10 Status in colord package in Ubuntu: Expired Status in gnome-control-center package in Ubuntu: Expired Bug description: in the past, I've used DisplayCalGUI to calibrate my displays. however, that software hasn't been updated to use Python3 properly, so it doesn't run on recent Ubuntu releases. I thought I'd try the builtin gnome calibration, but it seems completely broken on 20.10. I've tried two difference systems with fresh minimal installs, each has a different display and a different brand of colour calibration hardware. in both cases, they get to testing the coloured swatches, and fail, with an error saying: "Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device." however, looking in the output from `journalctl`, colord seems to claim that it succeeded in generating a profile. So I'm guessing there's something broken in the integration between colord and gnome-settings? all I know is it reports that it failed, and gnome doesn't show any new profile to use. here's the `journalctl` output: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: No of test patches = 64 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Omitted 0 zero measurements Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Find white & black points Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Initial white point = 1.051779 0.999535 0.796168 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [46B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.615651 0.622859 0.645454 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.647113 0.653246 0.680660 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.531396 0.531212 0.553325 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix and single gamma curve... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [26B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.009811 0.389211 0.558809 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.144281 0.347751 0.505066 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.198306 0.283542 0.312788 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Gamma = -1.574397 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Doing White point fine tune: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Before fine tune, rel WP = XYZ 0.95783065 0.99709777 0.79463644, Lab 99.887672 -0.619729 2.283133 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: After fine tune, rel WP = XYZ 0.96420288 1. 0.82490540, Lab 100.00 0.00 0.00 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: abs WP = XYZ 1.04542265 0.99666916 0.76687003, Lab 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.04542265 0.99666916 0.76687003, Lab = 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Scaling White Point by 1.003342 to make Y = 1.0 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Display Luminance = 0.940928 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: White point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Done gamma/shaper and matrix creation Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Profile done ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: colord 1.4.4-2build1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Wed Dec 23 13:51:43 2020 SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1909152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910140] Re: Alignment of password field in 20.04 login screen not in centre
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1910140 Title: Alignment of password field in 20.04 login screen not in centre Status in gnome-shell package in Ubuntu: Expired Bug description: ubuntu is now launching slowly for me it gives me a black screen at launch that shows the result of a system file check then it jumps to the login screen which seems strange as the alignment of the password field appears now on the left of the screen instead of in the centre as it used to be then ubuntu desktop starts, the screen seems to be shifting or 3 seconds then it adjusts itself to normal what should I reinstall to fix this please ? thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 19:35:37 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-01-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1910140/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909152] Re: color calibration fails when using gnome gui on 20.10
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1909152 Title: color calibration fails when using gnome gui on 20.10 Status in colord package in Ubuntu: Expired Status in gnome-control-center package in Ubuntu: Expired Bug description: in the past, I've used DisplayCalGUI to calibrate my displays. however, that software hasn't been updated to use Python3 properly, so it doesn't run on recent Ubuntu releases. I thought I'd try the builtin gnome calibration, but it seems completely broken on 20.10. I've tried two difference systems with fresh minimal installs, each has a different display and a different brand of colour calibration hardware. in both cases, they get to testing the coloured swatches, and fail, with an error saying: "Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device." however, looking in the output from `journalctl`, colord seems to claim that it succeeded in generating a profile. So I'm guessing there's something broken in the integration between colord and gnome-settings? all I know is it reports that it failed, and gnome doesn't show any new profile to use. here's the `journalctl` output: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: No of test patches = 64 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Omitted 0 zero measurements Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Find white & black points Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Initial white point = 1.051779 0.999535 0.796168 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [46B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.615651 0.622859 0.645454 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.647113 0.653246 0.680660 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.531396 0.531212 0.553325 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix and single gamma curve... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [26B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.009811 0.389211 0.558809 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.144281 0.347751 0.505066 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.198306 0.283542 0.312788 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Gamma = -1.574397 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Doing White point fine tune: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Before fine tune, rel WP = XYZ 0.95783065 0.99709777 0.79463644, Lab 99.887672 -0.619729 2.283133 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: After fine tune, rel WP = XYZ 0.96420288 1. 0.82490540, Lab 100.00 0.00 0.00 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: abs WP = XYZ 1.04542265 0.99666916 0.76687003, Lab 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.04542265 0.99666916 0.76687003, Lab = 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Scaling White Point by 1.003342 to make Y = 1.0 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Display Luminance = 0.940928 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: White point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Done gamma/shaper and matrix creation Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Profile done ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: colord 1.4.4-2build1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Wed Dec 23 13:51:43 2020 SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1909152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917972] [NEW] video driver
Public bug reported: Missing video driver ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/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: Fri Mar 5 23:14:32 2021 DistUpgraded: 2020-10-28 02:47:12,562 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-44-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] MachineType: LENOVO 4177RVU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=1bf42ead-69dd-4936-8fef-0af815b29be6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-10-28 (128 days ago) dmi.bios.date: 09/05/2016 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET79WW (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177RVU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvr83ET79WW(1.49):bd09/05/2016:br1.49:efr1.20:svnLENOVO:pn4177RVU:pvrThinkPadT420:rvnLENOVO:rn4177RVU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4177RVU dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917972 Title: video driver Status in xorg package in Ubuntu: New Bug description: Missing video driver ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/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: Fri Mar 5 23:14:32 2021 DistUpgraded: 2020-10-28 02:47:12,562 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-43-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-44-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] MachineType: LENOVO 4177RVU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=1bf42ead-69dd-4936-8fef-0af815b29be6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-10-28 (128 days ago) dmi.bios.date: 09/05/2016 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET79WW (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177RVU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.20 dmi.modalias:
[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
I have the same issue. As mentioned in reddit thread in OP, the login screen displays properly at 1366x768. I'm running MATE so I'm not sure how to implement the workaround @johnnyl33-k mentions for Xubuntu since there are no reflection options. I will note setting rotation to 'upside-down' in Control Center->Monitor Preference does not suffer from the tearing the 'normal' rotation does. It's just hard to work upside down! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libdrm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Google has not removed API access. They have stopped a google key from working. It works fine, as far as I can tell. But you need to get your own key. The well known PPA with VAAPI, https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev, has always worked like this. I use Fedora on another machine, and with my own keys, Chromium works exactly as before. On Sat, 6 Mar 2021 at 03:00, Michel-Ekimia <1816...@bugs.launchpad.net> wrote: > Sorry to use this bug report as a forum but IMO it is useless to spend > more time on chromium. > > Ubuntu & users should define a Blink-based open source browser like > Brave that could be supported nicely upstream unlike whats google is > doing by removing sync API access with google services > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816497 > > Title: > [snap] vaapi chromium no video hardware decoding > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917969] [NEW] Ubuntu dock extension fills journal with JavaScript errors
Public bug reported: It's annoying. The output of journalctl is full of JS ERROR messages and other problems with gjs. It's really broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 Uname: Linux 5.10.10-051010-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 6 03:21:34 2021 InstallationDate: Installed on 2014-06-05 (2465 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-26 (313 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "gnome-shell JavaScript errors. It's 312MB inflated." https://bugs.launchpad.net/bugs/1917969/+attachment/5473674/+files/ubuntu-dock-errors.log.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1917969 Title: Ubuntu dock extension fills journal with JavaScript errors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: It's annoying. The output of journalctl is full of JS ERROR messages and other problems with gjs. It's really broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 Uname: Linux 5.10.10-051010-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 6 03:21:34 2021 InstallationDate: Installed on 2014-06-05 (2465 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-26 (313 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1917969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917966] [NEW] Hp-Lip not working. Noprinter can be added
Public bug reported: Had installed Hp-lip several times, many ways, and can not ADD a printer after APP say has no printer detected. Also appears this error No system tray detected on this system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 22:22:25 2021 InstallationDate: Installed on 2021-02-19 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1917966 Title: Hp-Lip not working. Noprinter can be added Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Had installed Hp-lip several times, many ways, and can not ADD a printer after APP say has no printer detected. Also appears this error No system tray detected on this system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 22:22:25 2021 InstallationDate: Installed on 2021-02-19 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1917966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917962] [NEW] can't save selected_device parameter
Public bug reported: simple-scan can't find my HP scanner. If I bring up simple-scan from the apps menu the Scanner box is blank and there's no way to enter data into it. If I start it from the command line, passing scanner type and IP address ( simple-scan hpaio:/net/psc_2500_series?ip=10.0.0.1 ) it finds the scanner and scans, and this scanner shows up in the Preferences "Scanner" box, but there's no way to save it on the Preferences screen. I can't find any way to set and save this preference via application configuration either. Using dconf-editor I can edit the selected-device parameter to add my scanner to the selected-devices field but when I start simple-scan it doesn't see the device. Curiously, if I use dconf- editor to change the save-directory field, the new directory is used to save. I also am unable to find a way to add the scanner type & IP address to the apps menu launcher. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1917962 Title: can't save selected_device parameter Status in simple-scan package in Ubuntu: New Bug description: simple-scan can't find my HP scanner. If I bring up simple-scan from the apps menu the Scanner box is blank and there's no way to enter data into it. If I start it from the command line, passing scanner type and IP address ( simple-scan hpaio:/net/psc_2500_series?ip=10.0.0.1 ) it finds the scanner and scans, and this scanner shows up in the Preferences "Scanner" box, but there's no way to save it on the Preferences screen. I can't find any way to set and save this preference via application configuration either. Using dconf-editor I can edit the selected- device parameter to add my scanner to the selected-devices field but when I start simple-scan it doesn't see the device. Curiously, if I use dconf-editor to change the save-directory field, the new directory is used to save. I also am unable to find a way to add the scanner type & IP address to the apps menu launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1917962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793472] Re: [wishlist] Add mdadm into desktop by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1793472 Title: [wishlist] Add mdadm into desktop by default Status in OEM Priority Project: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Consider the situation that we have OEM systems with software raid devices and the desktop image will be installed on them as primary storage. Another work is to patch casper to support md (Please refer bug #1793444). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1793472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1319494] Re: Ubuntu installation image should come with mdadm
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released -- 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/1319494 Title: Ubuntu installation image should come with mdadm Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: It would be great if the Ubuntu installation image came with mdadm. If was unlucky enough to be Internetless while installing Ubuntu, I wouldn't be able to install to or create a RAID array. I know that Ubuntu has lessened its restrictions on installation image size, and since mdadm's installed size is 1.2MB, I think it should be included. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 Date: Wed May 14 17:27:51 2014 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InterpreterPath: /usr/bin/python3.4 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1319494/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1319494] Re: Ubuntu installation image should come with mdadm
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1319494 Title: Ubuntu installation image should come with mdadm Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: It would be great if the Ubuntu installation image came with mdadm. If was unlucky enough to be Internetless while installing Ubuntu, I wouldn't be able to install to or create a RAID array. I know that Ubuntu has lessened its restrictions on installation image size, and since mdadm's installed size is 1.2MB, I think it should be included. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 Date: Wed May 14 17:27:51 2014 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InterpreterPath: /usr/bin/python3.4 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1319494/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update
I am a happy user of the Ubuntu systems "account online" service happy, so far I think .. or maybe not now?!? it makes me think that between now and March 15 we could all be left on foot ... but what is Google? Did she start strangling her babies one after another? -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917906] Re: please sync qpdf 10.3.0-1 from debian experimental
By the way, I am updating the CUPS Snap to QPDF 10.3.0 right now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental Status in qpdf package in Ubuntu: Incomplete Bug description: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917906] Re: please sync qpdf 10.3.0-1 from debian experimental
As we are past Feature Freeze for Hirsute now, I cannot accept a new upstream version which provides new features. If your 10.3.0 release only provides bug fixes compared to the 10.2.0 which is in Hirsute now, I can sync it, otherwise not. Please tell me what is the case. ** Changed in: qpdf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental Status in qpdf package in Ubuntu: Incomplete Bug description: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 849624] Re: No command line switch to start Thunderbird with calendar view
** Changed in: thunderbird Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/849624 Title: No command line switch to start Thunderbird with calendar view Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird 3.1.13 on Ubuntu 11.04 Trying to evoke calendar from command line: `thunderbird -calendar` or `thunderbird about:calendar` does not seem to work I think it should https://developer.mozilla.org/en/Command_Line_Options and probably this is issue on Ubunty To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/849624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 849624]
Maybe you want to provide a patch? For addressbook it registers itself here: https://searchfox.org/comm-central/rev/e80a66e5cdd9fe3915b7979cbf3d7467bcb70cfa/mailnews/addrbook/modules/components.conf#17 then handles it here: https://searchfox.org/comm-central/rev/e80a66e5cdd9fe3915b7979cbf3d7467bcb70cfa/mailnews/addrbook/modules/AddrBookManager.jsm#526-539 I don't know if calendar has a suitable module to piggyback on, or if creating a new module is better. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/849624 Title: No command line switch to start Thunderbird with calendar view Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird 3.1.13 on Ubuntu 11.04 Trying to evoke calendar from command line: `thunderbird -calendar` or `thunderbird about:calendar` does not seem to work I think it should https://developer.mozilla.org/en/Command_Line_Options and probably this is issue on Ubunty To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/849624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 109943]
For the throbber I filed bug 1695950. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 849624]
Sure, i will look into this -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/849624 Title: No command line switch to start Thunderbird with calendar view Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird 3.1.13 on Ubuntu 11.04 Trying to evoke calendar from command line: `thunderbird -calendar` or `thunderbird about:calendar` does not seem to work I think it should https://developer.mozilla.org/en/Command_Line_Options and probably this is issue on Ubunty To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/849624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 849624]
Opening thunderbird with -calendar would be very useful. Any progress on that? Something is blocking ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/849624 Title: No command line switch to start Thunderbird with calendar view Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird 3.1.13 on Ubuntu 11.04 Trying to evoke calendar from command line: `thunderbird -calendar` or `thunderbird about:calendar` does not seem to work I think it should https://developer.mozilla.org/en/Command_Line_Options and probably this is issue on Ubunty To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/849624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
This bug was fixed in the package glib2.0 - 2.67.5-2 --- glib2.0 (2.67.5-2) experimental; urgency=medium * debian/tests/control: Build-Depend on libc6-dev; the `pollable` test requires it. See [upstream MR !1977][0]. The upstream tests now rely on finding "libutil.so", which is in libc6-dev. Once that MR, or something like it, is merged, we can remove this test-dep as the runtime library will be being used. [0]: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1977 -- Iain Lane Tue, 02 Mar 2021 18:29:23 + ** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
This bug was fixed in the package glib2.0 - 2.67.5-2
---
glib2.0 (2.67.5-2) experimental; urgency=medium
* debian/tests/control: Build-Depend on libc6-dev; the `pollable` test
requires it. See [upstream MR !1977][0]. The upstream tests now rely on
finding "libutil.so", which is in libc6-dev. Once that MR, or something
like it, is merged, we can remove this test-dep as the runtime library
will be being used.
[0]: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1977
-- Iain Lane Tue, 02 Mar 2021 18:29:23 +
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include from an extern C context
Status in glib2.0 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Triaged
Status in ukui-control-center package in Ubuntu:
Triaged
Bug description:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.
The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.
[Desktop-packages] [Bug 1917949] [NEW] Networkmanager takes a long time to connect to wifi after wake from suspend
Public bug reported: Networkmanager takes 10-15 seconds to connect to wifi after wake, as opposed to the normal 3-5 seconds. This bug has already been fixed by the upstream maintainers of networkmanager- I hope to see the fix included in 21.04 before it's release. The fix can be found here nm 1.30- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/16d649ea92a1c481a59395d8672224e9e40563a3 nm 1.26 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/5454681ab76ee02cfa85d65e29005b974efb3c52 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.26.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-418-server/nvidia-utils-418-server_418.152.00-0ubuntu2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.456 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 21:33:14 2021 IpRoute: default via 192.168.254.254 dev wlp58s0 proto dhcp metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.254.0/24 dev wlp58s0 proto kernel scope link src 192.168.254.23 metric 600 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Retire 0e4604c0-8174-4f20-a2b6-94cb936ce194 wifi 1614979809 Fri 05 Mar 2021 09:30:09 PM UTC yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp58s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Retire.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp58s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Retire 0e4604c0-8174-4f20-a2b6-94cb936ce194 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp58s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1917949 Title: Networkmanager takes a long time to connect to wifi after wake from suspend Status in network-manager package in Ubuntu: New Bug description: Networkmanager takes 10-15 seconds to connect to wifi after wake, as opposed to the normal 3-5 seconds. This bug has already been fixed by the upstream maintainers of networkmanager- I hope to see the fix included in 21.04 before it's release. The fix can be found here nm 1.30- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/16d649ea92a1c481a59395d8672224e9e40563a3 nm 1.26 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/5454681ab76ee02cfa85d65e29005b974efb3c52 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.26.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-418-server/nvidia-utils-418-server_418.152.00-0ubuntu2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.456 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 21:33:14 2021 IpRoute: default via 192.168.254.254 dev wlp58s0 proto dhcp metric 600 169.254.0.0/16 dev wlp58s0
[Desktop-packages] [Bug 1917941] Re: System-config-printer keeps asking for network printer credentials
test.py: https://pastebin.com/FJTWc1uX ** Attachment added: "Short PoC of the problem" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1917941/+attachment/5473614/+files/test.py -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1917941 Title: System-config-printer keeps asking for network printer credentials Status in system-config-printer package in Ubuntu: New Bug description: Hello. I think I found a small bug in the printing process of Xubuntu 20.04.02 LTS. I have a networked laser printer (Xerox Phaser 3250) that requires username/password credentials to print. The device is present in the CUPS page (see the Printers page in http://localhost:631) and uses the IPP protocol set to "ipp://192.168.1.10:631/ipp" URI. It is also visible in the system- config-printer window (XFCE Start button => Settings => Printers) and is set as default printer. The printer username/password are different than my PC username/password. Anyway, I noticed that the OS will sometimes pester me to enter the same credentials each time I try to print something. I recall the printing authorization window does have a "Remember password" checkbox that seemingly does nothing. Now why I am mentioning that this happens only sometimes? It's because I noticed that different programs will use different authorization windows to get printer credentials. For example, Mousepad will try to get credentials by using a CUPS popup dialog (I think). LibreOffice seems to popup its own small password entry window. This bug only applies to the cases where the printing is done via system-config-printer that uses its own authorization dialog. The printing works fine after credentials are entered though. So, after a short debug session I managed to narrow down the problem to this file: /usr/share/system-config-printer/jobviewer.py. I ran the applet.py and scp-dbus-service.py with the --debug option from command line to get some extra debug messages. Printing from Mousepad did not trigger any debug messages, but it did bring up the printing authorization dialog regardless. Like I've previously stated, Mousepad seems to use a different auth dialog, and I've verified (via seahorse) that this dialog works properly because it correctly stores the credentials into the keyring, and, if the Remember password checkbox is ticked, remembers them next time I try to print something. The problem only applies to the auth dialog triggered from jobviewer.py of system-config-printer. I managed to trigger the jobviewer auth dialog by trying to print something in LibreOffice Writer and then hitting Cancel in the small window that pops up. This will then trigger the *proper* jobviewer.py auth window to show up. It also triggers upon boot when there is something queued to be printed. It can also be reliably triggered queueing a print job, killing scp-dbus-service.py and applet.py and re-running them in this order: 1) /usr/share/system-config-printer/scp-dbus-service.py --debug 2) /usr/share/system-config-printer/applet.py --debug Though this jobviewer.py auth dialog will successfully save the printer credentials to the keyring, if the checkbox is ticked (verified with Seahorse), it will fail to read them next time, assume the credentials are missing, and ask the user to enter them. The error appears to happen in jobviewer.py: Line 1056: search_obj = ItemSearch(service, attrs) This line causes the following error to appear in the terminal: GLib-GIO-CRITICAL **: 19:28:31.663: g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed The call fails to fetch any credentials and instead returns an empty result. I've written a short python script (see test.py) that reproduces the issue and triggers the same error. Related libsecret documentation: https://developer.gnome.org/libsecret/0.20/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: XFCE Date: Fri Mar 5 19:34:54 2021 InstallationDate: Installed on 2020-01-20 (409 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Phaser-3250: ipp://192.168.1.10:631/ipp Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev
[Desktop-packages] [Bug 1917941] [NEW] System-config-printer keeps asking for network printer credentials
Public bug reported: Hello. I think I found a small bug in the printing process of Xubuntu 20.04.02 LTS. I have a networked laser printer (Xerox Phaser 3250) that requires username/password credentials to print. The device is present in the CUPS page (see the Printers page in http://localhost:631) and uses the IPP protocol set to "ipp://192.168.1.10:631/ipp" URI. It is also visible in the system-config-printer window (XFCE Start button => Settings => Printers) and is set as default printer. The printer username/password are different than my PC username/password. Anyway, I noticed that the OS will sometimes pester me to enter the same credentials each time I try to print something. I recall the printing authorization window does have a "Remember password" checkbox that seemingly does nothing. Now why I am mentioning that this happens only sometimes? It's because I noticed that different programs will use different authorization windows to get printer credentials. For example, Mousepad will try to get credentials by using a CUPS popup dialog (I think). LibreOffice seems to popup its own small password entry window. This bug only applies to the cases where the printing is done via system-config-printer that uses its own authorization dialog. The printing works fine after credentials are entered though. So, after a short debug session I managed to narrow down the problem to this file: /usr/share/system-config-printer/jobviewer.py. I ran the applet.py and scp-dbus-service.py with the --debug option from command line to get some extra debug messages. Printing from Mousepad did not trigger any debug messages, but it did bring up the printing authorization dialog regardless. Like I've previously stated, Mousepad seems to use a different auth dialog, and I've verified (via seahorse) that this dialog works properly because it correctly stores the credentials into the keyring, and, if the Remember password checkbox is ticked, remembers them next time I try to print something. The problem only applies to the auth dialog triggered from jobviewer.py of system- config-printer. I managed to trigger the jobviewer auth dialog by trying to print something in LibreOffice Writer and then hitting Cancel in the small window that pops up. This will then trigger the *proper* jobviewer.py auth window to show up. It also triggers upon boot when there is something queued to be printed. It can also be reliably triggered queueing a print job, killing scp-dbus-service.py and applet.py and re-running them in this order: 1) /usr/share/system-config-printer/scp-dbus-service.py --debug 2) /usr/share/system-config-printer/applet.py --debug Though this jobviewer.py auth dialog will successfully save the printer credentials to the keyring, if the checkbox is ticked (verified with Seahorse), it will fail to read them next time, assume the credentials are missing, and ask the user to enter them. The error appears to happen in jobviewer.py: Line 1056: search_obj = ItemSearch(service, attrs) This line causes the following error to appear in the terminal: GLib-GIO-CRITICAL **: 19:28:31.663: g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed The call fails to fetch any credentials and instead returns an empty result. I've written a short python script (see test.py) that reproduces the issue and triggers the same error. Related libsecret documentation: https://developer.gnome.org/libsecret/0.20/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: XFCE Date: Fri Mar 5 19:34:54 2021 InstallationDate: Installed on 2020-01-20 (409 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Phaser-3250: ipp://192.168.1.10:631/ipp Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 4: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Acer Predator PH317-52 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Phaser.ppd', '/etc/cups/ppd/Phaser-3250.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Phaser.ppd: Permission denied grep: /etc/cups/ppd/Phaser-3250.ppd: Permission denied
[Desktop-packages] [Bug 1917939] [NEW] windows maximise underneath dock
Public bug reported: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re-maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages 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/1917939 Title: windows maximise underneath dock Status in gnome-shell package in Ubuntu: New Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220550] Re: gnome-keyring resets password
Also, this appears to be a duplicate of this bug:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1086385
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1220550
Title:
gnome-keyring resets password
Status in gnome-keyring package in Ubuntu:
Confirmed
Status in seahorse package in Ubuntu:
New
Bug description:
Good day :)
I have Ubuntu installed on an encrypted LVM partition, with user auto-login
and an empty gnome-keyring password (I believe that an empty gnome-keyring
password on an encrypted LVM is safe... is it? :). Every 5th or 6th boot (I
don't know exact number) the gnome-keyring dialog pops out and asks me for a
password. It no longer accepts empty password. I tried to set the password to
some non-empty string ("a" or something like that), it again worked for several
boots, then again started to ask for the password. I have to enter the user's
password for the dialog to disappear. So it seems to me that something is
(randomly?) resetting the gnome-keyring password to match the login password.
Thanks and have a nice day!
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-keyring 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Wed Sep 4 09:02:11 2013
InstallationDate: Installed on 2013-08-03 (31 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release i386
(20130423.1)
MarkForUpload: True
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1220550/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220550] Re: gnome-keyring resets password
This appears to be an upstream bug (a very old one). Reported on
Seahorse Gitlab here:
https://gitlab.gnome.org/GNOME/seahorse/-/issues/320
** Bug watch added: gitlab.gnome.org/GNOME/seahorse/-/issues #320
https://gitlab.gnome.org/GNOME/seahorse/-/issues/320
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1220550
Title:
gnome-keyring resets password
Status in gnome-keyring package in Ubuntu:
Confirmed
Status in seahorse package in Ubuntu:
New
Bug description:
Good day :)
I have Ubuntu installed on an encrypted LVM partition, with user auto-login
and an empty gnome-keyring password (I believe that an empty gnome-keyring
password on an encrypted LVM is safe... is it? :). Every 5th or 6th boot (I
don't know exact number) the gnome-keyring dialog pops out and asks me for a
password. It no longer accepts empty password. I tried to set the password to
some non-empty string ("a" or something like that), it again worked for several
boots, then again started to ask for the password. I have to enter the user's
password for the dialog to disappear. So it seems to me that something is
(randomly?) resetting the gnome-keyring password to match the login password.
Thanks and have a nice day!
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-keyring 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Wed Sep 4 09:02:11 2013
InstallationDate: Installed on 2013-08-03 (31 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release i386
(20130423.1)
MarkForUpload: True
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1220550/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus issues in 3.38.3-3ubuntu1
Ok sorry... It's Xorg, but... Can you reproduce this under Wayland too? -- 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/1917926 Title: Window focus issues in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus issues in 3.38.3-3ubuntu1
Is this using X11 or Wayland? -- 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/1917926 Title: Window focus issues in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086385] Re: seahorse occasionally undoes password change
Reported to Seahorse Gitlab here: https://gitlab.gnome.org/GNOME/seahorse/-/issues/320 ** Bug watch added: gitlab.gnome.org/GNOME/seahorse/-/issues #320 https://gitlab.gnome.org/GNOME/seahorse/-/issues/320 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1086385 Title: seahorse occasionally undoes password change Status in seahorse package in Ubuntu: Confirmed Bug description: I first had the problem of being unable to change keyring password (3.6.0), which was resolved later (3.6.2) but after I've changed the default password (same as user login password) to (insecure) blank password, seahorse allows this for some time and later it decides to override it with the default password again. I manually upgraded to 3.6.3 and this helped a bit, meaning this bug appearing less frequently. But it's still there. I use Ubuntu 12.10 64-bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1086385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I have the same issue with the headphone's microphone. My Bose 700 connects and has sound output for A2DP, but terrible audio quality (HSP/HFP) when switching on headphone's microphone. Laptop: Acer Predator G9 591 2016 OS: Ubuntu 20.04.01 LTS Kernel: 5.4.0-66-generic Headset: Bose 700 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus issues in 3.38.3-3ubuntu1
Foundations had two people reproduce this :) ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- 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/1917926 Title: Window focus issues in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] [NEW] Window focus issues in 3.38.3-3ubuntu1
Public bug reported: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 ** Affects: mutter (Ubuntu) Importance: Critical Status: Triaged ** Tags: rls-hh-incoming -- 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/1917926 Title: Window focus issues in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus issues in 3.38.3-3ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1917926 Title: Window focus issues in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917926] Re: Window focus issues in 3.38.3-3ubuntu1
** Tags added: rls-hh-incoming ** Changed in: mutter (Ubuntu) Importance: Undecided => Critical -- 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/1917926 Title: Window focus issues in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086385] Re: seahorse occasionally undoes password change
I have this exact problem on Ubuntu 20.04.1 in x86_64. Seven years later... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1086385 Title: seahorse occasionally undoes password change Status in seahorse package in Ubuntu: Confirmed Bug description: I first had the problem of being unable to change keyring password (3.6.0), which was resolved later (3.6.2) but after I've changed the default password (same as user login password) to (insecure) blank password, seahorse allows this for some time and later it decides to override it with the default password again. I manually upgraded to 3.6.3 and this helped a bit, meaning this bug appearing less frequently. But it's still there. I use Ubuntu 12.10 64-bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1086385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086385] Re: seahorse occasionally undoes password change
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1086385 Title: seahorse occasionally undoes password change Status in seahorse package in Ubuntu: Confirmed Bug description: I first had the problem of being unable to change keyring password (3.6.0), which was resolved later (3.6.2) but after I've changed the default password (same as user login password) to (insecure) blank password, seahorse allows this for some time and later it decides to override it with the default password again. I manually upgraded to 3.6.3 and this helped a bit, meaning this bug appearing less frequently. But it's still there. I use Ubuntu 12.10 64-bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1086385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220550] Re: gnome-keyring resets password
I have this exact problem in Ubuntu 20.04.1 on x86_64. Nothing to add to
the description above. This captures it perfectly.
** Also affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1220550
Title:
gnome-keyring resets password
Status in gnome-keyring package in Ubuntu:
Confirmed
Status in seahorse package in Ubuntu:
New
Bug description:
Good day :)
I have Ubuntu installed on an encrypted LVM partition, with user auto-login
and an empty gnome-keyring password (I believe that an empty gnome-keyring
password on an encrypted LVM is safe... is it? :). Every 5th or 6th boot (I
don't know exact number) the gnome-keyring dialog pops out and asks me for a
password. It no longer accepts empty password. I tried to set the password to
some non-empty string ("a" or something like that), it again worked for several
boots, then again started to ask for the password. I have to enter the user's
password for the dialog to disappear. So it seems to me that something is
(randomly?) resetting the gnome-keyring password to match the login password.
Thanks and have a nice day!
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-keyring 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Wed Sep 4 09:02:11 2013
InstallationDate: Installed on 2013-08-03 (31 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release i386
(20130423.1)
MarkForUpload: True
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1220550/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220550] Re: gnome-keyring resets password
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1220550
Title:
gnome-keyring resets password
Status in gnome-keyring package in Ubuntu:
Confirmed
Status in seahorse package in Ubuntu:
New
Bug description:
Good day :)
I have Ubuntu installed on an encrypted LVM partition, with user auto-login
and an empty gnome-keyring password (I believe that an empty gnome-keyring
password on an encrypted LVM is safe... is it? :). Every 5th or 6th boot (I
don't know exact number) the gnome-keyring dialog pops out and asks me for a
password. It no longer accepts empty password. I tried to set the password to
some non-empty string ("a" or something like that), it again worked for several
boots, then again started to ask for the password. I have to enter the user's
password for the dialog to disappear. So it seems to me that something is
(randomly?) resetting the gnome-keyring password to match the login password.
Thanks and have a nice day!
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-keyring 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Wed Sep 4 09:02:11 2013
InstallationDate: Installed on 2013-08-03 (31 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release i386
(20130423.1)
MarkForUpload: True
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1220550/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915003] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-settings into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- settings/460.39-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917816] Re: Firefox not loading gifv, gifs
Downloaded the ubuntu-20.04.2.0-desktop-amd64.iso image and installed a virtual machine, updated it with apt update && apt dist-upgrade. Rebooted, tried firefox again and saw the same problem. Disabled most of the security and privacy restrictions in the firefox settings, same problem. # apt info firefox ... Version: 86.0+build3-0ubuntu0.20.04.1 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917816 Title: Firefox not loading gifv, gifs Status in firefox package in Ubuntu: New Bug description: Firefox 86.0-3, fresh installation of Ubuntu 20.04 with no additional repositories added other than for Google Chrome, no third-party drivers, etc. Full dist-upgrade run, rebooted and otherwise working fine. A version of firefox was pulled down using 'snap install firefox' and it did not have the same issues. Some gifs work, but no gifv so far. Not sure of the pattern. Example gifv from imgur.com: https://i.imgur.com/xFVwISe.gifv I've disabled all restrictions in the privacy and security settings. I've also started in safe-mode so no extensions. No reports of this issue on other operating systems or on https://bugzilla.mozilla.org No huge impact to me personally, but maybe something to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 86.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:40:12 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-03-03 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=86.0/20210222142601 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502LW.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502LW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502LW.309:bd09/01/2020:br5.17:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM15GU502LW_GU502LW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502LW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus M15 dmi.product.name: ROG Zephyrus M15 GU502LW_GU502LW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917840] Re: Please sync pipewire >= 0.3.22-2 from Debian
This bug was fixed in the package pipewire - 0.3.22-2 Sponsored for Daniel van Vugt (vanvugt) --- pipewire (0.3.22-2) experimental; urgency=medium [ Daniel van Vugt ] * Fix "the metadata crash" (LP: #1916716). Using upstream commit 3673265ae20d7b59e89cad6c5238c232796731b2 which is scheduled for inclusion in release 0.3.23. -- Iain Lane Thu, 04 Mar 2021 11:09:52 + ** Changed in: pipewire (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1917840 Title: Please sync pipewire >= 0.3.22-2 from Debian Status in pipewire package in Ubuntu: Fix Released Bug description: Please sync pipewire >= 0.3.22-2 from Debian to hirsute. It's a bugfix-only release required to fix bug 1916716: pipewire (0.3.22-2) experimental; urgency=medium [ Daniel van Vugt ] * Fix "the metadata crash" (LP: #1916716). Using upstream commit 3673265ae20d7b59e89cad6c5238c232796731b2 which is scheduled for inclusion in release 0.3.23. -- Iain Lane Thu, 04 Mar 2021 11:09:52 + https://salsa.debian.org/utopia-team/pipewire/-/tags/debian%2F0.3.22-2 https://salsa.debian.org/utopia-team/pipewire/-/commits/debian/experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1917840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914844] Re: Sync xserver-xorg-video-ati 1:19.1.0-2 (main) from Debian unstable (main)
This bug was fixed in the package xserver-xorg-video-ati - 1:19.1.0-2 Sponsored for Logan Rosen (logan) --- xserver-xorg-video-ati (1:19.1.0-2) unstable; urgency=medium * Team upload [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Repository, Repository-Browse. * Update standards version to 4.2.1, no changes needed. [ Julien Cristau ] * Pull fixes from upstream master including a GCC 10 build fix (closes: #957998). -- Julien Cristau Fri, 18 Sep 2020 14:58:08 +0200 ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1914844 Title: Sync xserver-xorg-video-ati 1:19.1.0-2 (main) from Debian unstable (main) Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: Please sync xserver-xorg-video-ati 1:19.1.0-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/patches/git_gcc10_build.patch: - backport an upstream commit to fix the build with gcc10 This was fixed in Debian. Changelog entries since current hirsute version 1:19.1.0-1ubuntu1: xserver-xorg-video-ati (1:19.1.0-2) unstable; urgency=medium * Team upload [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Repository, Repository-Browse. * Update standards version to 4.2.1, no changes needed. [ Julien Cristau ] * Pull fixes from upstream master including a GCC 10 build fix (closes: #957998). -- Julien Cristau Fri, 18 Sep 2020 14:58:08 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1914844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917909] [NEW] opencc 1.1.1+git20200624+ds2-6ubuntu1 breaks Rime simplification
Public bug reported: After upgrading libopencc-data and libopencc1.1 to 1.1.1+git20200624+ds2-6ubuntu1, I'm unable to type Simplified Chinese with Rime. It works fine if I downgrade opencc to 1.1.1+git20200624+ds2-5ubuntu1. The schema I use is luna pinyin. ** Affects: opencc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu. https://bugs.launchpad.net/bugs/1917909 Title: opencc 1.1.1+git20200624+ds2-6ubuntu1 breaks Rime simplification Status in opencc package in Ubuntu: New Bug description: After upgrading libopencc-data and libopencc1.1 to 1.1.1+git20200624+ds2-6ubuntu1, I'm unable to type Simplified Chinese with Rime. It works fine if I downgrade opencc to 1.1.1+git20200624+ds2-5ubuntu1. The schema I use is luna pinyin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencc/+bug/1917909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917906] [NEW] please sync qpdf 10.3.0-1 from debian experimental
Public bug reported: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1917906 Title: please sync qpdf 10.3.0-1 from debian experimental Status in qpdf package in Ubuntu: New Bug description: Sorry to do this again so soon, but I released qpdf 10.3.0 and uploaded to debian experimental. I have gotten the email from debian indicating that the package has been accepted, and it is visible on qa.debian.org, so hopefully it's "there" for purposes of doing the sync. If not, give it a few hours. :-) Thanks for helping to keep qpdf updated in Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1917906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Sorry to use this bug report as a forum but IMO it is useless to spend more time on chromium. Ubuntu & users should define a Blink-based open source browser like Brave that could be supported nicely upstream unlike whats google is doing by removing sync API access with google services -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915910] Re: evince does not print
The bug appeared again! The posting before shows the apparmor log file entry -- 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/1915910 Title: evince does not print Status in evince package in Ubuntu: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64 -linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915910] Re: evince does not print
AVC apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=16617 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 -- 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/1915910 Title: evince does not print Status in evince package in Ubuntu: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64 -linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853007]
As an addenda (and because the current downloadable version is still 78.*) I have to mention THE real problem with this bug. If Thunderbird is used long enough to accumulate 1 temporary files in the TEMP directory, so it has all the files from nsemail.eml to nsemail-.eml, Thunderbird will suddenly stop sending e-mails with an error. It can be solved by simply deleting the files. The system was a Windows 7 SP1 64bit with now latest TB 78.8.0. But we met this problem earlier on a few machines (Win 7 and 10 mixed) with older and latest TB versions, where unknowing the real cause we solved the problem by removing TB, cleaning every corner of the system and meanwhile cleaning the temp folders as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago)
[Desktop-packages] [Bug 1917301] Re: New poppler transition is ongoing
** Changed in: poppler (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1917301 Title: New poppler transition is ongoing Status in poppler package in Ubuntu: Fix Released Bug description: The bug is there to summarize the status of that transition for the proposed migration report Rebuilds are done but - libreoffice needs to migrate and it's autopkgtest are failing, that's fixed in the packaging Vcs and an upload is planned in the next day once 7.1.1 is out - gdal needs to migrate which is blocked on r-cran-sf/s390x failing tests, that has been reported to Debian now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961211 and a fix has been uploaded which is going to be synced next - if the fix works r-cran-stars needs a similar change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1917301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853007] Re: nsemail and nscopy files left in /tmp
As an addenda (and because the current version is still 78.*) I have to mention the real problem with this bug. If Thunderbird is used long enough to accumulate 1 temporary files in the TEMP directory, so it has all the files from nsemail.eml to nsemail-.eml, Thunderbird will suddenly stop sending e-mails with an error. It can be solved by simply deleting the files. My system was a Windows 7 SP1 64bit with now latest TB 78.8.0. But we met this problem on a few machines (Win 7 and 10 mixed) with older and latest TB versions, where unknowing the real cause we solved the problem by removing TB, cleaning every corner of the system and meanwhile cleaning the temp folders as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago) InstallationMedia:
[Desktop-packages] [Bug 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions
This bug was fixed in the package mutter - 3.38.3-3ubuntu1 --- mutter (3.38.3-3ubuntu1) hirsute; urgency=medium * debian/patches: Backport wayland input thread support (LP: #1690719) * debian/libmutter-7-0.symbols: Sync as per private symbols changes * debian/control: Set breaks on previous gnome-shell versions mutter (3.38.3-3) unstable; urgency=medium * Team upload * d/patches: Update to commit 3.38.3-20-g2818cfda8 from gnome-3-38 branch - Wayland geometry scale fixes - Fix a crash that can occur on resume from suspend - Fix drag-and-drop from X11 source to Wayland destination -- Marco Trevisan (Treviño) Thu, 25 Feb 2021 23:17:10 +0100 -- 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/1690719 Title: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions Status in GNOME Shell: Unknown Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland). It's not reliably smooth like you would see in Xorg or Mir demo servers. Feels like there is a blocking call being made in a GUI thread that shouldn't have any blocking calls. Although it's not clear if this is just a problem with pointer input or the shell compositing in general. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 Date: Mon May 15 13:23:22 2017 DisplayManager: lightdm GsettingsChanges: 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 2017-05-03 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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/1690719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions
This bug was fixed in the package gnome-shell - 3.38.3-3ubuntu1 --- gnome-shell (3.38.3-3ubuntu1) hirsute; urgency=medium * debian/patches: Switch to the new API to get actor from inputdevice (LP: #1690719) * debian/control: Bump dependency on mutter with input thread support * debian/patches: Update to MetaCursorTracker API change * debian/patches: Do not forward device IDs * debian/ubuntu-session-mods/ubuntu.json: Use desktop-icons-ng extension by default (LP: #1916511) gnome-shell (3.38.3-3) unstable; urgency=medium * Team upload * d/patches: Update to 3.38.3-9-gbdf31febe from gnome-3-38 branch - Use image-data in preference to app icon for notifications - Don't let fullscreen apps block the workspace-changing animation - Don't leave a non-interactable polkit prompt if authentication succeeds without requiring user interaction (LP: #1824874) - Fix a crash in the blur effect when taking a screenshot or screencast - Fix a crash involving apps' fallback icons -- Marco Trevisan (Treviño) Fri, 26 Feb 2021 00:51:19 +0100 ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Fix Released ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1690719 Title: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions Status in GNOME Shell: Unknown Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland). It's not reliably smooth like you would see in Xorg or Mir demo servers. Feels like there is a blocking call being made in a GUI thread that shouldn't have any blocking calls. Although it's not clear if this is just a problem with pointer input or the shell compositing in general. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 Date: Mon May 15 13:23:22 2017 DisplayManager: lightdm GsettingsChanges: 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 2017-05-03 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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/1690719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
This bug was fixed in the package gnome-shell - 3.38.3-3ubuntu1 --- gnome-shell (3.38.3-3ubuntu1) hirsute; urgency=medium * debian/patches: Switch to the new API to get actor from inputdevice (LP: #1690719) * debian/control: Bump dependency on mutter with input thread support * debian/patches: Update to MetaCursorTracker API change * debian/patches: Do not forward device IDs * debian/ubuntu-session-mods/ubuntu.json: Use desktop-icons-ng extension by default (LP: #1916511) gnome-shell (3.38.3-3) unstable; urgency=medium * Team upload * d/patches: Update to 3.38.3-9-gbdf31febe from gnome-3-38 branch - Use image-data in preference to app icon for notifications - Don't let fullscreen apps block the workspace-changing animation - Don't leave a non-interactable polkit prompt if authentication succeeds without requiring user interaction (LP: #1824874) - Fix a crash in the blur effect when taking a screenshot or screencast - Fix a crash involving apps' fallback icons -- Marco Trevisan (Treviño) Fri, 26 Feb 2021 00:51:19 +0100 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hi Olivier. Sorry to insist, but it's been now 4 months since the last news on this and I think people would like to know if this is still on the roadmap, or if those who want video decoding acceleration should move to Chrome or PPAs. Thanks again! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897454] Re: [snap] Chromium dev cuts off Wayland display
Even in Chrome where Wayland does seem to work (manually), it warns that gnome-shell/mutter is missing zwp_linux_explicit_synchronization_v1. I wonder if that explains the laggy feeling? -- 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/1897454 Title: [snap] Chromium dev cuts off Wayland display Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since v87 Chromium ships with support for Ozone/Wayland: https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again. This build flag is not disabled in dev (edge) channel build, so it should be possible to run Chromium with flags --enable-features=UseOzonePlatform --ozone-platform=wayland. This does not work due to environment variable DISABLE_WAYLAND set to 1 here: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Can you please provide the output of: $ sudo ubuntu-drivers list In the live session? There are two ways to get the nvidia kernel driver. One option is to compile it from scratch on the users machine with dkms. THe other option is to install a metapackage linux-modules-nvidia for the appropriate kernel flavour and the appropriate nvidia revsision which provides a prebuild, not linked, and secureboot signed nvidia module. So as to why the dkms one will not work or load on secureboot machines, unless one goes through cryptic MOK key enrollment procedure during boot. The secureboot signed nvidia module works on secureboot machines without any additional steps by the user. But the caveat is that the secureboot signed ones must be kept in correct tandem with the kernel flavour & nvidia revisions. Anything you install from the PPA will not be secureboot signed, and thus need MOK signing. ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: SYSTEM: Laptop: ASUS ROG GL552VW OS: Ubuntu 20.04.2 LTS GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic SUMMARY: From a fresh working install of Ubuntu 20.04, I downgraded from nvidia-driver-460 by installing nvidia-driver-440 (which actually is a transitional package to nvidia-driver-450 but I didn't know this). After reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. This was solved by uninstalling linux-modules-nvidia-460 packages and instead installing linux-modules-nvidia-450 packages (see WORKAROUND below for instructions). STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. WORKAROUND: WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to see what linux kenrel versions you have installed. Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did as follows from recovery mode with network (instead of entering recovery mode, you should be able to press CTRL+ALT+F1 from the blank screen after bootup, login with username and password and then running these commands): sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux- modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux- modules-nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-uvm.ko: Running
[Desktop-packages] [Bug 1917191]
(In reply to Gabriele Svelto [:gsvelto] from comment #13) > Ugh, this bug is affecting Linux users real badly on 86. Do we have a way to > reach out to distro maintainers to try and help them roll out a local fix for > their 86 builds? adding a few of them here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917191]
Jan, this might be important for you as well (archlinux). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917191]
This was also reported in Ubuntu (https://launchpad.net/bugs/1917191), by only 2 different users so far since the update to 86.0 was pushed to all supported Ubuntu releases. According to comment 7, this affects only users with an invalid color profile on Linux, which presumably/hopefully isn't such a large number of users. I'm okay with distro-patching (the patch is trivial enough), but then why isn't the change being uplifted to the 86 branch? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917191]
I've already backported this fix; thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917191]
I shipped Fedora Firefox updates yesterday, Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917191]
Ugh, this bug is affecting Linux users real badly on 86. Do we have a way to reach out to distro maintainers to try and help them roll out a local fix for their 86 builds? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update
If the profile is managed, it seems that local data is deleted - at least it becomes unusable, so it might as well be deleted. If that is avoidable, it would be good to do so. I can understand why you would want to delete the local data associated with a managed profile in some circumstances, but "Google deprecated an API" doesn't seem like one of them. Another mitigation would be to provide a message that makes it clearer that the problem is with Chromium and not with the managed account. That would save a lot of wasted time between employees and their company tech support. (Though maybe it's too late for this to be useful - perhaps everyone who is going to hit this bug has done so already.) -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 188342] Re: keymap fr/oss: numpad '.' mapped to period instead of KP_Decimal
Still affected by this with Ubuntu 20.04. In Ubuntu Budgie, there's no obvious parameter to solve this. The modification of .Xmodmap did not work for me. I added the following line in .bashrc (did not work in .profile): xmodmap -e 'keycode 91 = KP_Delete KP_Decimal' And now, problem solved ! ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/188342 Title: keymap fr/oss: numpad '.' mapped to period instead of KP_Decimal Status in xkeyboard-config: Fix Released Status in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Binary package hint: xserver-xorg-input-kbd In Ubuntu 7.10, xserver-xorg-input-kbd_1.2.0-1+1.2.1ubuntu1 with the following Xorg.conf settings: Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "fr" Option "XkbVariant""oss" EndSection Got: $ xmodmap -pke | grep 'keycode *91' keycode 91 = KP_Delete period comma U202F comma U202F Expected: $ xmodmap -pke | grep 'keycode *91' keycode 91 = KP_Delete KP_Decimal comma U202F comma U202F This issue is a MAJOR usability issue in OpenOffice.org Calc, as in the current state Calc is unusable to enter decimal numbers quickly. This is a major blocker for migration of Windows/Excel users to Ubuntu/OpenOffice.org. See bug #188331. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/188342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
