Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2212 - libbonobo-2.8.1-1 crashes kernel

Attached to Project: Arch Linux
Opened by ... (spider007) - Tuesday, 15 February 2005, 18:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

When I upgrade libbonobo 2.8.0-1 to libbonobo-2.8.1-1 my kernels blows up. Some stacktrace I cannot save appears and seconds later my system hangs. The backtrace shows some reisercalls. What information can I provide to solve this?
This task depends upon

Closed by  arjan timmerman (blaasvis)
Friday, 18 February 2005, 19:50 GMT
Reason for closing:  Not a bug
Additional comments about closing:  well seems it was resolved on irc...
Comment by Jan de Groot (JGC) - Tuesday, 15 February 2005, 19:10 GMT
I think it's time to run reiserfsck on your filesystem, because it's broken. I'm running libbonobo since I built it and it didn't give any problems. A userspace lib should not be able to give kernel oopses or crashes, this is a pure hardware problem, or maybe an inconsistent filesystem.
Comment by Judd Vinet (judd) - Wednesday, 16 February 2005, 00:42 GMT
Re-opened by request from spider007
Comment by ... (spider007) - Wednesday, 16 February 2005, 08:33 GMT
Although I did not provide much information I totally disagree with the closing of this call without waiting for feedback of the submitter that reiserfsck fixed the problem. The fact that this upgrade _shouldn't_ be able to give kernel oopses is a non-reason too; since it does give a kernel oops. :) I have upgraded a lot of packages, and am using this machine a lot but never had _any_ problems. Why is an upgrade of 1 package causing a kernel oops then?

I have checked every /var/log file and have tried to pipe the error to a file. No luck however; I can't grab the exact error with anything else then a camera ;)

So: What information can I provide to solve this?
Comment by ... (spider007) - Wednesday, 16 February 2005, 08:37 GMT
btw; I did perform a reiserfsck on the filesystem. It found no errors
Comment by ... (spider007) - Wednesday, 16 February 2005, 17:46 GMT
The problem was fixed by upgrading all packages but libbonobo; and then upgrade libbonobo alone.

Loading...