[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
Proposed fix here:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20449
--
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
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
FWIW the mutter workaround doesn't work for this issue.
--
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
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
This bug was fixed in the package language-selector - 0.220 --- language-selector (0.220) lunar; urgency=medium * data/pkg_depends, fontconfig/64-language-selector-prefer.conf: - Make Noto Sans Sinhala and Noto Serif Sinhala default fonts for rendering Sinhala (LP: #2000551). * Bump year in d/copyright * Bump Standards-Version to 4.6.2 -- Gunnar Hjalmarsson Wed, 28 Dec 2022 20:27:29 +0100 ** Changed in: language-selector (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: In Progress Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from jammy-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000649] [NEW] Xorg crashes or freezes
Public bug reported: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 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.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashes or freezes Status in xorg package in Ubuntu: New Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and
[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
> Ah! i (or we: sri lankan ubuntu users) need this replacement for all > other editions / desktops. I will make the change for Ubuntu 22.04 — our latest LTS — besides the current development version. As regards other desktops, all the official Ubuntu flavors will be affected by this change in language-selector- common. ** Description changed: + [ Impact ] + + The current default font for Sinhala (LKLUG) is unmaintained and comes + with issues. Noto offers Sinhala fonts with significantly higher + quality. + + fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of + changing that, the proposed change makes fontconfig give Noto Sans + Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and + that — together with installation of fonts-noto-core — seems to be + sufficient to achieve the desired result. + + [ Test Plan ] + + * Install language-selector-[common,gnome] from jammy-proposed. + + * Open Language Support and install the Sinhala language. + + * Open a terminal window and run this command: + + fc-match -a | grep -E 'LKLUG|Sinhala' + + * Confirm that Noto Sans Sinhala is listed before LKLUG. + + [ Where problems could occur ] + + No real problem in sight. Some Sinhala speaking users with fonts-noto- + core installed will indeed see a surprise change when it starts to + render Sinhala via Noto fonts instead of LKLUG. But that surprise ought + to make them happy. :) + + [ Original description ] + **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment - Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process ** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: language-selector (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: ubuntu-meta (Ubuntu Jammy) ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: language-selector (Ubuntu) Importance: Undecided => Wishlist ** Changed in: language-selector (Ubuntu) Status: New => Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: language-selector (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: language-selector (Ubuntu Jammy) Status: New => In Progress ** Changed in: language-selector (Ubuntu Jammy) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: In Progress Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher
[Desktop-packages] [Bug 2000644] [NEW] switching workspaces with shortcut sometimes freezes screen
Public bug reported: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 ** 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/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in gnome-shell package in Ubuntu: New Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260226] Re: Xorg layout switching shortcut doesn't update indicator
I'm seeing the same behaviour in a freshly installed Ubuntu 22.04.1 with
Wayland, where alt+shift layout switching was enabled with gnome-tweaks.
The layout itself switches on alt+shift but the layout indicator is
stuck showing the original layout. Switching with the default
super+space keybinding updates the layout indicator as well as the
layout. So I'm thinking this might be a broader issue, which also
includes e.g. https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1779327.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1260226
Title:
Xorg layout switching shortcut doesn't update indicator
Status in Indicator keyboard:
Confirmed
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
When I press the classic Xorg shortcut of "Alt+Shift" to switch the
keyboard layout from English to Greek, the layout changes but the
indicator is still showing "En".
If I use the new indicator-keyboard shortcut of "Win+Space", then
everything is fine.
So it appears that indicator-keyboard doesn't detect layout changes
caused by the Xorg layout switching shortcuts.
I'm including some information:
$ lsb_release -sc
trusty
$ dpkg-query -W indicator-keyboard
indicator-keyboard0.0.0+14.04.20131125-0ubuntu1
$ egrep -v '^#|^$' /etc/default/keyboard
XKBMODEL="pc105"
XKBLAYOUT="us,gr"
XKBVARIANT=","
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete+ledscroll(group_lock)"};
xkb_symbols { include
"pc+us+gr:2+inet(evdev)+group(alt_shift_toggle)"};
xkb_geometry { include "pc(pc105)" };
};
$ echo $DESKTOP_SESSION
gnome-fallback
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1260226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495190] Re: GNOME Shell shows outdated battery level for about a minute after a resume
Invalidating remaining task as other expired along time ago
** Changed in: ubuntu-gnome
Status: Incomplete => Invalid
--
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/1495190
Title:
GNOME Shell shows outdated battery level for about a minute after a
resume
Status in Ubuntu GNOME:
Invalid
Status in gnome-shell package in Ubuntu:
Expired
Status in gnome-shell source package in Wily:
Expired
Bug description:
Steps to reproduce:
1. Let the battery run down so only 1 bar is showing (for dramatic effect).
2. Suspend the laptop
3. Plug in A/C power
4. Let the laptop charge overnight
5. Resume the laptop
Expected behavior:
- The battery level shows 100%
Actual behavior:
- The battery level shows 1 bar, leading to thoughts like "omg did I
forget to plug it in? is my A/C charger broken?", and then, about 60
seconds later, suddenly jumps to 100%.
Since step 4 is rather long, for ease of reproduction you can use a different
method:
1. Unplug A/C power, verify that the battery icon changes accordingly
2. Suspend laptop
3. Plug A/C power
4. Resume laptop
Expect: battery icon shows A/C power is on
Actual: battery icon shows battery for ~60 seconds, until the next poll
interval, leading to the same kinds of stressful thoughts ("omg is it broken?
did I forget to plug the other end into a wall outlet?").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1495190/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000637] Re: Xorg freeze
See XorgLogOld.txt, this seems to be related to my KVM and the Nvidia driver thinks it can't find any valid display modes. This was not seen on Xubuntu 20.04 and the KVM seems to be working okay with other systems. -- 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/2000637 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Since a fresh install of Xubuntu 22.04 sometimes X launches to a white screen, other times I get a black screen. Restarting X seems to help sometimes. I turned display power management off and the problem persists. The system is responsive and usually I can still get to the text console. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Wed Dec 28 09:43:46 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:881a] InstallationDate: Installed on 2022-12-17 (11 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=2725c865-441b-4349-8465-3d167dcfc812 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.7 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.7:bd06/30/2010:br8.15:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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/xorg/+bug/2000637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000637] [NEW] Xorg freeze
Public bug reported: Since a fresh install of Xubuntu 22.04 sometimes X launches to a white screen, other times I get a black screen. Restarting X seems to help sometimes. I turned display power management off and the problem persists. The system is responsive and usually I can still get to the text console. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Wed Dec 28 09:43:46 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:881a] InstallationDate: Installed on 2022-12-17 (11 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=2725c865-441b-4349-8465-3d167dcfc812 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.7 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.7:bd06/30/2010:br8.15:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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 freeze jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2000637 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Since a fresh install of Xubuntu 22.04 sometimes X launches to a white screen, other times I get a black screen. Restarting X seems to help sometimes. I turned display power management off and the problem persists. The system is responsive and usually I can still get to the text console. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX
[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
>Can you please install language-selector-gnome and language-selector- common from the PPA I mentioned, and let us know what you think. I tested it on new ubuntu 22.10 VM and thank you. >I see that LKLUG is pulled by default by several meta packages, and I'd prefer to avoid stopping them from doing that. $ apt rdepends fonts-lklug-sinhala~fonts-lklug-sinhala~Reverse Depends: ubuntu-desktop, xubuntu-desktop, xubuntu-core, vanilla-gnome-desktop, ubuntustudio-desktop, ubuntukylin-desktop, ubuntucinnamon-desktop, ubuntu-unity-desktop, ubuntu-mate-desktop, ubuntu-mate-core, ubuntu-budgie-desktop, lubuntu-desktop, kubuntu-desktop, ubuntu-desktop-minimal Ah! i (or we: sri lankan ubuntu users) need this replacement for all other editions / desktops. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed ** Changed in: mutter (Ubuntu) Status: Confirmed => New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions Status in mutter package in Ubuntu: Confirmed Bug description: Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem didn't occur in previous version of ubuntu based on xorg. Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc or when heavy operations are done on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1982560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000626] Re: cp command loop when using ntfs3 package
Contents of errors in the journal log and remember sudo smartctl -a /dev/sdb | egrep "Pending|Reallocated" 5 Reallocated_Sector_Ct 0x0033 028 028 036Pre-fail Always FAILING_NOW 2978 197 Current_Pending_Sector 0x0012 100 100 000Old_age Always - 0 ** Attachment added: "Tjour1.txt" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+attachment/5638111/+files/Tjour1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package Status in evince package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. Second try on LEGACY computer: I make a script based on cp command. I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. @b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 a@b:~$ First disk root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 28 11:35:15 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-08-11 (138 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Desktop-packages] [Bug 2000626] Re: cp command loop when using ntfs3 package
Contents of full journal logs ** Attachment added: "journalctl -b" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000626/+attachment/5638110/+files/Tjour0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package Status in evince package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. Second try on LEGACY computer: I make a script based on cp command. I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. @b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 a@b:~$ First disk root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 28 11:35:15 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-08-11 (138 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash 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/2000626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 373113]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/373113 Title: [upstream] Writer imports Hebrew Word .doc file and missing some text after page break Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/373113/+attachment/2154880/+files/example.doc && lowriter -nologo example.doc Search for the word "סיכום המחקרים", LO finds it and highlights it. 4) What happens instead is it finds it, but does not highlight it. As well, the text does not appear in the document. WORKAROUND: Convert the document to .odt: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/373113/+attachment/2154880/+files/example.doc && unoconv --listener && unoconv -f odt example.doc && lowriter -nologo example.odt apt-cache policy unoconv unoconv: Installed: 0.3-6 Candidate: 0.3-6 Version table: *** 0.3-6 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages 100 /var/lib/dpkg/status Original Reporter Comments: It's a Microsoft Word document. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: openoffice.org-core 1:3.0.1-9ubuntu3 ProcEnviron: PATH=(custom, user) LANG=he_IL.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/373113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000626] [NEW] cp command loop when using ntfs3 package
Public bug reported: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. Second try on LEGACY computer: I make a script based on cp command. I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. @b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 a@b:~$ First disk root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 28 11:35:15 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-08-11 (138 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (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 evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package Status in evince package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On
[Desktop-packages] [Bug 2000459] Re: Only shows half of menu if right-clicks mouse on the desktop if scaling screen
** Tags added: originate-from-1996284 somerville -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000459] Re: Only shows half of menu if right-clicks mouse on the desktop if scaling screen
** Tags added: originate-from-1993491 -- 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/2000459 Title: Only shows half of menu if right-clicks mouse on the desktop if scaling screen Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: [Steps] 1. Cold boot with 4K monitor 2. Open Settings -> Display (Current resolution is 3840x2160, scaling: 100%) 3. Right click, the menu is well 4. Adjust the scaling to be 200%, 300%, 400% 5. Right click, the menu is broken [Actual behavior] Issue can be observed in the following combination - 36840x2160 - scaling: 200%, 300%, 400% - 2560x1440 - scaling: 200%, 300% - 1920x1080 - scaling: 200% To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
The attachment "0001-supply-Consistently-use-90-threshold-to-consider- a-b.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: In Progress Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
