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. Licensed under GNU GPL 
version 2.
  SimpleIMAPSSLRetriever:san...@mit.edu@outlook.office365.com:993:
0 messages (0 bytes) retrieved, 0 skipped

My system (mostly running 'unstable') just changed to Python 3.12 a day
or so ago, and getmail6 has failed since then (but not before).  Thus, I
suspect something is now incompatible between the getmail code and
Python 3.12's expectations.

Here is promised failure transcript with Python 3.12:

  $ /usr/bin/getmail --rcfile=rc-inbox
  getmail version 6.19.01
  Copyright (C) 1998-2024 Charles Cazabon and others. Licensed under GNU GPL 
version 2.
  SimpleIMAPSSLRetriever:san...@mit.edu@outlook.office365.com:993:

  Exception: please read docs/BUGS and include the following information in any 
bug report:

getmail version 6.19.01
Python version 3.12.4 (main, Jun 12 2024, 19:06:53) [GCC 13.2.0]

  Unhandled exception follows:
  File "/usr/bin/getmail", line 1077, in main
  success = go(configs, options.idle, options.only_account)
^^^
  File "/usr/bin/getmail", line 188, in go
  retriever.initialize(options)
  File "/usr/lib/python3/dist-packages/getmailcore/_retrieverbases.py", 
line 1807, in initialize
  self._connect()
  File "/usr/lib/python3/dist-packages/getmailcore/_retrieverbases.py", 
