Bug#864827: Whither Zotero 5?
On Sun, 24 Mar 2019 17:47:38 +0100 =?ISO-8859-1?Q?S=E9bastien?= Villemot wrote: > The main reason is lack of manpower (a lot of work in the Javascript > packages need to happen first). Thank you for the explanation. Is there a to-do list or some elaboration on the work that needs to be done?
Bug#864827: Whither Zotero 5?
For the benefit of those of us less technically astute, what exactly is preventing Zotero 5 from being packaged and loaded into unstable or experimental?
Bug#886063: libgnomecanvas: Don't release with Buster
I apologise. The relevant post is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885777#22: "Uh, wait... the mailing list post from October 2017 announcing the deprecation and removal of libgnome and libgnomeui and other related libraries didn't even list libgnomecanvas among the libraries to be removed, or xournal among the affected packages -- perhaps showing awareness that libgnomecanvas is in fact not related to libgnome in any way. Could it be that someone got overzealous and decided to remove libgnomecanvas for no good reason? Perhaps that can still be undone?"
Bug#886063: libgnomecanvas: Don't release with Buster
The Xournal package requires this package. If you refer to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885777#17, it appears that this package has been flagged for removal somewhat over-zealously: "libgnomecanvas is not related to libgnome in any way despite the name. It provides a high-performance canvas widget for GTK2, it is the standard canvas widget for GTK2. There is no good replacement for GTK3. I am not aware of any serious issues with it apart from it being old." I depend on Xournal, and as there is no suitable GTK3 replacement, I'm curious whether it is possible to appeal the decision to remove libgnomecanvas on the grounds that it apperntly is not part of the libgnome code base.
Bug#885777: (no subject)
> As far as I can tell libgnomecanvas2-0 is still in the distribution but > fails to compile because it needs some packages which are unmaintained. > > For the moment it is still in testing and unstable. However, Xournal has been removed from testing. If libgnomecanvas is staying in Buster, then shouldn't Xournal also?
Bug#885777:
I can't afford to lose this program. I've asked upstream what their plans are to migrate to GTK+ 3. What can non C programmers do to help?
Bug#856933: xserver-xorg-input-wacom: use Wacom tablet cause system freeze
Ditto on this bug. Infuriating as can be. My computer takes about 15 minutes to start, but it does behave normally _eventually_. Not that we all have time to throw around, but if you turn your Wacom-enabled computer on then take a nice hot shower, it might be working when you return. I've read on the ArchWiki (https://wiki.archlinux.org/index.php/Wacom_Tablet#System_freeze) that there might be a 'recursive deadlock' condition causing this problem. I skimmed through your bug reference and I'm not sure if it's the same problem.
Bug#794581: Happened again! Argh!
On Tue, 25 Aug 2015 18:42:11 -0400 Scott Kitterman wrote: > You should only have to downgrade breeze. Today's rebuild of kdecorations > should resolve its problems. > > So downgrade breeze to the testing version and upgrade kdecorations to the > +b1 version. So confirmed, thank you. This is technically my fault for mixing testing and sid packages, so I owe you all an apology. Having said that, will things be relatively stable for the next little while? I'm missing my window decorations now, but that's another bug that I hope will auto-correct with the next batch of packages entering testing. At least I can work around that and use my desktop again.
Bug#794581: Happened again! Argh!
So I ran aptitude dist-upgrade on my stretch box this afternoon. It updated libkdecorations2-5 and libkdecorations2private5 both to 4:5.3.2-2+b1. It also upgraded libkf5archive5 to 5.12.0-1+b1, along with 40 other packages which I don't think are related to this problem. Once again, KDE krashes as it did before. However, since breeze is already at the sid version, I can't upgrade it. How do I get my desktop back? Could the the kf5 libraries be held in sid and sent to testing in such a way that these breakages don't occur? If it weren't for the earlier advice to update breeze, I'd still be out of an operating system. This is no good!
Bug#794581: 5.13.0 crashes for me
On Thu, 20 Aug 2015 06:32:08 -0700 Zhitao Li wrote: > Or upgrade breeze package to Sid's version. > Really don't see why breeze is not migrated to testing after 16 days. This worked for me, thanks Zhitao. Yes, I'm not entirely sure why they did this. I mean, I know that they're piecemealing the kf5 transition, but aren't these sorts of grave dependency issues supposed to be anticipated _before_ going to testing?
Bug#794581: 5.13.0 crashes for me
KDE gets stuck at the welcome screen for me now. I updated my libkf5 packages to 5.13.0-1 at 9:15 (UTC) on 19 August. After rebooting, KDE won't load. .xsession-errors only indicates a crash but nothing of much use.
Bug#451535: This bug just ate my LVM2 volume group.
I totally empathise with Ian's frustration. I myself spent eight hours trying to circumvent this 'bug', to put it mildly. I tried to follow a half-dozen contradictory, inaccurate and incomplete walkthroughs with no success, so I'm giving up and starting from scratch. The walkthrough at http://wiki.debian.org/DebianInstaller/Rescue/Crypto does not exist. As this bug hasn't been addressed in 8 years, it may be worth giving up on it. If so, there should at least be bold warnings to anybody tempted to set up encrypted volumes that they will not be reusable if one needs to reinstall Debian unless they have highly advanced knowledge of hand-writing configuration files from rescue CDs. This would, at least, stop hundreds of aggregate human hours from being wasted. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#616686: anki: upgrading makes data from previous version unreadable
The good people over at http://ankisrs.net/ have a Debian package which, at least for me, has installed cleanly into Wheezy. Why can't we copy-and-paste that version into our repos - or at least into experimental? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567619: xserver-xorg: After upgrading squeeze xserver stops responding
Agreed. Upgrading to the 2.6.32-trunk kernel seems to be part of the problem. Thank God my 2.6.30 kernel is still on the system since I am able to boot into that. However, my Wacom digitiser still isn't being detected like it used to (which is a whole other issue). Do you need my Xorg.log? The only (possibly) relevant information that I can add is that I'm running on a 852/855GM (Intel) video card. Not working: CTRL+ALT+F# and CTRL+ALT+BKSP. Cannot drop into a shell to troubleshoot. CTRL+ALT+DELETE does reboot my system, eventually. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#487680: VERR_VM_DRIVER_VERSION_MISMATCH
Are the modules going to be upgraded to version 1.6.2 anytime soon in the repos? Is there any reason to keep the 1.5.6 binaries if they cannot be used out of the box? Borden Rhodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462421: claws-mail crashes with an X Window System error
Package: claws-mail Version: 3.2.0-2 Severity: grave Justification: renders package unusable When trying to run claws-mail from bash or KDE 4 the program will load briefly and then disappear. In bash, the following message will appear after the program has crashed: /* Begin Message */ The program 'claws-mail' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 5608 error_code 8 request_code 2 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) /* End Message */ Other GTK-based programs like Synaptec and or The GIMP run correctly without issue. From Ubuntu's debugging procedures, I tried to get a stack trace using the command > strace -Ff -tt claws-mail 2>&1 | tee strace-claws-mail.log and, to my surprise, claws-mail ran correctly without let or hinderance. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-5-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages claws-mail depends on: ii libaspell15 0.60.5-1 GNU Aspell spell-checker runtime l ii libc6 2.7-6GNU C Library: Shared libraries ii libcairo2 1.4.14-1 The Cairo 2D vector graphics libra ii libcompfaceg1 1:1.5.2-4Compress/decompress images for mai ii libetpan11 0.52-1 mail handling library ii libglib2.0-02.14.5-2 The GLib library of C routines ii libgtk2.0-0 2.12.5-2 The GTK+ graphical user interface ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libldap22.1.30.dfsg-13.5 OpenLDAP libraries ii libpango1.0-0 1.18.4-1 Layout and rendering of internatio ii libpisock9 0.12.3-2 library for communicating with a P ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libssl0.9.8 0.9.8g-4 SSL shared libraries Versions of packages claws-mail recommends: ii aspell-en [aspell-dictionary] 6.0-0-5.1 English dictionary for GNU Aspell ii claws-mail-i18n 3.2.0-2Locale data for Claws Mail (i18n s ii xfonts-100dpi 1:1.0.0-4 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-4 75 dpi fonts for X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
