[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops
** Description changed: [Impact] - * According to Nvidia README, the RTD3 doesn't support on non-laptop - machine + * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine + * Patch make system not enable RTD3 unless it's a laptop [Test Plan] - * Installed Nvidia GPU driver - * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created + * Install Ubuntu on machine + * Install GPU driver via 'ubuntu-drivers install' + * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] - * With non-laptop machine use RTD3 supported GPU may use more power. + * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Given ubuntu/impish is not exist in salsa, so I create it in my salsa git and another patch to include the change. https://salsa.debian.org/ycheng- guest/mutter/-/tree/salsa_wayland_race_fix_impish -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug
[Desktop-packages] [Bug 1949233] Re: Baloo File Extractor Closed Unexpectedly
Thanks for the bug report. As far as I can tell, Baloo has not been part of Ubuntu since 18.04. Where did you install it from? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1949233 Title: Baloo File Extractor Closed Unexpectedly Status in Ubuntu: Incomplete Bug description: Ballo File Extractor Closed Unexpectedly please report this error to help improve this software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 29 15:26:00 2021 DistUpgraded: 2021-01-08 14:56:49,798 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6310] [17aa:397f] InstallationDate: Installed on 2020-12-18 (315 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 2181 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c44a1ac5-9dee-4bf8-a246-6303f68e5c24 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-01-08 (294 days ago) dmi.bios.date: 10/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G585 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G585 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:svnLENOVO:pn2181:pvrLenovoG585:rvnLENOVO:rnLenovoG585:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG585: dmi.product.family: IDEAPAD dmi.product.name: 2181 dmi.product.sku: LENOVO_MT_2181 dmi.product.version: Lenovo G585 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Oct 17 09:09:38 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1949233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
MP for focal: https://salsa.debian.org/gnome- team/mutter/-/merge_requests/78 -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1949497] Re: [amdgpu] AMD R5 M430 dGPU freezes
Thanks for the bug report. Please try each of these separately: -- Edit /etc/environment and add: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 then reboot. -- Select 'Ubuntu on Xorg' on the login screen. -- ** Summary changed: - AMD R5 M430 dGPU freezes + [amdgpu] AMD R5 M430 dGPU freezes ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: amdgpu ** Tags added: hybrid i915 ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - [amdgpu] AMD R5 M430 dGPU freezes + [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Incomplete Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1949469] Re: gnome-shell is taking too much memory
Thanks for the bug report. Please start by uninstalling all your custom extensions. Don't just disable them because a really buggy extension can still leak when disabled. Then log in again and verify the problem is still occurring. If the problem is still occurring without extensions then while it is happening please run: ps auxw | grep gnome-shell > psoutput.txt and attach the resulting text file here. ** Tags added: gnome-shell-leak ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1949469 Title: gnome-shell is taking too much memory Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome shell is taking too much memory even if i disable all gnome extensions, it still the case, for now i'm having only 4 extensions but still taking almost the half of my memory knowning that i have 16GB RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 13:21:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-31 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Description changed: + [Impact] + + * Gdm crashed and user need to be an expert to know how to work around, +or need to reboot to fix. + + * OEM projects got certain SKU that can reliably reproduce this issue. + + * A merged patch in upstream fix the race condition. + + [Test Plan] + + * Use the SKU that can reliably reproduce this issue. + * Do a cold boot, and wait for 5 mins. The monitor should turned-black +but showing the Machine Vendor logo that was previously +displayed by plythmouth. + * Try to dog-food the deb from the proposed channel and make sure +all input events still properly propagate. + + [Where problems could occur] + + * If the patch is not properly working as expected, per the file this +patch touch, the user desktop session could stop responding to +mouse, keyboard, and touch screen input. + + [Other Info] + + * Can't think of any for now. + + + This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this
[Desktop-packages] [Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
If you find the patch in comment #2 helps then please propose it at https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Summary changed: - Removable drives are not auto-mounted after screen lock/unlock + [vmware] Removable drives are not auto-mounted after screen lock/unlock ** Tags added: vmware -- 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/1949352 Title: [vmware] Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: New Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948778] Re: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions
I've merged your old bug 1838644 into this one. -- 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/1948778 Title: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948778] Re: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948778 Title: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell
Thanks for the video! That "flash" seems to be the whole screen flickering to black. It can happen if the Wayland backend fails to assign a buffer to the screen for a frame. But it can also happen with monitor connection issues that may be hardware or software (kernel) problems. That's less likely on a laptop but not impossible (I've seen it there too). Let's assume it's a software bug in Mutter's Wayland backend, but I am out of ideas right now other than using 'Ubuntu on Xorg' as a workaround. ** Summary changed: - Random flashes in gnome-shell + [Notebook N7x0WU] Random black flickers in gnome-shell ** Summary changed: - [Notebook N7x0WU] Random black flickers in gnome-shell + [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1948778 Title: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off on NUC8i5INH
** Summary changed: - Power Savings doesn't turn monitor off in Wayland on NUC8i5INH + Power Savings doesn't turn monitor off on NUC8i5INH -- 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/1949262 Title: Power Savings doesn't turn monitor off on NUC8i5INH Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: On previous versions of Ubuntu, after 5 minutes, my monitor would turn off as per settings. Since I reinstalled fresh 21.10, this is not happening. Screen becomes black and stays powered on. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 30 08:11:02 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [8086:2079] InstallationDate: Installed on 2021-10-14 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Intel(R) Client Systems NUC8i5INH ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: INWHL357.0043.2021.0817.1957 dmi.board.name: NUC8i5INB dmi.board.vendor: Intel Corporation dmi.board.version: K29935-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: IN dmi.product.name: NUC8i5INH dmi.product.sku: BXNUC8i5INHPA dmi.product.version: K47340-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on some devices
Gerry, please follow the instructions in bug 1949262 instead. ** No longer affects: gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on some devices Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1929650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Just Got the Update now -- 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/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Focal: Fix Released Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
Thanks for uploading the fix for this bug report to -proposed. However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process. You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding where problems may occur. Thanks in advance!
** Also affects: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-prime (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: nvidia-prime (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Triaged
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in nvidia-prime source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
New
Status in nvidia-prime source package in Hirsute:
New
Status in ubuntu-drivers-common source package in Hirsute:
New
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
X-HWE-Bug: Bug #1946434
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding where problems may occur. Thanks in advance! ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: nvidia-prime (Ubuntu Focal) Status: New => Incomplete ** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. X-HWE-Bug: Bug #1946434 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding where problems may occur. Thanks in advance! ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: nvidia-prime (Ubuntu Focal) Status: New => Incomplete ** Changed in: nvidia-prime (Ubuntu Impish) Status: New => Incomplete ** Changed in: nvidia-prime (Ubuntu Impish) Status: Incomplete => Fix Released ** Also affects: nvidia-prime (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. X-HWE-Bug: Bug #1946434 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Missing SRU information
Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding where problems may occur. Thanks in advance! ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => Incomplete ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Hirsute: Incomplete Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. X-HWE-Bug: Bug #1946434 X-HWE-Bug: Bug #1946440 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (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/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949522] [NEW] Ruler in dark theme not visible
Public bug reported: Libreoffice with dark theme, ruler ticks and marks are also dark, so impossible to distinguish. System info: >snap list libreoffice 7.2.1.2 235latest/stable canonical✓ - >lsb_release -a No LSB modules are available. Distributor ID: Neon Description:KDE neon User - Plasma 25th Anniversary Edition Release:20.04 Codename: focal ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_20211102_173030.png" https://bugs.launchpad.net/bugs/1949522/+attachment/5537755/+files/Screenshot_20211102_173030.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1949522 Title: Ruler in dark theme not visible Status in libreoffice package in Ubuntu: New Bug description: Libreoffice with dark theme, ruler ticks and marks are also dark, so impossible to distinguish. System info: >snap list libreoffice 7.2.1.2 235latest/stable canonical✓ - >lsb_release -a No LSB modules are available. Distributor ID: Neon Description:KDE neon User - Plasma 25th Anniversary Edition Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936728] Re: missing ip v6 link local route by Network-Manager
Bug still exists in Lubuntu 21.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1936728 Title: missing ip v6 link local route by Network-Manager Status in network-manager package in Ubuntu: New Bug description: Hi, I was analyzing, why all the Ubuntu 20.04 machines in my network can operate at full ethernet speed over IPv4, but some are significantly slower when using ipv6. Short reason: Missing route by Network Manager long reason description: I'm using a FritzBox DOCSIS router (quit common in Germany), providing both IPv4 and IPv6 internet. The IPv6 prefix is assigned by the provider only dynamically and changes from time to time. Since this makes internal firewalling difficult, I've configured the Router use a second IPv6 network range, a unique local address range (ULA), starting with fd..., standard practice for IPv6. Thus the router advertises two ipv6 network prefixes, one official, which is dynamically assigned by the provider (2a02::...) and one ULA (fdfc:...), both a RA and for DHCP6 requests. I found that the machines in my network deal differently with that. Those Ubuntu 20.04 machines running Ubuntu Server and using netplan to configure interfaces, do things correctly. They assign an autogenerated IPv6-address for both ranges to the interfaces (lower 64 bit constructed from mac address) and two routes for each prefix, one interface/link local route and one to the router, e.g. (prefixes and addresses abbreviated for privacy reasons) 2a02:...::/64 dev eno1 proto ra metric 100 expires 6814sec pref medium 2a02:...::/64 via fe80::ROUTER dev eno1 proto ra metric 1024 expires 1414sec pref medium fdfc:...::/64 dev eno1 proto ra metric 100 expires 6814sec pref medium fdfc:...::/64 via fe80::ROUTER dev eno1 proto ra metric 1024 expires 1414sec pref medium fe80::/64 dev eno1 proto kernel metric 256 pref medium default via fe80::ROUTER dev eno1 proto ra metric 100 expires 1414sec mtu 1500 pref medium default via fe80::ROUTER dev eno1 proto ra metric 1024 expires 1414sec pref medium although the metric 1024 routes seem superfluous and useless, things work well, since the metric 100 routes (without via) allow the machine to directly communicate with each other, therefore fast (using the switch). On the other hand, those desktop machines running Lubuntu 20.04, thus using Network-Manager to configure interfaces, do things wrong (i.e. routes are missing, there's only via-routes for both prefixes) 2a02:...::/64 via fe80::ROUTER dev enp4s0 proto ra metric 100 pref medium fdfc:...::/64 via fe80::ROUTER dev enp4s0 proto ra metric 100 pref medium fe80::/64 dev enp4s0 proto kernel metric 100 pref medium default via fe80::ROUTER dev enp4s0 proto ra metric 100 pref medium as you can see, there is no route allowing the machine to directly communicate with other hosts, except for the link local fe80 route. Therefore, traffic between two machines in the LAN is not switched on the switch, but routed on the router, and thus significantly slower (although still working, that's why most people probably wouldn't notice). I've tried several settings in the ipv6 tab of the Networks Editor (edit connections -> select wired connection -> IPv6 Settings), but neither could I find a man page describing the Automatic Methods, nor did I find any effect when changing them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Jul 18 00:59:09 2021 InstallationDate: Installed on 2020-06-12 (400 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2
This bug was fixed in the package gnome-shell-extension-desktop-icons - 20.04.0-3~ubuntu20.04.4 --- gnome-shell-extension-desktop-icons (20.04.0-3~ubuntu20.04.4) focal; urgency=medium * Add desktopManager-Avoid-scheduling-multiple-_layoutChil.patch to fix crashes in st_bin_destroy (LP: #1898005) -- Brian Murray Thu, 14 Oct 2021 13:20:13 -0700 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Released Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
ake: Entering directory '/home/Christian/binutils-gdb/cygwin-obj/gdb' CXXLD gdb.exe http://www.compilatori.com/computers/smartphones/ cp-support.o: in function `gdb_demangle(char const*, int)': http://www.acpirateradio.co.uk/services/ios15/ /home/Christian/binutils-gdb/cygwin-obj/gdb/../../gdb/cp-support.c:1619:(.text+0x5502): http://www.logoarts.co.uk/property/lidar-sensor/ relocation truncated to fit: R_X86_64_PC32 against undefined symbol http://www.slipstone.co.uk/property/hp-of-cars/ `TLS init function for thread_local_segv_handler' http://www.mconstantine.co.uk/category/technology/ /home/Christian/binutils-gdb/cygwin-obj/gdb/../../gdb/cp-support.c:1619:(.text+0x551b): http://embermanchester.uk/property/chat-themes/ relocation truncated to fit: R_X86_64_PC32 against undefined symbol `TLS init function for thread_local_segv_handler' collect2: error: ld returned 1 exit status http://connstr.net/property/mars-researches/ make: *** [Makefile:1881: gdb.exe] Error 1 make: Leaving directory '/home/Christian/binutils-gdb/cygwin-obj/gdb' http://joerg.li/services/kia-rio-price/ $ g++ -v Using built-in specs. http://www.jopspeech.com/technology/thunderbolt-4/ COLLECT_GCC=g++ COLLECT_LTO_ http://www.go-mk-websites.co.uk/category/technology/ WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/10/lto-wrapper.exe Target: x86_64-pc-cygwin http://www.wearelondonmade.com/tech/driving-assistant/ Configured with: /mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/configure -- http://fishingnewsletters.co.uk/category/technology/ srcdir=/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0 --prefix=/usr --exec-prefix=/usr http://the-hunters.org/category/travel/ --localstatedir=/var --sysconfdir=/etc --docdir=/usr/share/doc/gcc -- https://waytowhatsnext.com/computers/discord-and-steam/ htmldir=/usr/share/doc/gcc/html -C --build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin --without-libiconv-prefix --without-libintl-prefix -- http://www.iu-bloomington.com/property/properties-in-turkey/ libexecdir=/usr/lib --with-gcc-major-version-only --enable-shared --enable-shared-libgcc --enable-static --enable-version-specific-runtime-libs --enable-bootstrap --enable-__cxa_atexit --with-dwarf2 https://komiya-dental.com/sports/telegram/ --with-tune=generic --enable-languages=c,c++,fortran,lto,objc,obj-c++ --enable-graphite --enable-threads=posix --enable-libatomic --enable-libgomp --enable-libquadmath http://www-look-4.com/health/winter-sickness/ --enable-libquadmath-support --disable-libssp --enable-libada --disable-symvers --with-gnu-ld --with-gnu-as --with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix --without-libintl-prefix --with-system-zlib https://www.webb-dev.co.uk/sports/gym-during-covid/ --enable-linker-build-id --with-default-libstdcxx-abi=gcc4-compatible --enable-libstdcxx-filesystem-ts Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.2.0 (GCC) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Won't Fix Status in network-manager source package in Precise: Won't Fix Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 830949] Re: [Intel N10 Graphics] Need Compiz' "Copy to Texture" plugin so can display on multi-head layouts bigger than the max GL texture size
--8<---
1 size_t fwrite(const void * __restrict ptr, size_t size,
http://www-look-4.com/category/travel/
2 size_t nmemb, register FILE * __restrict stream)
3 {
4 size_t retval; https://komiya-dental.com/category/technology/
5 __STDIO_AUTO_THREADLOCK_VAR;
6 http://www.iu-bloomington.com/category/technology/
7 > __STDIO_AUTO_THREADLOCK(stream);
8
9 retval = fwrite_unlocked(ptr, size, nmemb, stream);
10 https://waytowhatsnext.com/category/technology/
11 __STDIO_AUTO_THREADUNLOCK(stream);
12 http://www.wearelondonmade.com/category/travel/
13 return retval;
14 }
-->8---
http://www.jopspeech.com/category/travel/
Here, we are at line 7. Using the "next" command leads no where. However,
setting a breakpoint on line 9 and issuing "continue" works.
http://joerg.li/category/travel/
Looking at the assembly instructions reveals that we're dealing with the
critical section entry code http://the-hunters.org/technology/meta-symbol/ [1]
that should never be interrupted, in this
case by the debugger's implicit breakpoints: http://connstr.net/category/travel/
--8<---
... http://embermanchester.uk/category/travel/
1 add_s r0,r13,0x38
2 mov_s r3,1
3 llock r2,[r0]<-.
4 brne.nt r2,0,14 --. | http://www.slipstone.co.uk/category/travel/
5 scond r3,[r0] | |
6 bne -10 --|--'
7 brne_s r2,0,84 <-' http://www.logoarts.co.uk/category/travel/
...
-->8---
http://www.acpirateradio.co.uk/category/travel/
Lines 3 until 5 (inclusive) are supposed to be executed atomically. Therefore,
http://fishingnewsletters.co.uk/crypto/kelleci-bay/
GDB should never (implicitly) insert a breakpoint on lines 4 and 5, else the
http://www.compilatori.com/category/travel/
program will try to acquire the lock again by jumping back to line 3 and
gets stuck in an infinite loop. https://www.webb-dev.co.uk/category/technology/
The solution is to make GDB aware of these patterns so it inserts breakpoints
after the sequence -- line 6 in this example. The solution is to make GDB aware
of these patterns so it inserts breakpoints
http://www.go-mk-websites.co.uk/services/kyoto/
after the sequence -- line 6 in this example.
The solution is to make GDB aware of these patterns so it inserts breakpoints
after the sequence -- line 6 in this example.
http://www.mconstantine.co.uk/services/new-zealand/
The solution is to make GDB aware of these patterns so it inserts breakpoints
after the sequence -- line 6 in this example.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/830949
Title:
[Intel N10 Graphics] Need Compiz' "Copy to Texture" plugin so can
display on multi-head layouts bigger than the max GL texture size
Status in Compiz:
New
Status in Unity:
Won't Fix
Status in compiz package in Ubuntu:
New
Status in xserver-xorg-video-intel package in Ubuntu:
Invalid
Status in compiz source package in Oneiric:
Won't Fix
Status in xserver-xorg-video-intel source package in Oneiric:
Invalid
Status in compiz source package in Precise:
Invalid
Status in xserver-xorg-video-intel source package in Precise:
Invalid
Bug description:
This is part of the master bug 824099
Oneiric Alpha 3 installed on this system. Under testing, one test is
to plug in an external monitor and ensure that external video
functions properly. On this EeePC, it does not. (See photo attached to
this bug).
Once the external montior is plugged in, both the primary display and
the external display are horribly garbled. The only thing that exists
on the screen that's remotely readable is the panel at the top. The
rest of the desktop area is just a mess.
Affected systems:
Dell Latitude 2110 (Intel Corporation: N10 Family Integrated Graphics
Controller)
Asus EeePC 1001PXD (Intel Corporation: N10 Family Integrated Graphics
Controller)
Asus EeePC 1011PX (Intel Corporation: N10 Family Integrated Graphics
Controller)
Asus EeePC 1015PX (Intel Corporation: N10 Family Integrated Graphics
Controller)
Dell Mini 10 (Intel Corporation: N10 Family Integrated Graphics Controller)
To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/830949/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
With this patch (not sure yet whether it's relevant) in place:
... http://www-look-4.com/category/computers/
diff --git a/gdb/testsuite/lib/gdbserver-support.exp
b/gdb/testsuite/lib/gdbserver-support.
Exp https://komiya-dental.com/health/healthy-foods/
index a2cc80f28d..7b9c0eef6e 100644
--- a/gdb/testsuite/lib/gdbserver-support.exp
http://www.iu-bloomington.com/services/travel-services/
+++ b/gdb/testsuite/lib/gdbserver-support.exp
@@ -451,8 +451,10 @@ proc gdbserver_exit { is_mi } {
https://waytowhatsnext.com/technology/korean-technology/
# We use expect rather than gdb_expect because
# we want to suppress printing exception messages, otherwise,
http://www.wearelondonmade.com/category/health/
# remote_expect, invoked by gdb_expect, prints the exceptions.
+ set read_prompt 0
expect { http://www.jopspeech.com/category/property/
-i "$gdb_spawn_id" -re "$gdb_prompt $" {
+ set read_prompt 1 http://joerg.li/category/technology/
exp_continue
}
-i "$server_spawn_id" eof {
http://connstr.net/property/mars-researches/
@@ -463,6 +465,7 @@ proc gdbserver_exit { is_mi } {
warning "Timed out waiting for EOF in server after
$monitor_exit" http://the-hunters.org/category/technology/
}
}
+ gdb_assert {$read_prompt}
}
} http://embermanchester.uk/health/social-privacy/
close_gdbserver
...
and running in parallel with: http://fishingnewsletters.co.uk/category/shopping/
...
$ stress -c 5 http://www.slipstone.co.uk/category/services/
...
I ran into:
...
(gdb) PASS: gdb.multi/multi-target.exp: continue: non-stop=on: inferior 2
http://www.logoarts.co.uk/category/travel/
Remote debugging from host ::1, port 34088^M
Process build/gdb/testsuite/outputs/gdb.multi/multi-target/multi-target
created; pid http://www.go-mk-websites.co.uk/category/shopping/ = 8649^M
monitor exit^M
(gdb) Killing process(es): 8649^M
http://www.acpirateradio.co.uk/technology/facetime/
#9 0x16a2c57 in pop_all_targets_at_and_above(strata)
/home/vries/gdb_versions/devel/src/gdb/target.c:678
http://www.mconstantine.co.uk/category/shopping/
#10 0x1442749 in remote_unpush_target
http://www.compilatori.com/tech/xiaomi/
/home/vries/gdb_versions/devel/src/gdb/remote.c:5522
#11 0x1458c16 in remote_target::readchar(int)
/home/vries/gdb_versions/devel/src/gdb/remote.c:9137
https://www.webb-dev.co.uk/sports/how-to-choose-sportwear/
#12 0x145b25b in remote_target::getpkt_or_notif_sane_1(std::vector > >*, int, int, int*)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-desktop-privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1240336
Title:
After release upgrade, the user loses permissions for several basic
actions in the system
Status in gdm3 package in Ubuntu:
Won't Fix
Status in lightdm package in Ubuntu:
Triaged
Status in lxdm package in Ubuntu:
Triaged
Status in policykit-desktop-privileges package in Ubuntu:
Triaged
Bug description:
HOW TO REPRODUCE:
- Upgrade Ubuntu to the next release.
RESULT:
- The user looses permissions for several basic actions in the system.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: policykit-desktop-privileges 0.16
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Tue Oct 15 20:20:55 2013
InstallationDate: Installed on 2013-10-09 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: policykit-desktop-privileges
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout
/gdb/arch/arc.c:117:43: required from here http://www.compilatori.com/
/usr/include/c++/4.8.2/bits/hashtable_policy.h:195:39: error: no matching
https://www.mktrade.fi/ function for call to ‘std::pairhttp://www-look-4.com/
target_desc_deleter> >::pair(const arc_arch_features&, target_desc*&)’
: _M_v(std::forward<_Args>(__args)...) { } http://www.acpirateradio.co.uk/
^
/usr/include/c++/4.8.2/bits/hashtable_policy.h:195:39: note: candidates are:
https://www.webb-dev.co.uk/
In file included from /usr/include/c++/4.8.2/utility:70:0,
from /usr/include/c++/4.8.2/tuple:38,
http://www.logoarts.co.uk/
from /usr/include/c++/4.8.2/functional:55,
from ../../gdb/../gdbsupport/ptid.h:35,
https://komiya-dental.com/
from ../../gdb/../gdbsupport/common-defs.h:123,
from ../../gdb/arch/arc.c:19: http://www.slipstone.co.uk/
/usr/include/c++/4.8.2/bits/stl_pair.h:206:9: note: templatehttp://the-hunters.org/ class ... _Args2, long
unsigned int ..._Indexes2> std::pair<_T1, http://embermanchester.uk/
_T2>::pair(std::tuple<_Args1 ...>&, std::tuple<_Args2 ...>&, std::_Index_tuple
http://fishingnewsletters.co.uk/
<_Indexes1 ...>, std::_Index_tuple<_Indexes2 ...>)
pair(tuple<_Args1...>&, tuple<_Args2...>&, http://connstr.net/
^
>8-
http://joerg.li/
Thanks to Tome de Vries' investigation, same fix applies in ARC's case as well:
8<- http://www.jopspeech.com/
diff --git a/gdb/arch/arc.c b/gdb/arch/arc.c
index 3808f9f..a5385ce 100644 http://www.go-mk-websites.co.uk/
--- a/gdb/arch/arc.c
+++ b/gdb/arch/arc.c http://www.wearelondonmade.com/
@@ -114,7 +114,7 @@ struct arc_arch_features_hasher
target_desc *tdesc = arc_create_target_description (features);
https://waytowhatsnext.com/
/* Add the newly created target description to the repertoire. */
http://www.mconstantine.co.uk/
- arc_tdesc_cache.emplace (features, tdesc); http://www.iu-bloomington.com/
+ arc_tdesc_cache.emplace (features, target_desc_up (tdesc));
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1734541
Title:
encrypted home-directory is not unmounted on logout
Status in gnome-session:
New
Status in ecryptfs-utils package in Ubuntu:
Confirmed
Status in gdm3 package in Ubuntu:
Confirmed
Status in gnome-session package in Ubuntu:
Confirmed
Status in ecryptfs-utils package in Debian:
Fix Released
Bug description:
Current Situation:
If you log out from an user account with an encrypted home directory,
it is not automatically unmounted and encrypted again.
Expected behaviour:
If I log out from an user account with an encrypted home directory, Id expect
the homedir to be unmounted and encrypted again.
Stepts to reproduce:
log into an account with encrypted home directory. (lets call it: user)
Log out again
log into another account (which has sudo rights, lets call it: user2)
and now enter the following into a terminal:
user2@ubuntu: sudo su
user2@ubuntu: ls -la /home/user
you can see the files of the user
Reasons:
This is a security issue, because as a user you can reasonable expect your
data to be safe, if you log out. if you would simply log in as another user but
keep your data accessable you would simply switch user, instead of loggin out.
Many users only suspend their laptop while carrying it with them. Logging out
and suspending the user expects to have at least the home directory encrypted.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 26 16:18:39 2017
EcryptfsInUse: Yes
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1734541/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
#0 0x55befa524260 in execute_cfa_program (fde=0x621000f84c90, http://www-look-4.com/technology/peugeot-208/ insn_ptr=0x7fab8d86da86 , http://the-hunters.org/category/tech/ insn_end=0x7fab8d86da90 , gdbarch=0x621000be3d10, https://komiya-dental.com/computers/huawei-technology/ pc=0x81b3318e, fs=0x7ffe0a288d10, text_offset=0x0) at /home/smarchi/src/binutils-gdb/gdb/dwarf2/frame.c:367 http://www.iu-bloomington.com/crypto/china-affect-on-crypto/ #1 0x55befa52bf02 in dwarf2_frame_cache (this_frame=0x6210006cfde0, this_cache=0x6210006cfdf8) https://waytowhatsnext.com/crypto/cryptocurrency-taxes/ at /home/smarchi/src/binutils-gdb/gdb/dwarf2/frame.c:1025 #2 0x00 http://fishingnewsletters.co.uk/category/property/ 0055befa52ea38 in dwarf2_frame_this_id (this_frame=0x6210006cfde0, http://www.wearelondonmade.com/services/car-repair-services/ this_cache=0x6210006cfdf8, this_id=0x6210006cfe40) at /home/smarchi/src/binutils-gdb/gdb/dwarf2/frame.c:1226 http://www.jopspeech.com/property/slim-pen-2/ #3 0x55befa8dde95 in compute_frame_id (fi=0x6210006cfde0) at /home/smarchi/src/binutils-gdb/gdb/frame.c:588 http://joerg.li/tech/cars-comparison/ #4 0x55befa8de53e in get_frame_id (fi=0x6210006cfde0) at /home/smarchi/src/binutils-gdb/gdb/frame.c:636 http://connstr.net/tech/mars-surface/ #5 0x55befa8ecf33 in get_prev_frame (this_frame=0x6210006cfde0) http://www.go-mk-websites.co.uk/category/property/ at /home/smarchi/src/binutils-gdb/gdb/frame.c:2504 http://embermanchester.uk/property/chat-themes/ #6 0x55befb1ff582 in frame_info_to_frame_object (frame=0x6210006cfde0) http://www.mconstantine.co.uk/category/property/ at /home/smarchi/src/binutils-gdb/gdb/python/py-frame.c:364 http://www.slipstone.co.uk/computers/isofix/ #7 0x55befb201016 in gdbpy_newest_frame (self=0x7fabbcb11a40, args=0x0) at /home/smarchi/src/binutils-gdb/gdb/python/py-frame.c:599 #8 0x7fabc25f01aa in cfunction_vectorcall_NOARGS (func=0x7fabbca78d60, args=, nargsf=, kwnames=) at ../Objects/methodobject.c:459 http://www.logoarts.co.uk/tech/drone-cameras/ #9 0x7fabc2405d6d in _PyObject_Vectorcall (kwnames=, nargsf=, args=, callable=) at ../Include/cpython/abstract.h:127 http://www.acpirateradio.co.uk/property/applications/ #10 call_function (tstate=0x61209940, pp_stack=0x7ffe0a289370, oparg=, kwnames=0x0) at ../Python/ceval.c:4963 http://www.compilatori.com/health/premium-subscription/ #11 0x7fabc240def6 in _PyEval_EvalFrameDefault (f=, throwflag=) at ../Python/ceval.c:3469 https://www.webb-dev.co.uk/shopping/shopping-during-corona/ #12 0x7fabc241106b in function_code_fastcall (co=, args=, nargs=1, globals=) at ../Objects/call.c:283 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in xf86-video-amd: Unknown Status in Xfwm4: Unknown Status in xfwm4 package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Triaged Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Triaged Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Won't Fix Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly.
[Desktop-packages] [Bug 1949497] [NEW] AMD R5 M430 dGPU freezes
Public bug reported: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: AMD R5 M430 dGPU freezes Status in xorg package in Ubuntu: New Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219]
[Desktop-packages] [Bug 1949352] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1949352/+attachment/5537714/+files/monitors.xml.txt -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949352] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1949352/+attachment/5537712/+files/ProcEnviron.txt -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949352] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1949352/+attachment/5537710/+files/GsettingsChanges.txt -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949352] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1949352/+attachment/5537713/+files/ShellJournal.txt -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949352] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1949352/+attachment/5537711/+files/ProcCpuinfoMinimal.txt -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
apport information ** Tags added: apport-collected impish wayland-session ** Description changed: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. - I could fix the issue by modifying the source code as given in the - attached patch. + I could fix the issue by modifying the source code as given in the attached patch. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2021-11-01 (1 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Package: gnome-shell 40.5-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 + RelatedPackageVersions: mutter-common 40.5-1ubuntu2 + Tags: wayland-session impish + Uname: Linux 5.13.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1949352/+attachment/5537709/+files/Dependencies.txt -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799998] Re: 20% of volume is like 0%
Is there a way to edit the base volume on my end? Currently it's 100% -> 0db. It could be 100% -> +11db. -- 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/178 Title: 20% of volume is like 0% Status in pulseaudio package in Ubuntu: Confirmed Bug description: There is no sound on my laptop when volume is set to 20% or less. Also, when I set it to 100%, its output is lower than on Windows. The problem occurs when using a headphone as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: roinujnosde 1600 F...m pulseaudio /dev/snd/controlC0: roinujnosde 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 13:33:21 2018 InstallationDate: Installed on 2018-10-09 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911432] Re: [SRU] wslu 3.2.1-0ubuntu1.1 to focal
I think it wasn't quite clear that we have a MRE SRU exception for this package - maybe I need to update https://wiki.ubuntu.com/wslu-Updates to make sure we include the link to the exception in the bug description everytime a backport is created. I'll take care of it later. But yeah, since this is covered by an MRE, I think it should be good to perform a review. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911432 Title: [SRU] wslu 3.2.1-0ubuntu1.1 to focal Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Focal: New Bug description: [Impact] it is proposed to be updated from 2.x to 3.x inside 21.04 circle. The detailed impact can be found on LP: #1895525. [Test Case] * checkout the ubuntu/master branch on wslu GitHub or launchpad repository; * Run the autopktest with command "autopkgtest path/to/folder -- null" in Ubuntu 20.04 on WSL1 and WSL2. * View the result of the test, it should be passed with 7 Windows Explorer open and 3 webpage open on the default browser. [Regression Potential] This is a large version update from 2.x to 3.x. There is currently one known issue LP: #1911379 that is already merged into hirsute. Other potential regressions would be a result of badly generated ~/.config/wslu/, or a badly merged package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947600] Re: Default browser changed from firefox to chrome
Reassigning to firefox, the issue is that snaps have no integration with the alternatives system so x-www-browser isn't pointing to firefox as it used to. We checked the archive for users of the alternative and we those we not important enough to consider the issue as a rls blocker for impish. We will get it to for the LTS as we complete the firefox deb to snap transition. ** Package changed: ubuntu-release-upgrader (Ubuntu) => firefox (Ubuntu) ** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1947600 Title: Default browser changed from firefox to chrome Status in firefox package in Ubuntu: Confirmed Bug description: Upgraded from 21.04 to 21.10. Using firefox since forever as default browser (with chrome as sporadic backup) After the upgrade, my default browser switched to chrome. No big problem, changed it back to FF in the settings ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 16:02:01 2021 InstallationDate: Installed on 2020-11-03 (349 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to impish on 2021-10-18 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947600] [NEW] Default browser changed from firefox to chrome
You have been subscribed to a public bug: Upgraded from 21.04 to 21.10. Using firefox since forever as default browser (with chrome as sporadic backup) After the upgrade, my default browser switched to chrome. No big problem, changed it back to FF in the settings ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 16:02:01 2021 InstallationDate: Installed on 2020-11-03 (349 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to impish on 2021-10-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: firefox (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Confirmed ** Tags: amd64 apport-bug dist-upgrade impish rls-ii-incoming -- Default browser changed from firefox to chrome https://bugs.launchpad.net/bugs/1947600 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 1945899] Re: package libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
** Information type changed from Private Security to Public -- 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/1945899 Title: package libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_74_83_generic_81 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 26 12:17:16 2021 DpkgHistoryLog: Start-Date: 2021-09-26 12:16:42 Commandline: /usr/bin/unattended-upgrade Upgrade: gcc-10-base:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libitm1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libquadmath0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgcc1:amd64 (1:10.2.0-5ubuntu1~20.04, 1:10.3.0-1ubuntu1~20.04), libtsan0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libubsan1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgfortran5:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), liblsan0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgomp1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgcc-s1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libatomic1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libcc1-0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libstdc++6:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04) DuplicateSignature: package:libreoffice-help-common:1:6.4.7-0ubuntu0.20.04.1 Setting up libgomp1:amd64 (10.3.0-1ubuntu1~20.04) ... dpkg: error processing package libreoffice-help-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-05 (392 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all 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.5 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to focal on 2020-10-10 (357 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1945899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949233] Re: Baloo File Extractor Closed Unexpectedly
** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1949233/+attachment/5537070/+files/acpidump.txt ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1949233 Title: Baloo File Extractor Closed Unexpectedly Status in xorg package in Ubuntu: New Bug description: Ballo File Extractor Closed Unexpectedly please report this error to help improve this software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 29 15:26:00 2021 DistUpgraded: 2021-01-08 14:56:49,798 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6310] [17aa:397f] InstallationDate: Installed on 2020-12-18 (315 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 2181 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c44a1ac5-9dee-4bf8-a246-6303f68e5c24 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-01-08 (294 days ago) dmi.bios.date: 10/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G585 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G585 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:svnLENOVO:pn2181:pvrLenovoG585:rvnLENOVO:rnLenovoG585:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG585: dmi.product.family: IDEAPAD dmi.product.name: 2181 dmi.product.sku: LENOVO_MT_2181 dmi.product.version: Lenovo G585 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Oct 17 09:09:38 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1949233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949187] Re: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949187 Title: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: sometime system freezes ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: systemd-timesyncd:amd64: Configure systemd:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 29 16:00:03 2021 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:i386:1.16.2-4ubuntu0.1 Setting up libgstreamer1.0-0:i386 (1.16.2-2) ... Setcap worked! gst-ptp-helper is not suid! dpkg: error processing package libgstreamer-plugins-base1.0-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-10-28 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1949187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949303] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1949303 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: i don't no ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-38-generic Date: Sat Oct 30 21:28:43 2021 InstallationDate: Installed on 2021-05-09 (175 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1949303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261211] Re: No multichannel support on Creative CA0132
Launchpad has imported 8 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=67071. 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 2013-12-16T03:17:06+00:00 thetallest wrote: Multichannel sound is not working on my Creative CA0132 sound card. Stereo is working just fine but I cannot get 5.1 to work. when I run 'speaker-test -c 6' sound only comes out of the front 2 speakers and if I add '-Dsurround51' it returns "Channels count (6) not available for playbacks: Invalid argument". My alsa info http://www.alsa- project.org/db/?f=3a5ca77035da6be08769128daa43dcbc59badb93 Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/3 On 2014-02-25T02:24:15+00:00 sean_mccully wrote: I have the exact same issue with same card, http://www.alsa- project.org/db/?f=a8ae0aa3c0da4d697c1df5f403001dff50bb6e51 Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/4 On 2014-02-27T01:31:40+00:00 superquad.vortex2 wrote: https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_ca0132.c?id=825315bc5b5c33e5af5124ff100ef05a30ad722f since it no longer used snd_hda_multi_out_analog_xxx functions + ca0132_setup_stream(codec, spec->dacs[0], stream_tag, 0, format); only single DAC is used for stereo playback - .channels_max = 2, + .channels_max = 6, the change in channels_max has no effect since spec->multiout is not used anymore info->stream[SNDRV_PCM_STREAM_PLAYBACK].channels_max = spec->multiout.max_channels; Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/5 On 2017-03-26T10:57:32+00:00 842mono wrote: http://www.alsa- project.org/db/?f=f458ee979a3e2052a3095d0d1e958200a20c022f I have the same issue. I have a g1 sniper z87. The only thing that works is stereo audio. The card includes 5.1 audio ports and a headphone port. I can only get sound through the "front speaker out" of the 5.1 ports. See this from board's manual: https://drive.google.com/open?id=0B0f0nmVh2CHdb08xLWhYOElXa2c Also microphone doesn't work at all. Link to board's manual download.gigabyte.eu/FileList/Manual/mb_manual_g1.sniper-z87_e.pdf Link to board's webpage http://www.gigabyte.us/Motherboard/G1Sniper-Z87-rev-11#kf Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/6 On 2021-11-01T17:59:35+00:00 kungfujesus06 wrote: I too am seeing this issue with the onboard audio for an EVGA X299 Dark. Manual: https://www.evga.com/support/manuals/files/151-SX-E299.pdf I've not yet tried to install Windows somewhere, configure the sound card there, and reboot. Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/8 On 2021-11-01T17:59:59+00:00 kungfujesus06 wrote: Oh, and kernel: 5.14.13 Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/9 On 2021-11-01T18:29:40+00:00 kungfujesus06 wrote: So, I managed to get at least 5 channels working (not sure what's up with LFE) by adding to the quirks table the PCI ID presented by my motherboard to match the X99 one. So, something is likely not working entirely correctly with the model=auto stuff? Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1261211/comments/10 On 2021-11-01T18:49:52+00:00 kungfujesus06 wrote: So, I know the "quirks" bit has been looked down on a bit and model=auto is the preferred way to setup things with pin arrangements but...this fix worked for me and as far as I can tell, everything works, including DSP effects. --- /tmp/patch_ca0132_old.c 2021-11-01 14:47:55.720188567 -0400 +++ patch_ca0132.c 2021-11-01 14:10:04.334728000 -0400 @@ -1306,6 +1306,7 @@ SND_PCI_QUIRK(0x1458, 0xA026, "Gigabyte G1.Sniper Z97", QUIRK_R3DI), SND_PCI_QUIRK(0x1458, 0xA036, "Gigabyte GA-Z170X-Gaming 7", QUIRK_R3DI), SND_PCI_QUIRK(0x3842, 0x1038, "EVGA X99 Classified", QUIRK_R3DI), + SND_PCI_QUIRK(0x3842, 0x104b, "EVGA X299 Dark", QUIRK_R3DI), SND_PCI_QUIRK(0x1102, 0x0013, "Recon3D", QUIRK_R3D), SND_PCI_QUIRK(0x1102, 0x0018, "Recon3D", QUIRK_R3D), SND_PCI_QUIRK(0x1102, 0x0051, "Sound Blaster AE-5",
[Desktop-packages] [Bug 1949469] [NEW] gnome-shell is taking too much memory
Public bug reported: gnome shell is taking too much memory even if i disable all gnome extensions, it still the case, for now i'm having only 4 extensions but still taking almost the half of my memory knowning that i have 16GB RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 13:21:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-31 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1949469 Title: gnome-shell is taking too much memory Status in gnome-shell package in Ubuntu: New Bug description: gnome shell is taking too much memory even if i disable all gnome extensions, it still the case, for now i'm having only 4 extensions but still taking almost the half of my memory knowning that i have 16GB RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 13:21:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-31 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on some devices
In my case, adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment worked. After reboot, the screen turns off and stays off. I will do further testing if this has some side effects. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on some devices Status in Mutter: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1929650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949466] [NEW] apparmor warning when using chromedriver snap
Public bug reported:
Hello,
I noticed my logs are flooded by the following messages when using the
chromedriver snap (95.0.4638.69):
AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromedriver" name="/proc/2749786/mem"
pid=2749786 comm="bef84659f723721" requested_mask="r" denied_mask="r"
fsuid=1001 ouid=1001
I managed to fix it by adding the following line in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver :
owner @{PROC}/@{pid}/mem r,
and then running :
sudo apparmor_parser -r
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver
However I understand this change will get overwritten every time the
snap is updated, so it would make sense to add this line in the snap
package itself.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: apparmor
** Description changed:
Hello,
- I noticed my logs are flooded by the following messages when using
chromedriver (95.0.4638.69):
- ```
- AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromedriver"
name="/proc/2749786/mem" pid=2749786 comm="bef84659f723721" requested_mask="r"
denied_mask="r" fsuid=1001 ouid=1001
- ```
+ I noticed my logs are flooded by the following messages when using
+ chromedriver (95.0.4638.69):
+
+ AVC apparmor="DENIED" operation="open"
+ profile="snap.chromium.chromedriver" name="/proc/2749786/mem"
+ pid=2749786 comm="bef84659f723721" requested_mask="r" denied_mask="r"
+ fsuid=1001 ouid=1001
+
I managed to fix it by adding the following line in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver :
- `owner @{PROC}/@{pid}/mem r,``
- and then running `sudo apparmor_parser -r
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver`
+
+ owner @{PROC}/@{pid}/mem r,
+
+ and then running :
+
+ sudo apparmor_parser -r
+ /var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver
** Description changed:
Hello,
I noticed my logs are flooded by the following messages when using
chromedriver (95.0.4638.69):
AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromedriver" name="/proc/2749786/mem"
pid=2749786 comm="bef84659f723721" requested_mask="r" denied_mask="r"
fsuid=1001 ouid=1001
-
- I managed to fix it by adding the following line in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver :
+ I managed to fix it by adding the following line in
+ /var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver :
owner @{PROC}/@{pid}/mem r,
and then running :
sudo apparmor_parser -r
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver
+
+ However I understand this change will get overwritten every time the
+ snap is updated, so it would make sense to add this line in the snap
+ package itself.
** Summary changed:
- apparmor warning when using chromedriver
+ apparmor warning when using chromedriver snap
** Description changed:
Hello,
- I noticed my logs are flooded by the following messages when using
- chromedriver (95.0.4638.69):
+ I noticed my logs are flooded by the following messages when using the
+ chromedriver snap (95.0.4638.69):
AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromedriver" name="/proc/2749786/mem"
pid=2749786 comm="bef84659f723721" requested_mask="r" denied_mask="r"
fsuid=1001 ouid=1001
I managed to fix it by adding the following line in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver :
owner @{PROC}/@{pid}/mem r,
and then running :
sudo apparmor_parser -r
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver
However I understand this change will get overwritten every time the
snap is updated, so it would make sense to add this line in the snap
package itself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1949466
Title:
apparmor warning when using chromedriver snap
Status in chromium-browser package in Ubuntu:
New
Bug description:
Hello,
I noticed my logs are flooded by the following messages when using the
chromedriver snap (95.0.4638.69):
AVC apparmor="DENIED" operation="open"
profile="snap.chromium.chromedriver" name="/proc/2749786/mem"
pid=2749786 comm="bef84659f723721" requested_mask="r" denied_mask="r"
fsuid=1001 ouid=1001
I managed to fix it by adding the following line in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver :
owner @{PROC}/@{pid}/mem r,
and then running :
sudo apparmor_parser -r
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver
However I understand this change will get overwritten every time the
snap is updated, so it would make sense to add this line in the snap
package itself.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949466/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell
I also tested quiet splash mitigations=off without luck -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell
@Daniel #14 i have 1 wallpaper active, not automaticly changed -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell
The screen record of the glitch ** Attachment added: "glitch.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+attachment/5537666/+files/glitch.mp4 -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949433] [NEW] The progress remains inactive and instaling software seems to be doing nothing. Using the cli works.
Public bug reported: When trying to install hexchat there is no progress shown. It seems like installation does nothing. Using the cli works. I was using the flathub (flatpak) to install the aarch64 version of hexchat. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software 40.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 07:46:42 2021 InstallationDate: Installed on 2021-10-26 (6 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) InstalledPlugins: gnome-software-plugin-flatpak 40.4-1build1 gnome-software-plugin-snap40.4-1build1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 impish uec-images wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1949433 Title: The progress remains inactive and instaling software seems to be doing nothing. Using the cli works. Status in gnome-software package in Ubuntu: New Bug description: When trying to install hexchat there is no progress shown. It seems like installation does nothing. Using the cli works. I was using the flathub (flatpak) to install the aarch64 version of hexchat. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software 40.4-1build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 07:46:42 2021 InstallationDate: Installed on 2021-10-26 (6 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) InstalledPlugins: gnome-software-plugin-flatpak 40.4-1build1 gnome-software-plugin-snap40.4-1build1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1949433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Changed in: fedora Importance: Unknown => Undecided ** Changed in: fedora Status: Unknown => New ** Changed in: fedora Remote watch: Red Hat Bugzilla #1985251 => None ** Package changed: fedora => ubuntu-translations ** No longer affects: ubuntu-translations ** Bug watch removed: Red Hat Bugzilla #1985251 https://bugzilla.redhat.com/show_bug.cgi?id=1985251 ** Project changed: hplip => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Description changed: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing - in GTK. + in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Package changed: mutter (Fedora) => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: Red Hat Bugzilla #1516859 => None ** No longer affects: ubuntu ** Bug watch removed: Red Hat Bugzilla #1516859 https://bugzilla.redhat.com/show_bug.cgi?id=1516859 ** Project changed: xorg-server => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 => None ** No longer affects: ubuntu ** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
If we could then it would be nice to mitigate this by simply ensuring GTK in the gnome-shell process can find the Wayland server automatically instead of X11. Because if we don't find a blanket solution like that then we'll keep getting similar gnome-shell crash reports. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Description changed: + GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing + in GTK. + https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
Like the similar upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/1475, this appears to be caused by the intersection of: (a) GTK being used in the gnome-shell process (usually by extensions); and (b) The absence of an Xserver for GTK to connect to (Xwayland is only started on-demand now). It looks like one possible offender using GTK is gnome-shell-extension- appindicator. I'm not sure about the other extensions, and it's hard to tell with desktop-icons-ng which in theory uses GTK in a safe way (in a separate client process). -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
