[Desktop-packages] [Bug 1995550] [NEW] gnome-terminal doesn't restore to original size after being maximized
Public bug reported: Steps: 1. Open gnome-terminal, it will has size 80x24. 2. Maximize the window. 3. Restore (un-maximize). Expected: the size should be 80x24. Actual: the size is smaller (74x21). Repeat the steps, and it will be more smaller and more more smaller. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 3 09:41:05 2022 InstallationDate: Installed on 2021-06-05 (515 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-28 (66 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1995550 Title: gnome-terminal doesn't restore to original size after being maximized Status in gnome-terminal package in Ubuntu: New Bug description: Steps: 1. Open gnome-terminal, it will has size 80x24. 2. Maximize the window. 3. Restore (un-maximize). Expected: the size should be 80x24. Actual: the size is smaller (74x21). Repeat the steps, and it will be more smaller and more more smaller. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 3 09:41:05 2022 InstallationDate: Installed on 2021-06-05 (515 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-28 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1995550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Same behavior with an Entroware laptop on 5.15.0-52-generic (both touchpad and internal keyboard, function keys work) Hard to tell who's the culprit among the kernel, libusb, udev and gdm One weird thing in the context of resuming : The Xorg.log generated by gdm shows: (II) UnloadModule: "libinput" message [...] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6) [...] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7) [...] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8) (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9) (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10) Typically: [79.317] (II) config/udev: Adding input device Chicony USB2.0 Camera: Chicony (/dev/input/event9) [79.317] (**) Chicony USB2.0 Camera: Chicony : Applying InputClass "libinput keyboard catchall" [79.317] (II) Using input driver 'libinput' for 'Chicony USB2.0 Camera: Chicony ' [79.317] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 43 paused 0 [79.317] (**) Chicony USB2.0 Camera: Chicony : always reports core events [79.317] (**) Option "Device" "/dev/input/event9" [79.319] (II) event9 - Chicony USB2.0 Camera: Chicony : is tagged by udev as: Keyboard [79.319] (II) event9 - Chicony USB2.0 Camera: Chicony : device is a keyboard [79.319] (II) event9 - Chicony USB2.0 Camera: Chicony : device removed [79.319] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input17/event9" [79.319] (II) XINPUT: Adding extended input device "Chicony USB2.0 Camera: Chicony " (type: KEYBOARD, id 12) [79.319] (**) Option "xkb_model" "pc105" [79.319] (**) Option "xkb_layout" "fr" [79.319] (**) Option "xkb_variant" "azerty" [79.320] (II) event9 - Chicony USB2.0 Camera: Chicony : is tagged by udev as: Keyboard [79.320] (II) event9 - Chicony USB2.0 Camera: Chicony : device is a keyboard (a webcam tagged keyboard?) I don't know if it's related, but if it is it could be a problem with udev rules during resume? -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA
[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap
Please give deb-package back. Let people at lease a choice! Snap is a Bug not deb. -- 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/1962021 Title: Make the deb package install the firefox snap Status in firefox package in Ubuntu: Fix Released Bug description: Canonical and Mozilla are working together to make the firefox snap the only supported package in Ubuntu, thus deprecating the deb package in the archive. This bug tracks the transformation of the firefox package in the archive into a transitional package that installs the snap, much like was done for chromium-browser in Ubuntu 19.10. There are a number of known problems and regressions with the snap compared to the deb (see https://bugzilla.mozilla.org/show_bug.cgi?id=snap and https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap), those are actively being worked on and will be addressed in due time, please refrain from using this bug to point them out. Instead, file separate bugs in the upstream bug tracker (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify this is about the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978295] [xdg-desktop-portal/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: Fix Committed Bug description: [Impact] * The OpenDirectory method of the OpenURI portal opens a file manager window showing the requested directory, but it doesn't select the passed file in that directory. This affects all users of this API, particularly the chromium and firefox snaps. * This is an upstream bug that was fixed in later versions of xdg- desktop-portal, this SRU backports the fix to the 1.6 series that's in focal. [Test Plan] * On a focal machine, install the chromium snap, launch it and download any file from a web page (from e.g. https://kernel.org/) * Once the download is complete, browse to chrome://downloads * Click the "Show in folder" link for the downloaded file, this opens a Nautilus window showing the contents of the default downloads directory (e.g. $HOME/Downloads) * Expected result: the downloaded file is selected in the Nautilus window * Actual result without the patch: no file is selected * Similarly for the firefox snap, downloading a file and clicking the "Show in Folder" button in the downloads panel should select the downloaded file * General functionality of all other portals (including the wallpaper portal) should be thoroughly tested to look out for regressions [Where problems could occur] * The backported patches potentially affect other portals (not just OpenURI), including the Wallpaper portal. * Therefore the functionality of all other portals should be thoroughly tested to ensure there are no functional regressions. [Other Info] * The firefox snap wasn't using this API before version 103.0, which at the time of writing this hasn't officially been released yet (it is due for release tomorrow, 2022-07-26). In the meantime it can be installed from the candidate channel. [Original Description] This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
When I use a browser on: "https://calendar.google.com/;, the calendar events are not repeated. They only appear once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
Upon returning from an appointment the flickering has returned. The fractional scaling setting must have been a coincidence. -- 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/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995364] Re: Pointer moves to bottom right of screen automatically
Not sure if issue lies with libinput, just a guess ** Package changed: ubuntu => libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1995364 Title: Pointer moves to bottom right of screen automatically Status in libinput package in Ubuntu: New Bug description: On my laptop I have an USB-C hub connected via thunderbolt with 2 external displays attached to it. When I close the laptop lid the pointer moves to the bottom right in steps of about half a second each. I am able to move the mouse, but the automatic moving happens also when I'm moving the mouse around. If i move the pointer to the top left of the screen it takes about 4 seconds for the pointer to reach the bottom right in 10 evenly spaced steps. The touchpad of the laptop is disabled. It also happens when the mouse is disconnected. I'm running Ubuntu 22.04 on a fresh install with Nvidia also installed. The issue also happens when using the integrated intel graphics. System inf $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ inxi -Fxxz System: Kernel: 5.15.0-52-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 42.4 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish) Machine: Type: Laptop System: Notebook product: PD5x_7xPNP1_PNR1_PNN1_PNT1 v: N/A serial: Chassis: No Enclosure type: 10 serial: Mobo: Notebook model: PD5x_7xPNP1_PNR1_PNN1_PNT1 serial: UEFI: INSYDE v: 1.07.02 date: 07/14/2022 Battery: ID-1: BAT0 charge: 79.7 Wh (100.0%) condition: 79.7/77.3 Wh (103.1%) volts: 13.0 min: 11.4 model: Notebook BAT serial: status: Full CPU: Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB L3: 24 MiB Speed (MHz): avg: 540 high: 871 min/max: 400/4679:4700:3500 cores: 1: 465 2: 438 3: 502 4: 400 5: 400 6: 625 7: 425 8: 437 9: 405 10: 738 11: 472 12: 854 13: 447 14: 871 15: 614 16: 439 17: 731 18: 499 19: 517 20: 536 bogomips: 107520 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Alder Lake-P Integrated Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel ports: active: DP-5,DP-6 off: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-7 bus-ID: 00:02.0 chip-ID: 8086:46a6 Device-2: NVIDIA GA104 [Geforce RTX 3070 Ti Laptop GPU] vendor: CLEVO/KAPOK driver: N/A pcie: speed: Unknown lanes: 63 bus-ID: 01:00.0 chip-ID: 10de:24a0 Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 3-8:3 chip-ID: 5986:214c Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1 compositor: gnome-shell driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: 0 Monitor-1: DP-5 model: HP E24 G4 res: 1920x1080 dpi: 93 diag: 604mm (23.8") Monitor-2: DP-6 model: HP E24 G4 res: 1920x1080 dpi: 93 diag: 604mm (23.8") OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes Audio: Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:51c8 Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: Unknown lanes: 63 bus-ID: 01:00.1 chip-ID: 10de:228b Sound Server-1: ALSA v: k5.15.0-52-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 2d:00.0 chip-ID: 8086:2723 IF: wlp45s0 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 2f:00.0 chip-ID: 10ec:8168 IF: enp47s0 state: down mac: Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-1.3:3 chip-ID: 0bda:8153 IF: enx34298f74affb state: down mac: Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-10:5 chip-ID: 8087:0029 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 3.0 lmp-v: 5.2 sub-v: 237e Drives: Local Storage: total: 931.51 GiB used: 20 GiB (2.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 31.9 C Partition: ID-1: / size: 915.32 GiB used: 20 GiB (2.2%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
I use google calendar. The updated packages are given below: 2022-11-02 07:54:57 startup archives unpack 2022-11-02 07:54:58 upgrade libssl-dev:amd64 3.0.5-2ubuntu1 3.0.5-2ubuntu2 2022-11-02 07:54:58 status half-configured libssl-dev:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:58 status unpacked libssl-dev:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:58 status half-installed libssl-dev:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:58 status unpacked libssl-dev:amd64 3.0.5-2ubuntu2 2022-11-02 07:54:58 upgrade libssl3:i386 3.0.5-2ubuntu1 3.0.5-2ubuntu2 2022-11-02 07:54:58 status triggers-pending libc-bin:amd64 2.36-0ubuntu4 2022-11-02 07:54:58 status half-configured libssl3:i386 3.0.5-2ubuntu1 2022-11-02 07:54:58 status unpacked libssl3:i386 3.0.5-2ubuntu1 2022-11-02 07:54:58 status half-configured libssl3:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:58 status half-installed libssl3:i386 3.0.5-2ubuntu1 2022-11-02 07:54:58 status unpacked libssl3:i386 3.0.5-2ubuntu2 2022-11-02 07:54:58 upgrade libssl3:amd64 3.0.5-2ubuntu1 3.0.5-2ubuntu2 2022-11-02 07:54:58 status unpacked libssl3:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:58 status half-installed libssl3:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:58 status unpacked libssl3:amd64 3.0.5-2ubuntu2 2022-11-02 07:54:59 upgrade openssl:amd64 3.0.5-2ubuntu1 3.0.5-2ubuntu2 2022-11-02 07:54:59 status half-configured openssl:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:59 status unpacked openssl:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:59 status half-installed openssl:amd64 3.0.5-2ubuntu1 2022-11-02 07:54:59 status triggers-pending man-db:amd64 2.10.2-2 2022-11-02 07:54:59 status unpacked openssl:amd64 3.0.5-2ubuntu2 2022-11-02 07:54:59 upgrade kicad-footprints:all 6.0.7-0-202207270739+26e8be980~11~ubuntu22.10.1 6.0.9-0-202210312007+6705da57c~11~ubuntu22.10.1 2022-11-02 07:54:59 status half-configured kicad-footprints:all 6.0.7-0-202207270739+26e8be980~11~ubuntu22.10.1 2022-11-02 07:54:59 status unpacked kicad-footprints:all 6.0.7-0-202207270739+26e8be980~11~ubuntu22.10.1 2022-11-02 07:54:59 status half-installed kicad-footprints:all 6.0.7-0-202207270739+26e8be980~11~ubuntu22.10.1 2022-11-02 07:55:02 status unpacked kicad-footprints:all 6.0.9-0-202210312007+6705da57c~11~ubuntu22.10.1 2022-11-02 07:55:02 upgrade kicad-packages3d:all 6.0.7-0-202207270742+cd9551df~9~ubuntu22.10.1 6.0.9-0-202210312027+45df600c~9~ubuntu22.10.1 2022-11-02 07:55:02 status half-configured kicad-packages3d:all 6.0.7-0-202207270742+cd9551df~9~ubuntu22.10.1 2022-11-02 07:55:02 status unpacked kicad-packages3d:all 6.0.7-0-202207270742+cd9551df~9~ubuntu22.10.1 2022-11-02 07:55:02 status half-installed kicad-packages3d:all 6.0.7-0-202207270742+cd9551df~9~ubuntu22.10.1 2022-11-02 07:55:31 status unpacked kicad-packages3d:all 6.0.9-0-202210312027+45df600c~9~ubuntu22.10.1 2022-11-02 07:55:32 startup packages configure 2022-11-02 07:55:32 configure kicad-footprints:all 6.0.9-0-202210312007+6705da57c~11~ubuntu22.10.1 2022-11-02 07:55:32 status unpacked kicad-footprints:all 6.0.9-0-202210312007+6705da57c~11~ubuntu22.10.1 2022-11-02 07:55:32 status half-configured kicad-footprints:all 6.0.9-0-202210312007+6705da57c~11~ubuntu22.10.1 2022-11-02 07:55:32 status installed kicad-footprints:all 6.0.9-0-202210312007+6705da57c~11~ubuntu22.10.1 2022-11-02 07:55:32 configure kicad-packages3d:all 6.0.9-0-202210312027+45df600c~9~ubuntu22.10.1 2022-11-02 07:55:32 status unpacked kicad-packages3d:all 6.0.9-0-202210312027+45df600c~9~ubuntu22.10.1 2022-11-02 07:55:32 status half-configured kicad-packages3d:all 6.0.9-0-202210312027+45df600c~9~ubuntu22.10.1 2022-11-02 07:55:32 status installed kicad-packages3d:all 6.0.9-0-202210312027+45df600c~9~ubuntu22.10.1 2022-11-02 07:55:32 configure libssl3:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status unpacked libssl3:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status half-configured libssl3:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status installed libssl3:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 configure libssl3:i386 3.0.5-2ubuntu2 2022-11-02 07:55:32 status unpacked libssl3:i386 3.0.5-2ubuntu2 2022-11-02 07:55:32 status half-configured libssl3:i386 3.0.5-2ubuntu2 2022-11-02 07:55:32 status installed libssl3:i386 3.0.5-2ubuntu2 2022-11-02 07:55:32 configure libssl-dev:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status unpacked libssl-dev:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status half-configured libssl-dev:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status installed libssl-dev:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 configure openssl:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status unpacked openssl:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status half-configured openssl:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 status installed openssl:amd64 3.0.5-2ubuntu2 2022-11-02 07:55:32 trigproc man-db:amd64 2.10.2-2 2022-11-02 07:55:32 status half-configured man-db:amd64 2.10.2-2 2022-11-02 07:55:33 status installed man-db:amd64 2.10.2-2 2022-11-02 07:55:33 trigproc libc-bin:amd64 2.36-0ubuntu4 2022-11-02
[Desktop-packages] [Bug 1995364] [NEW] Pointer moves to bottom right of screen automatically
You have been subscribed to a public bug: On my laptop I have an USB-C hub connected via thunderbolt with 2 external displays attached to it. When I close the laptop lid the pointer moves to the bottom right in steps of about half a second each. I am able to move the mouse, but the automatic moving happens also when I'm moving the mouse around. If i move the pointer to the top left of the screen it takes about 4 seconds for the pointer to reach the bottom right in 10 evenly spaced steps. The touchpad of the laptop is disabled. It also happens when the mouse is disconnected. I'm running Ubuntu 22.04 on a fresh install with Nvidia also installed. The issue also happens when using the integrated intel graphics. System inf $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ inxi -Fxxz System: Kernel: 5.15.0-52-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 42.4 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish) Machine: Type: Laptop System: Notebook product: PD5x_7xPNP1_PNR1_PNN1_PNT1 v: N/A serial: Chassis: No Enclosure type: 10 serial: Mobo: Notebook model: PD5x_7xPNP1_PNR1_PNN1_PNT1 serial: UEFI: INSYDE v: 1.07.02 date: 07/14/2022 Battery: ID-1: BAT0 charge: 79.7 Wh (100.0%) condition: 79.7/77.3 Wh (103.1%) volts: 13.0 min: 11.4 model: Notebook BAT serial: status: Full CPU: Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB L3: 24 MiB Speed (MHz): avg: 540 high: 871 min/max: 400/4679:4700:3500 cores: 1: 465 2: 438 3: 502 4: 400 5: 400 6: 625 7: 425 8: 437 9: 405 10: 738 11: 472 12: 854 13: 447 14: 871 15: 614 16: 439 17: 731 18: 499 19: 517 20: 536 bogomips: 107520 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Alder Lake-P Integrated Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel ports: active: DP-5,DP-6 off: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-7 bus-ID: 00:02.0 chip-ID: 8086:46a6 Device-2: NVIDIA GA104 [Geforce RTX 3070 Ti Laptop GPU] vendor: CLEVO/KAPOK driver: N/A pcie: speed: Unknown lanes: 63 bus-ID: 01:00.0 chip-ID: 10de:24a0 Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 3-8:3 chip-ID: 5986:214c Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1 compositor: gnome-shell driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: 0 Monitor-1: DP-5 model: HP E24 G4 res: 1920x1080 dpi: 93 diag: 604mm (23.8") Monitor-2: DP-6 model: HP E24 G4 res: 1920x1080 dpi: 93 diag: 604mm (23.8") OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes Audio: Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:51c8 Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: Unknown lanes: 63 bus-ID: 01:00.1 chip-ID: 10de:228b Sound Server-1: ALSA v: k5.15.0-52-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 2d:00.0 chip-ID: 8086:2723 IF: wlp45s0 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 2f:00.0 chip-ID: 10ec:8168 IF: enp47s0 state: down mac: Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-1.3:3 chip-ID: 0bda:8153 IF: enx34298f74affb state: down mac: Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-10:5 chip-ID: 8087:0029 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 3.0 lmp-v: 5.2 sub-v: 237e Drives: Local Storage: total: 931.51 GiB used: 20 GiB (2.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 31.9 C Partition: ID-1: / size: 915.32 GiB used: 20 GiB (2.2%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 38.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 378 Uptime: 27m Memory: 62.52 GiB used: 2.55 GiB (4.1%) Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.3.0 alt: 11 Packages: 1914 apt: 1905 snap: 9 Shell: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.13 ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Pointer moves to bottom right of screen automatically
[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.
OK then we are only waiting for version 43.1 to reach kinetic.
--
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/1994519
Title:
DisplayLink display is black on plug-in and mutter crash after moving
cursor on DisplayLink display.
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
This is recent regression with reproduction rate 100%.
This is regression mutter-43, Ubuntu 22.04 works fine.
Bug is raised on Gnome/mutter:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
Fix is under review:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676
### Steps to reproduce
1. Login
2. Attach DisplayLink device with display connected
3. Notice that display is visible in Display Preferences but display stays
blank.
4. Move cursor over DisplayLink display.
5. Mutter crashes.
### What happened
Mutter crashes, user is asked to log-in again.
### What did you expect to happen
Mutter does not crash.
### Relevant logs, screenshots, screencasts etc.
Crash in line:
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226
Crash backtrace:
```
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at
../src/backends/native/meta-renderer-native.c:204
204 render_device = renderer_gpu_data->render_device;
(gdb) bt
#0 0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00)
at ../src/backends/native/meta-renderer-native.c:204
#1 0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00,
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24,
stride=96, cursor_width=64, cursor_height=64, format=875713089,
error=0x7ffda9443108) at
../src/backends/native/meta-cursor-renderer-native.c:1329
#2 0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96,
gbm_format=875713089) at
../src/backends/native/meta-cursor-renderer-native.c:1399
#3 0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL,
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
at ../src/backends/native/meta-cursor-renderer-native.c:1574
#4 0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00,
sprite_wayland=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1670
#5 0x7f9209c07788 in realize_cursor_sprite_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00)
at ../src/backends/native/meta-cursor-renderer-native.c:1836
#6 0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580,
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at
../src/backends/native/meta-cursor-renderer-native.c:1854
#7 0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1087
#8 0x7f9209aac8fa in meta_cursor_renderer_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/meta-cursor-renderer.c:413
#9 0x7f9209aaca07 in meta_cursor_renderer_force_update
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
#10 0x7f9209bc4dc6 in update_cursor_sprite_texture
(cursor_surface=0x55eb1924d880) at
../src/wayland/meta-wayland-cursor-surface.c:79
#11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-cursor-surface.c:179
#12 0x7f9209be3774 in meta_wayland_surface_role_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:1938
#13 0x7f9209be14b6 in meta_wayland_surface_apply_state
(surface=0x55eb16305e60, state=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:882
#14 0x7f9209be19c7 in meta_wayland_surface_commit
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
#15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150,
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
#16 0x7f9209d1ae2e in () at /lib/x86_64-linux-gnu/libffi.so.8
#17 0x7f9209d17493 in () at /lib/x86_64-linux-gnu/libffi.so.8
#18 0x7f920aea42a0 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#19 0x7f920aea8694 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
Could you check your /var/log/dpkg.log to see which packages got updated today for you? are the duplicate going away after a session restart? what sort of calendar account do you use? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
> I found turning off fractional scaling made it go away. Only Xorg fractional scaling changes the display hardware mode directly. If we're still talking about Wayland only then I would not expect fractional scaling to have triggered the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.
gnome-42 branch does not reproduce this bug.
This is happening on main branch which has 43.0 version. There is no gnome-43
branch yet.
--
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/1994519
Title:
DisplayLink display is black on plug-in and mutter crash after moving
cursor on DisplayLink display.
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
This is recent regression with reproduction rate 100%.
This is regression mutter-43, Ubuntu 22.04 works fine.
Bug is raised on Gnome/mutter:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
Fix is under review:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676
### Steps to reproduce
1. Login
2. Attach DisplayLink device with display connected
3. Notice that display is visible in Display Preferences but display stays
blank.
4. Move cursor over DisplayLink display.
5. Mutter crashes.
### What happened
Mutter crashes, user is asked to log-in again.
### What did you expect to happen
Mutter does not crash.
### Relevant logs, screenshots, screencasts etc.
Crash in line:
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226
Crash backtrace:
```
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at
../src/backends/native/meta-renderer-native.c:204
204 render_device = renderer_gpu_data->render_device;
(gdb) bt
#0 0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00)
at ../src/backends/native/meta-renderer-native.c:204
#1 0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00,
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24,
stride=96, cursor_width=64, cursor_height=64, format=875713089,
error=0x7ffda9443108) at
../src/backends/native/meta-cursor-renderer-native.c:1329
#2 0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96,
gbm_format=875713089) at
../src/backends/native/meta-cursor-renderer-native.c:1399
#3 0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL,
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
at ../src/backends/native/meta-cursor-renderer-native.c:1574
#4 0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00,
sprite_wayland=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1670
#5 0x7f9209c07788 in realize_cursor_sprite_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00)
at ../src/backends/native/meta-cursor-renderer-native.c:1836
#6 0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580,
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at
../src/backends/native/meta-cursor-renderer-native.c:1854
#7 0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1087
#8 0x7f9209aac8fa in meta_cursor_renderer_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/meta-cursor-renderer.c:413
#9 0x7f9209aaca07 in meta_cursor_renderer_force_update
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
#10 0x7f9209bc4dc6 in update_cursor_sprite_texture
(cursor_surface=0x55eb1924d880) at
../src/wayland/meta-wayland-cursor-surface.c:79
#11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-cursor-surface.c:179
#12 0x7f9209be3774 in meta_wayland_surface_role_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:1938
#13 0x7f9209be14b6 in meta_wayland_surface_apply_state
(surface=0x55eb16305e60, state=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:882
#14 0x7f9209be19c7 in meta_wayland_surface_commit
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
#15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150,
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
#16 0x7f9209d1ae2e in () at /lib/x86_64-linux-gnu/libffi.so.8
#17 0x7f9209d17493 in () at /lib/x86_64-linux-gnu/libffi.so.8
#18 0x7f920aea42a0 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#19
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
Thanks for the information above, I will use "ubuntu-bug" next time. I've followed your instructions the for "apport-collect" command and sent the information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
apport information ** Tags added: apport-collected ** Description changed: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2019-11-25 (1073 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-calendar 43.0-2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 + Tags: kinetic + Uname: Linux 5.19.0-23-generic x86_64 + UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) + UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1995457/+attachment/5628527/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1995457/+attachment/5628528/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1995457/+attachment/5628529/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1995457 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags removed: regression-release ** Changed in: gnome-calendar (Ubuntu) Importance: Critical => High ** No longer affects: ubuntu-gnome ** Changed in: gnome-calendar (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-11-25 (1073 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-calendar 43.0-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (4 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
I'm still seeing issues with full screen video in firefox. Perhaps it’s a separate issue, but the static looks similar in its blockiness. ** Attachment added: "trim.B65976FD-B044-4CA2-B25F-2C8720927D82.MOV" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+attachment/5628526/+files/trim.B65976FD-B044-4CA2-B25F-2C8720927D82.MOV -- 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/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Invalid ** Changed in: ubuntu-settings (Ubuntu Kinetic) Status: Confirmed => Invalid ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Kinetic) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: ubuntu-settings (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: ubuntu-settings (Ubuntu Kinetic) Assignee: Dave Jones (waveform) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Invalid Status in pulseaudio source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Invalid Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Invalid Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
Static is confined to specific windows or surfaces, disappears behind other windows. Static seems to have stopped completely when fractional scaling is turned off. ** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] [NEW] [amdgpu] intermittent green static
You have been subscribed to a public bug: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apport-collected kinetic third-party-packages wayland-session -- [amdgpu] intermittent green static https://bugs.launchpad.net/bugs/1995320 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995457] Re: Gnome calendar multiplies event widgets on every app relaunch
** Also affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags added: kinetic regression-release ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1995457 Title: Gnome calendar multiplies event widgets on every app relaunch Status in Ubuntu GNOME: New Status in gnome-calendar package in Ubuntu: New Bug description: Since the latest update this morning, the Gnome calendar app repeats every event display, based on how many times I've restarted the app. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1995457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995477] Re: package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4
*** This bug is a duplicate of bug 1924684 *** https://bugs.launchpad.net/bugs/1924684 ** This bug has been marked a duplicate of bug 1924684 package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.1.9-9805 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1995477 Title: package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist Status in libreoffice package in Ubuntu: New Bug description: libre office package is connected to openoffice package. i cant update the full system bc there is always a error mssg with broken libre office package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 2 11:25:18 2022 DpkgTerminalLog: Vorbereitung zum Entpacken von .../libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.6_all.deb ... Entpacken von libreoffice-common (1:6.4.7-0ubuntu0.20.04.6) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.6_all.deb (--unpack): Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist ErrorMessage: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist InstallationDate: Installed on 2019-07-29 (1191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist UpgradeStatus: Upgraded to focal on 2020-05-16 (900 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
** Changed in: mutter Status: Unknown => New -- 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/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995477] [NEW] package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus
Public bug reported: libre office package is connected to openoffice package. i cant update the full system bc there is always a error mssg with broken libre office package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 2 11:25:18 2022 DpkgTerminalLog: Vorbereitung zum Entpacken von .../libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.6_all.deb ... Entpacken von libreoffice-common (1:6.4.7-0ubuntu0.20.04.6) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.6_all.deb (--unpack): Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist ErrorMessage: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist InstallationDate: Installed on 2019-07-29 (1191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist UpgradeStatus: Upgraded to focal on 2020-05-16 (900 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1995477 Title: package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist Status in libreoffice package in Ubuntu: New Bug description: libre office package is connected to openoffice package. i cant update the full system bc there is always a error mssg with broken libre office package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 2 11:25:18 2022 DpkgTerminalLog: Vorbereitung zum Entpacken von .../libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.6_all.deb ... Entpacken von libreoffice-common (1:6.4.7-0ubuntu0.20.04.6) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.6_all.deb (--unpack): Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist ErrorMessage: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist InstallationDate: Installed on 2019-07-29 (1191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: Versuch, »/usr/bin/soffice« zu überschreiben, welches auch in Paket openoffice-debian-menus 4.1.6-9790 ist UpgradeStatus: Upgraded to focal on 2020-05-16 (900 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
Still a problem on jammy, and removing switch-on-connect does fix things there. The result of that change is that plugging in a new (never seen before) USB device does *not* automatically switch to it, but once the device has been selected as the output, it will subsequently be automatically selected when plugged in (or at least that's my experience on my PC). And it also clears up the "always selects headphones output" issue on the Pi. I'll target this to jammy given we're still getting duplicate reports about it (LP: #1995459 is the latest) ** Also affects: pulseaudio (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Confirmed Status in pulseaudio source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Confirmed Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995459] Re: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 This sounds like a duplicate of LP: #1877194 -- a workaround is available in that report (see comment 2) ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1995459 Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2489 https://gitlab.gnome.org/GNOME/mutter/-/issues/2489 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2489 Importance: Unknown Status: Unknown -- 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/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995459] [NEW] [vc4-hdmi - vc4-hdmi-0, playback] Playback problem
Public bug reported: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1995459 Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.
I suggest the best way to get the fix into jammy is to propose a cherry
pick upstream to the 'gnome-42' branch (hoping for version 42.7)
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mutter-43.1 fixed-upstream
--
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/1994519
Title:
DisplayLink display is black on plug-in and mutter crash after moving
cursor on DisplayLink display.
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
This is recent regression with reproduction rate 100%.
This is regression mutter-43, Ubuntu 22.04 works fine.
Bug is raised on Gnome/mutter:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
Fix is under review:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676
### Steps to reproduce
1. Login
2. Attach DisplayLink device with display connected
3. Notice that display is visible in Display Preferences but display stays
blank.
4. Move cursor over DisplayLink display.
5. Mutter crashes.
### What happened
Mutter crashes, user is asked to log-in again.
### What did you expect to happen
Mutter does not crash.
### Relevant logs, screenshots, screencasts etc.
Crash in line:
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226
Crash backtrace:
```
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at
../src/backends/native/meta-renderer-native.c:204
204 render_device = renderer_gpu_data->render_device;
(gdb) bt
#0 0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00)
at ../src/backends/native/meta-renderer-native.c:204
#1 0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00,
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24,
stride=96, cursor_width=64, cursor_height=64, format=875713089,
error=0x7ffda9443108) at
../src/backends/native/meta-cursor-renderer-native.c:1329
#2 0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96,
gbm_format=875713089) at
../src/backends/native/meta-cursor-renderer-native.c:1399
#3 0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL,
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
at ../src/backends/native/meta-cursor-renderer-native.c:1574
#4 0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00,
sprite_wayland=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1670
#5 0x7f9209c07788 in realize_cursor_sprite_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00)
at ../src/backends/native/meta-cursor-renderer-native.c:1836
#6 0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580,
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at
../src/backends/native/meta-cursor-renderer-native.c:1854
#7 0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1087
#8 0x7f9209aac8fa in meta_cursor_renderer_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/meta-cursor-renderer.c:413
#9 0x7f9209aaca07 in meta_cursor_renderer_force_update
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
#10 0x7f9209bc4dc6 in update_cursor_sprite_texture
(cursor_surface=0x55eb1924d880) at
../src/wayland/meta-wayland-cursor-surface.c:79
#11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-cursor-surface.c:179
#12 0x7f9209be3774 in meta_wayland_surface_role_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:1938
#13 0x7f9209be14b6 in meta_wayland_surface_apply_state
(surface=0x55eb16305e60, state=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:882
#14 0x7f9209be19c7 in meta_wayland_surface_commit
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
#15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150,
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
#16 0x7f9209d1ae2e in () at /lib/x86_64-linux-gnu/libffi.so.8
#17 0x7f9209d17493 in
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
Yes you're both right (and I wasn't paying enough attention) that it sounds like a pipewire task is required here. ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep
Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1878367. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-09-12T13:33:49+00:00 jan.public wrote: Description of problem: I have a two display setup in GNOME Wayland. One DVI, 100% scaled regular display and one Display Link, 150% scaled HiDPI display. When I maximize a window, for example gedit, on the right 150% scaled screen and lock the system with Tux-L, after unlocking the system (after waiting for roughly 30 minutes) gedit moved to the other 100% scaled window and is there in a weird place (see screenshot). How reproducible: Not always, maybe related to the waiting time between locking and unlocking the screen. I will try to figure out if this is related and update this issue with my findings. Steps to Reproduce: 1. Set up a configuration as described. 2. Open gedit maximized on the right display. 3. Lock the system with Tux-L 4. Wait for a relative long time (say 30 minutes) 5. Unlock the screen by typing in the password. Actual results: gedit moved to the left display and is positioned in a wrong way (see screenshot) Expected results: gedit should be in the same display as when the system was locked. Additional info: I do not think that this issue is related to suspending the system, as I could reproduce after fresh boot without having the system suspended. $ inxi -G Graphics: Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] driver: amdgpu v: kernel Display: wayland server: Fedora Project X.org 1.20.8 driver: ati,modesetting unloaded: fbdev,vesa resolution: 1: 1920x1080~60Hz 2: 1680x1050~60Hz OpenGL: renderer: Radeon RX 560 Series (POLARIS11 DRM 3.37.0 5.7.11-200.fc32.x86_64 LLVM 10.0.0) v: 4.6 Mesa 20.1.5 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/0 On 2020-09-12T13:34:26+00:00 jan.public wrote: Created attachment 1714638 GNOME display settings Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/1 On 2020-09-12T13:35:51+00:00 jan.public wrote: Created attachment 1714639 gedit moved to the other screen and in a wrong position Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/2 On 2020-09-12T13:41:05+00:00 jan.public wrote: You can see in the screenshot that it looks like that gedit is aligned at the top of the larger window, but having the size of the smaller window. In reality the bottoms of the windows are aligned, not the tops. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/3 On 2020-09-12T13:47:01+00:00 jan.public wrote: See also: bug 1815492. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/4 On 2020-09-12T15:58:26+00:00 jan.public wrote: See also: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/5 On 2020-09-14T10:14:23+00:00 jan.public wrote: See also: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1001984 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/6 On 2020-10-03T19:42:03+00:00 jan.public wrote: See also: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092 https://bugs.launchpad.net/gnome-shell/+bug/1295267 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/380 https://github.com/linuxmint/Cinnamon/issues/5487 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/7 On 2020-10-19T09:38:47+00:00 jan.public wrote: In GNOME mutter gitlab (https://gitlab.gnome.org/GNOME/mutter/-/issues/1419#note_937356) it was pointed out to me that the incorrect placement of the windows in the monitors happens when the monitors of different size and resolution are aligned at the bottom. When they are aligned at the top, the problem disappears.
[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep
Maybe related to this: https://gitlab.gnome.org/GNOME/mutter/-/issues/230#note_1551972. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #230 https://gitlab.gnome.org/GNOME/mutter/-/issues/230 ** Bug watch added: Red Hat Bugzilla #1878367 https://bugzilla.redhat.com/show_bug.cgi?id=1878367 ** Also affects: gnome-shell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1878367 Importance: Unknown Status: Unknown -- 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/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell package in Fedora: Unknown 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/dash-to-dock/+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 1993327] Re: Misalignment of label alongside Icon size slider under Ubuntu Desktop page
** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993327 Title: Misalignment of label alongside Icon size slider under Ubuntu Desktop page Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In System Settings, the label alongside the Icon size slider under Ubuntu Desktop page is misaligned with the slider, as shown in the attached screenshot. It is placed a bit too low from the position of the slider. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 19:58:27 2022 InstallationDate: Installed on 2022-09-24 (24 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995412] Re: Expandable folders option disappeared
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1995412 Title: Expandable folders option disappeared Status in nautilus package in Ubuntu: Triaged Bug description: Ubuntu 22.10 nautilus: Installed: 1:43.0-1ubuntu1 Nautilus click on 'Preferences' Expandable folders option was present in Ubuntu 22.04 now disappeared in Ubuntu 22.10. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 1 18:54:22 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1580, 879)' InstallationDate: Installed on 2022-10-25 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect
On Ubuntu 22.10 I was able to connect a xbox one controller. However, this only worked after upgrading the firmware of the controller to the latest (by using Xbox Accessories app on Windows). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1750146 Title: Xbox (One) Wireless Controller won't connect Status in gnome-control-center: Confirmed Status in Linux: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center. Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode. This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB). Please fix. See the attached system information below. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 09:26:14 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.
Hi,
I am DisplayLink developer.
This is already fixed and merged in here:
https://gitlab.gnome.org/GNOME/mutter/-/commit/c57a500ccbd16694e7cbb3408b1da5dc8efb44ba
Can you please cherry-pick that fix?
--
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/1994519
Title:
DisplayLink display is black on plug-in and mutter crash after moving
cursor on DisplayLink display.
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
In Progress
Bug description:
This is recent regression with reproduction rate 100%.
This is regression mutter-43, Ubuntu 22.04 works fine.
Bug is raised on Gnome/mutter:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
Fix is under review:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676
### Steps to reproduce
1. Login
2. Attach DisplayLink device with display connected
3. Notice that display is visible in Display Preferences but display stays
blank.
4. Move cursor over DisplayLink display.
5. Mutter crashes.
### What happened
Mutter crashes, user is asked to log-in again.
### What did you expect to happen
Mutter does not crash.
### Relevant logs, screenshots, screencasts etc.
Crash in line:
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226
Crash backtrace:
```
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at
../src/backends/native/meta-renderer-native.c:204
204 render_device = renderer_gpu_data->render_device;
(gdb) bt
#0 0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00)
at ../src/backends/native/meta-renderer-native.c:204
#1 0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00,
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24,
stride=96, cursor_width=64, cursor_height=64, format=875713089,
error=0x7ffda9443108) at
../src/backends/native/meta-cursor-renderer-native.c:1329
#2 0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96,
gbm_format=875713089) at
../src/backends/native/meta-cursor-renderer-native.c:1399
#3 0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL,
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
at ../src/backends/native/meta-cursor-renderer-native.c:1574
#4 0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00,
sprite_wayland=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1670
#5 0x7f9209c07788 in realize_cursor_sprite_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00)
at ../src/backends/native/meta-cursor-renderer-native.c:1836
#6 0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580,
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at
../src/backends/native/meta-cursor-renderer-native.c:1854
#7 0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1087
#8 0x7f9209aac8fa in meta_cursor_renderer_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/meta-cursor-renderer.c:413
#9 0x7f9209aaca07 in meta_cursor_renderer_force_update
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
#10 0x7f9209bc4dc6 in update_cursor_sprite_texture
(cursor_surface=0x55eb1924d880) at
../src/wayland/meta-wayland-cursor-surface.c:79
#11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-cursor-surface.c:179
#12 0x7f9209be3774 in meta_wayland_surface_role_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:1938
#13 0x7f9209be14b6 in meta_wayland_surface_apply_state
(surface=0x55eb16305e60, state=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:882
#14 0x7f9209be19c7 in meta_wayland_surface_commit
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
#15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150,
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
#16 0x7f9209d1ae2e in () at /lib/x86_64-linux-gnu/libffi.so.8
#17 0x7f9209d17493 in () at /lib/x86_64-linux-gnu/libffi.so.8
#18 0x7f920aea42a0
[Desktop-packages] [Bug 1995201] Re: remote desktop screen sharing does not work
Thank you for your reply. Indeed i think the documentation needs much improvement. The reason i tried xrdp was that the "it just needs to be turned on in g-c-c" did not work. https://askubuntu.com/questions/1422263/rdp-on- ubuntu-desktop-22-04 was one of the hint i followed which led into the wrong direction. In the meantime i got things working on 2 of my 4 systems see https://askubuntu.com/a/1438504/129227 and i explicitly mentioned that the links i followed might be misleading (which is part of the problem). I might not be alone in misconfiguring the system due to it not working out of the box so it's probably better to change the status of this bug and do something about it instead of getting more frustrated people out there. Still two of my systems do not work properly and the messages from /var/syslog and other logs IMHO need much improvement in giving hints what to do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1995201 Title: remote desktop screen sharing does not work Status in remmina package in Ubuntu: Invalid Bug description: https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor- ubuntu-22-04 and https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/ https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote- desktop-control/ advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be able to use it. Unfortunately on multiple machines i was not able to get it working and it seems for various reasons. On the other hand i couldn't find proper bug reports yet. There are quite a few stackexhange questons out there related to 22.04 remote desktop sharing such as * https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless * https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot * https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works * https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl * https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl I'd expect that the remote desktop sharing works out of the box and needs no further configuration and fiddling. Especially it should work if already logged in. There seem to be so many parts involved in this that there is IMHO a need to have a look at this from an overarching enduser viewpoint instead of assuming that users have to take a sysadmin course to use Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the system and not trying to implement bug #1 of Ubuntu. Let's start with the machine where i think things are getting close to working and the message in /var/log/syslog is: ``` Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X server on display 11 to startup Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started successfully for user wf on display 11 Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel server for display 11 Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on display 11, waiting until the window manager (pid 101543) exits to end the session Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X server on display 11 to startup Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server active on display 11 Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured attempting to start the window manager on display 11, aborting connection Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 101543, display 11) exited quickly (0 secs). This could indicate a window manager config problem Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session and auth_end from pid 101542 Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 101544) on display 11 Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp channel server (pid 102029) on display 11 Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 (pid 101544) returned exit code 1 and signal number 0 Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for display 11 (pid 102029) exit code 0 and signal number 0 Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets: Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session: username wf, display :11.0, session_pid 101542, ip :::2.0.0.10:59651 - socket: 12 ``` And i get a black screen in the rdp client on my mac os machine from which i try to connect with Microsoft Remote Desktop To manage
[Desktop-packages] [Bug 310270]
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/310270 Title: Dell XPS M1330 volume keys as pressed two times Status in KDE Multimedia: Incomplete Status in xserver-xorg-input-evdev package in Ubuntu: Incomplete Bug description: All my volume multimedia keys (vol-up, vol-down, mute) works bad on my Dell XPS M1330 on Kubuntu with Kde4.2 beta. Every keys works as if it was pressed twice, so i raise up my volume by two levels, and when I mute the volume, it mutes and than unmutes. Sorry for my english. If you need more information, ask me. Everything was working good on Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/kdemultimedia/+bug/310270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
