Bug#1074583: upstream has provided a one-line patch to fix it

2024-07-08 Thread Sanjoy Mahajan
Upstream has a one-line patch to fix this issue, which I've tested with success. The commit id is given in the github issue: -Sanjoy

Bug#1074583: reported upstream too

2024-07-04 Thread Sanjoy Mahajan
I've also just reported this issue upstream, as it happens with the latest upstream version. Link to github issue: https://github.com/getmail6/getmail6/issues/199

Bug#1074583: getmail6: fails at startup with "TypeError: IMAP4_SSL.__init__()" after change to python3.12

2024-07-01 Thread Sanjoy Mahajan
Package: getmail6 Version: 6.19.01-1 Severity: grave getmail6 now crashes at startup with the error shown below in the transcript. It works fine with Python 3.11: $ python3.11 /usr/bin/getmail --rcfile=rc-inbox getmail version 6.19.01 Copyright (C) 1998-2024 Charles Cazabon and others. Lic

Bug#1068644: gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade

2024-04-08 Thread Sanjoy Mahajan
On 2024-04-08 18:30, Andreas Metzler wrote: >> It fails with "*** Fatal error: The encryption algorithm is not supported." > > Thank you and sorry. I have done a bisect and will try reverting the > offending upstream commit as a hotfix. Thank you for the quick fix. I've just updated the package

Bug#1054398: bing: error "not enough hosts were found to perform the bandwidth analysis"

2023-10-27 Thread Sanjoy Mahajan
On 2023-10-27 09:07, Patrick Matthäi wrote: > What happens if you use bing 192.168.7.123 192.168.7.1 > > where .1 is your gw and .123 your own ipv4 in this subnet instead of > localhost It doesn't seem very happy. Here's a log. There are a bunch of errors or at least messages surrounding some

Bug#1054398: bing: error "not enough hosts were found to perform the bandwidth analysis"

2023-10-23 Thread Sanjoy Mahajan
Package: bing Version: 1.3.5-5 Severity: grave X-Debbugs-Cc: none, Sanjoy Mahajan Bing has not worked for me for many versions. bing 1.1 works fine, but 1.3 in all versions that I've tried for years always fails. Here's the log from a typical example ("gw" is the router

Bug#728444: is there an "unbreaks" tag for once xpdf is fixed?

2013-12-08 Thread Sanjoy Mahajan
On upgraing to the latest fontconfig, aptitude wants to uninstall xpdf, which is reasonable since xpdf doesn't work with the latest fontconfig. I am tempted to let aptitude have its way, but I want xpdf back once it gets fixed. Is that possibility automated in any way, e.g. an "unbreaks" tag onc

Bug#635842: likely fix for your backend crash

2011-08-03 Thread Sanjoy Mahajan
Norbert, As you write, "cups became completely unusable, as the lpd backend just happens to die with a strange error." For me the problem started with the upgrade to 1.4.7. I had a slightly different symptom, namely that the socket backend would die with status -8 ("crashed"), but only on my HP

Bug#629863: cannot reproduce with iproute 20110315-1

2011-06-14 Thread Sanjoy Mahajan
It's iproute 20110315-1, which is the same as yours. Oh, damn, I just figured it out, and I have egg of my face: $ which ip /usr/local/sbin/ip # ls -l /usr/local/sbin/ip -rwxr-xr-x 1 root root 88488 Dec 27 2003 /usr/local/sbin/ip So I must have installed it by hand 7 years ago and never noticed

Bug#629863: isc-dhcp-client: error dhcping means no routes are installed

2011-06-08 Thread Sanjoy Mahajan
Package: isc-dhcp-client Version: 4.1.1-P1-17 Severity: grave File: /sbin/dhclient-script Today I noticed that ifup using dhcp kept failing, and I had to add the routes manually. The problem was in running dhclient, which would give an error when executing the following shell command from /sbin/d

Bug#598896: no problems on my x201s

2010-10-09 Thread Sanjoy Mahajan
Using LIBGL_ALWAYS_SOFTWARE=1 does work around the error for me; it's still there without that environment setting (I'm using the i915 driver w/ 945GM chipset). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists

Bug#598896: python-visual: i915_program_error: Exceeded max instructions

2010-10-02 Thread Sanjoy Mahajan
Package: python-visual Version: 1:5.12-1.1+b2 Severity: grave Using VPython (python-visual in Debian) now always produces i915_program_error: Exceeded max instructions For example, $ python /usr/share/doc/python-visual/examples/doublependulum.py i915_program_error: Exceeded max instructio

Bug#564946: xserver-xorg-video-intel: screen flickers, tears, turns pink

2010-01-13 Thread Sanjoy Mahajan
> At least the flickering and 'screen turns to pink' issues are a kernel > bug (or multiple kernel bugs). Adding i915.powersave=0 to the kernel > command line should work around that. Thanks. That fixed the pink screen and the flickering (and the 'tearing'). -- To UNSUBSCRIBE, email to debia

Bug#564946: xserver-xorg-video-intel: screen flickers, tears, turns pink

2010-01-12 Thread Sanjoy Mahajan
Package: xserver-xorg-video-intel Version: 2:2.9.1-2 Severity: grave The flickering in #56 has returned since I upgraded the X server and kernel a couple days ago (I'm tracking 'unstable'). Now it flickers a once or twice per minute. In addition, one of the Firefox windows often gets shifted

Bug#558459: cups: printing fails with "cupsRasterOpen failed" msg

2009-11-30 Thread Sanjoy Mahajan
You are right. I just found the same message: [Job 1026] psc: symbol lookup error: psc: undefined symbol: _ZN13GfxColorSpace5parseEP6Object -Sanjoy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian

Bug#558459: cups: printing fails with "cupsRasterOpen failed" msg

2009-11-28 Thread Sanjoy Mahajan
Package: cups Version: 1.4.2-2 Severity: grave Since an 'aptitude dist-upgrade' a couple hours ago, printing hasn't worked. For example, 'lp file.pdf' always failed with a message like the following in the error_log [Job 1026] prnt/hpcups/HPCupsFilter.cpp 485: cupsRasterOpen failed, fd = 0 The

Bug#375240: ctwm: right click for TwmWindows crashes ctwm

2006-06-24 Thread Sanjoy Mahajan
Package: ctwm Version: 3.7-2.1 Severity: grave >From my .xsession-errors: > Congratulations; you have found a bug in CTWM. > If a core file was generated in the current working directory, > please try to extract the stack trace, and mail the results along > with a description of what you were go

Bug#365134: which X server is correct?

2006-05-18 Thread Sanjoy Mahajan
I just ran into this problem as well, and was about to report the same workaround (changing /usr/bin/X11/xdm to /usr/bin/xdm in /etc/init.d/xdm and /etc/X11/default-display-manager). But I'm still not sure which X server to use in /etc/X11/xdm/Xservers. There's -rwxr-xr-x 1 root root 1878204 200