lsb_release crashed with IOError in getstatusoutput()

Bug #217297 reported by Bart Rose
48
This bug affects 6 people
Affects Status Importance Assigned to Milestone
lsb (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: lsb

I have mapped <Control><Alt>Delete to the gnome-system-monitor in metacity w/ gconf. If I switch between metacity and compiz w/ the fusion-icon, when I come back to metacity and try to ctrl-alt-del I get the reported message. This only happens after cycling between metacity and compiz then back. I don't known if this is an lsb problem or fusion-icon. Thanks for any insight and let me know if you need any other info.

Thinkpad R52
Hardy Beta
kernel: 2.6.24-16-generic
lsb v 3.2-4ubuntu1

ProblemType: Crash
Architecture: i386
Date: Mon Apr 14 09:40:34 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/lsb_release
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: lsb-release 3.2-4ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/lsb_release -irc
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/lsb_release', '-irc']
SourcePackage: lsb
Title: lsb_release crashed with IOError in getstatusoutput()
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner video

Tags: apport-crash
Revision history for this message
Bart Rose (jbrose3) wrote :
Revision history for this message
GrumpyPiano (grumpypiano) wrote :

I seem to get this crash report from Apport when I try to launch gnome-system-monitor through eee-control-tray (for eeepc).
Dunno if the crash report will help. I don't even see how these are related.

Revision history for this message
GrumpyPiano (grumpypiano) wrote :

Sorry for posting again, but what I actually experience (not what apport tells me) is quite like this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/248788/
Except I have no idea why the bug was closed. I can't see how to run it.

Changed in lsb (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Is this still an issue for you? Which Ubuntu version do you use? Thank you for telling us!

Changed in lsb (Ubuntu):
status: New → Confirmed
Revision history for this message
Jazz (iguanamiyagi) wrote :

I just experienced this issue on 12.04 LTS.

Revision history for this message
Victor Mitin (caesarmv) wrote :

The same here, 12.04 LTS
Linux cd 3.2.0-33-generic-pae #52-Ubuntu SMP Thu Oct 18 16:39:21 UTC 2012 i686 i686 i386 GNU/Linux

Revision history for this message
avejidah (avejidah) wrote :

Same issue. 12.04 LTS, fully updated as of today.

Revision history for this message
Thomas (tom-rosary) wrote :

same problem since last week in 12.04 LTS (3.5.0-25-generic)

Revision history for this message
Christian (bolek2000) wrote :

Same problem with my laptop 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with fresh updates. I have the impression that this in my case always happened when the update manager starts automatically.
I friend of mine, whom I installed her laptop to try Ubuntu along with Windows also has this error message quite a lot of times.

Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

Changed in lsb (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.