Bug#984953: libgtkmm-3.0-1v5: GParted crashes on Gdk::Pixbuf::get_width() const ()

Package: libgtkmm-3.0-1v5 Version: 3.24.2-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: moonwal...@syrius.us Dear Maintainer, I attempted to launch GParted and saw it crash immediately after initially showing its window I attempted to delete all /root/.gtkrc*,

Bug#917643: Acknowledgement (zram-tools uses outdated by 7 years approach in setting up zram thread count)

I have also submitted an upstream bug report ( https://github.com/highvoltage/zram-tools/issues/3), but considering the last commit is from three years ago I'm not holding my breath that it gets addressed. Alexey -- This message was created with 100% recycled electrons On Sat, Dec 29, 2018 at

Bug#917643: zram-tools uses outdated by 7 years approach in setting up zram thread count

Package: zram-tools Version: 0.3.2-1 Severity: important Dear Maintainer, zram module has max_comp_streams property since around 2011, and nowadays it is (at least on x86/amd64) is autodetected to match the CPU core count. Setting up multiple zram devices is inefficient even if each one is set

Bug#917136: (no subject)

This bug is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917124 My layout is as follows: sda8:00 465.8G 0 disk ├─sda1 8:1040M 0 part /boot/efi ├─sda2 8:20 128G 0 part │

Bug#906098: kde-telepathy-text-ui: Invisible characters in the chat window: File not found error message (html url encoded) in textbox.

I can confirm having the same issue. The message 'file not found' seems to refer to the content of the file /usr/share/ktelepathy/Template.html. I suspect the call to open said template is written incorrectly - the end result is instead of opening the file itself it tries to interpret a

Bug#838734: Recurring issue

This has been a recurring issue for me. IIRC in recent couple months there were two Plasma upgrades in Debian Unstable, 5.7 and then 5.8. In both cases Plasma Discover blew away plasma-workspace and bunch of other KDE packages (including self) with zero warning. If at the very least among the list

Bug#645139: workaround

I was able to work around this bug by downgrading rubygems to stable (1.3.7), installing redmine and then upgrading rubygems back to 1.8.10-1.