Your message dated Thu, 10 Jul 2008 15:04:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Sun-java5 breaking xterms
has caused the Debian Bug report #446950,
regarding sun-java5-bin: crashes xterm on installation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
446950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446950
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sun-java5-bin
Version: 1.5.0-10-3
Severity: serious
This "bug" may be covering a bunch of packages, I suspect, actually.
Either way, what I'm seeing is totally unacceptable for a "stable"
release.
After noticing that azureus doesn't work anymore (it used to),
i.e., crashes, popup windows not closing, top showing java use
101 (yes, 101) %CPU, etc., etc., started looking for java.
Found realpath /usr/bin/java to be /usr/bin/gij-4.1. Decided to
get Sun's (actually I think I always had it and don't remember
switching). OK, apt-get install sun-java5-jdk, but xterm running
this crashes, can't even notice what the problem is. Next I'm
told to do dpkg --configure -a, repeating install after that
crashes xterm again (while setting up sun-java5-bin). After a
few tries, decided to remove the misbehaving sun-java5 packages,
this finally allows a glimpse as to what might be wrong:
kaste(3): sudo apt-get remove --purge sun-java5-bin
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
sun-java5-bin sun-java5-jre
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
dpkg: error processing sun-java5-bin (--remove):
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
dpkg: error processing sun-java5-jre (--remove):
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
Errors were encountered while processing:
sun-java5-bin
sun-java5-jre
E: Sub-process /usr/bin/dpkg returned an error code (1)
Well, at least xterm doesn't crash this time.
Before this, my system was perfectly "up-to-date", BTW, so
this is quite a shock. To summarize, the way I see it:
1) sun-java5-* really broken.
2) dpkg crashing due to sun-java5-* brokenness.
3) dpkg crashing and taking xterm with it.
4) azureus completely unusable with gij-4.1.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20
Locale: LANG=lv_LV.UTF-8, LC_CTYPE=lv_LV.UTF-8 (charmap=UTF-8)
-- debconf information:
shared/accepted-sun-dlj-v1-1: false
shared/error-sun-dlj-v1-1:
shared/present-sun-dlj-v1-1:
--- End Message ---
--- Begin Message ---
tag 446950 + wontfix
thanks
> Sorry, it's probably too late for that. I have switched to lenny and
> have Sun Java 6 now. Everything seems to be working fine.
closing the report
--- End Message ---
