Bug#989831: konsole: Bitmap fonts rendered incorrectly if display scaling is enabled

Package: konsole Version: 4:20.12.3-1 Followup-For: Bug #989831 X-Debbugs-Cc: t...@seoss.co.uk On 16/06/2021 05:07, Norbert Preining wrote: > On Mon, 14 Jun 2021, Tim Small wrote: >> instead each character is rendered with large amounts >> of surrounding space. >> >> T

Bug#989834: konsole: Only possible to select the smallest available size for OpenType Bitmap fonts

Package: konsole Version: 4:20.12.3-1 Severity: normal Tags: a11y X-Debbugs-Cc: t...@seoss.co.uk When selecting a bitmap font via Konsole -> Settings -> Configure Konsole -> Profiles -> Edit -> Appearance -> Font -> Choose, only the smallest font size is displayed for OpenType bitmap fonts. e.g.

Bug#989831: konsole: Bitmap fonts rendered incorrectly if display scaling is enabled

Package: konsole Version: 4:20.12.3-1 Severity: normal Tags: a11y X-Debbugs-Cc: t...@seoss.co.uk When a bitmap font is selected, and display scaling is also enabled (KDE -> System Settings -> Display Configuration -> Global scale != 100%), then the fonts are rendered at their unscaled size (this i

Bug#928710: drkonqi: segfault after using reload button to get backtrace for dolphin

Package: drkonqi Version: 5.14.5-1 Severity: normal dolphin crashed, and I didn't have sufficient debug sym installed. I installed them, and then hit the "reload" button to re-do the backtrace, at which point drkonqi crashed. Backtrace below: Application: drkonqi (drkonqi), signal: Segmentation

Bug#844707: plasma-workspace: plasmadesktop - excessive cpu usage, slow desktop operation

Package: plasma-workspace Version: 4:5.8.2-1 Severity: important plasmashell consumes excessive CPU, increases over time. Possibly I'm hitting a couple of bugs here, but I'm not sure... plasmashell starts by stat()ing about 4 files per second, and consuming 50% of one CPU core. CPU then cli

Bug#829075: plasma-workspace: plasmashell crashes - debug symbols not available in unstable apparently?

Package: plasma-workspace Version: 4:5.6.5.1-1 Severity: normal KDE bug tracker reports debug symbols unavailable for plasmashell, even though the debug symbol package with a matching version number is installed. ii plasma-workspace 4:5.6.5.1-1 amd64Plasma Workspace for KF5 ii

Bug#745611: libkscreensaver5: Can't unlock screen with locker set to 'Desktop Widgets', and multiple monitors configured

Package: libkscreensaver5 Version: 4:4.11.8-1 Severity: important The Unlock popup fails to display when screen locker is set to 'Desktop Widgets', and multiple monitors configured - leaving desktop irrevocably locked. With the second display disabled, the unlock widget appears. With the second

Bug#551894: ktimetracker: Fixed in 4.3.4

Package: ktimetracker Severity: normal Fixed with 4:4.3.4 in testing. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-openvz-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en

Bug#551894: 4.3.2 reports itself as 4.3.1, distorted gui

Package: ktimetracker Version: 4:4.3.2-1 Severity: normal Same behaviour here - makes this package pretty-much useless... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-openvz-amd64 (SMP

Bug#545963: ktimetracker: Idle detection assumes task has not been stopped manually.

Package: ktimetracker Version: 4:4.2.4-1 Severity: important 1 Create and start a new task. 2 Leave the desktop idle beyond the "idle timer" setting (e.g. 15 minutes) - an idle detection dialog pops up - do not ack the dialog. 3 Manually stop the task (e.g. with 30 minutes elapsed on the task). 4

Bug#494971: KArm doesn't honor the 'detect idle after XX minutes' setting

Package: ktimetracker Severity: normal Some initial investigation suggested that this might be an X libraries related bug. Seems to be fixed in testing... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel

Bug#529802: Export history works incorrectly

Package: ktimetracker Version: 4:4.2.4-1 Severity: normal Bug still present in Squeeze. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc5-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8

Bug#494971: karm: Bug still present on lenny/amd64

Package: karm Version: 4:3.5.9-5 Followup-For: Bug #494971 I'm seeing this as well, and it renders karm pretty useless for me, unfortunately. Can't find the bug in upstream bug tracker either... https://bugs.kde.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__all__&produc

Bug#320838: kdm uses /dev/random, instead of /dev/urandom, and blocks on some systems with poor entropy

Christopher Martin wrote: On August 1, 2005 21:16, Tim Small wrote: Package: kdm Version: 4:3.3.2-1 Severity: important On machines with not much entropy, kdm blocks on startup as it runs out of entropy from /dev/random. It should probably use /dev/urandom instead. Possibly related to

Bug#320838: kdm uses /dev/random, instead of /dev/urandom, and blocks on some systems with poor entropy

Package: kdm Version: 4:3.3.2-1 Severity: important On machines with not much entropy, kdm blocks on startup as it runs out of entropy from /dev/random. It should probably use /dev/urandom instead. Possibly related to #294267 #240027 #298254 and maybe others. This is particularly troublesome o