[Desktop-packages] [Bug 1861542] Re: gnome-shell crashed with SIGSEGV (when using touchscreen) in meta_window_updates_are_frozen (window=0x0) from meta_window_actor_sync_updates_frozen from meta_compo
I faced the same problem with Konsole. It crashes when I touch the screen (Lenovo ThinkVision M14t, which identifies as a Wacom-compliant touchscreen). Is there any fix for this that I can try? -- 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/1861542 Title: gnome-shell crashed with SIGSEGV (when using touchscreen) in meta_window_updates_are_frozen (window=0x0) from meta_window_actor_sync_updates_frozen from meta_compositor_sync_updates_frozen Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/933 https://errors.ubuntu.com/problem/1429b22c6db5a0aea5fe70c0da3b07fe46cf8553 --- Crash dump for a previous bug report ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 23:43:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input libvirt lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1861542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
The correct fix should in kernel driver or GPU firmware.
Please track on drm-intel#6851.
** Changed in: oem-priority
Status: In Progress => Incomplete
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescr
[Desktop-packages] [Bug 1967857] Re: Upgrade espeak-ng to version 1.51
Expected in https://packages.ubuntu.com/kinetic/espeak-ng ** Changed in: espeak-ng (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak-ng in Ubuntu. https://bugs.launchpad.net/bugs/1967857 Title: Upgrade espeak-ng to version 1.51 Status in espeak-ng package in Ubuntu: Fix Released Bug description: Please upgrade espeak-ng to version 1.51. The current package 1.50 is from December 2021 and 1.51 is from April 2022 with many fixes. See also https://github.com/espeak-ng/espeak-ng/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak-ng/+bug/1967857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
The simple workaround is to remove the package, or remove the entry from the udev file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)
** Changed in: gnome-control-center Status: Unknown => New ** Changed in: mutter Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1990207 Title: "Night Light unavailable" in Settings (but the quick settings toggle for it works) Status in gnome-control-center: New Status in Mutter: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: "Night Light unavailable" in Settings (but the quick settings toggle for it works). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861542] Re: gnome-shell crashed with SIGSEGV (when using touchscreen) in meta_window_updates_are_frozen (window=0x0) from meta_window_actor_sync_updates_frozen from meta_compo
It appears this crash stopped happening in Ubuntu 20.10 and later, but there doesn't seem to be any record of *what* fixed it. Certainly the ThinkVision M14t works for me - I've been using it in 22.04 and 22.10. ** No longer affects: gnome-shell (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1861542 Title: gnome-shell crashed with SIGSEGV (when using touchscreen) in meta_window_updates_are_frozen (window=0x0) from meta_window_actor_sync_updates_frozen from meta_compositor_sync_updates_frozen Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/933 https://errors.ubuntu.com/problem/1429b22c6db5a0aea5fe70c0da3b07fe46cf8553 --- Crash dump for a previous bug report ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 23:43:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input libvirt lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1861542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1990207 Title: "Night Light unavailable" in Settings (but the quick settings toggle for it works) Status in gnome-control-center: New Status in Mutter: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: "Night Light unavailable" in Settings (but the quick settings toggle for it works). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990253] [NEW] On-screen keyboard fails to appear on Snap software
Public bug reported: I have 22.04.1 LTS on HP ProBook 4545s. When you make any text insertion box of browser or website active in a Snap software, for example in the latest Brave Snap package, tapping nor clicking a text insertion area does not bring up the keyboard. This can be worked around by enabling accessability icon and on-screen keyboard for forever in the upper system tray. If I an collect any diagnostic data for this please send me the instructions and I'll see what I can do. Thanks ** Affects: gnome-shell (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/1990253 Title: On-screen keyboard fails to appear on Snap software Status in gnome-shell package in Ubuntu: New Bug description: I have 22.04.1 LTS on HP ProBook 4545s. When you make any text insertion box of browser or website active in a Snap software, for example in the latest Brave Snap package, tapping nor clicking a text insertion area does not bring up the keyboard. This can be worked around by enabling accessability icon and on-screen keyboard for forever in the upper system tray. If I an collect any diagnostic data for this please send me the instructions and I'll see what I can do. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox
I can't seem to reproduce the bug in a 22.04.1 VM with guest additions
installed. Not in Wayland or Xorg. Desktop resizing works.
Do you see the issue in just Xorg sessions ("Ubuntu on Xorg") or Wayland
too ("Ubuntu" on the login screen)?
** Tags added: virtualbox
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1989726
Title:
Only a quarter of the screen showing in VirtualBox
Status in mutter package in Ubuntu:
In Progress
Bug description:
Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on
VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and
restarted twice.
I've tried Xubuntu and Kubuntu 22.04 and they both work without any
errors.
Screenshot here: https://i.stack.imgur.com/KI0YO.png
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989726/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990256] [NEW] [regression] Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen
You have been subscribed to a public bug: Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen. This is a regression of what was previously fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then broken again upstream. Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to set mode 2008x1274 on CRTC 32: Invalid argument Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: jammy virtualbox -- [regression] Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen https://bugs.launchpad.net/bugs/1990256 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990256] Re: [regression] Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen
Based on comments in https://gitlab.gnome.org/GNOME/mutter/-/issues/2384, a new fix might be coming in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2482 ** Changed in: linux (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Package changed: linux (Ubuntu) => mutter (Ubuntu) -- 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/1990256 Title: [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen Status in mutter package in Ubuntu: Triaged Bug description: Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen. This is a regression of what was previously fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then broken again upstream. Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to set mode 2008x1274 on CRTC 32: Invalid argument Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990256] Re: [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen
** Summary changed: - [regression] Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen + [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen ** Description changed: - Non-default GPUs (vboxvideo) in VirtualBox hang at the login screen. + Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen. This is a regression of what was previously fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then broken again upstream. Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to set mode 2008x1274 on CRTC 32: Invalid argument Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented ** Summary changed: - [regression] Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen + [regression] Non-default GPUs (VBoxVGA/VBoxSVGA) in VirtualBox freeze at the login screen ** Description changed: - Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen. + Non-default GPUs (VBoxVGA/VBoxSVGA) in VirtualBox freeze at the login + screen. This is a regression of what was previously fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then broken again upstream. Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to set mode 2008x1274 on CRTC 32: Invalid argument Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented ** Tags added: vboxvideo -- 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/1990256 Title: [regression] Non-default GPUs (VBoxVGA/VBoxSVGA) in VirtualBox freeze at the login screen Status in mutter package in Ubuntu: Triaged Bug description: Non-default GPUs (VBoxVGA/VBoxSVGA) in VirtualBox freeze at the login screen. This is a regression of what was previously fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then broken again upstream. Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS update: Failed to set mode 2008x1274 on CRTC 32: Invalid argument Sep 20 18:14:49 vjam gnome-shell[903]: Failed to post KMS update: drmModeCrtcSetGamma on CRTC 32 failed: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox
** Changed in: mutter (Ubuntu) Status: In Progress => Incomplete ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1989726 Title: Only a quarter of the screen showing in VirtualBox Status in mutter package in Ubuntu: Incomplete Bug description: Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and restarted twice. I've tried Xubuntu and Kubuntu 22.04 and they both work without any errors. Screenshot here: https://i.stack.imgur.com/KI0YO.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox
A guy on Reddit helped me. If I click logout I get this popup message: xmessage VBoxClient: Failed to register resizing support, rc=VERR_RESOURCE_BUSY OK then the whole screen appears and I can use the desktop. And I can also log out if I click log out again. But when I restart the error happens all over again and I have to get the error popup before I can use the desktop. I don't know about the xorg thing because I don't have a login screen, I just go straight to desktop. But it's fine, I gave up on getting Gnome to work anyway because KDE is just so much more configurable and uses less screen space and is neater. I'll try Gnome again in a few years to see if it's improved. Thanks! -- 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/1989726 Title: Only a quarter of the screen showing in VirtualBox Status in mutter package in Ubuntu: Incomplete Bug description: Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and restarted twice. I've tried Xubuntu and Kubuntu 22.04 and they both work without any errors. Screenshot here: https://i.stack.imgur.com/KI0YO.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990262] [NEW] Screen reset randomly when moving cursors
Public bug reported: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990262 Title: Screen reset randomly when moving cursors Status in mutter package in Ubuntu: New Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990262] Re: Screen reset randomly when moving cursors
** Attachment added: "sosreport-ubuntu-2022-09-07-zluxqrd.tar" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+attachment/5617344/+files/sosreport-ubuntu-2022-09-07-zluxqrd.tar -- 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/1990262 Title: Screen reset randomly when moving cursors Status in mutter package in Ubuntu: New Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990262] Re: Screen reset randomly when moving cursors
** Attachment added: "20220907_145805.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+attachment/5617343/+files/20220907_145805.mp4 -- 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/1990262 Title: Screen reset randomly when moving cursors Status in mutter package in Ubuntu: New Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1990262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990263] [NEW] bamfdaemon crashes with libwnck3 43.0-1
Public bug reported: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81 ../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 ** Affects: libwnck3 (Ubuntu) Importance: Critical Status: New ** Tags: block-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: New Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990263] Re: bamfdaemon crashes with libwnck3 43.0-1
** Description changed: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 + + Happens when running gnome-xorg/x11 session under gnome-shell 43.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: New Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 Happens when running gnome-xorg/x11 session under gnome-shell 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990253] Re: On-screen keyboard fails to appear on Snap software
*** This bug is a duplicate of bug 1831039 *** https://bugs.launchpad.net/bugs/1831039 This sounds like bug 1831039. ** Tags added: jammy osk ** This bug has been marked a duplicate of bug 1831039 When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome -- 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/1990253 Title: On-screen keyboard fails to appear on Snap software Status in gnome-shell package in Ubuntu: New Bug description: I have 22.04.1 LTS on HP ProBook 4545s. When you make any text insertion box of browser or website active in a Snap software, for example in the latest Brave Snap package, tapping nor clicking a text insertion area does not bring up the keyboard. This can be worked around by enabling accessability icon and on-screen keyboard for forever in the upper system tray. If I an collect any diagnostic data for this please send me the instructions and I'll see what I can do. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox
** Changed in: mutter (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1989726 Title: Only a quarter of the screen showing in VirtualBox Status in mutter package in Ubuntu: Won't Fix Bug description: Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and restarted twice. I've tried Xubuntu and Kubuntu 22.04 and they both work without any errors. Screenshot here: https://i.stack.imgur.com/KI0YO.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990262] Re: Screen reset randomly when moving cursors
Moved to the kernel because flickering like that is always the kernel's fault/responsibility. There's nothing mutter can do to make sub-frame flickers. Please check bug 1958191 to see if it's the same issue fixed in 5.17.7 and later or by i915.enable_dc=0 intel_idle.max_cstate=2 If that's not the issue then when the flickering is happening next please run: lspci -k > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Package changed: mutter (Ubuntu) => linux-oem-5.17 (Ubuntu) ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Incomplete -- 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/1990262 Title: Screen reset randomly when moving cursors Status in linux-oem-5.17 package in Ubuntu: Incomplete Bug description: [Summary] The monitor occurs the flicker problem while moving the mouse if the external monitor is connected to type-c port via type-c-to-DP/HDMI dongle. [Steps to reproduce] 1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to type-c-port 2. Moving the mouse [Expected result] No broken screen while moving the mouse [Actual result] Screen broken sometimes [Failure rate] 2/2 - video record: https://drive.google.com/file/d/1Ad1I57IiAjcZzk423dmsAfpcsNKKrEF_/view?usp=sharing [Additional information] system-manufacturer: LENOVO system-product-name: ThinkStation P360 Ultra bios-version: S0FKT22A CPU: 12th Gen Intel(R) Core(TM) i5-12400T (12x) GPU: 00:02.0 Display controller [0380]: Intel Corporation Device [8086:4692] (rev 0c) 6f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] (rev a1) kernel-version: 5.17.0-1015-oem monitor: BenQ 4K EL2870U Sep 07 13:22:50 ubuntu gnome-shell[1853]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77d66170]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:22:50 ubuntu gnome-shell[1853]: ../clutter/clutter/clutter-actor.c:9279: Actor '[:0x557b77efc8e0]' tried to allocate a size of -2147483648.00 x -2147483648.00 Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b75686370] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712a730] is on because it needs an allocation. Sep 07 13:23:00 ubuntu gnome-shell[1853]: Can't update stage views actor [:0x557b7712c6c0] is on because it needs an allocation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1990262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988339] Re: Ubuntu doesn't change the keyboard layout
~$ cat /etc/default/keyboard # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="" BACKSPACE="guess" The configuration from "Settings" never was saved to "/etc/default/keyboard" ** Attachment added: "This configuration never was saved to /etc/default/keyboard" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1988339/+attachment/5617399/+files/Bildschirmfoto%20vom%202022-09-20%2009-21-58.png -- 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/1988339 Title: Ubuntu doesn't change the keyboard layout Status in evince package in Ubuntu: New Bug description: If you have more then 2 layouts then often after restart Ubuntu don't switch layouts. I started to see this problem maybe after Ubuntu 20.10(?) The problem have roots in the installation process. 3 weeks back I reinstalled Ubuntu Budgie. I choose German layout what was qwertZ. qwertZ is crazy uncomfortable if you migrate from English qwertY layout. So I replaced it with Germany qwertY. Now I have (1)English, (2)Russian, (3)German qwertY . But every second time I restart the laptop I get German qwertZ! Here is stackoverflow questions from other users https://unix.stackexchange.com/questions/627270/ubuntu-doesnt-change-the-keyboard-layout A workaround that I found is to open the Region & Language settings and change the order of the Input Sources. This workaround is temporary, so next time it happens I need to do that again (in my case is changing the order of 2 layouts in EN->RU placeholder simply by drag and drop and when it happens again, switch back RU->EN, so I guess the order itself doesn't matter). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Aug 31 15:28:40 2022 InstallationDate: Installed on 2022-07-02 (60 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1988339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990277] [NEW] Nautilus crashes when open a new window from the panel
Public bug reported: Nautilus can add it's favorites to the panel icon. So, the user can right-click on an icon to open any favorites folder. If a Nautilus windows is already open, opening any folder from favorites crashes nautilus. journalctl -e: сен 20 15:32:42 Compy kernel: nautilus[107750]: segfault at 0 ip sp 7ffe8815c688 error 14 in nautilus[5612a329f000+> сен 20 15:32:42 Compy kernel: Code: Unable to access opcode bytes at RIP 0xffd6. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 15:30:40 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/usr/bin/fish SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-06-08 (103 days ago) usr_lib_nautilus: file-roller3.42.0-1 nautilus-share 0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1990277 Title: Nautilus crashes when open a new window from the panel Status in nautilus package in Ubuntu: New Bug description: Nautilus can add it's favorites to the panel icon. So, the user can right-click on an icon to open any favorites folder. If a Nautilus windows is already open, opening any folder from favorites crashes nautilus. journalctl -e: сен 20 15:32:42 Compy kernel: nautilus[107750]: segfault at 0 ip sp 7ffe8815c688 error 14 in nautilus[5612a329f000+> сен 20 15:32:42 Compy kernel: Code: Unable to access opcode bytes at RIP 0xffd6. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 15:30:40 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/usr/bin/fish SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-06-08 (103 days ago) usr_lib_nautilus: file-roller3.42.0-1 nautilus-share 0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
"Is there a working work-around available?" Yes, install the Debian FireFox-esr which does not use snap. Google for: Ubuntu firefox esr https://ubuntuhandbook.org/index.php/2022/03/install-firefox-esr- ubuntu/ -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853007]
Alan is referring to the bug regarding appdata/local/temp/pidxxx folders : bug 1769423 This continues to be a problem in release version TB 102.2.2 win64 TB needs to stop creating permanent pid folders which contain read only copies of attachments that are stored permanently. Although you can edit the Properties to remove the read- only. But how many people know about the appdata>Local> Temp? Most people have appdata as a hidden folder and do not even know about it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 metric 600 169.254.0.0/16 dev wlp58
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
** Description changed:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel beta/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-media-
samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
- About the last point, it may be that unfortunately only those with newer
- generations of Intel CPUs will have luck with this, but it's still an
- uncertainty. So reports are highly welcome.
-
Currently it seems to work for all reporters on Xorg, but not for all
reporters on Wayland.
Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
- the main snap via [2]. Comments before #176 refer to candidate/hwacc,
- which is [3] and _should_ be roughly equivalent to [1], but I wouldn't
- be surprised if it turned out not to be.
+ the main snap via [2]. Comments before #176 refer to [3] and _should_ be
+ roughly equivalent to [1], but I wouldn't be surprised if it turned out
+ not to be.
[1]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
[2]:
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
[3]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel beta/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg, but not for all
reporters on Wayland.
Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
the main snap via [2]. Comments before #176 refer to [3] and _should_
be roughly equivalent to [1], but I wouldn't be surprised if it turned
out not to be.
[1]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
[2]:
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
[3]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168
--Original Bug report -
Libva is no longer working f
[Desktop-packages] [Bug 1514630] Re: Chromium DEV - new update disable all GPU optons on FGLRX driver
*** This bug is a duplicate of bug 1816497 *** https://bugs.launchpad.net/bugs/1816497 ** This bug has been marked a duplicate of bug 1816497 [snap] vaapi chromium no video hardware decoding -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1514630 Title: Chromium DEV - new update disable all GPU optons on FGLRX driver Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, From last time I use Chromium DEV PPA for Ubuntu and all GPU options work fine. Now after two or one latest update all GPU options in chrome:gpu is disabled - I have only software mode, not like before hardware accelerated. Only software... I try enable it but I can. I try log my browser in terminal: " x@x-Aspire-7551:~$ chromium-browser libva info: VA-API version 0.38.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so libva info: va_openDriver() returns -1 [9508:9508:1110/003050:FATAL:sandbox_seccomp_bpf_linux.cc(203)] Check failed: policy->PreSandboxHook(). #0 0x7f78d82a544e base::debug::StackTrace::StackTrace() #1 0x7f78d82c406e logging::LogMessage::~LogMessage() #2 0x7f78df86aa12 #3 0x7f78df869d82 #4 0x7f78df869fe4 #5 0x7f78df870d29 #6 0x7f78df8729b7 #7 0x7f78df30fee4 #8 0x7f78df30e401 content::ContentMain() #9 0x5573383c693a #10 0x7f78cecb1a40 __libc_start_main #11 0x5573383c67f9 Received signal 6 #0 0x7f78d82a544e base::debug::StackTrace::StackTrace() #1 0x7f78d82a552b #2 0x7f78cf06bd10 #3 0x7f78cecc6267 gsignal #4 0x7f78cecc7eca abort #5 0x7f78d82a4055 base::debug::BreakDebugger() #6 0x7f78d82c41a5 logging::LogMessage::~LogMessage() #7 0x7f78df86aa12 #8 0x7f78df869d82 #9 0x7f78df869fe4 #10 0x7f78df870d29 #11 0x7f78df8729b7 #12 0x7f78df30fee4 #13 0x7f78df30e401 content::ContentMain() #14 0x5573383c693a #15 0x7f78cecb1a40 __libc_start_main #16 0x5573383c67f9 r8: a4d9f5b7eaf0 r9: a4d9f5b7eae0 r10: 0008 r11: 0206 r12: 7ffe974d72b8 r13: 7ffe974d6e30 r14: r15: 7f78e0084b98 di: 2524 si: 2524 bp: 7ffe974d6dd0 bx: 7ffe974d72b0 dx: 0006 ax: cx: 7f78cecc6267 sp: 7ffe974d6a78 ip: 7f78cecc6267 efl: 0206 cgf: 0033 erf: trp: msk: cr2: [end of stack trace] [9455:9488:1110/003050:ERROR:browser_gpu_channel_host_factory.cc(132)] Failed to launch GPU process. " Also in chrome:gpu I have in log message: "Log Messages GpuProcessHostUIShim: The GPU process exited with code 256." Also look at my graphics feature in chrome:gpu: Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use force_cube_map_positive_x_allocation init_texture_max_anisotropy regenerate_struct_names scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Linux AMD drivers incorrectly return initial value of 1 for TEXTURE_MAX_ANISOTROPY: 348237 Applied Workarounds: init_texture_max_anisotropy Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Linux AMD drivers handle struct scopes incorrectly: 403957 Applied Workarounds: regenerate_struct_names Linux ATI drivers crash on binding incomplete cube map texture to FBO: 518889 Applied Workarounds: force_cube_map_positive_x_allocation ANyone know how to fix it? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 48.0.2552.0-0ubuntu1~ppa1~15.10.1 [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Nov 10 00:32:01 2015 InstallationDate: Installed on 2014-05-01
[Desktop-packages] [Bug 1526430] Re: [Touch] No touch works at all
** Summary changed:
- Change suggestion for touch support
+ [Touch] No touch works at all
** Tags added: desktop-touch patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1526430
Title:
[Touch] No touch works at all
Status in chromium-browser package in Ubuntu:
New
Bug description:
Right after installing 14.04 finger touch worked all right with
Chromium (Wacom touchscreen): I could at least scroll pages and go
back/forward. However, at some point, after one of updates, it
stopped. I have no idea how it was before, but following code added to
the /usr/bin/chromium-browser brings touch back:
finger_id=$(xinput list | grep "Finger touch")
if [ ${#finger_id} != 0 ]; then
finger_id=${finger_id#*id=}
finger_id=$(expr match "$finger_id" '\([0-9]*\).*')
CHROMIUM_FLAGS="$CHROMIUM_FLAGS --touch-devices=$finger_id"
fi
I'm not professional in coding, so this may be clumsy, but perhaps a
better version of the above can be added when the script is updated.
Attached, a patched version of the script.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1526430/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1547483] Re: chromium-browser selects the first entry in srcset element
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1547483 Title: chromium-browser selects the first entry in srcset element Status in chromium-browser package in Ubuntu: Incomplete Bug description: The chormium browser (v37) if showing the first entry in a srcset attribute for IMG tags. Given: http://codepen.io/anon/pen/zxPZYM Expected: largest image to be shown (running on Full HD res) Actual: First entry in the srcset list is displayed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917 ProcVersionSignature: Ubuntu 3.13.0-77.121~precise1-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 Date: Fri Feb 19 13:00:34 2016 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2016-01-22T23:46:52.310138 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1547483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544880] Re: video fullscreen playback emits keys (control/key sequences) into current foreground window
Please bump if still reproducible.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1544880
Title:
video fullscreen playback emits keys (control/key sequences) into
current foreground window
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
Playing a video in full-screen mode (html5) emits keys into foreground
("ghost keyboard" inputs).
These key sequences affect the currently selected/foregrounded Window, e.g.
the goneme-terminal flickers the text up and down, changes window focus and
inputs control characters scrambling the typed commandline.
Controlled typing on the commandline is nearly impossible this way, text is
garbled (see screenshot attachment).
Pausing the video stops this behaviour.
This happens on a fresh profile without any extensions/addons.
example youtube video: https://www.youtube.com/watch?v=JHEHPRDVEp4
I logged the keys with
xev 2>&1|while /bin/true ; do read ans; echo $ans;date -Ins ;done >
/tmp/xev.timestamped.log
and add the output here as attachment. From the log it seems to be
these type of repeating sequences (disregard beginning and end of
file, since it is mouse over xev movements):
2016-02-12T10:17:24,551960729+0100
MotionNotify event, serial 34, synthetic NO, window 0x601,
2016-02-12T10:17:24,553774616+0100
root 0xc4, subw 0x0, time 159126531, (41,126), root:(42,178),
2016-02-12T10:17:24,555947203+0100
state 0x0, is_hint 0, same_screen YES
2016-02-12T10:17:24,560815414+0100
2016-02-12T10:17:24,627034521+0100
MotionNotify event, serial 34, synthetic NO, window 0x601,
2016-02-12T10:17:24,629079758+0100
root 0xc4, subw 0x0, time 159126618, (41,125), root:(42,177),
2016-02-12T10:17:24,631013278+0100
state 0x0, is_hint 0, same_screen YES
2016-02-12T10:17:24,632850769+0100
Currently I doo not know how to debug this further, is there a
possibility to debug the video playback in chromium browser?
Thanks for looking into it,
Martin
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 48.0.2564.82-0ubuntu0.14.04.1.1108
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
Uname: Linux 3.19.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 12 09:41:13 2016
Desktop-Session:
'gnome-fallback'
'/etc/xdg/xdg-gnome-fallback:/usr/share/upstart/xdg:/etc/xdg'
'/usr/share/gnome-fallback:/usr/share/gnome:/usr/local/share/:/usr/share/'
EcryptfsInUse: Yes
Env:
'None'
':/home/martin/local/lib'
InstallationDate: Installed on 2016-01-12 (30 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Load-Avg-1min: 0.85
Load-Processes-Running-Percent: 0.5%
MachineType: LENOVO 4180AA6
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-49-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET76WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4180AA6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4180AA6:pvrThinkPadT420:rvnLENOVO:rn4180AA6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4180AA6
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
gconf-keys: /desktop/gnome/applications/browser/exec =
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser
%s\n'/desktop/gnome/url-handlers/https/enabled =
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser
%s\n'/desktop/gnome/url-handlers/http/enabled =
b'true\n'/desktop/gnome/session/required_components/windowmanager =
b''/apps/metacity/general/compositing_manager =
b''/desktop/gnome/interface/icon_theme =
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1544880/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535390] Re: Chromium's built-in PDF renderer crashes when rendering some files, takes unity down
This seems to have fixed itself. Tested for Unity and Ubuntu on Xorg. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1535390 Title: Chromium's built-in PDF renderer crashes when rendering some files, takes unity down Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium reliably crashes when opening some PDF files (not all of them). When it does, unity (compiz) is taken down with it and I'm taken back to the login screen. At that point logging in results in compiz seemingly crashing again, and a reboot is needed to allow logging in again. I'm attaching a PDF file that reliably triggers the crash. Note that the file renders fine in e.g. evince. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 47.0.2526.106-0ubuntu0.14.04.1.1107 ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20 Uname: Linux 3.16.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 18:15:10 2016 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2015-03-25 (299 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64+mac (20150218.1) Load-Avg-1min: 1.15 Load-Processes-Running-Percent: 0.3% MachineType: TOSHIBA Satellite A200 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic root=UUID=f7263bc4-72bc-441d-9b44-570c4df94a18 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03K01CCE:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A200 dmi.product.version: PSAE3E-03K01CCE dmi.sys.vendor: TOSHIBA gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b'' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2016-01-13T07:48:20.494539 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1535390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552298] Re: chromium-browser should depend on kmod
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1552298 Title: chromium-browser should depend on kmod Status in chromium-browser package in Ubuntu: Incomplete Bug description: The chromium-browser package should depend on the kmod package due to the following workaround in /usr/bin/chromium-browser: lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 There are situations in which chromium-browser can be installed without kmod already being installed such as in a container for Libertine (the convergence container for phones/tablets/future desktop). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1552298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625517] Re: Clicking inside address bar does not update PRIMARY buffer (middle-mouse clipboard)
** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low -- 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/1625517 Title: Clicking inside address bar does not update PRIMARY buffer (middle- mouse clipboard) Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When I click in the address bar once, the entire URL is selected. In most other applications, this is an indicator that my PRIMARY buffer [1] has been updated with the full URL. However, when I MMB-paste, the previous contents of the buffer appear. This has tripped me up on many occasions. Steps to reproduce: 1: Open a text editor, or any other recepticle for pasted text. 2: Select some text on a page. 3: Middle-click in the text editor, and verify that it's the text you selected in step 2. 4: Click the address bar in Chromium. The URL is highlighted. 5: Middle-click in the text editor again. 6: Hit Ctrl+z. Frustratedly go back to your browser. Click the address bar once, then again to deselect everything. Then drag or triple-click to select all. 7: Middle-click in the text editor again. Now it works. Expected results: In step 5, the full URL of the page you were visiting should have appeared. However, it's still the text you selected in step 2. I'm using Chromium version 52.0.2743.116 Built on Ubuntu , running on Ubuntu 16.04 (64-bit) [1]: I'm not shouting, this is what it's called. It's also known as the "middle-mouse clipboard". See also https://tronche.com/gui/x/icccm/sec-2.html#s-2.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1625517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625517] Re: Clicking inside address bar does not update PRIMARY buffer (middle-mouse clipboard)
Reported upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=1365943 -- 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/1625517 Title: Clicking inside address bar does not update PRIMARY buffer (middle- mouse clipboard) Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When I click in the address bar once, the entire URL is selected. In most other applications, this is an indicator that my PRIMARY buffer [1] has been updated with the full URL. However, when I MMB-paste, the previous contents of the buffer appear. This has tripped me up on many occasions. Steps to reproduce: 1: Open a text editor, or any other recepticle for pasted text. 2: Select some text on a page. 3: Middle-click in the text editor, and verify that it's the text you selected in step 2. 4: Click the address bar in Chromium. The URL is highlighted. 5: Middle-click in the text editor again. 6: Hit Ctrl+z. Frustratedly go back to your browser. Click the address bar once, then again to deselect everything. Then drag or triple-click to select all. 7: Middle-click in the text editor again. Now it works. Expected results: In step 5, the full URL of the page you were visiting should have appeared. However, it's still the text you selected in step 2. I'm using Chromium version 52.0.2743.116 Built on Ubuntu , running on Ubuntu 16.04 (64-bit) [1]: I'm not shouting, this is what it's called. It's also known as the "middle-mouse clipboard". See also https://tronche.com/gui/x/icccm/sec-2.html#s-2.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1625517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990287] [NEW] Two-finger right-click and drag causes additional click
Public bug reported: I've found a consistent issue since upgrading from 20.04 to 22.04 where performing a two-finger tap (to right click) and then quickly performing a single tap drag causes a click event on the release of the drag. One place this manifests is when in a browser, if you two-finger right-click on a link, then quickly (must be done quickly) drag the cursor over the menu (eg open in new tab). When the finger is released from the drag, it performs a click on the menu item. It also happens in other applications as far as I can tell. Not a critical bug, but very frustrating as the muscle memory means lots of mis-clicks. I've found the timing between the two-finger tap and one-finger drag must be small (fraction of a section) to trigger the behaviour. I've tried installing 22.04 fresh, with no change. I'm using a Lenovo Thinkpad Carbon X1 G9. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 14:16:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5] InstallationDate: Installed on 2022-09-19 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XWCTO1WW ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=ab25a65e-dd77-4b5c-bd5e-75691f427498 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1990287 Title: Two-finger right-click and drag causes additional click Status in xorg package in Ubuntu: New Bug description: I've found a consistent issue since upgrading from 20.04 to 22.04 where performing a two-finger tap (to right click) and then quickly performing a single tap drag causes a click event on the release of the drag. One place this manifests is when in a browser, if you two-finger right-click on a link, then quickly (must be done quickly) drag the cursor over the menu (eg open in new tab). When the finger is released from the drag, it performs a click on the menu item. It also happens in other applications as far as I can tell. Not a critical bug, but very frustrating as the muscle memory means lots of mis-clicks. I've found the timing between the two-finger tap and one-finger drag must be small (fraction of a section) to trigger the behaviour. I've tried installing 22.04 fresh, with no change. I'm using a Lenovo Thinkpad Carbon X1 G9. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Also, you can install the regular Firefox following this instructions. In this case, you will change the snap version for the .deb one. and it contains instructions for avoiding the re-installation of Firefox snap and for getting automated updates for the .deb version via unattended- upgrades: https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt- ubuntu-22-04 -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988686] Re: Read failure Photo SD Memory Card in USB
it's fixed in https://launchpad.net/ubuntu/+source/nautilus/1:43.0-1ubuntu1 ** Changed in: nautilus (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988686 Title: Read failure Photo SD Memory Card in USB Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: Tried to read my SD memory card in the USB slot. Nautilus responded with message box "Force Close" or "Wait". Nautilus is outputting the following messages to Syslog when trying to display the device. Sep 4 14:41:42 Desktopps nautilus[31175]: specified class size for type 'NautilusXContentBar' is smaller than the parent type's 'GtkInfoBar' class size Sep 4 14:41:42 Desktopps nautilus[31175]: g_once_init_leave: assertion 'result != 0' failed Sep 4 14:41:42 Desktopps nautilus[31175]: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_box_append: assertion 'GTK_IS_WIDGET (child)' failed Able to read this memory card in a Ubuntu 22.04 system. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 15:08:36 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1988686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1514484 Title: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes Status in chromium-browser package in Ubuntu: Fix Committed Bug description: You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever comes after the first space is going to be interpreted as an URL by the actual chromium binary. Easy repro: 1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg: $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init 2. Run chromium: $ /usr/bin/chromium-browser 3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'. The cause for this funny behavior is the lack of quotes around $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the script. I've tried working around it but couldn't, no amount of escaping and extra quotes seems to help if it's called like that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989131] Re: [snap] What about PDF MimeType in .desktop file?
** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1989131 Title: [snap] What about PDF MimeType in .desktop file? Status in chromium-browser package in Ubuntu: Fix Committed Bug description: I see with a recent commit (https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from- source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added more MimeType entries in the .desktop file. What about PDF, since Chromium has a pretty good built-in PDF viewer? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982349] Re: Manage energy profile settings
Hello Gabriel, or anyone else affected,
Accepted adsys into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: adsys (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
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/1982349
Title:
Manage energy profile settings
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
New
Status in adsys source package in Jammy:
Fix Committed
Bug description:
[Impact]
Adsys cannot currently manage GSettings power management keys, such
as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
* Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
* Double click on the last entry: Whether to hibernate ...
* Enable it, set the value to "hibernate"
* On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
* Observe the logs that indicate the parsing of the dconf key:
DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
* Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
This code is located in the dconf policy application manager and
restricted to it. The negative impact in case of a new bug will be
seen by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982348] Re: Describe if a key requires an Ubuntu Pro subscription
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1982348 Title: Describe if a key requires an Ubuntu Pro subscription Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Before applying policies, adsys checks for the existence of an Ubuntu Pro subscription. If not found, all keys with the exception of dconf keys are filtered, as they require Ubuntu Pro. Annotate the generated ADMX/ADML files with this information. [Test Plan] * Open the Group Policy Management Editor * Navigate to User Configuration > Administrative Templates > Ubuntu > Session Management > User Scripts > Logoff scripts * The description should contain the following line: An Ubuntu Pro subscription on the client is required to apply this policy. [Where problems could occur] This is a purely visual change that only impacts generated XML files. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982351] Re: [SRU] Backport adsys-windows binary package
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982330] Re: Cannot apply policies from uppercase class path like "MACHINE"
Hello Gabriel, or anyone else affected,
Accepted adsys into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: adsys (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
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/1982330
Title:
Cannot apply policies from uppercase class path like "MACHINE"
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
New
Status in adsys source package in Jammy:
Fix Committed
Bug description:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g.
Machine), but they are uppercase (e.g. MACHINE). This prevents any
GPOs from being applied.
This is a common occurence with GPOs created by Microsoft, like the
Default Domain Policy.
[Test Plan]
Reproduction:
* Mark the Default Domain Policy as active for the client, and set some
Ubuntu policy entries.
* Restart and/or manually sync the client machine.
* Observe the log message indicating that parsing the GPO failed:
Policy "Default Domain Policy" doesn't have any policy for class
"user" open
/var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol:
no such file or directory
* Observe that the Ubuntu policies were not applied.
To confirm the bug is fixed, repeat the steps above after applying the
fix, and the policies should be applied.
[Where problems could occur]
* Fixing this bug will allow adsys to parse, and possibly fail when
applying policies from an uppercase path, whereas before it silently
ignored them. Fixes for these potential bugs have also been submitted.
[Other Info]
The issue was initially reported on GitHub:
https://github.com/ubuntu/adsys/issues/346
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982330/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982343] Re: Cannot parse policy entries with unsupported types
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1982343 Title: Cannot parse policy entries with unsupported types Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Policies with unsupported types are currently unable to be parsed. Even if Ubuntu doesn't support these types we should still be able to parse the Microsoft ones - otherwise we are unable to apply any of the GPOs. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu supports a limited subset of types, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982342] Re: Cannot parse policies with empty values
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1982342 Title: Cannot parse policies with empty values Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] In addition to empty data, some Microsoft policy entries happen to have empty values as well. See the following entry: // [key;value;type;size;data] : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. This fails hard when parsing, returning an `empty value` error, rendering the remaining policies unparsable. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not support policy entries with empty values, we must still be able to parse them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982345] Re: Cannot parse policy entries with no data
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1982345 Title: Cannot parse policy entries with no data Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] The Default Domain Policy for Computers has a bunch of SystemCertificates keys with no data which adsys fails to parse. Here are some examples: Software\Policies\Microsoft\SystemCertificates\ACRS\Certificates Software\Policies\Microsoft\SystemCertificates\ACRS\CRLs Software\Policies\Microsoft\SystemCertificates\ACRS\CTLs Software\Policies\Microsoft\SystemCertificates\CA\Certificates Software\Policies\Microsoft\SystemCertificates\CA\CRLs Software\Policies\Microsoft\SystemCertificates\CA\CTLs Software\Policies\Microsoft\SystemCertificates\Disallowed\Certificates Software\Policies\Microsoft\SystemCertificates\Disallowed\CRLs Software\Policies\Microsoft\SystemCertificates\Disallowed\CTLs Software\Policies\Microsoft\SystemCertificates\DPNGRA\Certificates When examined with a hex editor, these look like the following: : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. The last field of the [key;value;type;size;data] stanza is entirely empty (semicolon succeeded immediately by a closing brace) whereas we expect a null character. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not have policy entries with no data, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy for Computers on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/384 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982347] Re: Username is case sensitive when applying policies on login
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1982347 Title: Username is case sensitive when applying policies on login Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] Reproduction: * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases * Observe multiple files created at /var/cache/adsys/policies With the fix applied, remove *all* cached policies at /var/cache/adsys/policies and attempt to login with different case combinations of the AD account, e.g.: administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz As root, check the contents of /var/cache/adsys/policies - you should only see a lowercase entry: administra...@warthogs.biz [Where problems could occur] Target name normalization is exercised by the code that dumps policies applied for a given user, and by the code that updates or creates a policy for a given user. If this happens to cause a bug, it will render the core part of adsys unusable. We believe this is highly unlikely given that in some cases, adsys already used the lowercase variant of the username to apply and display policies. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514484] Re: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1514484 Title: Chromium start-up script doesn't accept argument values with spaces in $CHROMIUM_FLAGS, cause is lack of quotes Status in chromium-browser package in Ubuntu: Fix Committed Bug description: You can't have arguments with spaces inside CHROMIUM_FLAGS, whatever comes after the first space is going to be interpreted as an URL by the actual chromium binary. Easy repro: 1. Set user's CHROMIUM_FLAGS with an argument containing spaces, eg: $ echo 'CHROMIUM_FLAGS=--user-agent="A B C"' > .chromium-browser.init 2. Run chromium: $ /usr/bin/chromium-browser 3. See 2 extra open tabs, one trying to open URL 'B', the other 'C'. The cause for this funny behavior is the lack of quotes around $CHROMIUM_FLAGS in the script installed in /usr/bin/chromium-browser -- it calls $LIBDIR/$APPNAME $CHROMIUM_FLAGS "$@" by the end of the script. I've tried working around it but couldn't, no amount of escaping and extra quotes seems to help if it's called like that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1514484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
can't find anything in the udev, removing brltty breaks some dependencies. Braille is good an all but I think somebody did not do their testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Hello,
beattie, le mar. 20 sept. 2022 15:21:36 -, a ecrit:
> can't find anything in the udev,
That's be in ./lib/udev/rules.d/85-brltty.rules, this line:
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
> I think somebody did not do their testing.
Not many people have a CH340/CH341-based adapter to notice the issue.
Samuel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1990189
Title:
brlttty claiming CH341 usbtty device blocking access
Status in brltty package in Ubuntu:
New
Bug description:
While this problem seems to have been fixed for FTDI and CP210 based
devices CH340/CH341 based (and possibly other USB serial adapters) are
unusable except by brltty.
[139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using
xhci_hcd
[139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86,
idProduct=7523, bcdDevice= 2.63
[139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
[139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
[139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
[139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as
/devices/virtual/input/input24
[139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while
'brltty' sets config #1
[139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected
from ttyUSB0
[139100.786136] ch341 1-2.1.2:1.0: device disconnected
[143917.740171] usb 1-2.1.2: USB disconnect, device number 17
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: brltty 6.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Sep 19 12:01:21 2022
InstallationDate: Installed on 2022-08-23 (27 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: brltty
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990293] [NEW] Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Public bug reported: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain this message . how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050 /boot/efi vfat defaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T/media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . see more details in french : https://forum.ubuntu-fr.org/viewtopic.php?id=2073925 ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain this message . how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 - - LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4 defaults 0 0 + LABEL=WD8PRO2 /Vidéos/WD8PRO2 + ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . + + + see more details in french : https://forum.ubuntu-fr.org/viewtopic.php?id=2073925 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain this message . how can i use trash again please ? iznobe@iznobe-PC:~$ cat /e
[Desktop-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
** Description changed: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain this message . how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . - - see more details in french : https://forum.ubuntu-fr.org/viewtopic.php?id=2073925 + Exactly same file systeme mounted on same directory , with same trash + directory is working fine on ubuntu 22.04 ** Description changed: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain this message . how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash - directory is working fine on ubuntu 22.04 + directory is working fine on ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain this message . how can i use
[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Might it be the case that I somehow removed or emptied /etc/modprobe.d/blacklist.conf ? --- pre --- # https://askubuntu.com/a/67028/289138 $ dpkg -S /etc/modprobe.d/blacklist.conf dpkg -S /etc/modprobe.d/blacklist.conf $ sudo apt install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" kmod --- /pre --- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p
[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Might i have emptied or removed /etc/modprobe.d/blacklist.conf by mistake? It was awfully empty!? --- pre --- # https://askubuntu.com/a/67028/289138 $ dpkg -S /etc/modprobe.d/blacklist.conf kmod: /etc/modprobe.d/blacklist.conf $ sudo apt install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" kmod ... --- /pre --- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Tags added: foundations-triage-discuss -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
** Description changed: Hi , when i delete a file where is in another partition than " / " or - mounted in /media/ , i obtain this message . + mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
I'm not sure if this problem is happening on Linux Mint 21 or Ubuntu 22.04.1. While Linux Mint is based on Ubuntu, it is not the same as Ubuntu, and may have behaviors (and bugs!) that differ from Ubuntu's. Could you clarify which Linux distro you're experiencing this problem on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990110] [NEW] package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10
You have been subscribed to a public bug: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Sep 16 16:04:12 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-09-16 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 Snap: firefox 104.0.2-1 (latest/stable) Snap.Changes: no changes found Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 https://bugs.launchpad.net/bugs/1990110 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990263] Re: bamfdaemon crashes with libwnck3 43.0-1
https://gitlab.gnome.org/GNOME/libwnck/-/merge_requests/46 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: New Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 Happens when running gnome-xorg/x11 session under gnome-shell 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
i have this probleme only on ubuntu 22.04.1 LTS AND on linux mint 21 . i have tested on ubuntu 20.04 and all works fine . i have a debian testing , if you want , i can do the same things to see if the problem is still present on this OS . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990110] Re: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10
** Package changed: ubuntu => firefox (Ubuntu) -- 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/1990110 Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 Status in firefox package in Ubuntu: New Bug description: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Sep 16 16:04:12 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-09-16 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 Snap: firefox 104.0.2-1 (latest/stable) Snap.Changes: no changes found Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990313] [NEW] [FFe] Sync Debian pipewire packaging adding new system group
Public bug reported: I am requesting a Feature Freeze Exception to sync Debian's packaging change for pipewire that adds a new 'pipewire' system group with tweaks to system resource limits. The new 'pipewire' group is not used by default, but it's available for users to opt into if they think they need it. Since I'm not familiar with the resource limits, I wanted to get confirmation from people who understand the impact of this change and whether it's appropriate for Ubuntu 22.10 now. https://salsa.debian.org/utopia-team/pipewire/-/commit/a8fd8933 https://salsa.debian.org/utopia-team/pipewire/-/commit/8052ea41 https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance- tuning#rlimits ** Affects: pipewire (Ubuntu) Importance: Wishlist Status: New ** Tags: kinetic upgrade-software-version ** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1990313 Title: [FFe] Sync Debian pipewire packaging adding new system group Status in pipewire package in Ubuntu: New Bug description: I am requesting a Feature Freeze Exception to sync Debian's packaging change for pipewire that adds a new 'pipewire' system group with tweaks to system resource limits. The new 'pipewire' group is not used by default, but it's available for users to opt into if they think they need it. Since I'm not familiar with the resource limits, I wanted to get confirmation from people who understand the impact of this change and whether it's appropriate for Ubuntu 22.10 now. https://salsa.debian.org/utopia-team/pipewire/-/commit/a8fd8933 https://salsa.debian.org/utopia-team/pipewire/-/commit/8052ea41 https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance- tuning#rlimits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1990313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950822] Re: simple-scan improperly sets scanned image size
This bug still occurs in Xubuntu 22.04.1, Simple Scan version 42.1. Now when the paper size is set to automatic, a letter-sized sheet scanned from the platen results in black filler to legal size at the bottom of the scan. Is this bug ever going to be addressed or even checked for confirmation, or is it too low a priority at this time? Just asking, not accusing or demanding. If you need more information, feel free to let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1950822 Title: simple-scan improperly sets scanned image size Status in simple-scan package in Ubuntu: New Bug description: This is a follow-on to bug 1916550, which expired with no action taken, despite my supplying you with all the information you requested. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy simple-scan simple-scan: Installed: 40.5-1 Candidate: 40.5-1 Version table: *** 40.5-1 500 500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status I have attached a debug log generated from the scans, and I will also be attaching the relevant screenshots, one at a time n the next 6 comments. What I expected to happen is simply this: When I set the Preference for page-size to Automatic, I expect the pages to scan as platen-sized for platen scans and legal sized for feeder scans. When I set the Preference for page-size to Letter, I expect to get all letter sized scans with no excess junk in the image. Here is what happens: Start simple-scan. Set Prefereneces to page size: Automatic (attachment #1) Scan an image on the platen, then scan a text, also on the platen (attachment #2) - Note that both images are the correct size - letter+minimal extra (A4?) Scan a text via the feeder, then scan an image through the feeder (attachment #3) - Note that the scans are both the same size - letter+ Set Preferences to page size Letter (attachment #4) Scan an image page on the platen, then scan an image on the platen (attachment #5) - Note that the image scan is correctly coming out as a letter-sized page, but the text has a black box filling in a legal size page under the actual letter size paper. Scan a text page through the feeder, then an image page through the feeder (attachment #6) - Note these are both the correct letter size. The command line I used to get this log was: $ simple-scan -d &> scan.log Log attached here. Please fix this. I will note that one of the issues I wrote bug 1916550 has been solved, but offhand I don't remember which. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1950822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980545] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1980545 Title: Update evolution-data-server to 3.44.4 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.4/NEWS The current version in Ubuntu 22.04 LTS is 3.44.2. Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980545] Re: Update evolution-data-server to 3.44.4
This bug was fixed in the package evolution-data-server - 3.44.4-0ubuntu1 --- evolution-data-server (3.44.4-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1980545) -- Nathan Pratta Teodosio Wed, 06 Jul 2022 10:46:37 -0300 ** Changed in: evolution-data-server (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1980545 Title: Update evolution-data-server to 3.44.4 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.4/NEWS The current version in Ubuntu 22.04 LTS is 3.44.2. Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
no such file as *brltty.rules" in my udev. What I did that seems to work is: sudo systemctl stop brltty-udev.service sudo systemctl mask brltty-udev.service sudo systemctl stop brltty.service sudo systemctl disable brltty.service Not sure if this is best or even a good idea but at least it stops brltty from stealing my serial port. Since I don't use brltty it does not hurt me that brltty can't coexist with my CH340 serial port. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: New Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917313] Re: New 2.36 serie requires a new ABI
I'm closing this bug since I've updated our version tracker to no longer alert to the new series. gtk4 no longer uses atk so the new series of atkmm because orphaned. https://gitlab.gnome.org/GNOME/atkmm/-/issues/4 ** Changed in: atkmm1.6 (Ubuntu) Status: Triaged => Fix Released ** Bug watch added: gitlab.gnome.org/GNOME/atkmm/-/issues #4 https://gitlab.gnome.org/GNOME/atkmm/-/issues/4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to atkmm1.6 in Ubuntu. https://bugs.launchpad.net/bugs/1917313 Title: New 2.36 serie requires a new ABI Status in atkmm1.6 package in Ubuntu: Fix Released Bug description: The source package should be renamed for that serie Skipping 2.28.1 which is only including build system changes has fails to build 'automake: error: cannot open < build/dist-changelog.am: No such file or directory' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atkmm1.6/+bug/1917313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989714] Re: FFE: Switch dependencies from webkitgtk 4.0 to 4.1
We can postpone to 23.04. I can still work on the Debian side even if we aren't progressing on the Ubuntu side. Thanks for the review. I'll go ahead and close this. ** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1989714 Title: FFE: Switch dependencies from webkitgtk 4.0 to 4.1 Status in webkit2gtk package in Ubuntu: Won't Fix Bug description: Impact -- The webkit2gtk source package provides 3 different API builds: - 4.0 for GTK3 using libsoup2 - 4.1 for GTK3 using libsoup3 (otherwise same as 4.0) - 5.0 for GTK4 using libsoup3 I am requesting a Feature Freeze Exception to be able to switch dependencies from 4.0 to 4.1 for Ubuntu 22.10 The Desktop Team has an outstanding todo item to stop using libsoup2 in main. We got more than halfway done for Ubuntu 22.10 but still won't finish for 22.10, even with this Feature Freeze Exception but it gets us closer. https://people.canonical.com/~ubuntu-archive/transitions/html/libsoup3-main.html It's bad for security updates that we need to do so many builds as part of the webkit2gtk source package. We still won't be able to drop the 4.0 build for 22.10 but this gets us closer for 23.04. Affected Packages - https://people.canonical.com/~ubuntu-archive/transitions/html/webkit2gtk-4.0.html Example --- https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/32183b4 https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/fc58345 Many packages will also need their meson.build/configure.ac/CMakeLists.txt patches to look for 4.1 instead of 4.0 Future Goals Stop building the webkitgtk 4.0 API for Ubuntu 23.04 Stop using libsoup2 in main for Ubuntu 23.04 Stop building libsoup2 for Ubuntu 23.10 Debian will begin freezing in early January and will be frozen for several months while they prepare for the Debian 12 release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1989714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990287] Re: Two-finger right-click and drag causes additional click
It sounds like you're moving too fast for the default tap-to-click thresholds :) I would recommend disabling tap-to-click in Settings so that only physical clicks of the pad are used as button press events. If you need very accurate, very fast input then always use physical buttons. ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Package changed: xorg (Ubuntu) => libinput (Ubuntu) ** Changed in: libinput (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1990287 Title: Two-finger right-click and drag causes additional click Status in libinput package in Ubuntu: Opinion Bug description: I've found a consistent issue since upgrading from 20.04 to 22.04 where performing a two-finger tap (to right click) and then quickly performing a single tap drag causes a click event on the release of the drag. One place this manifests is when in a browser, if you two-finger right-click on a link, then quickly (must be done quickly) drag the cursor over the menu (eg open in new tab). When the finger is released from the drag, it performs a click on the menu item. It also happens in other applications as far as I can tell. Not a critical bug, but very frustrating as the muscle memory means lots of mis-clicks. I've found the timing between the two-finger tap and one-finger drag must be small (fraction of a section) to trigger the behaviour. I've tried installing 22.04 fresh, with no change. I'm using a Lenovo Thinkpad Carbon X1 G9. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 14:16:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5] InstallationDate: Installed on 2022-09-19 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XWCTO1WW ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=ab25a65e-dd77-4b5c-bd5e-75691f427498 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1990287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990287] Re: Two-finger right-click and drag causes additional click
** Changed in: libinput (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1990287 Title: Two-finger right-click and drag causes additional click Status in libinput package in Ubuntu: Confirmed Bug description: I've found a consistent issue since upgrading from 20.04 to 22.04 where performing a two-finger tap (to right click) and then quickly performing a single tap drag causes a click event on the release of the drag. One place this manifests is when in a browser, if you two-finger right-click on a link, then quickly (must be done quickly) drag the cursor over the menu (eg open in new tab). When the finger is released from the drag, it performs a click on the menu item. It also happens in other applications as far as I can tell. Not a critical bug, but very frustrating as the muscle memory means lots of mis-clicks. I've found the timing between the two-finger tap and one-finger drag must be small (fraction of a section) to trigger the behaviour. I've tried installing 22.04 fresh, with no change. I'm using a Lenovo Thinkpad Carbon X1 G9. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 20 14:16:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d5] InstallationDate: Installed on 2022-09-19 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XWCTO1WW ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=ab25a65e-dd77-4b5c-bd5e-75691f427498 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1990287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981722] Re: Update gjs to 1.72.1
** Changed in: gjs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1981722 Title: Update gjs to 1.72.1 Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable series associated with GNOME 42 https://gitlab.gnome.org/GNOME/gjs/-/blob/1.72.2/NEWS The current version of gjs in Ubuntu 22.04 LTS is 1.72.0. 2 of the bugfixes from 1.72.1 are already in Ubuntu 22.04. One of the others fixes a memory leak. Test Case 1 - Install the update Log out Log back in GNOME Shell should still work well Test Case 2 --- Verify that the gjs apps still run ok: - gnome-books - gnome-characters - gnome-maps - gnome-sound-recorder - gnome-sushi - gnome-weather Test Case 3 --- gjs has build tests and autopkgtests (installed tests). Those should all complete successfully. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. gjs is part of core GNOME and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1981722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960954] Re: Update gvfs to 1.50
** Changed in: gvfs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1960954 Title: Update gvfs to 1.50 Status in gvfs package in Ubuntu: Fix Released Bug description: gvfs 1.50 switched to libsoup3 which we will not be including in Ubuntu 22.04 LTS.2 We should stay with the 1.48 series unless we want to revert this commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/beaaf78 https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1960954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Tags added: originate-from-1989842 sutton -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] [NEW] [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
Public bug reported:
> If the upload is a new upstream microrelease, the relevant part of the
upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the
same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball
merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
> request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
TBC, I'll provide soon.
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
** Affects: oem-priority
Importance: High
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
TBC, I'll provide soon.
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-
[Desktop-packages] [Bug 1990312] [NEW] Can't change desktop language in Ubuntu 22.04
You have been subscribed to a public bug: I initially installed Ubuntu 22.04 with the English language. Now, I'd like to use the Ubuntu desktop in the German language. I believe I've done everything needed. I rebooted of course. The login screen is now in German, but my user desktop is still in English, except the calendar showing the date. See the attached screenshot. Here is the output of the "locale" command: LANG=de_DE.UTF-8 LANGUAGE=en LC_CTYPE=en_US.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Am I the only one having this issue? Thanks in advance Michael ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Can't change desktop language in Ubuntu 22.04 https://bugs.launchpad.net/bugs/1990312 You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990312] Re: Can't change desktop language in Ubuntu 22.04
Set the package to "ubuntu-meta" containing "ubuntu-desktop" ** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1990312 Title: Can't change desktop language in Ubuntu 22.04 Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I initially installed Ubuntu 22.04 with the English language. Now, I'd like to use the Ubuntu desktop in the German language. I believe I've done everything needed. I rebooted of course. The login screen is now in German, but my user desktop is still in English, except the calendar showing the date. See the attached screenshot. Here is the output of the "locale" command: LANG=de_DE.UTF-8 LANGUAGE=en LC_CTYPE=en_US.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Am I the only one having this issue? Thanks in advance Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990345] [NEW] gnome shell keeps growing in size/ram
Public bug reported: every 2 or 3 days I have to alt+F2 and "r" to restart gnome-shell to release ram, because it grows and grows until it starts swapping. Restarting gives me another 2 or 3 days of breathing room :) and then rinse and repeat. lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 apt-cache policy gnome-shell gnome-shell: Installed: 42.4-0ubuntu0.22.04.1 Candidate: 42.4-0ubuntu0.22.04.1 Version table: *** 42.4-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages gnome-extensions list gsconn...@andyholmes.github.io ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:18:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1990345 Title: gnome shell keeps growing in size/ram Status in gnome-shell package in Ubuntu: New Bug description: every 2 or 3 days I have to alt+F2 and "r" to restart gnome-shell to release ram, because it grows and grows until it starts swapping. Restarting gives me another 2 or 3 days of breathing room :) and then rinse and repeat. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy gnome-shell gnome-shell: Installed: 42.4-0ubuntu0.22.04.1 Candidate: 42.4-0ubuntu0.22.04.1 Version table: *** 42.4-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages gnome-extensions list gsconn...@andyholmes.github.io ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:18:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990346] [NEW] gnome terminal window shrinks in size on every maximize/restore cicle
Public bug reported: every time I maximize a terminal window and return it to the restored size, it shrinks in size every just slightly. I would expect it to return to the previous size as it was before I maximized. lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.44.0-1ubuntu1 Candidate: 3.44.0-1ubuntu1 Version table: *** 3.44.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:22:50 2022 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1990346 Title: gnome terminal window shrinks in size on every maximize/restore cicle Status in gnome-terminal package in Ubuntu: New Bug description: every time I maximize a terminal window and return it to the restored size, it shrinks in size every just slightly. I would expect it to return to the previous size as it was before I maximized. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.44.0-1ubuntu1 Candidate: 3.44.0-1ubuntu1 Version table: *** 3.44.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:22:50 2022 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1990346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990345] Re: gnome shell keeps growing in size/ram
Thanks for the bug report. Four possible causes of memory leaks come to mind: 1. Unsupported extensions like gsconn...@andyholmes.github.io - they can still leak even when disabled. So please ensure the extension has been fully deleted, and then log in again. 2. If you use the screenshot feature then bug 1973638 is a major leaker (fix coming in gnome-shell 42.5). 3. Nvidia users also report bug 1974029 but that's graphics memory only. It won't show up in 'top' or 'ps'. 4. Judging by other bug reports I suspect there might be leaks in ubuntu-appindicat...@ubuntu.com so try disabling that one. But it's not been confirmed. If the problem still occurs after considering all of the above then next time it is noticeable please run: ps auxw | grep gnome-shell > psgs.txt journalctl -b0 > journal.txt and attach the resulting text files here. Also, to avoid "me too" comments from other users clouding the issue I will make this bug private until the cause of the problem has been found. ** Information type changed from Public to Private ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: gnome-shell-leak -- 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/1990345 Title: gnome shell keeps growing in size/ram Status in gnome-shell package in Ubuntu: Incomplete Bug description: every 2 or 3 days I have to alt+F2 and "r" to restart gnome-shell to release ram, because it grows and grows until it starts swapping. Restarting gives me another 2 or 3 days of breathing room :) and then rinse and repeat. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy gnome-shell gnome-shell: Installed: 42.4-0ubuntu0.22.04.1 Candidate: 42.4-0ubuntu0.22.04.1 Version table: *** 42.4-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages gnome-extensions list gsconn...@andyholmes.github.io ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:18:15 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990346] Re: gnome terminal window shrinks in size on every maximize/restore cicle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1288655, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1288655 Terminal height shrinks - repeatedly restored shorter than the previous height -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1990346 Title: gnome terminal window shrinks in size on every maximize/restore cicle Status in gnome-terminal package in Ubuntu: New Bug description: every time I maximize a terminal window and return it to the restored size, it shrinks in size every just slightly. I would expect it to return to the previous size as it was before I maximized. lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.44.0-1ubuntu1 Candidate: 3.44.0-1ubuntu1 Version table: *** 3.44.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 Uname: Linux 5.19.2-051902-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 06:22:50 2022 InstallationDate: Installed on 2019-07-26 (1152 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-terminal UpgradeStatus: Upgraded to jammy on 2022-08-19 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1990346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971752] Re: Toggling F11 for fullscreen reduces the restored window size
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 ** This bug is no longer a duplicate of bug 1947606 Unmaximizing window results in different number of rows from before maximizing it ** This bug has been marked a duplicate of bug 1288655 Terminal height shrinks - repeatedly restored shorter than the previous height -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1971752 Title: Toggling F11 for fullscreen reduces the restored window size Status in gnome-terminal package in Ubuntu: New Bug description: When I open a Gnome Terminal window at a given size (say 80 columns x 24 rows), press F11 to go full-screen, and then press F11 to restore the window to it's original size, it will be a bit smaller! It will lose both height and width. If I keep toggling with F11, the window will reduce to 3 lines and... I'm not sure exactly how many columns, but it's less than it had. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 18:03:50 2022 InstallationDate: Installed on 2022-04-26 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1971752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947606] Re: Unmaximizing window results in different number of rows from before maximizing it
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1288655, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1288655 Terminal height shrinks - repeatedly restored shorter than the previous height -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1947606 Title: Unmaximizing window results in different number of rows from before maximizing it Status in gnome-terminal package in Ubuntu: Confirmed Bug description: When having e.g. a 7 rows high window (with two tabs) and maximizing + unmaximizing it, the result is a 6 rows high window. Repeat it and it goes to 5, 4, and finally 3 rows in height. It doesn't shrink past 3 rows. It is especially noticeable with a long narrow window along the bottom of the screen, where the distance to the bottom screen edge increases every time the window height shrinks. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-terminal 3.38.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 17:19:44 2021 InstallationDate: Installed on 2020-10-30 (353 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to impish on 2021-09-17 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1947606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
** Tags removed: hirsute impish ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