line 714, in _connect
  self.conn = imaplib.IMAP4_SSL(
  ^^
TypeError: IMAP4_SSL.__init__() takes from 1 to 3 positional arguments but 
5 were given

  Please also include configuration information from running getmail
  with your normal options plus "--dump".


-- System Information:
Debian Release: sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages getmail6 depends on:
ii  python3  3.12.2-1

getmail6 recommends no packages.

getmail6 suggests no packages.

-- no debconf information



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 packages to 3.8.5-2
and have re-tested: The connection works fine now.

-- 
-Sanjoy



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 bandwidth information.  The dots
at the end were ongoing when I ctrl-Ced it.

# bing 192.168.7.165 192.168.7.1
Found 2 key hosts
0: 192.168.7.165 (192.168.7.165)
1: 192.168.7.1 (192.168.7.1)
--
Using 10 data payload sizes:
44 205 367 529 691 852 1014 1176 1338 1500 
--
ttl=1 probe_res=2 host=192.168.7.165
 --bing.c:740--  -> hit
  adding host 192.168.7.165 at ttl 0
ttl=1 probe_res=2 host=192.168.7.1
 --bing.c:740--  -> hit
  adding host 192.168.7.1 at ttl 1
Found 2 hosts
0: 0 - 192.168.7.165 (insight.lan/192.168.7.165)
1: 1 - 192.168.7.1 (gw/192.168.7.1)


 0 192.168.7.1650.004 ms, 1.000/2 ,  80.0%,   
0.0%
 |   8361.29Kb/s, 845.78 us (  884 bytes), 1.000/2
 | 11.78Mb/s,   1.50 ms ( 2216 bytes)
 1 192.168.7.1  1.509 ms, 0.981/7 ,  30.0%,   
0.0%

Round 1 hinvalid:  11 (55.0%), linvalid:   0 (0.0%), redo:   0 (0.0%), total:   
11 (55.0%)
RTT status for method 0
0: (  0.008) (  0.008) (  0.014) (  0.033) (  0.010) (  0.009) (  0.009)
0.008  (  0.013)0.009  
1:1.747 1.901  (  2.531) (  2.996)2.463 2.546 2.808 
3.196  (  4.566)3.817  
Host level regression errors for method 0
0: - - - - - - -   
-0. -   -0. 
1:0.11310.0480 - -   -0.0513   -0.1874   -0.1459
0.0217 -0.2018 
Link level rtt differences for method 0
1: - - - - - - -
3.1880 -3.8080 
Link level regression errors for method 0
1: - - - - - - -   
-0. -   -0. 


 0 192.168.7.1650.004 ms, 1.000/2 ,  80.0%,   
0.0%
 |   .-- b/s, ---.-- ms (- bytes), -.---/--
 | 13.38Mb/s,   1.54 ms ( 2573 bytes)
 1 192.168.7.1  1.543 ms, 0.938/8 ,  20.0%,   
0.0%

Round 2 hinvalid:  10 (50.0%), linvalid:   0 (0.0%), redo:   0 (0.0%), total:   
10 (50.0%)
RTT status for method 0
0: (  0.008) (  0.008) (  0.014) (  0.033) (  0.010) (  0.009) (  0.009)
0.008  (  0.013)0.009  
1:1.747 1.901 1.981 2.180 2.463 2.546  (  2.808) (  
3.196)2.792 3.817  
Host level regression errors for method 0
0: - - - - - - -   
-0. -   -0. 
1:0.09400.0550   -0.0592   -0.05450.0343   -0.0757 - 
-   -0.41240.4184 
Link level rtt differences for method 0
1: - - - - - - - 
- -3.8080 
Link level regression errors for method 0
1: - - - - - - - 
- - - 


 0 192.168.7.1650.004 ms, 1.000/2 ,  80.0%,   
0.0%
 |   4133.97Kb/s, ---.-- ms (- bytes), 1.000/2
 | 14.50Mb/s,   1.56 ms ( 2831 bytes)
 1 192.168.7.1  1.566 ms, 0.910/9 ,  10.0%,   
0.0%

Round 3 hinvalid:   9 (45.0%), linvalid:   0 (0.0%), redo:   0 (0.0%), total:   
 9 (45.0%)
RTT status for method 0
0: (  0.008) (  0.008) (  0.014) (  0.033) (  0.010) (  0.009) (  0.009)
0.008  (  0.013)0.009  
1:1.747 1.901 1.981 2.180 2.463 2.546  (  2.602)
2.562 2.792 3.817  
Host level regression errors for method 0
0: - - - - - - -   
-0. -   -0. 
1:0.07910.0550   -0.0443   -0.02460.0792   -0.0160 -   
-0.3585   -0.30780.5379 
Link level rtt differences for method 0
1: - - - - - - -
2.5540 -3.8080 
Link level regression errors for method 0
1: - - - - - - -   
-0. -   -0. 


 0 192.168.7.1650.004 ms, 1.000/2 ,  80.0%,   
0.0%
 |   4133.97Kb/s, ---.-- ms (- bytes), 1.000/2
 | 14.85Mb/s,   1.56 ms ( 2894 bytes)
 1 192.168.7.1  1.564 ms, 0.902/9 ,  10.0%,   
0.0%

Round 4 hinvalid:   9 (45.0%), linvalid:   0 (0.0%), redo:   0 (0.0%), total:   
 9 (45.0%)
RTT status for method 0
0: (  0.008) (  0.008) (  0.014) (  0.033) (  0.010) (  0.009) (  0.009)
0.008  (  0.013)0.009  
1:1.747 1.901 1.981 2.180 2.463  (  2.546)2.515 
2.562 2.792 3.817  
Host level regression errors for method 0
0: - - - - - - -   
-0. -   -0.

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 on the local network).
It always fails with the error "not enough hosts were found to perform
the bandwidth analysis".

# bing localhost gw
Found 2 key hosts
0: localhost (127.0.0.1)
1: gw (192.168.7.1)
--
Using 10 data payload sizes:
44 205 367 529 691 852 1014 1176 1338 1500 
--
ttl=1 probe_res=2 host=127.0.0.1
 --bing.c:740--  -> hit
  adding host localhost at ttl 0
ttl=1 probe_res=2 host=192.168.7.1
bing: error: at ttl 1 the return path from gw went through the 192.168.7.165 
interface instead of 192.168.7.165 for the other hosts
Found 1 hosts
0: 0 - localhost (insight.lan/127.0.0.1)
bing: not enough hosts were found to perform the bandwidth analysis


-- System Information:
Debian Release: sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bing depends on:
ii  libc6  2.37-12

