[Desktop-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
best to file a separate bug anyway that said, I'm not sure if this should block the updates, since I wasn't able to reproduce it with a gpu of the same family -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
The DNSmasq change is in impish as well. Since we (intentionally) referenced but not closed the bug by the upload I'll have to tag that manually. ** Changed in: dnsmasq (Ubuntu Impish) Status: Triaged => Fix Released -- 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/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Fix Released Status in network-manager source package in Impish: Fix Released Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934607] Re: aptd ibelieve crashed
** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1934607 Title: aptd ibelieve crashed Status in Ubuntu: Incomplete Bug description: ??? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 4 15:23:22 2021 DistUpgraded: 2021-07-04 15:23:15,866 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:4f43] InstallationDate: Installed on 2021-07-04 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-148-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2021-07-04 (0 days ago) dmi.bios.date: 11/02/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: CO96510J.86A.5493.2006.1102.1728 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DQ965GF dmi.board.vendor: Intel Corporation dmi.board.version: AAD41676-400 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrCO96510J.86A.5493.2006.1102.1728:bd11/02/2006:svnBriteComputers:pn:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-400:cvn:ct2:cvr: dmi.sys.vendor: Brite Computers version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 4 15:12:47 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 input2.4G Wireless Mouse MOUSE, id 8 inputSONiX USB DEVICE KEYBOARD, id 9 inputSONiX USB DEVICE KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12327 vendor HWP xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934647] Re: Nvidia driver black screen at login.
Thanks for the bug report. Please be careful to only report one problem per bug. You can open multiple bugs. Let's make this bug about the black screen issue only. To debug that further we will need to see a system log from when the Nvidia driver was installed and you did NOT have "recovery nomodeset" kernel parameters. Please run: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt journalctl -b-3 > prevboot3.txt journalctl -b-4 > prevboot4.txt journalctl -b-5 > prevboot5.txt and attach the resulting text files. ** 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/1934647 Title: Nvidia driver black screen at login. Status in Ubuntu: Incomplete Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 10:54:41 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933413] Re: identification don't disppear
*** This bug is a duplicate of bug 1824874 *** https://bugs.launchpad.net/bugs/1824874 Thanks. That appears to be bug 1824874 which is fixed in Ubuntu 21.04 updates. Please install Ubuntu 21.04, as 20.10 reaches end-of-life this month. ** This bug has been marked a duplicate of bug 1824874 undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed] -- 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/1933413 Title: identification don't disppear Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I input the password of identification,the window don't disppear,which cover the manu bar of system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.84 Wed May 26 20:14:59 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 14:22:32 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.84, 5.8.0-57-generic, x86_64: installed nvidia, 460.84, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107GL [Quadro P1000] [10de:1cb1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P1000] [1028:11bc] InstallationDate: Installed on 2021-02-20 (123 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Precision 5820 Tower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=a9dfdda6-34c8-4611-855a-64de11bb2c68 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2019 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 002KVM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd09/23/2019:br1.13:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn002KVM:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 5820 Tower dmi.product.sku: 0738 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1933413] Re: identification don't disppear
At 2021-07-06 10:10:11, "Daniel van Vugt" <1933...@bugs.launchpad.net> wrote: >Thanks but that link is not downloadable. Maybe try giving the file a >simple name in English? > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1933413 > >Title: > identification don't disppear > >Status in gnome-shell package in Ubuntu: > Incomplete > >Bug description: > After I input the password of identification,the window don't > disppear,which cover the manu bar of system. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ubuntu15 > ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. > .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. > .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file. > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: > NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.84 Wed May 26 20:14:59 > UTC 2021 > GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) > ApportVersion: 2.20.11-0ubuntu50.7 > Architecture: amd64 > BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Jun 24 14:22:32 2021 > DistUpgraded: Fresh install > DistroCodename: groovy > DistroVariant: ubuntu > DkmsStatus: > nvidia, 460.84, 5.8.0-57-generic, x86_64: installed > nvidia, 460.84, 5.8.0-59-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > NVIDIA Corporation GP107GL [Quadro P1000] [10de:1cb1] (rev a1) (prog-if 00 > [VGA controller]) > Subsystem: Dell GP107GL [Quadro P1000] [1028:11bc] > InstallationDate: Installed on 2021-02-20 (123 days ago) > InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) > MachineType: Dell Inc. Precision 5820 Tower > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=a9dfdda6-34c8-4611-855a-64de11bb2c68 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/23/2019 > dmi.bios.release: 1.13 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.13.0 > dmi.board.name: 002KVM > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.13.0:bd09/23/2019:br1.13:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn002KVM:rvrA00:cvnDellInc.:ct3:cvr: > dmi.product.family: Precision > dmi.product.name: Precision 5820 Tower > dmi.product.sku: 0738 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200714-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933413/+subscriptions ** Attachment added: "2021-06-24 14-20-01.png" https://bugs.launchpad.net/bugs/1933413/+attachment/5509225/+files/2021-06-24%2014-20-01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933413 Title: identification don't disppear Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I input the password of identification,the window don't disppear,which cover the manu bar of system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64
[Desktop-packages] [Bug 1934589] Re: No log in button
Thanks for the bug report. That screenshot appears to show a custom theme, which is where the login button is meant to be defined. You need to report this bug to the creator of the theme you are using. ** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1934589 Title: No log in button Status in Ubuntu: Invalid Bug description: Can't believe You did it on purpose so reporting it as a bug. There is no log in button after entering the password on the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1934589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934564] Re: Ubuntu logo shows as forbidden/missing icon in About
** Summary changed: - Ubuntu logo shows as forbidden sign in About + Ubuntu logo shows as forbidden/missing icon in About -- 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/1934564 Title: Ubuntu logo shows as forbidden/missing icon in About Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Running the Ubuntu Impish Indri development branch, everything is up to date. For some reason, when I go to the About page, the forbidden sign is shown in place of what's supposed to be a Ubuntu logo. What is expected to happen: The Ubuntu logo shows correctly. What happened: The forbidden sign is shown in the place where it's supposed to show the Ubuntu logo. lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-control-center: gnome-control-center: Installed: 1:40.0-1ubuntu1 Candidate: 1:40.0-1ubuntu1 Version table: *** 1:40.0-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 15:48:49 2021 InstallationDate: Installed on 2021-02-02 (150 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) 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/1934564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934527] Re: Window switching with Alt-Tab stops working after a while
*** This bug is a duplicate of bug 1933996 *** https://bugs.launchpad.net/bugs/1933996 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1933996, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1933996 Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] -- 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/1934527 Title: Window switching with Alt-Tab stops working after a while Status in gnome-shell package in Ubuntu: Confirmed Bug description: On Ubuntu 21.04,since around 01 July 2021, Alt-Tab works as usual for a while after logging in, but then stops entirely (that is, it does nothing; the switcher overlay fails to appear, and switching between windows does not work). I made _no_ configuration change, and Alt-Tab continues to be configured in the keyboard shortcuts settings as usual. This has been described by other users here: https://askubuntu.com/questions/1349544/alttab-stops-working-after-a -while-in-ubuntu-21-04 There seems to be some possible connection to Thunderbird in particular, and the fact that in the left-hand-side launcher (?) / favourites of the Ubuntu desktop, the Thunderbird icon starts behaving strangely, e.g. does not show the open Thunderbird windows when clicking on it ... while other applications work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934564] Re: Ubuntu logo shows as forbidden sign in About
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/1934564 Title: Ubuntu logo shows as forbidden/missing icon in About Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Running the Ubuntu Impish Indri development branch, everything is up to date. For some reason, when I go to the About page, the forbidden sign is shown in place of what's supposed to be a Ubuntu logo. What is expected to happen: The Ubuntu logo shows correctly. What happened: The forbidden sign is shown in the place where it's supposed to show the Ubuntu logo. lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-control-center: gnome-control-center: Installed: 1:40.0-1ubuntu1 Candidate: 1:40.0-1ubuntu1 Version table: *** 1:40.0-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 15:48:49 2021 InstallationDate: Installed on 2021-02-02 (150 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) 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/1934564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933413] Re: identification don't disppear
Thanks but that link is not downloadable. Maybe try giving the file a simple name in English? -- 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/1933413 Title: identification don't disppear Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I input the password of identification,the window don't disppear,which cover the manu bar of system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.84 Wed May 26 20:14:59 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 14:22:32 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.84, 5.8.0-57-generic, x86_64: installed nvidia, 460.84, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107GL [Quadro P1000] [10de:1cb1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P1000] [1028:11bc] InstallationDate: Installed on 2021-02-20 (123 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Precision 5820 Tower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=a9dfdda6-34c8-4611-855a-64de11bb2c68 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2019 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 002KVM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd09/23/2019:br1.13:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn002KVM:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 5820 Tower dmi.product.sku: 0738 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
PPAs are not supported and you use them at your own risk. Please don't log bugs about packages from a PPA because we can't help with them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen
** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934688] Re: Tearing
** Package changed: xorg (Ubuntu) => xfce4 (Ubuntu) ** Tags added: tearing -- 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/1934688 Title: Tearing Status in xfce4 package in Ubuntu: New Bug description: The tearing image is present all over this t61. especially at scroll. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jul 5 20:50:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 7661V9Z PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=a3374028-cf0f-495f-9a41-121bf48bd983 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.release: 2.41 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 7661V9Z dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:br2.41:efr1.6:svnLENOVO:pn7661V9Z:pvrThinkPadT61:rvnLENOVO:rn7661V9Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 7661V9Z dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1934688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok
this is the dumptool in the windows. ** Attachment added: "RtHDDump_V236.zip" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+attachment/5509207/+files/RtHDDump_V236.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1918458 Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok Status in alsa-driver package in Ubuntu: Confirmed Bug description: Expect : sound from speaker Instead, obtain : no sound. Tried various configuration of /etc/modprobe.d/alsa-conf with : options snd-hda-intel model= and options snd-intel-dspcfg dsp_driver=3 or 1 and systematic reboot. Either I get dummy output, or I get proper output detection, alsamixer and pavucontrol seems 100% ok, but no sound comes from the speakers. I'm under a dualboot with Windows 10, BIOS fast boot disabled. Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thibauts 1522 F pulseaudio /dev/snd/pcmC0D0p: thibauts 1522 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 18:10:30 2021 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp Symptom_Jack: Grey Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.release: 1.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Guinness_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 5 dmi.product.name: Swift SF515-51T dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok
Does the speaker work normally in the windows? If yes, please run this dumptool to get the codec setting. Then in the linux, run 'sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef', and run 'alsa-info --no-upload' to get the alsa-info.txt. Please upload both generated log files. thx. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1918458 Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok Status in alsa-driver package in Ubuntu: Confirmed Bug description: Expect : sound from speaker Instead, obtain : no sound. Tried various configuration of /etc/modprobe.d/alsa-conf with : options snd-hda-intel model= and options snd-intel-dspcfg dsp_driver=3 or 1 and systematic reboot. Either I get dummy output, or I get proper output detection, alsamixer and pavucontrol seems 100% ok, but no sound comes from the speakers. I'm under a dualboot with Windows 10, BIOS fast boot disabled. Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thibauts 1522 F pulseaudio /dev/snd/pcmC0D0p: thibauts 1522 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 18:10:30 2021 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp Symptom_Jack: Grey Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.release: 1.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Guinness_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 5 dmi.product.name: Swift SF515-51T dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 105586] Re: mpg123 does not support large files
** Changed in: mpg123 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/105586 Title: mpg123 does not support large files Status in mpg123 package in Ubuntu: Fix Released Bug description: Binary package hint: mpg123-esd I was saving a MP3 stream to WAV file, and mpg123 (which is actually symlinked to mpg123-esd on my system) died when the output file hit 2GB in size. It appears that mpg123-esd needs to be recompiled with largefile support. Largefile support should be enabled for all programs. system:bhalla370: mpg123 -w poodles.wav -@ http://10.0.0.251:9100/listen.m3u High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3 version 0.60; written and copyright by Michael Hipp and others free software (LGPL/GPL) without any warranty but with best wishes Directory: http://10.0.0.251:9100/ Playing MPEG stream 1 of 1: listen ... Note: Junk at the beginning (0x024a09a3) MPEG 1.0 layer III, 64 kbits/s, 44100 Hz joint-stereo zsh: file size limit exceeded (core dumped) mpg123 -w poodles.wav -@ http://10.0.0.251:9100/listen.m3u system:bhalla384: ls -alt /opt/mp3/poodles.wav -rw-r--r--1 bhalla users2147483647 Apr 10 18:41 /opt/mp3/poodles.wav To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/105586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 297080] Re: mpg123 fails playing icecast streams
** Changed in: mpg123 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/297080 Title: mpg123 fails playing icecast streams Status in mpg123 package in Ubuntu: Fix Released Bug description: Binary package hint: mpg123 1) Ubuntu Release Information: Description: Ubuntu 8.10 Release: 8.10 2) Package Version: mpg123: Installed: 1.4.3-3 Candidate: 1.4.3-3 3) I expected to play a streaming icecast server through Asterisk which failed. I tested and narrowed the problem down to the version of mpg123 currently in stable. 4) Using the command "mpg123 -s http://twit.am/listen > test.mp3" I got the following output: -BEGIN OUTPUT High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3 version 1.4.3; written and copyright by Michael Hipp and others free software (LGPL/GPL) without any warranty but with best wishes Directory: http://twit.am/ Playing MPEG stream 1 of 1: listen ... ICY-NAME: TWiT After Hours (Pre-recorded) ICY-URL: http://twit.am/listen MPEG 1.0 layer III, 64 kbit/s, 44100 Hz mono ICY-META: StreamTitle='1918-11-11_WINSTONCHURCHILL_00 - Winston Churchill'; Note: Illegal Audio-MPEG-Header 0xcbb47d34 at offset 0x30ae. [parse.c:657] error: not attempting to resync... [mpg123.c:571] error: ...in decoding next frame: Lost track in the bytestream and did not attempt resync. (code 27) [0:01] Decoding of listen finished. -END OUTPUT This seems to be a known and fixed problem, see the news archive at http://www.mpg123.org/cgi-bin/news.cgi regarding both "resync is enabled again for ICY streams (the trouble in the past was due to a reader bug, not the streams)" and "workaround for frames that fail decoding (bad frame body, missing bit reservoir): fill up with silence" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/297080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632268] Re: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
*** This bug is a duplicate of bug 1572167 *** https://bugs.launchpad.net/bugs/1572167 ** This bug has been marked a duplicate of bug 1572167 package libavcodec-ffmpeg-extra56:amd64 7:2.7.6-0ubuntu0.15.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1632268 Title: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mpg123 package in Ubuntu: Confirmed Bug description: not possible to deinstall that package by any means ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmpg123-0:i386 1.22.4-1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 11 10:45:19 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libmpg123-0:i386:1.22.4-1 Unpacking linux-libc-dev:amd64 (4.4.0-42.62) over (4.4.0-38.57) ... dpkg: error processing package libmpg123-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 2016-07-12 (90 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: mpg123 Title: package libmpg123-0:i386 1.22.4-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/mpg123/+bug/1632268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632268] Re: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
*** This bug is a duplicate of bug 1572167 *** https://bugs.launchpad.net/bugs/1572167 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mpg123 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1632268 Title: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mpg123 package in Ubuntu: Confirmed Bug description: not possible to deinstall that package by any means ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmpg123-0:i386 1.22.4-1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 11 10:45:19 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libmpg123-0:i386:1.22.4-1 Unpacking linux-libc-dev:amd64 (4.4.0-42.62) over (4.4.0-38.57) ... dpkg: error processing package libmpg123-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 2016-07-12 (90 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: mpg123 Title: package libmpg123-0:i386 1.22.4-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/mpg123/+bug/1632268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808624] Re: package libmpg123-0:amd64 1.22.4-1 failed to install/upgrade: package libmpg123-0:amd64 is not ready for configuration cannot configure (current status 'half-insta
*** This bug is a duplicate of bug 1572167 *** https://bugs.launchpad.net/bugs/1572167 ** This bug has been marked a duplicate of bug 1632268 package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ** This bug is no longer a duplicate of bug 1632268 package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ** This bug has been marked a duplicate of bug 1572167 package libavcodec-ffmpeg-extra56:amd64 7:2.7.6-0ubuntu0.15.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1808624 Title: package libmpg123-0:amd64 1.22.4-1 failed to install/upgrade: package libmpg123-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in mpg123 package in Ubuntu: New Bug description: Trying to fix grub but the operation fails ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmpg123-0:amd64 1.22.4-1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Dec 15 15:39:44 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2018-12-15 15:39:25 Commandline: apt-get install -y boot-repair Requested-By: nitish (1000) Install: python-gi:amd64 (3.20.0-0ubuntu1, automatic), pastebinit:amd64 (1.5-1, automatic), gawk:amd64 (1:4.1.3+dfsg-0.1, automatic), boot-sav:amd64 (4ppa65, automatic), boot-sav-extra:amd64 (4ppa65, automatic), glade2script:amd64 (3.2.3~ppa4, automatic), libsigsegv2:amd64 (2.10-4, automatic), boot-repair:amd64 (4ppa65) DuplicateSignature: package:libmpg123-0:amd64:1.22.4-1 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libmpg123-0:amd64 (--configure): package libmpg123-0:amd64 is not ready for configuration ErrorMessage: package libmpg123-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-03-29 (260 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: mpg123 Title: package libmpg123-0:amd64 1.22.4-1 failed to install/upgrade: package libmpg123-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1808624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934697] [NEW] Default keyring password keeps resetting if set to empty
Public bug reported: My system (on which I'm the only user) has full-disk encryption turned on, and I thus have the same password for both the encryption password and my user account. Likewise, I have automatic login turned on so I don't have to type my password twice, as it would be quite redundant. With automatic login turned on, I thus changed my password for my default keyring to be nothing, as one, the security of full-disk encryption solves all of the needs that a keyring password would for me, and two, I'd like to not have to enter my keyring password every time I boot. Issue is that for some strange reason the keyring password miraculously keeps resetting to the password of my user account. I don't know why, I don't know how, but it's been happening for at least the past couple of months, awaiting me to make an Ubuntu One account so I could report the issue. The machine that's affected has been wiped at least three times over the past few months (due to various reasons), and the issue has also happened on another machine I was temporarily using at one point. --- OS Version: Ubuntu 20.04.2 LTS Package Version: 3.36-1 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Description changed: My system (on which I'm the only user) has full-disk encryption turned on, and I thus have the same password for both the encryption password and my user account. Likewise, I have automatic login turned on so I don't have to type my password twice, as it would be quite redundant. With automatic login turned on, I thus changed my password for my - default keyring to be nothing, as the security of full-disk encryption - solves all of the needs that a keyring password would for me. + default keyring to be nothing, as one, the security of full-disk + encryption solves all of the needs that a keyring password would for me, + and two, I'd like to not have to enter my keyring password every time I + boot. Issue is that for some strange reason the keyring password miraculously keeps resetting to the password of my user account. I don't know why, I don't know how, but it's been happening for at least the past couple of months, awaiting me to make an Ubuntu One account so I could report the issue. The machine that's affected has been wiped at least three times over the past few months (due to various reasons), and the issue has also happened on another machine I was temporarily using at one point. --- OS Version: Ubuntu 20.04.2 LTS Package Version: 3.36-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1934697 Title: Default keyring password keeps resetting if set to empty Status in seahorse package in Ubuntu: New Bug description: My system (on which I'm the only user) has full-disk encryption turned on, and I thus have the same password for both the encryption password and my user account. Likewise, I have automatic login turned on so I don't have to type my password twice, as it would be quite redundant. With automatic login turned on, I thus changed my password for my default keyring to be nothing, as one, the security of full-disk encryption solves all of the needs that a keyring password would for me, and two, I'd like to not have to enter my keyring password every time I boot. Issue is that for some strange reason the keyring password miraculously keeps resetting to the password of my user account. I don't know why, I don't know how, but it's been happening for at least the past couple of months, awaiting me to make an Ubuntu One account so I could report the issue. The machine that's affected has been wiped at least three times over the past few months (due to various reasons), and the issue has also happened on another machine I was temporarily using at one point. --- OS Version: Ubuntu 20.04.2 LTS Package Version: 3.36-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1934697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713021] Re: Minimize/unminimize animations do nothing for the first 100ms or so
** Changed in: gnome-shell Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713021 Title: Minimize/unminimize animations do nothing for the first 100ms or so Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Triaged Bug description: gnome-shell's minimize/unminimize animations do nothing for almost the first 100ms or so. They look slow because the easeInExpo curve does nothing for most of the first half of the animation time: https://developer.gnome.org/clutter/stable/ClutterTimeline.html#ClutterAnimationMode A much more responsive, natural and fluid curve with the same overall duration would be to use an easeOut* curve. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1713021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713931] Re: Shell ignores all search results if not all metadata available
** Changed in: gnome-shell Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713931 Title: Shell ignores all search results if not all metadata available Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using current artful, g-s 3.25.91 and snapd-glib 1.18, looking for "vlc" or "gimp" in the gnome-shell overview returns a "no result", after deleting the snapd plugin and restarting g-s it lists them fine bug #1713929 is about the fact that there are no snap listed, this bug about the fact that one plugin can/do block others from returning results To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1713931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720838] Re: Nvidia gnome control center scale gets overridden on reboot
** Changed in: mutter Status: Confirmed => Expired -- 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/1720838 Title: Nvidia gnome control center scale gets overridden on reboot Status in Mutter: Expired Status in mutter package in Ubuntu: Won't Fix Bug description: When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my session. If I reboot then the scale is reset back to 100% but the value on the control center "displays" section shows "200%". To work around it I save the scale to 100% then save it back to 200%. After rebooting I have to do this every time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.82 Wed Jul 19 21:16:49 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1) ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 2 11:34:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230] InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET70W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 2 11:32:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1720838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735969] Re: Windows move to background
** Changed in: gnome-shell Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1735969 Title: Windows move to background Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Ubuntu 17.10 mutter 3.26.2-0ubuntu0.1 Open three windows, one using the entire left half of the screen, one using the entire right half of the screen, and one small window that you put (entirely) in front of the large window on the left side. If you focus the window on the right side, the small window is put behind the large window on the left side. I expect the small window to remain in front of the large window on the left side since it is not affected by the window on the right side. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1735969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717923] Re: GNOME: Unable to log in: invalid monitor configuration, Logical monitors not adjecent
** Changed in: mutter Status: Confirmed => Expired -- 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/1717923 Title: GNOME: Unable to log in: invalid monitor configuration, Logical monitors not adjecent Status in Mutter: Expired Status in mutter package in Ubuntu: Incomplete Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". journal excerpt === Aug 22 21:12:31 gnome-shell[23153]: Ignoring invalid monitor configuration for LVDS1:LGD:0x02f8:0x, VGA1:???:0x:0x: Logical monitors not adjecent Aug 22 21:12:32 kernel: gnome-shell[23153]: segfault at 8 ip 7f5a7c06ebd0 sp 7ffdc85ce7c8 error 4 in libmutter-1.so.0.0.0[7f5a7c015000+13e000] Workaround == Move or remove the hidden file ~/.config/monitors.xml to be able to log in to GNOME Shell. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1717923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
** Changed in: mutter Status: Confirmed => Expired -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Mutter: Expired Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses
** Changed in: gnome-shell Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/968213 Title: Too many icons in Gnome Shell Activities Overview require ellipses Status in GNOME Shell: Expired Status in One Hundred Papercuts: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Several apps in the default Ubuntu 17.04 or 17.10 install have Ellipses when shown in GNOME Shell's Activities Overview. This was made worse by switching GNOME Shell to use the Ubuntu font because the Ubuntu font is a bit wider than GNOME's default Cantarell font so some apps that didn't require ellipses in 17.04 require them now in 17.10 Alpha. The upstream GNOME bug proposes that apps names be allowed to use 2 lines. This is similar to what the Settings app (gnome-control-center) does. This is also really bad for languages that use more characters than English. Original Bug Title -- Gnome Shell Activities Overview should show full names on mouse hover Original Bug Report --- The title says it all --- especially when choosing recent documents, if they start with the same say 12 or 14 letters, it's impossible to differentiate them (see attached screenshot). When mouse is hovering an icon, the full name of the application/document should be shown. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/968213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713931]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/1713931 Title: Shell ignores all search results if not all metadata available Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using current artful, g-s 3.25.91 and snapd-glib 1.18, looking for "vlc" or "gimp" in the gnome-shell overview returns a "no result", after deleting the snapd plugin and restarting g-s it lists them fine bug #1713929 is about the fact that there are no snap listed, this bug about the fact that one plugin can/do block others from returning results To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1713931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720838]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help. -- 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/1720838 Title: Nvidia gnome control center scale gets overridden on reboot Status in Mutter: Expired Status in mutter package in Ubuntu: Won't Fix Bug description: When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my session. If I reboot then the scale is reset back to 100% but the value on the control center "displays" section shows "200%". To work around it I save the scale to 100% then save it back to 200%. After rebooting I have to do this every time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.82 Wed Jul 19 21:16:49 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1) ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 2 11:34:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230] InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET70W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 2 11:32:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1720838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717923]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help. -- 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/1717923 Title: GNOME: Unable to log in: invalid monitor configuration, Logical monitors not adjecent Status in Mutter: Expired Status in mutter package in Ubuntu: Incomplete Bug description: After updating to gnome 3.25.91, and now testing in 3.26, I cannot login to wayland session, either ubuntu o vanilla gnome. Xorg session works fine, and wayland session worked fine before updating. The only error I can detect in the logs is "Unrecoverable failure in required component org.gnome.Shell.desktop". journal excerpt === Aug 22 21:12:31 gnome-shell[23153]: Ignoring invalid monitor configuration for LVDS1:LGD:0x02f8:0x, VGA1:???:0x:0x: Logical monitors not adjecent Aug 22 21:12:32 kernel: gnome-shell[23153]: segfault at 8 ip 7f5a7c06ebd0 sp 7ffdc85ce7c8 error 4 in libmutter-1.so.0.0.0[7f5a7c015000+13e000] Workaround == Move or remove the hidden file ~/.config/monitors.xml to be able to log in to GNOME Shell. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 09:44:01 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-27 (52 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1717923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713021]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/1713021 Title: Minimize/unminimize animations do nothing for the first 100ms or so Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Triaged Bug description: gnome-shell's minimize/unminimize animations do nothing for almost the first 100ms or so. They look slow because the easeInExpo curve does nothing for most of the first half of the animation time: https://developer.gnome.org/clutter/stable/ClutterTimeline.html#ClutterAnimationMode A much more responsive, natural and fluid curve with the same overall duration would be to use an easeOut* curve. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1713021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735969]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/1735969 Title: Windows move to background Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Ubuntu 17.10 mutter 3.26.2-0ubuntu0.1 Open three windows, one using the entire left half of the screen, one using the entire right half of the screen, and one small window that you put (entirely) in front of the large window on the left side. If you focus the window on the right side, the small window is put behind the large window on the left side. I expect the small window to remain in front of the large window on the left side since it is not affected by the window on the right side. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1735969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692394]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/1692394 Title: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=772287 When I press the volume keys on my keyboard the shell displays an overlay showing the volume level. Normally this overlay is stationary, but sometimes when adjusting the volume, the overlay shifts slightly a pixel or two left or right. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Mon May 22 11:02:57 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (18 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1692394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys
** Changed in: gnome-shell Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1692394 Title: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=772287 When I press the volume keys on my keyboard the shell displays an overlay showing the volume level. Normally this overlay is stationary, but sometimes when adjusting the volume, the overlay shifts slightly a pixel or two left or right. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Mon May 22 11:02:57 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (18 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1692394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 968213]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/968213 Title: Too many icons in Gnome Shell Activities Overview require ellipses Status in GNOME Shell: Expired Status in One Hundred Papercuts: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Several apps in the default Ubuntu 17.04 or 17.10 install have Ellipses when shown in GNOME Shell's Activities Overview. This was made worse by switching GNOME Shell to use the Ubuntu font because the Ubuntu font is a bit wider than GNOME's default Cantarell font so some apps that didn't require ellipses in 17.04 require them now in 17.10 Alpha. The upstream GNOME bug proposes that apps names be allowed to use 2 lines. This is similar to what the Settings app (gnome-control-center) does. This is also really bad for languages that use more characters than English. Original Bug Title -- Gnome Shell Activities Overview should show full names on mouse hover Original Bug Report --- The title says it all --- especially when choosing recent documents, if they start with the same say 12 or 14 letters, it's impossible to differentiate them (see attached screenshot). When mouse is hovering an icon, the full name of the application/document should be shown. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/968213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help. -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Mutter: Expired Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828638] Re: Support sane option --scan-area on GUI applications
** Description changed: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 - See Also: https://gitlab.gnome.org/GNOME/simple-scan/issues/103 + See also: + https://gitlab.gnome.org/GNOME/simple-scan/issues/103 + https://gitlab.com/sane-project/frontend/xsane/-/issues/1 + https://sourceforge.net/p/gscan2pdf/bugs/389/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1828638 Title: Support sane option --scan-area on GUI applications Status in xsane: New Status in simple-scan package in Ubuntu: New Status in xsane package in Ubuntu: New Bug description: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 See also: https://gitlab.gnome.org/GNOME/simple-scan/issues/103 https://gitlab.com/sane-project/frontend/xsane/-/issues/1 https://sourceforge.net/p/gscan2pdf/bugs/389/ To manage notifications about this bug go to: https://bugs.launchpad.net/xsane/+bug/1828638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1918458 Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok Status in alsa-driver package in Ubuntu: Confirmed Bug description: Expect : sound from speaker Instead, obtain : no sound. Tried various configuration of /etc/modprobe.d/alsa-conf with : options snd-hda-intel model= and options snd-intel-dspcfg dsp_driver=3 or 1 and systematic reboot. Either I get dummy output, or I get proper output detection, alsamixer and pavucontrol seems 100% ok, but no sound comes from the speakers. I'm under a dualboot with Windows 10, BIOS fast boot disabled. Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thibauts 1522 F pulseaudio /dev/snd/pcmC0D0p: thibauts 1522 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 18:10:30 2021 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp Symptom_Jack: Grey Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.release: 1.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Guinness_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 5 dmi.product.name: Swift SF515-51T dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875056] Re: locate-pointer (w/ ctrl key) not working
AFAICT, my left CTRL key is working but I won't be able to enable this feature. Actually looking at Thomas's screenshot I've noticed that the dconf setting apparently has been moved from settings-daemon/mouse to desktop/interface, what explains that I wouldn't found the key definition in the schemas.xml file even in the deprecated-keys section. But setting the key true in the new config won't enable either. I can also notice that toggling the key value in dconf won't change the the value in the "official" Settings/mouseand keyboard section or even in the Tweak app. And BTW the new dconf description reads that the pointer location will be be triggered by pressing *any* key (?) - as can be seen in Thomas's screenshot. Seems like the gnome shell is still expecting for the old key activation. I've tried to add the "locate pointer" in the schemas.xml's settings-daemon/interface but it won't show up aon dconf and won't activate anything either (even after reboot). Would there be a way to redirect the key from desktop/interface to settings-daemon/mouse so that the shell could grab it ? I'm on 21.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1875056 Title: locate-pointer (w/ ctrl key) not working Status in gnome-shell package in Ubuntu: Confirmed Bug description: It was working for an hour and then stopped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 19:09:37 2020 InstallationDate: Installed on 2020-03-31 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) SourcePackage: gnome-settings-daemon 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/1875056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767505] Re: Rhythmbox Radio - Internal Data Stream Error
Hi all I installed it from https://flathub.org/apps/details/org.gnome.Rhythmbox3 via flatpak and the problem is gone I have ubuntu 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1767505 Title: Rhythmbox Radio - Internal Data Stream Error Status in rhythmbox package in Ubuntu: Expired Bug description: When trying to play any radio station, I get a dialog that states after about 20 seconds of playing: Couldn't start playback Internal data stream error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934688] [NEW] Tearing
Public bug reported: The tearing image is present all over this t61. especially at scroll. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jul 5 20:50:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 7661V9Z PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=a3374028-cf0f-495f-9a41-121bf48bd983 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.release: 2.41 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 7661V9Z dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:br2.41:efr1.6:svnLENOVO:pn7661V9Z:pvrThinkPadT61:rvnLENOVO:rn7661V9Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 7661V9Z dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1934688 Title: Tearing Status in xorg package in Ubuntu: New Bug description: The tearing image is present all over this t61. especially at scroll. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Mon Jul 5 20:50:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 7661V9Z PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=a3374028-cf0f-495f-9a41-121bf48bd983 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.release: 2.41 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 7661V9Z dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:br2.41:efr1.6:svnLENOVO:pn7661V9Z:pvrThinkPadT61:rvnLENOVO:rn7661V9Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 7661V9Z dmi.product.version: ThinkPad T61
[Desktop-packages] [Bug 1881712] Re: gnome-software says connection is metered while is not
Same issue on 21.04 -- 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/1881712 Title: gnome-software says connection is metered while is not Status in gnome-software package in Ubuntu: Confirmed Bug description: I open gnome-software and i see a message 'automatic updates paused' for my connection is metered but my connection is NOT metered. see attached screenshot. corrado@corrado-HP-x4-gg-0525ebook-PC:~$ inxi -Fx System:Host: corrado-HP-x4-gg-0525ebook-PC Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 10.2 Wh condition: 16.4/16.4 Wh (100%) model: 13-42 OA03031 status: Charging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 1696 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1697 2: 1696 3: 1696 4: 1697 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Suyin type: USB driver: uvcvideo bus ID: 1-1.5:3 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 20.0.7 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-26-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 689.33 GiB used: 6.76 GiB (1.0%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB Partition: ID-1: / size: 31.25 GiB used: 6.75 GiB (21.6%) fs: ext4 dev: /dev/sdb5 Swap: ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 39.0 C mobo: 39.0 C Fan Speeds (RPM): N/A Info: Processes: 236 Uptime: 49m Memory: 3.78 GiB used: 1.39 GiB (36.7%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.00 corrado@corrado-HP-x4-gg-0525ebook-PC:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 08:57:28 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-05-26 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200525) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-21 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 Package: gnome-software 3.36.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-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-software/+bug/1881712/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas
installed too the last vmoon release... same problem with last updates mesa-va-drivers: Installed: 21.1.2-1 Candidate: 21.1.2-1 Version table: *** 21.1.2-1 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status mesa-vulkan-drivers: Installed: 21.1.2-1 Candidate: 21.1.2-1 Version table: *** 21.1.2-1 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ** Attachment added: "The moon with unreadable characters" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867581/+attachment/5509169/+files/Screenshot%20from%202021-07-05%2020-17-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867581 Title: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas Status in mesa package in Ubuntu: Incomplete Bug description: ubuntu-bug mesa does not work, i don't see a package named mesa On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from https://sourceforge.net/projects/virtualmoon/ shows the characters reduced to small rectangles and the image of the moon is empty. On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems. The problem happens with both sessions X11 and Wayland. I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291 and you may see the result of the malfunction on this page but the problem seems due to mesa 20. I have an intel CPU and Graphic unit corrado@corrado-x5-ff-0309:~$ inxi -Gxx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0 direct render: Yes corrado@corrado-x5-ff-0309:~$ I asked a question for this problem: https://answers.launchpad.net/ubuntu/+question/689328 so now I'm opening this problem if you suggest me the package name to be used opening the problem with ubuntu-bug i will open a new bug --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2020-03-09 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: mesa (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Tags: focal ubuntu single-occurrence reproducible Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867581/+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 1925320] Re: Backport packages for 20.04.3 HWE stack
I've got updates for mesa 21.0.1-2 July 1st and it was upgrade from 20.2.6 which worked without such problems. Then July 2nd there was upgrade to 21.0.3-0. I'm not sure if the problems started with 21.0.1. Also there are programs that work without graphical glitches. Suprisingly Firefox doesn't have problems but my main webbrowser Vivaldi does. Also I was able to watch Amazon Prime using ElectronPlayer the videos display without glitches however the menus of that program do have glitches. Also I've checked LiveCD image of Impish and there wasn't any problems with that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934684] [NEW] Can't Move, Resize or Maximize Firefox Anymore
Public bug reported: Since the most recent Firefox update, I've lost the ability to control Firefox's window in Kubuntu 20.04. Upon launch, it launches in a un-maximized state where I cannot drag it by its title bar. I have to hold down the alt-key an click the window to move it. Hovering the mouse-cursor on any corner of window doesn't produce any indication that you can resize the Firefox window and "clicking an dragging corners" does nothing (which should resize instead). The maximize button is completely missing from the title bar of Firefox and the superKey+pageUp doesn't maximize the window either. I realize that I'm pointing out multiple things in one post, but I suspect all of these things are stemming from the same source problem, because all these problems started happening after the latest Firefox update in Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 89.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lonnie 1629 F pulseaudio /dev/snd/controlC0: lonnie 1629 F pulseaudio BuildID: 20210622155641 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Mon Jul 5 11:28:01 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-26 (435 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=89.0.2/20210622155641 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RSA5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Bonobo WS dmi.board.vendor: System76 dmi.board.version: bonw13 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Bonobo WS dmi.product.sku: Not Applicable dmi.product.version: bonw13 dmi.sys.vendor: System76 ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1934684 Title: Can't Move, Resize or Maximize Firefox Anymore Status in firefox package in Ubuntu: New Bug description: Since the most recent Firefox update, I've lost the ability to control Firefox's window in Kubuntu 20.04. Upon launch, it launches in a un-maximized state where I cannot drag it by its title bar. I have to hold down the alt-key an click the window to move it. Hovering the mouse-cursor on any corner of window doesn't produce any indication that you can resize the Firefox window and "clicking an dragging corners" does nothing (which should resize instead). The maximize button is completely missing from the title bar of Firefox and the superKey+pageUp doesn't maximize the window either. I realize that I'm pointing out multiple things in one post, but I suspect all of these things are stemming from the same source problem, because all these problems started happening after the latest Firefox update in Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 89.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18
[Desktop-packages] [Bug 462419] Re: evince apparmor profile prevents movies from opening
By the end of the previous comment I had experienced a weird bug. But I decided to post it here as a separate comment because this is still relevant to this thread. I resolved the issues by: 1. changing the default player 2. opening a PDF document that contains a link to a local video 3. clicking the link to the video (and failing to open) 4. closing evince and opening the same document again 5. clicking the link to the video again (and succeeding this time) I had to reproduce those steps for both totem and for vlc, ... but now, everything just works! After that initial hurdle, changing default players results in opening the correct default video player. I'm not really sure what happened, but the issue just fixed itself. There are still some odd messages in the kernel log (see attached file). I don't know if this is reproducible elsewhere, or if this bug should be marked as resolved or not, as I'm way past due to do a clean install of the newest Ubuntu: rolandog@computer:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 rolandog@computer:~$ apt-cache policy evince evince: Installed: 3.38.0-1 Candidate: 3.38.0-1 Version table: *** 3.38.0-1 500 500 http://nl.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I hope this helps out someone getting unexpected behavior. ** Attachment added: "rolandog-apparmor-kernel-audit-2.txt" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+attachment/5509157/+files/rolandog-apparmor-kernel-audit-2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/462419 Title: evince apparmor profile prevents movies from opening Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: Binary package hint: evince Trying to open a movie with vlc or totem from within evince. I get the error: "Failed to execute child process vlc (Permission denied)". The same with totem. I have been looking at all the "apparmor prevents" bugs that have been reported of late. DVI printing, chromium, etc... the package maintainers' strategy has been to add an exceptions to the apparmor profile as the bugs come in. May I comment that this is a ludicrous situation? There are going to be numerous helper applications that people might want to use within a PDF file... why is apparmor blocking them all? [22:47][kirkwood][~] > lsb_release -rd Description:Ubuntu 9.10 Release:9.10 [22:48][kirkwood][~] > apt-cache policy evince evince: Installed: 2.28.1-0ubuntu1 Candidate: 2.28.1-0ubuntu1 Version table: *** 2.28.1-0ubuntu1 0 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status Expected to happen: movie opens when clicked on What happens instead: help application (totem/vlc) prevented from running by apparmor Reproducible: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 462419] Re: evince apparmor profile prevents movies from opening
Hello everyone. I've read the whole thread and I am experiencing a related bug. My specific scenario is that I'm creating a PDF (by exporting from Emacs / Org-Mode) that contains a link to a local video. It may have been a recent change in an AppArmor that has resulted in the videos not opening anymore (or maybe a security patch?), but I'm not able to open either mp4 or webm videos like I could with mpv. I read the /etc/apparmor.d/abstractions/evince file, and added the following to the /etc/apparmor.d/local/usr.bin.evince file: # vim:syntax=apparmor # # abstraction used by evince binaries # # supported archivers /usr/bin/mpv ixr, /usr/bin/totem ixr, /usr/bin/vlc ixr, After performing: rolandog@computer:~$ sudo apparmor_parser --reload /etc/apparmor.d/usr.bin.evince I get the following error: profile /usr/bin/evince: has merged rule /usr/bin/totem with conflicting x modifiers ERROR merging rules for profile /usr/bin/evince, failed to load Playback with mpv (the player I had set as default) still doesn't work (is blocked by AppArmor), and, after running the following command, I get the messages shown in the attached file: rolandog@computer:~$ grep audit /var/log/kern.log After removing the totem line I get a similar error, but for vlc. After removing both the totem line and the vlc line, I don't get an error (and I can launch mpv (the default I had set). However, I'm torn because this worked for me, but there may be others that may have similar use-cases to mine that would prefer other players. ** Attachment added: "Semi-anonymized matching audit kernel logs from rolandog" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+attachment/5509133/+files/rolandog-apparmor-kernel-audit.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/462419 Title: evince apparmor profile prevents movies from opening Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: Binary package hint: evince Trying to open a movie with vlc or totem from within evince. I get the error: "Failed to execute child process vlc (Permission denied)". The same with totem. I have been looking at all the "apparmor prevents" bugs that have been reported of late. DVI printing, chromium, etc... the package maintainers' strategy has been to add an exceptions to the apparmor profile as the bugs come in. May I comment that this is a ludicrous situation? There are going to be numerous helper applications that people might want to use within a PDF file... why is apparmor blocking them all? [22:47][kirkwood][~] > lsb_release -rd Description:Ubuntu 9.10 Release:9.10 [22:48][kirkwood][~] > apt-cache policy evince evince: Installed: 2.28.1-0ubuntu1 Candidate: 2.28.1-0ubuntu1 Version table: *** 2.28.1-0ubuntu1 0 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status Expected to happen: movie opens when clicked on What happens instead: help application (totem/vlc) prevented from running by apparmor Reproducible: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931264] Re: Random, unsolicited (no mouse or keyboard input), scrolling.
Firefox and Opera browsers. I've noticed it in NANO and from the GUI Software list also. -- 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/1931264 Title: Random, unsolicited (no mouse or keyboard input), scrolling. Status in firefox package in Ubuntu: Incomplete Bug description: Web browsers (and I've also noticed this in the text editor) will randomly scroll up and/or down. This occurs without mouse movement or keyboard input. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 89.0+build2-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tscs-admin 137848 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Jun 8 10:30:40 2021 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-02 (676 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.1.1 dev eno1 proto static metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.222 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-07-25 (318 days ago) dmi.bios.date: 07/05/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0125.2011.0705.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-209 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0125.2011.0705.1517:bd07/05/2011:svnSeneca:pnpro270296:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr: dmi.product.name: pro270296 dmi.sys.vendor: Seneca To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
This bug was fixed in the package network-manager - 1.30.0-1ubuntu4 --- network-manager (1.30.0-1ubuntu4) impish; urgency=medium * d/t/nm.py: adapt to changes dnsmasq behavior (LP: #1894619) -- Christian Ehrhardt Fri, 02 Jul 2021 11:13:46 +0200 ** Changed in: network-manager (Ubuntu Impish) Status: New => Fix Released -- 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/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Fix Released Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: Fix Released Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
** Changed in: gnome-shell Status: Confirmed => Expired -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Expired Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]
** Changed in: gnome-shell-legacy-bugs Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1734095 Title: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed] Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software and Updates app and attempt to change anything it does not popup the authorization dialog and will not let changes through. In sylog I see Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of begin_modal failed Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed to show modal dialog. Dismissing authentication request for action-id com.ubuntu.softwareproperties.applychanges cookie 1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740 Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: ERROR:root:Authentication canceled, changes have not been saved Before the upgrade it was ok. Other apps that require authorisation function as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 23 10:07:44 2017 DisplayManager: lightdm InstallationDate: Installed on 2014-10-21 (1128 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Expired Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734095]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help. -- 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/1734095 Title: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed] Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software and Updates app and attempt to change anything it does not popup the authorization dialog and will not let changes through. In sylog I see Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of begin_modal failed Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed to show modal dialog. Dismissing authentication request for action-id com.ubuntu.softwareproperties.applychanges cookie 1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740 Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: ERROR:root:Authentication canceled, changes have not been saved Before the upgrade it was ok. Other apps that require authorisation function as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 23 10:07:44 2017 DisplayManager: lightdm InstallationDate: Installed on 2014-10-21 (1128 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
@ubuntu-sru-bot
regressions triggered by reprepro have been retried, and have been now
cleared.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Committed
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Committed
Status in reprepro source package in Groovy:
Fix Committed
Status in reprepro source package in Hirsute:
Fix Committed
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip,
[Desktop-packages] [Bug 1863763] Re: gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows
20.0.4 from ubuntu 20.04 was backported to 18.04 roughly a year ago
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1863763
Title:
gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows
Status in mesa package in Ubuntu:
Fix Released
Bug description:
There is a bug in mesa version 19.2.x where x>2, manifesting itself as
window contents in large windows on 4K display renders with an
incorrect vertical offset, making the desktop largely unusable for
some customers.
The bug is fixed in latest 19.3 series and 20.0 rc series, but since
Ubuntu 18.04.1 still uses 19.2 series, a manual backport is needed.
Please cherry-pick mesa master commit
451cf228d53ba8f51beb3dcf04370e126fb7ccb6 ("svga: Fix banded DMA
upload") to fix the issue, alternatively switch to mesa 19.3 series.
Thanks,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
Uname: Linux 5.5.0+ x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 18 05:53:02 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-02-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0+
root=UUID=3fa8a33e-bea4-42a8-9e5b-6a0b922e77d9 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/30/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863763/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
See reprepro verification comments at
https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1933363
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done verification-done-focal
verification-done-groovy verification-done-hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
Fix Committed
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in reprepro source package in Focal:
Fix Committed
Status in reprepro source package in Groovy:
Fix Committed
Status in reprepro source package in Hirsute:
Fix Committed
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
[Desktop-packages] [Bug 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
fixed in 20.04 and up ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1865536 Title: OBS consumes all memory, fixed in upstream Mesa Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas
does it happen with current updates? ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867581 Title: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas Status in mesa package in Ubuntu: Incomplete Bug description: ubuntu-bug mesa does not work, i don't see a package named mesa On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from https://sourceforge.net/projects/virtualmoon/ shows the characters reduced to small rectangles and the image of the moon is empty. On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems. The problem happens with both sessions X11 and Wayland. I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291 and you may see the result of the malfunction on this page but the problem seems due to mesa 20. I have an intel CPU and Graphic unit corrado@corrado-x5-ff-0309:~$ inxi -Gxx Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0 direct render: Yes corrado@corrado-x5-ff-0309:~$ I asked a question for this problem: https://answers.launchpad.net/ubuntu/+question/689328 so now I'm opening this problem if you suggest me the package name to be used opening the problem with ubuntu-bug i will open a new bug --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2020-03-09 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: mesa (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Tags: focal ubuntu single-occurrence reproducible Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
Yes it works with the MESA packages from the ubunturepos. The problem occurs after adding the kisak mesa fresh ppa and upgrading to the latest stable MESA release. It only happens when Wayland is used. I always use this otherwise great ppa to keep my MESA drivers up to date. Sadly the packages in the ubuntu are often to old if you use your system for gaming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835459] Re: libgl1-mesa-glx errors
that's just chrome complaining that it can't use hw acceleration (which is expected for a remote connection) ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835459 Title: libgl1-mesa-glx errors Status in mesa package in Ubuntu: Invalid Bug description: I have a VPS with Ubuntu 18.04 (implementation of pure software, Digital Ocean) and I connect through Windows 10 with an X server, Xming and I run Google-Chrome Remote. It works well and opens the Chrome remote control on my Windows, although it is quite slow, but it works. However, it throws some GPU and OpenGL errors that I can not solve. I have reported and are quite frequent errors, as recommended, I reinstalled the mesa-utils and libgl1-glx-mesa packages, and errors persist. Attached capture of these. I have installed (bionic): libgl1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-data libglvnd0 liglx-mesa0 libglx0 dbus dbus-x11 I have searched for help in the stackoverflow forums without any success. OpenGL Propierties: ~$ glxinfo | grep "OpenGL versión" libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext Major opcode of failed request: 148 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 Current serial number in output stream: 45 And the characteristics of the graphics of my VPS: ~ $ lspci -vk 00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine Physical Slot: 2 Flags: fast devsel, IRQ 10 Memory at f800 (32-bit, non-prefetchable) [size = 64M] Memory at fc00 (32-bit, non-prefetchable) [size = 16M] Memory at fd05 (32-bit, non-prefetchable) [size = 8K] I / O ports at c0a0 [size = 32] Expansion ROM at 000c [disabled] [size = 128K] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
** Changed in: linux-oem-osp1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: oem-priority Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688200] Re: libgles2-mesa-dev breaks gstreamer-imx video acceleration (14.04 armhf)
that doesn't sound right, a -dev package can't break it, sounds like you were missing some updates or getting a mixed set of them anyway, it's been four years, probably not an issue anymore if it ever was ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1688200 Title: libgles2-mesa-dev breaks gstreamer-imx video acceleration (14.04 armhf) Status in mesa package in Ubuntu: Invalid Bug description: Installing libgles2-mesa-dev 10.1.3-0ubuntu0.6 armhf together with libxcb-randr0 breaks accelerated video playback with gstreamer-imx on UDOObuntu 2.1.2 (based on Ubuntu 14.04 LTS - see http://www.udoo.org/downloads/). This could be broken installation scripts or missing Pre-Depends. For example, video playback works fine on udoobuntu-udoo-qdl-desktop_2.1.img: # VIDEO + SOUND OK - without libgles2-mesa-dev installed gst-launch-1.0 playbin uri=file:///home/udooer/big_buck_bunny_720p_h264.mp4 gst123 big_buck_bunny_720p_h264.mp4 Introduce breakage by installing libgles2-mesa-dev *without* having libxcb-randr0 installed: sudo apt-get -y --purge remove libxcb-randr0 && sudo apt-get -y install libgles2-mesa-dev gst-launch-1.0 playbin uri=file:///home/udooer/big_buck_bunny_720p_h264.mp4 # BLACK & PAUSED gst123 big_buck_bunny_720p_h264.mp4 # SOUND ONLY + BLACK WINDOW Note that just uninstalling libgles2-mesa-dev does *NOT* fix the issue, only uninstalling libxcb-randr0 and reinstalling it before or without libgles2-mesa-dev brings video playback back to live. Workaround1, complete libxcb-randr0 installation before installing libgles2-mesa-dev: sudo apt-get -y --purge remove libxcb-randr0 && sudo apt-get -y install libxcb-randr0 && sudo apt-get -y install libgles2-mesa-dev # VIDEO + SOUND OK for gst-launch-1.0 and gst123 Workaround2, install all dependencies before libgles2-mesa-dev: sudo apt-get -y --purge remove libxcb-randr0 && sudo apt-get -y install libegl1-mesa-dev && sudo apt-get -y install libgles2-mesa-dev # VIDEO + SOUND OK for gst-launch-1.0 and gst123 So it looks like the libgles2-mesa-dev installation process if run before libxcb-randr0 has finished installation (libc triggers run, etc), messes up some configuration bits of libxcb-randr0 which stick around even after libgles2-mesa-dev is uninstalled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgles2-mesa-dev 10.1.3-0ubuntu0.6 Uname: Linux 3.14.56-udooqdl-02044-gddaad11 armv7l ApportVersion: 2.14.1-0ubuntu3.23 Architecture: armhf Date: Thu May 4 09:51:33 2017 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1688200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
vainfo works just fine with gnome-shell/wayland ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid ** Changed in: libva (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682913] Re: [radeon] corrupt gfx with Faeria/Payday 2
works fine here now ** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1682913 Title: [radeon] corrupt gfx with Faeria/Payday 2 Status in mesa package in Ubuntu: Fix Released Bug description: I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed graphical issues in some games, that render partially black. E.g.: - menu of Payday 2: https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/ - menu of Faeria: https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/ I've traced the issue to a missing lib, libgles1, which for some reason has been removed from the 17.04 repos, as using Oibaf's PPA and manually installing the lib from it fixes the issues on these games. So, please build a version for Mesa 17.0.3 and put it in the repos, it's needed by some games. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1682913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684755] Re: Missing dependency to libtxc-dxtn-s2tc:amd64
** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1684755 Title: Missing dependency to libtxc-dxtn-s2tc:amd64 Status in mesa package in Ubuntu: Invalid Status in steam package in Ubuntu: Invalid Bug description: Steam is missing a dependency to libtxc-dxtn-s2tc:amd64 How to reproduce: - Install steam from the Ubuntu repositories - Use the mesa drivers - Download a game that requires GL_EXT_TEXTURE_COMPRESSION_S3TC (e.g. Dota 2) - Steam throws an error on game start Workaround: - Install libtxc-dxtn-s2tc:amd64 https://github.com/ValveSoftware/Dota-2/issues/1213 Release: Ubuntu 17.04 Package: steam:i386 (1:1.0.0.54+repack-2ubuntu5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1684755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen
groovy is soon EOL, please upgrade to 21.04 and let us know if this is fixed there ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: Incomplete Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877762] Re: 1360x768 Vega graphics display staggered
so this is a kernel bug impish will soon get 5.13, but you also have the option of installing oem-5.13 from focal-proposed (apt install linux-oem-20.04c) ** Package changed: mesa (Ubuntu) => linux (Ubuntu) -- 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/1877762 Title: 1360x768 Vega graphics display staggered Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This was the go-to resolution pre-update. All of the other modes seem to work. Release 20.04 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-29-generic x86_64 MATE 1.24.0 Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1) lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) As you can see from the attached image, the display shifts to the right every few lines. Still working on installing the full amdgpu package (libffs 6 required, 7 installed so I'm working on the bits). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1877762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934552] Re: Graphical glitches on Radeon RX 6700 XT
already fixed in 21.0.3 which is in hirsute-proposed, mind giving it a try? ** Also affects: mesa (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1934552 Title: Graphical glitches on Radeon RX 6700 XT Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Hirsute: Incomplete Bug description: Ubuntu 21.04, mesa 21.0.1-2 amd64 Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568 Graphical glitches can be seen occasionally on screen with the RX 6700 XT graphics card. This is fixed upstream with the above merged MR, so please backport it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
I can't reproduce it with a Pro W5700, which is a NAVI 10 just like RX 5600 XT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
did you get it with 21.0.1? it was in proposed for several weeks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextual action
** Summary changed: - Nautilus crashes when opening multiple "Places" folders from launch panel + Nautilus crashes when opening places from the dock contextual action ** Summary changed: - Nautilus crashes when opening places from the dock contextual action + Nautilus crashes when opening places from the dock contextmenu -- 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/1934579 Title: Nautilus crashes when opening places from the dock contextmenu Status in nautilus package in Ubuntu: Incomplete Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934527] Re: Window switching with Alt-Tab stops working after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1934527 Title: Window switching with Alt-Tab stops working after a while Status in gnome-shell package in Ubuntu: Confirmed Bug description: On Ubuntu 21.04,since around 01 July 2021, Alt-Tab works as usual for a while after logging in, but then stops entirely (that is, it does nothing; the switcher overlay fails to appear, and switching between windows does not work). I made _no_ configuration change, and Alt-Tab continues to be configured in the keyboard shortcuts settings as usual. This has been described by other users here: https://askubuntu.com/questions/1349544/alttab-stops-working-after-a -while-in-ubuntu-21-04 There seems to be some possible connection to Thunderbird in particular, and the fact that in the left-hand-side launcher (?) / favourites of the Ubuntu desktop, the Thunderbird icon starts behaving strangely, e.g. does not show the open Thunderbird windows when clicking on it ... while other applications work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
dnsmasq tested all fine with the new NM. Only the odd systemd blocker holds us back now. -- 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/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934527] Re: Window switching with Alt-Tab stops working after a while
** Tags added: hirsute ** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934527 Title: Window switching with Alt-Tab stops working after a while Status in gnome-shell package in Ubuntu: New Bug description: On Ubuntu 21.04,since around 01 July 2021, Alt-Tab works as usual for a while after logging in, but then stops entirely (that is, it does nothing; the switcher overlay fails to appear, and switching between windows does not work). I made _no_ configuration change, and Alt-Tab continues to be configured in the keyboard shortcuts settings as usual. This has been described by other users here: https://askubuntu.com/questions/1349544/alttab-stops-working-after-a -while-in-ubuntu-21-04 There seems to be some possible connection to Thunderbird in particular, and the fact that in the left-hand-side launcher (?) / favourites of the Ubuntu desktop, the Thunderbird icon starts behaving strangely, e.g. does not show the open Thunderbird windows when clicking on it ... while other applications work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
This is in proposed and working fine there. -- https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081 Your team Desktop Packages is requested to review the proposed merge of ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934527] [NEW] Window switching with Alt-Tab stops working after a while
You have been subscribed to a public bug: On Ubuntu 21.04,since around 01 July 2021, Alt-Tab works as usual for a while after logging in, but then stops entirely (that is, it does nothing; the switcher overlay fails to appear, and switching between windows does not work). I made _no_ configuration change, and Alt-Tab continues to be configured in the keyboard shortcuts settings as usual. This has been described by other users here: https://askubuntu.com/questions/1349544/alttab-stops-working-after-a -while-in-ubuntu-21-04 There seems to be some possible connection to Thunderbird in particular, and the fact that in the left-hand-side launcher (?) / favourites of the Ubuntu desktop, the Thunderbird icon starts behaving strangely, e.g. does not show the open Thunderbird windows when clicking on it ... while other applications work. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment hirsute -- Window switching with Alt-Tab stops working after a while https://bugs.launchpad.net/bugs/1934527 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934657] [NEW] evince document viewer prints with very low resolution
Public bug reported: I am running Ubuntu 20.04, and I am new to Linux systems. The resolution of the printouts is so low, I cannot read them. The printer drivers are up-to-date. Any ideas on how to possibly resolve this bug? Do you need any further information from me? ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1934657 Title: evince document viewer prints with very low resolution Status in evince package in Ubuntu: New Bug description: I am running Ubuntu 20.04, and I am new to Linux systems. The resolution of the printouts is so low, I cannot read them. The printer drivers are up-to-date. Any ideas on how to possibly resolve this bug? Do you need any further information from me? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1934657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934648] Re: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound
Could you please try the bootargs of "snd_hda_intel.codec_mask=0x1" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1934648 Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Right speaker crackles while left speaker is intact. Tried many quirks including those posted here -> https://ubuntuforums.org/showthread.php?t=2464361 (That OP is me only). I also tried to position quirk as mentioned in troubleshooting guide -- didn't work. I am yet to try to use a live boot and see if problem is hardware or not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ucalyptus 2157 F pulseaudio /dev/snd/pcmC0D0c: ucalyptus 2157 F...m pulseaudio /dev/snd/pcmC0D0p: ucalyptus 2157 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 13:53:04 2021 InstallationDate: Installed on 2020-03-16 (475 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jul 05 13:50:11 ucalyptus dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=121 pid=1409 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 13:51:09 ucalyptus systemd[1400]: pulseaudio.service: Succeeded. Jul 05 13:51:19 ucalyptus systemd[1400]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1934648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934520] Re: Nautilus very slow to start after 20.04 upgrade
Unsure what save or open dialogs you mention but if that's the file selectors in other desktop applications that's not nautilus but probably gtk (or another toolkit, depending of the application you are using) -- 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/1934520 Title: Nautilus very slow to start after 20.04 upgrade Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus takes up to 50 seconds to start, even in save or open dialogs. Attached is the output for time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-08-11 (1421 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (431 days ago) UserGroups: root wireshark _MarkForUpload: True usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934520] Re: Nautilus very slow to start after 20.04 upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1934520 Title: Nautilus very slow to start after 20.04 upgrade Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus takes up to 50 seconds to start, even in save or open dialogs. Attached is the output for time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-08-11 (1421 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (431 days ago) UserGroups: root wireshark _MarkForUpload: True usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932311] Re: migrate to llvm 12
** Changed in: mesa (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1932311 Title: migrate to llvm 12 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: (split off from bug 1917763) [Impact] Mesa should migrate to llvm 12 for new AMDGPU features and HW support. Normally this would be done during the devel series, but this version was delayed too much to migrate before hirsute was out. [Fix] Build-depend on the new packages, including libclc which is now built from llvm sources. [Test case] Test AMD graphics and/or qemu desktop (llvmpipe) after installing migrated packages. [Regression potential] This has been in Impish for a month now without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
focal update is available too
** Tags added: verification-needed-focal
** Changed in: mesa (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Committed
Status in mesa source package in Hirsute:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925434] Re: New bugfix release 21.0.3
** Changed in: mesa (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1925434 Title: New bugfix release 21.0.3 Status in mesa package in Ubuntu: Invalid Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] This is the last point-release of the 21.0.x-series, we should put it in hirsute so latest bugfixes would get there, and in focal for 20.04.3 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening multiple "Places" folders from launch panel
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1934579 Title: Nautilus crashes when opening multiple "Places" folders from launch panel Status in nautilus package in Ubuntu: Incomplete Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933022] Re: gnome control-center crashed with sigsegv in g_str_hash() whenever I try to add input sources
** Changed in: gnome-desktop3 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1933022
Title:
gnome control-center crashed with sigsegv in g_str_hash() whenever I
try to add input sources
Status in gnome-desktop:
Unknown
Status in gnome-desktop3 package in Ubuntu:
Fix Committed
Status in gnome-desktop3 source package in Hirsute:
In Progress
Status in gnome-desktop3 package in Debian:
Fix Released
Bug description:
[Impact]
If the dconf key show-all-sources is "true", any attempt to add new
input sources via Settings results in a segfault. It means that users
can't make use of the so-called "exotic" XKB keyboard layouts.
The proposed upload includes a cherry picked upstream commit which
fixes the issue.
[Test Plan]
1. Enable show-all-sources:
gsettings set org.gnome.desktop.input-sources show-all-sources true
2. Select Settings -> Region & Language and click the + button to add
an input source.
-> Find that g-c-c crashes.
3. Install the gnome-desktop3 binaries from hirsute-proposed.
4. Repeat step 2.
-> Find that you are able to add an input source.
[Where problems could occur]
The change is a targeted fix to address the issue at hand. It was
committed upstream on April 22, and no reported regression.
[Original description]
I've been facing the problems for about 9 months now. Back then I
thought that maybe getting a new version would solve the problem, but
turns out it didn't. Whenever I try to add some Input Sources from it
just crashes.
Reproducing it is very easy: running gnome-control-center, then going
to Input Sources settings and clicking Add(+) would generate the
crash. But the weird thing is that I've been unable to reproduce it in
VM. And I also tried to reinstall most of the packages which, I think
if changed/misconfigured would cause this but it didn't help. I also
tried to use debsums to give some clues but didn't find any.
After enough digging, this is what I can retrieve from gdb:
#0 g_str_hash (v=0x506) at ../../../glib/ghash.c:2333
p = 0x506
h = 5381
#1 0x77c6e174 in g_hash_table_lookup_node (hash_return=, key=0x506, hash_table=0x563a6180 = {...}) at
../../../glib/ghash.c:472
node_hash =
hash_value =
have_tombstone = 0
step = 0
node_index =
first_tombstone = 0
node_hash =
__func__ = "g_hash_table_lookup_extended"
#2 g_hash_table_lookup_extended (hash_table=0x563a6180 = {...},
lookup_key=lookup_key@entry=0x506, orig_key=orig_key@entry=0x0,
value=value@entry=0x7fffcbb0) at ../../../glib/ghash.c:1548
node_hash =
__func__ = "g_hash_table_lookup_extended"
#3 0x76f03013 in gnome_xkb_info_get_layout_info (self=, id=id@entry=0x506 ,
display_name=display_name@entry=0x7fffcc10,
short_name=short_name@entry=0x0, xkb_layout=xkb_layout@entry=0x0,
xkb_variant=xkb_variant@entry=0x0) at ../libgnome-desktop/gnome-xkb-info.c:1042
priv = 0x56395600
layout = 0x76262ba0
__func__ = "gnome_xkb_info_get_layout_info"
#4 0x555fe467 in input_source_row_new
(self=self@entry=0x568d22b0, type=type@entry=0x556dcac3 "xkb",
id=id@entry=0x506 ) at
../panels/keyboard/cc-input-chooser.c:236
display_name = 0x0
row = 0x0
widget =
#5 0x555fe81d in add_rows_to_table (self=self@entry=0x568d22b0,
info=info@entry=0x56450320, list=0x55c82100 = {...},
list@entry=0x55c8bec0 = {...}, type=type@entry=0x556dcac3 "xkb",
default_id=0x0) at ../panels/keyboard/cc-input-chooser.c:723
table = 0x5677 = {[0x5657bb00 "cm+mmuock"] =
0x56ca91a0, [0x56506340 "us+3l"] = 0x56400920, [0x5656f6f0
"ph+capewell-dvorak"] = 0x56cb6f50, [0x5660caf0 "us+dvorak-l"] =
0x56ca9620, [0x5656cd40 "gb+mac_intl"] = 0x56cb6950,
[0x5650de80 "gh+gillbt"] = 0x56cb61d0, [0x56571540 "apl+aplx"] =
0x56ca94a0, [0x565063a0 "us+3l-cros"] = 0x56cb64d0, [0x565062b0
"us+carpalx-full-intl"] = 0x56400aa0, [0x56506070 "us+sun_type6"] =
0x56cb6350, [0x56505f50 "us+drix"] = 0x56ca9320, [0x56506b40
"cm+dvorak"] = 0x56cb6dd0, [0x564faaf0 "us+dvp"] = 0x56cb6650,
[0x564faa80 "us+dvorak-classic"] = 0x564004a0, [0x564fad30
"us+olpc2"] = 0x56400c20, [0x5656f2d0 "ml+us-intl"] = 0x56400620,
[0x564f9c70 "eu"] = 0x56400320, [0x56506310
"us+carpalx-full-altgr-intl"] = 0x564007a0, [0x5656c390 "gb+intl"] =
0x56ca97a0, [0x56506fc0 "ca+eng"] = 0x56cb67d0, [0x565714a0
"apl+aplplusII"] = 0x56400f20, [0x564fafb0 "us+norman"] =
0x56400da0,
[Desktop-packages] [Bug 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
Upgraded the ubuntu-drivers-common from 1:0.8.6.5 to 1:0.9.0 from focal on ThinkPad P15v, this issue is fixed. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
The new NM tests were fine (even against the old dnsmasq due to the or in the regex). NM hit a few non related systemd test issues - I re-triggered those. Finally I did now start the new NM tests against the blocked dnsmasq. Overall that should hopefully resolve both and let them migrate. -- 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/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Groovy: Fix Released Status in network-manager source package in Groovy: Invalid Status in dnsmasq source package in Hirsute: Fix Released Status in network-manager source package in Hirsute: Invalid Status in dnsmasq source package in Impish: Triaged Status in network-manager source package in Impish: New Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934648] [NEW] [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: Right speaker crackles while left speaker is intact. Tried many quirks including those posted here -> https://ubuntuforums.org/showthread.php?t=2464361 (That OP is me only). I also tried to position quirk as mentioned in troubleshooting guide -- didn't work. I am yet to try to use a live boot and see if problem is hardware or not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ucalyptus 2157 F pulseaudio /dev/snd/pcmC0D0c: ucalyptus 2157 F...m pulseaudio /dev/snd/pcmC0D0p: ucalyptus 2157 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 13:53:04 2021 InstallationDate: Installed on 2020-03-16 (475 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jul 05 13:50:11 ucalyptus dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=121 pid=1409 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 13:51:09 ucalyptus systemd[1400]: pulseaudio.service: Succeeded. Jul 05 13:51:19 ucalyptus systemd[1400]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1934648 Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Right speaker crackles while left speaker is intact. Tried many quirks including those posted here -> https://ubuntuforums.org/showthread.php?t=2464361 (That OP is me only). I also tried to position quirk as mentioned in troubleshooting guide -- didn't work. I am yet to try to use a live boot and see if problem is hardware or not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ucalyptus 2157 F pulseaudio /dev/snd/pcmC0D0c: ucalyptus 2157 F...m pulseaudio /dev/snd/pcmC0D0p: ucalyptus 2157 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 13:53:04 2021 InstallationDate: Installed on 2020-03-16 (475 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jul 05 13:50:11 ucalyptus dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=121 pid=1409 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 13:51:09 ucalyptus systemd[1400]: pulseaudio.service: Succeeded. Jul 05 13:51:19 ucalyptus systemd[1400]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc.
[Desktop-packages] [Bug 1934647] Re: Nvidia driver black screen at login.
** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1934647/+attachment/5509102/+files/nvidia-bug-report.log.gz -- 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/1934647 Title: Nvidia driver black screen at login. Status in xorg package in Ubuntu: New Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 10:54:41 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1934647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934647] [NEW] Nvidia driver black screen at login.
Public bug reported: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 10:54:41 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1934647 Title: Nvidia driver black screen at login. Status in xorg package in Ubuntu: New Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 5 10:54:41 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery
[Desktop-packages] [Bug 1186702] Re: WebDAV: LibreOffice does not handle vnd.sun.star.webdav protocol out-of-the-box
** Changed in: libreoffice (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) -- 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/1186702 Title: WebDAV: LibreOffice does not handle vnd.sun.star.webdav protocol out- of-the-box Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Libreoffice is able to open documents located on a WebDAV server if provided with an URL starting with the vnd.sun.star.webdav protocol. (for instance: vnd.sun.star.webdav://example.com/webdav/my-document.odt ) Unfortunately, after installing Libreoffice on Ubuntu these URL aren't still handled correctly. Whether you click on a link in your browser or you try to open the URL from the command line with xdg-open vnd.sun.star.webdav://... you get a message saying that this protocol is unknown. What I expected was that LibreOffice would start and would open the document. A workaround is to create a Desktop file with the following informations: [Desktop Entry] Name=WebDav LibreOffice Exec=/usr/bin/libreoffice %u Type=Application Terminal=false Categories=System; MimeType=x-scheme-handler/vnd.sun.star.webdav; and then to copy it in /usr/share/applications Afterwards you have to run sudo update-desktop-database so that Ubuntu will take the new protocol into account. A more definitive solution would be to modify the libreoffice-base Desktop file that comes with libreoffice (also located in /usr/share/applications) to add the MimeType properties described above. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sun Jun 2 11:51:56 2013 InstallationDate: Installed on 2013-05-12 (20 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1186702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934644] [NEW] gsettings-desktop-schemas 40 breaks workspace nagivation with gnome-shell 38
Public bug reported: gsettings-desktop-schemas 40 is supposed to be used with gnome-shell 40, not 38, and hence has moved the Page_up/Down (and ) shortcuts for moving between workspaces from vertical to horizontal settings, breaking workspace navigation in gnome-shell 38. This commit needs to be reverted until gnome-shell 40 lands: https://salsa.debian.org/gnome-team/gsettings-desktop- schemas/-/commit/a7b057cde57a6509a91fd80b492460a036a04ade Once gnome-shell 40 lands, the revert should be reverted and Breaks: gnome-shell (<< 40) should be added. ** Affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1934644 Title: gsettings-desktop-schemas 40 breaks workspace nagivation with gnome- shell 38 Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: gsettings-desktop-schemas 40 is supposed to be used with gnome-shell 40, not 38, and hence has moved the Page_up/Down (and ) shortcuts for moving between workspaces from vertical to horizontal settings, breaking workspace navigation in gnome-shell 38. This commit needs to be reverted until gnome-shell 40 lands: https://salsa.debian.org/gnome-team/gsettings-desktop- schemas/-/commit/a7b057cde57a6509a91fd80b492460a036a04ade Once gnome-shell 40 lands, the revert should be reverted and Breaks: gnome-shell (<< 40) should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1934644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927071] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** Changed in: chromium-browser (Ubuntu) Status: Expired => New -- 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/1927071 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: New Bug description: Here is the first bug report : https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1882232 It seems that there is a regression, pre-installation script of apt installed chromium-browser package doesn't detect that it is running in a chroot anymore. => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
