[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Thanks for the report. Is it fixed in newer series of Ubuntu? If not we
need to start by the devel one
> the readings from iio-poll-als are unstable, or could freeze on
certain value
isn't that the real issue? is that an hardware or firmware bug? could it
be fixed rather than worked around in udev rules?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in iio-sensor-proxy package in Ubuntu:
New
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] [NEW] Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Public bug reported:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als", and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test whether
it's ambient light sensors are working properly without unexpected
brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
** Affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in iio-sensor-proxy package in Ubuntu:
New
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
This is debdiff for iio-sensor-proxy for focal
** Patch added: "iio-sensor-proxy_2.8-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5565591/+files/iio-sensor-proxy_2.8-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in iio-sensor-proxy package in Ubuntu:
New
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
Looks like xorg-server will get the fix in "21" instead of "1.21". Although that's probably not really important to anyone here because Ubuntu switched to using the separate 'xwayland' package in impish which already has the fix. It might be relevant to focal HWE in future though. Maybe Ubuntu 20.04.5? -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in xorg-server package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Fix Released Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Tags added: nvidia-wayland wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-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..01.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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
** Tags removed: nvidia-drm.modeset ** Tags added: nvidia-wayland -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in xorg-server package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Fix Released Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948410] Re: [nvidia] Software cursor in Wayland sessions (EGLStreams)
** Tags removed: nvidia-drm.modeset ** Tags added: jammy nvidia-wayland wayland wayland-session -- 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/1948410 Title: [nvidia] Software cursor in Wayland sessions (EGLStreams) Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Software cursor used in Wayland sessions (EGLStreams). To see it just add this to /etc/environment: CLUTTER_PAINT=damage-region and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Closed due to no reply after 5 months. If anyone still experiences problems then please open new bugs for them using the 'ubuntu-bug' command. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: systemd (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-430 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Won't Fix Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 239941] Re: Can not read Chinese
Thank you for reporting this bug to Ubuntu. Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: rhythmbox (Ubuntu) Status: New => Won't Fix -- 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/239941 Title: Can not read Chinese Status in rhythmbox package in Ubuntu: Won't Fix Bug description: Binary package hint: rhythmbox The chinese name of the song can not be read ProblemType: Bug Architecture: i386 Date: Sat Jun 14 15:41:29 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.11.5-0ubuntu7 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux 2.6.24-18-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/239941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
hirsute (21.04) is EOL, but Thank you for your research @Bastian ** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950697] Re: gray desktop or login loop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1950697 Title: gray desktop or login loop Status in lightdm package in Ubuntu: New Bug description: I'm using Ubuntu 20.04 (all upgrades) I was using MATE until I decided to go back to budgie since MATE started hogging system resources. after removing MATE and trying to login with budgie I only get a gray screen. I reinstalled lightdm, budgie desktop, nvidia drivers, etc. the only desktop environment that I can use is GNOME(Metacity) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Nov 11 15:45:05 2021 InstallationDate: Installed on 2017-08-04 (1560 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmConfig: [Seat:*] autologin-guest=false #autologin-user=diego #autologin-user-timeout=0 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-10-31T12:18:08.840234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1950697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1504724] Re: lightdm crashed with SIGSEGV in munmap()
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: lightdm (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504724 Title: lightdm crashed with SIGSEGV in munmap() Status in lightdm package in Ubuntu: Incomplete Bug description: crash at startup ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Fri Oct 9 23:46:03 2015 ExecutablePath: /usr/sbin/lightdm LightdmGreeterLog: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/99_ubuntu-mate.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (2433) terminated with status 1 LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/99_ubuntu-mate.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (2426) killed by TERM signal ProcCmdline: lightdm --session-child 12 19 ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f8c59f0fb94 <_dl_fini+452>: add0x8(%rax),%r12 PC (0x7f8c59f0fb94) ok source "0x8(%rax)" (0x7f8c4a545e08) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: munmap () at ../sysdeps/unix/syscall-template.S:81 _dl_unmap_segments (l=0x1d2c910, l=0x1d2c910) at ./dl-unmap-segments.h:32 _dl_unmap (map=map@entry=0x1d2c910) at ../sysdeps/x86_64/tlsdesc.c:140 _dl_close_worker (map=map@entry=0x1d2c440) at dl-close.c:641 _dl_close_worker (map=0x1d2c440) at dl-close.c:125 Title: lightdm crashed with SIGSEGV in munmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1504724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
** Changed in: lightdm (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: New Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: lightdm (Ubuntu) Status: Triaged => Incomplete ** Changed in: lxdm (Ubuntu) Status: Triaged => Incomplete ** Changed in: policykit-desktop-privileges (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm3 package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Incomplete Status in lxdm package in Ubuntu: Incomplete Status in policykit-desktop-privileges package in Ubuntu: Incomplete Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473149] Re: Lightdm refuses to work after installing kubuntu-desktop
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: lightdm (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1473149 Title: Lightdm refuses to work after installing kubuntu-desktop Status in lightdm package in Ubuntu: Incomplete Bug description: After installing kubuntu-desktop meta package I saw a prompt telling me that both sddm and lightdm are available and I am forced to choose one between them.so I chose lightdm.on the next reboot I was unable to use GUI. After 2-3 weeks,I retried using sudo dpkg-reconfigure lightdm and selected lightdm.still fails to run GUI. sddm works fine and is able to handle both Plasma and Unity. Ubuntu 15.04 with lightdm 1.14.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 9 21:15:22 2015 InstallationDate: Installed on 2015-06-09 (30 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1473149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
I'm not sure we should investigate this at all until at least 42 is released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
For Today, the version of MondemManager in jammy 1.18.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
> In order to make work the nvidia drivers in the 17-rc6 im just change in > "more drivers" option of ubuntu, the current versión of the nvidia driver > for another (511 to 470 for example). > Im using hybrid graphics mode in the bios. Great discovery on enabling the NVidia drivers under Ubuntu. A side note for Kubuntu users, run: sudo software-properties-qt Then toggle the driver version on the Additional Drivers tab. A second note. In order to boot into discrete graphics mode, change the profile to "nvidia" either in NVidia settings or command line: sudo prime-select nvidia Reboot into BIOS and select the dedicated graphics option. I assigned the following command to a shortcut key to boot reboot directly to BIOS: systemctl reboot --firmware-setup -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962403] Re: Gamepads are no longer detected
I filed a store request to have the joystick interface auto-connected: https://forum.snapcraft.io/t/auto-connecting-the-joystick-interface-for- the-firefox-snap/28981. Regarding that kernel bug, please file a separate issue against the linux source package. ** Changed in: firefox (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Gamepads are no longer detected + [snap] Gamepads are no longer detected ** Tags added: snap ** Changed in: firefox (Ubuntu) Importance: Undecided => Medium ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1962403 Title: [snap] Gamepads are no longer detected Status in firefox package in Ubuntu: Confirmed Bug description: After the upgrade from Firefox deb to Firefox snap, my gamepad is no longer being detected. One gamepad is a Feitun FM0013, a gamepad with at least 5 operation modes I've found so far: Nintendo Switch Pro Controller, X-Box wired controller, PS3 wired controller, PS3 wireless controller and generic Bluetooth controller. From these 5 operation modes, X-Box wired controller, PS3 wired controller and generic Bluetooth controller work on my computer, while Nintendo Switch Pro Controller mode is found but doesn't detect any buttons while using PS3 wireless controller mode isn't found. When using on my notebook and smartphone, I normally use this gamepad in generic Bluetooth controller mode, as I want to use it wirelessly more often. I have noticed that any of the modes that worked with Firefox deb (X-Box wired controller, PS3 wired controller and generic Bluetooth controller) stopped working with the snap. Steps to reproduce: 1) Have Firefox installed as a snap; 2) Connect gamepad with one of its compatible modes; 3) Access page/game to test the gamepad (https://hacks.mozilla.org/2013/12/the-gamepad-api/ or https://luser.github.io/gamepadtest/ or http://www.cross-code.com/en/start for example); 4) Notice how the gamepad isn't detected. I have a Redragon Seymur 2 too, and it also isn't detected. Using the Firefox from the Mozilla page, the gamepads are found and appear as follow in the luser's page: gamepad: 0079-0006-DragonRise Inc. Generic USB Joystick gamepad: 045e-028e-Microsoft X-Box 360 pad The X-Box 360 one is the Feitun. Using Bluetooth, the Feitun appear as: gamepad: 1949-0402-Gamepad So, unfortunately, Firefox snap is unusable to play games while using gamepads. For example, I can play CrossCode on the Chromium snap, but am unable to play it on Firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Feb 27 11:25:06 2022 InstallationDate: Installed on 2017-06-13 (1719 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap.Changes: não foram encontradas alterações SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2019-12-22 (797 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
.. and the PPA means I am now running the 510 drivers successfully. Thanks again, Martin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Released Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Figured how to get the virtualbox gdb run. ** Attachment added: "gdb-virtualbox.txt" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+attachment/5565368/+files/gdb-virtualbox.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Regarding falling back to earlier releases, I have created a local repository on my system. Given this I should be able to place the back- level packages and then force those versions in synaptic. I am not experienced in reading the gdb output, but it seems to me that the call which generates the segfault is from libgail.so and libgail was among those updated on 1 March from ..ubuntu1 to ..ubuntu1.1 version. Given this, would it make sense for me to back-level that one package? Perhaps all those updated to ..ubunto1.1 from ..ubuntu1, which includes gtk updates? I don't want to create more problems by missing co-dependencies in version levels, so I will wait for your guidance before I proceed further. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962818] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1962818/+attachment/5565348/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
apport information ** Tags added: apport-collected jammy ** Description changed: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu78 + Architecture: amd64 + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-01-16 (45 days ago) + InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) + Package: lightdm 1.30.0-0ubuntu5 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_AU:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 + Tags: jammy + Uname: Linux 5.15.0-18-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1962818/+attachment/5565346/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962818] LightdmUsersConfig.txt
apport information ** Attachment added: "LightdmUsersConfig.txt" https://bugs.launchpad.net/bugs/1962818/+attachment/5565347/+files/LightdmUsersConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963380] Re: clic milieu // central click
root@hippo:/home/hippo# dmidecode # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. 69 structures occupying 2740 bytes. Table at 0x000E85DF. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Hewlett-Packard Version: K01 v02.90 Release Date: 07/16/2013 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 2.90 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Hewlett-Packard Product Name: HP Compaq Elite 8300 SFF Version: Not Specified Serial Number: CZC3520WWN UUID: 40e9c000-6629-11e3-8cc6-2c44fd2578ef Wake-up Type: Power Switch SKU Number: QV996AV Family: 103C_53307F G=D Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Hewlett-Packard Product Name: 3397 Version: Not Specified Serial Number: CZC3520WWN Asset Tag: Features: Board is a hosting board Board is removable Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Hewlett-Packard Type: Low Profile Desktop Lock: Not Present Version: Not Specified Serial Number: CZC3520WWN Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Not Specified Handle 0x0004, DMI type 7, 19 bytes Cache Information Socket Designation: CPU Internal L1 Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Through Location: Internal Installed Size: 256 kB Maximum Size: 256 kB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Parity System Type: Unified Associativity: 8-way Set-associative Handle 0x0005, DMI type 7, 19 bytes Cache Information Socket Designation: CPU Internal L2 Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Through Location: Internal Installed Size: 1 MB Maximum Size: 1 MB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 8-way Set-associative Handle 0x0006, DMI type 7, 19 bytes Cache Information Socket Designation: CPU Internal L3 Configuration: Enabled, Not Socketed, Level 3 Operational Mode: Write Back Location: Internal Installed Size: 8 MB Maximum Size: 8 MB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 16-way Set-associative Handle 0x0007, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 32 GB Error Information Handle: Not Provided Number Of Devices: 4 Handle 0x0008, DMI type 11, 5 bytes OEM Strings String 1: ABS 70/71 60 61 62 63; String 2: FBYTE#2U2V3E3P3V3X4766676J6b7H7M7Q7T7W7a7m8D9A9zag.Hr; String 3: BUILDID#12WWIDIW603#SABF#DABF; Handle 0x0009, DMI type 24, 5 bytes Hardware Security Power-On Password Status: Disabled Keyboard Password Status: Disabled Administrator Password Status: Disabled Front Panel Reset Status: Disabled Handle 0x000A, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x000B, DMI type 41, 11 bytes Onboard Device Reference Designation:
[Desktop-packages] [Bug 1963380] [NEW] clic milieu // central click
Public bug reported: Please activate my central click with mouse like other linux distribution ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-input-evdev (not installed) ProcVersionSignature: Ubuntu 5.13.0-30.33-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 3 18:49:20 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu InstallationDate: Installed on 2022-01-30 (31 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-lowlatency root=UUID=c82d7eee-e37b-49a5-aa78-5cabb7293023 ro threadirqs quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 2.90 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuQV996AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: QV996AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1963380 Title: clic milieu // central click Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: Please activate my central click with mouse like other linux distribution ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-input-evdev (not installed) ProcVersionSignature: Ubuntu 5.13.0-30.33-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 3 18:49:20 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu InstallationDate: Installed on 2022-01-30 (31 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-lowlatency root=UUID=c82d7eee-e37b-49a5-aa78-5cabb7293023 ro threadirqs quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 2.90 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuQV996AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: QV996AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1963380/+subscriptions -- Mailing
[Desktop-packages] [Bug 1963380] Re: clic milieu // central click
root@hippo:/home/hippo# lsinput /dev/input/event0 bustype : BUS_HOST vendor : 0x0 product : 0x1 version : 0 name: "Power Button" phys: "PNP0C0C/button/input0" bits ev : (null) (null) /dev/input/event1 bustype : BUS_HOST vendor : 0x0 product : 0x1 version : 0 name: "Power Button" phys: "LNXPWRBN/button/input0" bits ev : (null) (null) /dev/input/event2 bustype : BUS_USB vendor : 0x46d product : 0x400d version : 273 name: "Logitech K230" phys: "usb-:00:1a.0-1.6/input2:2" uniq: "400d-01-9a-23-d9" bits ev : (null) (null) (null) (null) (null) (null) (null) /dev/input/event3 bustype : BUS_USB vendor : 0x46d product : 0x4054 version : 273 name: "Logitech Wireless Mouse" phys: "usb-:00:14.0-3/input1:2" uniq: "4054-e7-fd-d0-7b" bits ev : (null) (null) (null) (null) /dev/input/event4 bustype : BUS_HOST vendor : 0x0 product : 0x0 version : 0 name: "HP WMI hotkeys" phys: "wmi/input0" bits ev : (null) (null) (null) (null) /dev/input/event5 bustype : (null) vendor : 0x0 product : 0x0 version : 0 name: "HDA Intel PCH Mic" phys: "ALSA" bits ev : (null) (null) /dev/input/event6 bustype : (null) vendor : 0x0 product : 0x0 version : 0 name: "HDA Intel PCH Line" phys: "ALSA" bits ev : (null) (null) /dev/input/event7 bustype : (null) vendor : 0x0 product : 0x0 version : 0 name: "HDA Intel PCH Line Out" phys: "ALSA" bits ev : (null) (null) /dev/input/event8 bustype : (null) vendor : 0x0 product : 0x0 version : 0 name: "HDA Intel PCH Front Headphone" phys: "ALSA" bits ev : (null) (null) /dev/input/event9 bustype : (null) vendor : 0x0 product : 0x0 version : 0 name: "HDA Intel PCH HDMI/DP,pcm=3" phys: "ALSA" bits ev : (null) (null) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1963380 Title: clic milieu // central click Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: Please activate my central click with mouse like other linux distribution ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-input-evdev (not installed) ProcVersionSignature: Ubuntu 5.13.0-30.33-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 3 18:49:20 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu InstallationDate: Installed on 2022-01-30 (31 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-lowlatency root=UUID=c82d7eee-e37b-49a5-aa78-5cabb7293023 ro threadirqs quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 2.90 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuQV996AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.product.sku: QV996AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1963380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I attempted to use gdb on virtualbox first, but received errors. Given this I was able to provide what you wanted with fcl. Hopefully it will provide you with enough information to diagnose the problem. ** Attachment added: "gdb-fcl.txt" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+attachment/5565328/+files/gdb-fcl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962510] Re: failing tests with new sssd, blocks python3-defaults
I troubleshooted this initially in https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170, when all tests were failing, and reached the same patch that mwhudson did, but the tests were still failing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Could you try to follow https://wiki.ubuntu.com/Backtrace to provide more details on the crash? The log suggest you didn't update much but that includes glibc, do you know your way around dpkg and apt enough to try to go back to the binary packages from https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.5 and see if that resolves your issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962510] Re: failing tests with new sssd, blocks python3-defaults
The package isn't regressing tests since it's not present in the release pocket at the moment. In any case adsys is in a target promotion for desktop for the incoming LTS, bug #1936907, we will own the issues as we do for any of our other packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
Unassigning from me, as I don't know how to make more progress here. ** Changed in: adsys (Ubuntu) Assignee: Andreas Hasenack (ahasenack) => (unassigned) ** Changed in: adsys (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: New Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
The two programs are completely broken for me at this time. I use them on a daily basis, so this is a real problem for me. There may be additional broken programs that I have yet to encounter, but I have not hit any others yet. Given the behavior started suddenly yesterday after years of operation I suspect that an update to one of the dependencies of the library where the crash occurs is the cause. I am not a developer, and thus unable to track this down personally. Given my suspicions I attached a zip containing the update logs in hopes someone with the proper tools can identify the problem. I should be able to back out the particular change once it is identified. If you need further information please let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962510] Re: failing tests with new sssd, blocks python3-defaults
Removing the tag means that this package will reenter the release pocket with failing tests. Who is responsible for fixing these tests? The standard for proposed-migration is that we don't regret tests. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1962818 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963279] [NEW] [SRU] libreoffice 7.2.6 for impish
Public bug reported: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * Version 7.2.5 is currently released in impish. For a list of fixed bugs compared to 7.2.5 see the list of bugs fixed in the release candidates of 7.2.6 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.2.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu Impish) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Impish) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Impish) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Impish) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- 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/1963279 Title: [SRU] libreoffice 7.2.6 for impish Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Impish: In Progress Bug description: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * Version 7.2.5 is currently released in impish. For a list of fixed bugs compared to 7.2.5 see the list of bugs fixed in the release candidates of 7.2.6 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.2.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan
[Desktop-packages] [Bug 1944113]
*** Bug 147745 has been marked as a duplicate of this bug. *** -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944113]
Same on Version: 7.3.0.3 / LibreOffice Community Build ID: 30(Build:3) CPU threads: 4; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.3.0-7 Calc: threaded -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944113]
Can confirm still exist in Version: 7.3.0.3 / LibreOffice Community Build ID: 30(Build:3) CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-CA (en_CA.UTF-8); UI: en-US 7.3.0-6 Calc: threaded -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5
Please attach the reproducing pipeline; it's a bit tricky to organise access to Jetson hardware to the right people, so if you had a reproducer that we could run without Jetson hardware, that would be best! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline Status in Gstreamer1.0: Unknown Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Bionic: New Bug description: Few specific h264 and h265 RTSP input streams sources when used with nvidia specific gst-v4l2 based gstreamer-1.0 (version gst-1.14 and ubuntu-18.04) decode pipeline intermittently yields very low fps (in the range of [~0/1 fps]). Issue seems caused by the gst_video_decoder_drain_out function erroneously getting called inside gst_video_decoder_chain_forward function. Required changes to fix the issue seems available with gst-1.16 and to resolve the issue need to backport the relevant OSS fixes from gst-1.16 to gst-1.14 on ubuntu-18.04. The mentioned issue was reported on with: https://bugzilla.gnome.org/show_bug.cgi?id=796771 Corresponding fix was incorporated with below: https://github.com/GStreamer/gst-plugins-base/commit/62cb08404b9bd055c45cc1d5b71141e927ad748a We need to backport above fix on top of gst-1.14.5 on ubuntu-18.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.14 on ubuntu-18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on u
Hi Kunal, It might be tricky to organise testing on Jetson platforms for people that will prepare the fix. In any case, could you share instructions to reproduce? If there's a way to craft a test pipeline that trigger the issue without Jetson hardware, that would be best. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: New Status in gstreamer1.0 source package in Focal: New Bug description: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Comment on attachment 9266065
1753242_esr91.patch
[Triage Comment]
Previously approved by wsmwk; moving flag to esr91 version of patch.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Thunderbird 91.7.0:
https://hg.mozilla.org/releases/comm-esr91/rev/10a8a57ef967
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Sorry, still something to sort out with that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
The test changes won't merge. The changes to msgHdrView.js apply fine.
Uplifting without the tests seems like a bad idea, how do you want to
proceed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Created attachment 9266065
1753242_esr91.patch
fixed version for esr91 based on comment 11.
Diff to comment 11:
```
➜ hg diff
diff --git a/mail/test/browser/attachment/browser_openAttachment.js
b/mail/test/browser/attachment/browser_openAttachment.js
--- a/mail/test/browser/attachment/browser_openAttachment.js
+++ b/mail/test/browser/attachment/browser_openAttachment.js
@@ -39,17 +39,17 @@ add_task(async function setupModule(modu
be_in_folder(folder);
// @see logic for tmpD in msgHdrView.js
tmpD = PathUtils.join(
Services.dirsvc.get("TmpD", Ci.nsIFile).path,
"pid-" + Services.appinfo.processID
);
- let savePath = PathUtils.join(tmpD, "saveDestination");
+ savePath = PathUtils.join(tmpD, "saveDestination");
await IOUtils.makeDirectory(savePath);
Services.prefs.setStringPref("browser.download.dir", savePath);
Services.prefs.setIntPref("browser.download.folderList", 2);
Services.prefs.setBoolPref("browser.download.useDownloadDir", true);
Services.prefs.setIntPref("security.dialog_enable_delay", 0);
let mockedExecutable = FileUtils.getFile("TmpD", ["mockedExecutable"]);
@@ -406,12 +406,8 @@ add_task(async function saveToDiskPrompt
let file = await checkFileSaved(tmpD);
file.remove(false);
Assert.ok(MockFilePicker.shown, "file picker was shown");
MockFilePicker.reset();
Services.prefs.setBoolPref("browser.download.useDownloadDir", true);
});
-registerCleanupFunction(() => {
- // Remove created folders.
- folder.deleteSelf(null);
-});
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Please grab this one for 91: https://hg.mozilla.org/try-comm-
central/rev/cd62aeb78d449ab78f05db634320ae06f33de437
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959604]
Comment on attachment 9262175
Bug 1753242 - use a tmp subdir for opening temp files. r=darktrojan
[Triage Comment]
Approved for esr91
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959604
Title:
[upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
readable to everyone
Status in Mozilla Thunderbird:
Fix Released
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
thunderbird saves opened attachments to /tmp with permissions
according to umask setting. This was fixed a long time ago with a
protected folder /tmp/mozilla_${USER}0 and was still working correctly
as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.
Ubuntu 20.04.3 LTS
Kernel release:5.13.0-25-generic
Architecture: x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] [NEW] Screencast not recording
Public bug reported: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Summary changed: - Screencast not working (stops in 2 seconds) + Screencast not recording -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959373] Re: Please merge plymouth 0.9.5+git20211018-1 (main) from Debian unstable (main)
** Changed in: plymouth (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1959373 Title: Please merge plymouth 0.9.5+git20211018-1 (main) from Debian unstable (main) Status in plymouth package in Ubuntu: Fix Released Bug description: https://merges.ubuntu.com/p/plymouth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1959373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963241] [NEW] [FFe] evince 42
Public bug reported: . ** 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/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: New Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960458] Re: patch git_socket_dir.patch causing FTBFS in gspell
This bug was fixed in the package at-spi2-core - 2.42.0-2ubuntu3.1 --- at-spi2-core (2.42.0-2ubuntu3.1) jammy; urgency=medium * debian/patches/git_socket_dir.patch: - include some extra fixes from upstream to better handling non existing directories and relative paths (lp: #1960458) -- Sebastien Bacher Tue, 15 Feb 2022 18:29:33 +0100 ** Changed in: at-spi2-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: Fix Released Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1118323] Re: cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()
I've gotten around the bug by: * Shutting down cups service * Deleting * /etc/cups/printers.conf* * /etc/cups/classes.conf* * /etc/cups/subscriptions.conf* * Rebooting * Adding printer using the "Additional Printer Settings" button rather than the "Add" button on initial screen All three sets of deleted files were auto-created again, and no crash dialog appeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-pk-helper in Ubuntu. https://bugs.launchpad.net/bugs/1118323 Title: cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va() Status in cups-pk-helper package in Ubuntu: Confirmed Bug description: Ao tentar adicionar uma impressora, o sistema retorna uma mensagem de erro. Além do mais, não consegui localizar uma impressora em rede. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: cups-pk-helper 0.2.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Thu Feb 7 10:35:09 2013 ExecutablePath: /usr/lib/i386-linux-gnu/cups-pk-helper-mechanism InstallationDate: Installed on 2013-02-06 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130206) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/cups-pk-helper-mechanism ProcEnviron: Signal: 5 SourcePackage: cups-pk-helper StacktraceTop: ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1118323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1118323] Re: cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()
I went to add a Kyocera Mita FS-1030D+ with an IB-21E NIC.
1. Tapped Windows key
2. Searched for "printers"
3. Saw list of printers already added in settings app in printer section
(Two printers originally listed - one not connected, one auto-added by network
detection)
4. Clicked "Add" button in the titlebar to add Kyocera
5. Add printer dialog appears, spinner shown briefly, then "System program
problem detected"
I now get a similar system program problem detected every time I sign
into my account.
I was able to add the printer through older looking Gnome printer dialog
("Additional Printer Settings" button), but still get a crash every time
I sign in.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-pk-helper in Ubuntu.
https://bugs.launchpad.net/bugs/1118323
Title:
cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()
Status in cups-pk-helper package in Ubuntu:
Confirmed
Bug description:
Ao tentar adicionar uma impressora, o sistema retorna uma mensagem de
erro. Além do mais, não consegui localizar uma impressora em rede.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: cups-pk-helper 0.2.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Thu Feb 7 10:35:09 2013
ExecutablePath: /usr/lib/i386-linux-gnu/cups-pk-helper-mechanism
InstallationDate: Installed on 2013-02-06 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130206)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/cups-pk-helper-mechanism
ProcEnviron:
Signal: 5
SourcePackage: cups-pk-helper
StacktraceTop:
?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_variant_new_va () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_variant_new () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1118323/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I can say, that I have this dialog only if I have a flatpak updates, not apt updates. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962836] Re: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume
Alsa info after suspend http://alsa- project.org/db/?f=5616145ad14337953bcf0df255cc83693c829e2d -- 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/1962836 Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962836] [NEW] [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume
Public bug reported: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 ** 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/1962836 Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962836/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I wonder if you need to install gnome-software Deb maybe. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962283] Re: Ubuntu dock has a border
Looks like the pending fix might come from yaru-theme (in proposed) rather than gnome-shell (in proposed)? ** Changed in: yaru-theme (Ubuntu) Status: Invalid => Fix Committed ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags added: fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1962283 Title: Ubuntu dock has a border Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Ubuntu dock has a grey (gray) border. Confirmed on a couple of jammy machines. Seems to be a recent regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 25 13:40:40 2022 InstallationDate: Installed on 2021-11-05 (111 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock 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/1962283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
No I am not familiar with this feature. I also can't seem to trigger it in jammy (reported in impish). Even when I have updates awaiting installation it just powers off when told to. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962820] Re: Application icons are shaking when scale to 200%
** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1962820 Title: Application icons are shaking when scale to 200% Status in OEM Priority Project: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.Bug 1889102 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
@Daniel, do you have any idea what changed that the option starting to show only now on Ubuntu sessions? -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962679] Re: take screenshot does not work
Thanks, reported upstream on https://gitlab.gnome.org/GNOME/totem/-/issues/508 ** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #508 https://gitlab.gnome.org/GNOME/totem/-/issues/508 ** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Changed in: totem (Ubuntu) Status: Confirmed => Triaged ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/-/issues/508 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962679 Title: take screenshot does not work Status in Totem: Unknown Status in totem package in Ubuntu: Triaged Bug description: playing an .avi video i select 'take screensot' and i have a small window with a message 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report'corrado@corrado-p5-jj-0203:~$ inxi -SGx System: Host: corrado-p5-jj-0203 Kernel: 5.15.0-18-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 41.3 Distro: Ubuntu 22.04 (Jammy Jellyfish) Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1680x1050~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.2.2 direct render: Yes corrado@corrado-p5-jj-0203:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 41~alpha~20220222-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 06:26:15 2022 InstallationDate: Installed on 2022-02-08 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1962679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
Hi: Let me double check and reply for you later.Tks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958398] Re: seahorse does not show in HUD for "gpg"
** Changed in: seahorse (Ubuntu) Importance: Undecided => Low ** Changed in: seahorse (Ubuntu) Status: New => Triaged -- 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/1958398 Title: seahorse does not show in HUD for "gpg" Status in seahorse package in Ubuntu: Triaged Bug description: Seahorse does not show as an option when typing "gpg" in HUD but it should. It is being offered as a choice when typing "password". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1958398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
The log has errors like boltd[712]: /usr/libexec/boltd: symbol lookup error: /usr/libexec/boltd: undefined symbol: g_log_structured_standard could you share the output of $ ldd -r /usr/libexec/boltd it sounds like an old version of glib has been installed taking of the ubuntu version? ** Changed in: modemmanager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962820] Re: Application icons are shaking when scale to 200%
@daniel, Thanks for your quick feedback. And yes, if I removed the gnome-shell-extension-ubuntu-dock this issue is gone, no shaking and no extra dots. So it should be a bug of gnome- shell-extension-ubuntu-dock while not gnome-shell. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962820 Title: Application icons are shaking when scale to 200% Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.Bug 1889102 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962820] Re: Application page abnormal when scale to 200%
The shaking problem is new, but the problem with too many dots is covered by bug 1889102 already. Does removing ubuntu-dock fix the shaking also? ** Summary changed: - Application page abnormal when scale to 200% + Application icons are shaking when scale to 200% ** Description changed: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: - 1.On Applications page there are 9 pots on the right border. + 1.Bug 1889102 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962820 Title: Application icons are shaking when scale to 200% Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Bug description: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.Bug 1889102 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962823] Re: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort()
This is the most common gnome-shell crash in jammy that has a partial stack trace but it's still not enough information. We also can't read any of the associated journal logs due to bug 1962454. Judging by similar crashes like bug 1962817 I would say most instances of this crash are going to be bug 1782984. Please try logging into a Wayland session as a workaround. ** Summary changed: - /usr/bin/gnome-shell:6:__pthread_kill_implementation:__pthread_kill_internal:__GI___pthread_kill:__GI_raise:__GI_abort + gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort() ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** 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/1962823 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort() Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962823] [NEW] gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: High Status: Confirmed ** Tags: focal impish jammy kylin-21.10 -- 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/1962823 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() from __pthread_kill_internal() from __GI___pthread_kill() from __GI_raise() from __GI_abort() Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962820] Re: Application page abnormal when scale to 200%
Here is the screencast to reproduce this issue. ** Attachment removed: "gnome-shell-200.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962820/+attachment/5565204/+files/gnome-shell-200.webm ** Attachment added: "gnome-shell-p200.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962820/+attachment/5565207/+files/gnome-shell-p200.webm -- 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/1962820 Title: Application page abnormal when scale to 200% Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.On Applications page there are 9 pots on the right border. 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962820] Re: Application page abnormal when scale to 200%
Here is screen record after reproduce this issue. ** Attachment added: "gnome-shell-200.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962820/+attachment/5565204/+files/gnome-shell-200.webm ** Description changed: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. + 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.On Applications page there are 9 pots on the right border. 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 ** Tags added: oem-priority originate-from-1961012 sutton ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority 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/1962820 Title: Application page abnormal when scale to 200% Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.On Applications page there are 9 pots on the right border. 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962820] [NEW] Application page abnormal when scale to 200%
Public bug reported: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.On Applications page there are 9 pots on the right border. 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 ** Affects: oem-priority Importance: Undecided Assignee: Bin Li (binli) Status: Confirmed ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1961012 sutton -- 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/1962820 Title: Application page abnormal when scale to 200% Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce steps] 1.open setting and change scale to max（200%） 2.click 'Show Applications' at bottom-left corner. 3.drag one icon to another one to create a group folder of icons, then open it and close. 4.click 'Show Applications' again. Expected Result: 1.Applications pages show correctly. Actual result: 1.On Applications page there are 9 pots on the right border. 2.The icons on Applications page are shaking. [Additional information] Platform:ThinkCentre M70t Gen3 / ThinkPad X1 Yoga CPU:Intel OS:Ubuntu 20.04.3 LTS gnome-shell:3.36.9-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