bing recommends no packages.

bing suggests no packages.

-- no debconf information



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 once
xpdf is fixed such that my daily "aptitude dist-upgrade" will somehow
know to offer to install the fixed xpdf?

-- 
-Sanjoy


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



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 PSC 2710 printer (not on the Xerox laserprinters at work).  I suspect
that the cause in your case is the same as in mine; thus, you should be
able to use the fix that I describe below.

The Arch linux bug forum at 
pointed me to a fix that is in cups upstream (1.4.8 and 1.5.0):



Those versions are not yet in the Debian archives, so I applied the
upstream patch to 1.4.7.  However, before I could recompile cups, I
needed to fix a FTBFS due to a problem in some of the ppd files in the
hp-ppd package.  See BTS #588317 for the report and my patch to fix that
problem.

Then cups recompiled fine.  (Although I had to omit my usual -j3 flag or
else the build failed.  But that problem will be the subject of a
separate bug report, if I can reproduce it reliably.)

-Sanjoy



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



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 a
problem until recently.

Thus, feel free to close the bug.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org




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/dhclient-script:

  ip -4 addr add 192.168.101.18/255.255.255.0 broadcast 192.168.101.255 dev 
wlan0 label wlan0

The error was:

  Error: an inet prefix is expected rather than "192.168.101.18/255.255.255.0".

In the address, the information after the slash needs to be the number
of "1" bits in the netmask, rather than the netmask itself.  The
following hacky diff fixes it for me, but I doubt it's the best fix:

--- /sbin/dhclient-script   2011-05-19 02:13:42.0 -0400
+++ /sbin/dhclient-script   2011-06-08 19:17:00.0 -0400
@@ -140,6 +140,7 @@
 fi
 if [ -n "$new_subnet_mask" ]; then
 new_mask="/$new_subnet_mask"
+new_mask_bits=`echo "$new_subnet_mask" | awk -F. '{print 
($1+$2+$3+$4)/255*8;}'`
 fi
 if [ -n "$alias_subnet_mask" ]; then
 alias_mask="/$alias_subnet_mask"
@@ -209,7 +210,7 @@
[ "$old_ip_address" != "$new_ip_address" ] ||
[ "$reason" = "BOUND" ] || [ "$reason" = "REBOOT" ]; then
 # new IP has been leased or leased IP changed => set it
-ip -4 addr add ${new_ip_address}${new_mask} ${new_broadcast_arg} \
+ip -4 addr add ${new_ip_address}/${new_mask_bits} 
${new_broadcast_arg} \
 dev ${interface} label ${interface}
 
 if [ -n "$new_interface_mtu" ]; then


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages isc-dhcp-client depends on:
ii  debianutils  4   Miscellaneous utilities specific t
ii  iproute  20110315-1  networking and traffic control too
ii  isc-dhcp-common  4.1.1-P1-17 common files used by all the isc-d
ii  libc62.13-4  Embedded GNU C Library: Shared lib

isc-dhcp-client recommends no packages.

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd  (no description available)
pn  resolvconf (no description available)

-- Configuration Files:
/etc/dhcp/dhclient.conf changed:
supersede domain-name "mit.edu";
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
netbios-name-servers, netbios-scope, interface-mtu;


-- debconf-show failed

-- 
-Sanjoy

`Until lions have their historians, tales of the hunt shall always
 glorify the hunters.'  --African Proverb



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



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.debian.org



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 instructions

A seemingly related problem is that the rendering is *very* choppy.  The
pendulum leaps roughly from one extreme to the other, without going
through intermediate positions.  This choppiness makes VPython nearly
unusuable for displaying simulations.

It shouldn't be so jerky and slow.  The hardware is a Thinkpad T60 w/
Intel integrated graphics (945GM).  Several years ago, on much slower
CPU and graphics hardware, I didn't see this problem.

That was with earlier versions of VPython and the X server, but I don't
think VPython itself is responsible.  There's a discussion on the
vpython mailing list at

  

Rather, I suspect that hardware acceleration isn't working.

The X server pieces are

  xserver-xorg-video-intel 2.12.0+shadow-2
  xserver-xorg-core1.7.7-7
  xserver-xorg 7.5+7

Let me know the proper place to report this bug, if you know!

-Sanjoy

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.35.3 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-visual depends on:
ii  libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii  libboost-python1.42.0   1.42.0-4 Boost.Python Library
ii  libboost-signals1.42.0  1.42.0-4 managed signals and slots library 
ii  libboost-thread1.42.0   1.42.0-4 portable C++ multi-threading
ii  libc6   2.11.2-6 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-6 The Cairo 2D vector graphics libra
ii  libcairomm-1.0-11.8.4-3  C++ wrappers for Cairo (shared lib
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.4.2-2  FreeType 2 font engine, shared lib
ii  libgcc1 1:4.4.4-17   GCC support library
ii  libgl1-mesa-glx [libgl1 7.7.1-4  A free implementation of the OpenG
ii  libglade2-0 1:2.6.4-1library to load .glade files at ru
ii  libglademm-2.4-1c2a 2.6.7-2  C++ wrappers for libglade2 (shared
ii  libglib2.0-02.24.2-1 The GLib library of C routines
ii  libglibmm-2.4-1c2a  2.24.2-1 C++ wrapper for the GLib toolkit (
ii  libglu1-mesa [libglu1]  7.7.1-4  The OpenGL utility library (GLU)
ii  libgtk2.0-0 2.20.1-1+b1  The GTK+ graphical user interface 
ii  libgtkglext11.2.0-1.1OpenGL Extension to GTK+ (shared l
ii  libgtkglextmm-x11-1.2-0 1.2.0-4  C++ bindings for GtkGLExt (Shared 
ii  libgtkmm-2.4-1c2a   1:2.20.3-1   C++ wrappers for GTK+ (shared libr
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libpango1.0-0   1.28.1-1 Layout and rendering of internatio
ii  libpangomm-1.4-12.26.2-1 C++ Wrapper for pango (shared libr
ii  libpng12-0  1.2.44-1 PNG library - runtime
ii  libsigc++-2.0-0c2a  2.2.4.2-1type-safe Signal Framework for C++
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libstdc++6  4.4.4-17 The GNU Standard C++ Library v3
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxml2 2.7.7.dfsg-4 GNOME XML library
ii  libxmu6 2:1.0.5-2X11 miscellaneous utility library
ii  libxrender1 1:0.9.6-1X Rendering Extension client libra
ii  libxt6  1:1.0.7-1X11 toolkit intrinsics library
ii  python  2.6.6-3  interactive high-level object-orie
ii  python-central  0.6.16+nmu1  register and build utility for Pyt
ii  python-numpy1:1.4.1-4Numerical Python adds a fast array
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

python-visual recommends no packages.

Versions of packages python-visual suggests:
ii  idle  2.6.6-3IDE for Python using Tkinter (defa

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



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 to the left
by a few hundred pixels: not the toolbar, just the part displaying a
webpage, leaving the toolbar where it was.  Sending that Firefox
window behind other windows and then bringing it forward often fixes it.

Also, as I was writing this email, the whole screen turned pink.
Suspending and resuming (S3) restored the screen to its normal state.

The hardware is a Thinkpad T60 with Intel graphics and wireless.

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Jan 27  2008 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1712764 Jan  7 14:31 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03)

/var/lib/x11/xorg.conf.md5sum does not exist.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 1371 Jun 10  2009 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
EndSection

Section "ServerFlags"
   Option "DontZap" "false"
EndSection

#Section "Device"
#   Identifier  "Configured Video Device"
#EndSection

Section "Device"
Identifier  "Intel Corporation Mobile Integrated Graphics 
Controller"
#   Driver  "i810"
#   BusID   "PCI:0:2:0"
  Option "MonitorLayout" "CRT,LFP"
  Option "Clone" "true"
  Option "DevicePresence" "true"
EndSection

Section "Monitor"
Identifier  "Configured Monitor"
EndSection

Section "Screen"
Identifier  "Default Screen"
Monitor "Configured Monitor"
EndSection


Xorg X server log files on system:
-rw-r--r-- 1 root root 34418 Jan 12 17:14 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.7.3.902 (1.7.4 RC 2)
Release Date: 2009-12-26
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.2-dsa-ia32 i686 Debian
Current Operating System: Linux approx 2.6.32-trunk-686 #1 SMP Sun Jan 10 
06:32:16 UTC 2010 i686
Kernel command line: BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 
root=UUID=96e6c8e5-fa38-4ac1-a749-4499ebc58575 ro quiet
Build Date: 07 January 2010  07:24:24PM
xorg-server 2:1.7.3.902-1 (bui...@murphy.debian.org) 
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 11 17:03:59 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section.  Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Configured Monitor"
(==) No device specified for screen "Default Screen".
Using the first device section listed.
(**) |   |-->Device "Intel Corporation Mobile Integrated Graphics Controller"
(**) Option "DontZap" "false"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set 

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.org



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 printer is a HP PSC 2710.  I suspected the poppler upgrade caused
or exposed the problem, so I downgraded the poppler-utils,
libpoppler5, and libpoppler-dev packages from version 0.12.2-1 back to
version 0.12.0-2.1.  Printing works again!

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cups depends on:
ii  adduser3.111 add and remove users and groups
ii  bc 1.06.95-2 The GNU bc arbitrary precision cal
ii  cups-client1.4.2-2   Common UNIX Printing System(tm) - 
ii  cups-common1.4.2-2   Common UNIX Printing System(tm) - 
ii  debconf [debconf-2.0]  1.5.28Debian configuration management sy
ii  ghostscript8.70~dfsg-2   The GPL Ghostscript PostScript/PDF
ii  libavahi-client3   0.6.25-2  Avahi client library
ii  libavahi-common3   0.6.25-2  Avahi common library
ii  libc6  2.10.2-2  GNU C Library: Shared libraries
ii  libcups2   1.4.2-2   Common UNIX Printing System(tm) - 
ii  libcupscgi11.4.2-2   Common UNIX Printing System(tm) - 
ii  libcupsdriver1 1.4.2-2   Common UNIX Printing System(tm) - 
ii  libcupsimage2  1.4.2-2   Common UNIX Printing System(tm) - 
ii  libcupsmime1   1.4.2-2   Common UNIX Printing System(tm) - 
ii  libcupsppdc1   1.4.2-2   Common UNIX Printing System(tm) - 
ii  libdbus-1-31.2.16-2  simple interprocess messaging syst
ii  libgcc11:4.4.2-3 GCC support library
ii  libgnutls262.8.5-2   the GNU TLS library - runtime libr
ii  libgssapi-krb5-2   1.7dfsg~beta3-1   MIT Kerberos runtime libraries - k
ii  libijs-0.350.35-7IJS raster image transport protoco
ii  libkrb5-3  1.7dfsg~beta3-1   MIT Kerberos runtime libraries
ii  libldap-2.4-2  2.4.17-2.1OpenLDAP libraries
ii  libpam0g   1.1.0-4   Pluggable Authentication Modules l
ii  libpaper1  1.1.23+nmu1   library for handling paper charact
ii  libpoppler50.12.2-1  PDF rendering library
ii  libslp11.2.1-7.6 OpenSLP libraries
ii  libstdc++6 4.4.2-3   The GNU Standard C++ Library v3
ii  libusb-0.1-4   2:0.1.12-13   userspace USB programming library
ii  lsb-base   3.2-23Linux Standard Base 3.2 init scrip
ii  perl-modules   5.10.1-8  Core Perl modules
ii  poppler-utils  0.12.2-1  PDF utilitites (based on libpopple
ii  procps 1:3.2.8-2 /proc file system utilities
ii  ssl-cert   1.0.25simple debconf wrapper for OpenSSL
ii  ttf-freefont   20090104-4Freefont Serif, Sans and Mono True
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages cups recommends:
ii  cups-driver-gutenprint  5.2.4-1  printer drivers for CUPS
ii  foomatic-filters4.0-20090509-1.1 OpenPrinting printer support - fil
ii  ghostscript-cups8.70~dfsg-2  The GPL Ghostscript PostScript/PDF

Versions of packages cups suggests:
ii  cups-bsd  1.4.2-2Common UNIX Printing System(tm) - 
ii  cups-pdf  2.5.0-12   PDF printer for CUPS
ii  cups-ppdc 1.4.2-2Common UNIX Printing System(tm) - 
ii  foomatic-db   20090616-1 OpenPrinting printer support - dat
ii  foomatic-db-engine4.0-20090509-2 OpenPrinting printer support - pro
ii  hplip 3.9.10-1   HP Linux Printing and Imaging Syst
ii  smbclient 2:3.4.3-1  command-line SMB/CIFS clients for 
ii  udev  147-5  /dev/ and hotplug management daemo
pn  xpdf-korean | xpdf-japane  (no description available)

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp, dnssd



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



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 going, to
> <[EMAIL PROTECTED]>.  Thank you for your support.

This is with xorg 7.0.  I log in via xdm, which runs my .xsession, and
its last line execs ctwm.  When I right click on the root window
(which is a xsetbg jpg background, but that shouldn't matter), ctwm
crashes.  My .twmrc file has:

Button3 = : root : f.menu "TwmWindows"

I hope the following backtrace from the core file is useful (but it
seems to have no useful symbols):

(gdb) bt
#0  0xb7c2d7c7 in raise () from /lib/tls/libc.so.6
#1  0xb7c2f06b in abort () from /lib/tls/libc.so.6
#2  0x08057869 in ?? ()
#3  0x080929fc in _IO_stdin_used ()
#4  0x0001 in ?? ()
#5  0x0276 in ?? ()
#6  0xb7d38480 in _IO_list_all () from /lib/tls/libc.so.6
#7  0x080ed620 in ?? ()
#8  0xb7bf66a4 in ?? ()
#9  0xbfcf0de8 in ?? ()
#10 
#11 0x08061768 in ?? ()
#12 0x080e3370 in ?? ()
#13 0x08094a91 in _IO_stdin_used ()
#14 0x in ?? ()

ctwm worked fine (perhaps in an earlier version) with xorg 6.8 or 6.9
or xfree 4.3.  The crashes started today, after I upgraded to xorg 7.0
and then reinstalled ctwm (the massive 'apt-get upgrade' deleted the
ctwm package), which is why I'm not sure whether I was using ctwm 3.7
when all was working fine.

-Sanjoy

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.f9c7d2a9a5af
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)

Versions of packages ctwm depends on:
ii  libc62.3.6-13GNU C Library: Shared libraries
ii  libice6  1:1.0.0-3   X11 Inter-Client Exchange library
ii  libjpeg626b-13   The Independent JPEG Group's JPEG 
ii  librplay33.3.2-10Shared libraries for the rplay net
ii  libsm6   1:1.0.0-4   X11 Session Management library
ii  libx11-6 2:1.0.0-6   X11 client-side library
ii  libxext6 1:1.0.0-4   X11 miscellaneous extension librar
ii  libxmu6  1:1.0.1-3   X11 miscellaneous utility library
ii  libxpm4  1:3.5.4.2-3 X11 pixmap library
ii  libxt6   1:1.0.0-5   X11 toolkit intrinsics library
ii  m4   1.4.4-1 a macro processing language
ii  x11-common   1:7.0.22X Window System (X.Org) infrastruc

ctwm recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



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 2006-04-03 23:44 /usr/bin/X11/Xorg
[from xserver-xorg   6.9.0.dfsg.1-6]

or

-rwsr-sr-x 1 root root 7800 2006-04-03 23:44 /usr/bin/X11/X
[from xserver-common 6.9.0.dfsg.1-6]

Is one better than the other?

-Sanjoy

`A society of sheep must in time beget a government of wolves.'
   - Bertrand de Jouvenal


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]