blkid returns nothing

Bug #1216688 reported by YannUbuntu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

On Ubuntu 12.04 . And reproduced also on Ubuntu 13.04.

sudo blkid returns no output, while other tools such as parted or fdisk work correctly.

Boot-Info on 12.04.2: http://paste.ubuntu.com/6016679/
Boot-Info on 13.04: http://paste.ubuntu.com/6016641/
Example under 12.10 with strace blkid in comment #6.

Revision history for this message
Phillip Susi (psusi) wrote :

What if you run blkid -p /dev/sda?

Changed in util-linux (Ubuntu):
status: New → Incomplete
Revision history for this message
YannUbuntu (yannubuntu) wrote :

The output says- /dev/sda: PTTYPE="dos"

Changed in util-linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Phillip Susi (psusi) wrote :

How about blkid -c /dev/null?

Revision history for this message
YannUbuntu (yannubuntu) wrote :

First, a blank line pops up in the terminal, ready to type in another command. A second later, a window pops up stating: "System program problem detected" and asks if I want to report the problem. Once I click to report the problem, it says: "Sorry, the application blkid has closed unexpectedly."

I tried closing the terminal, opening again and trying again. This time I get a fresh line like before, but no error messages pop up. Basically, nothing appeared to happen.

Rebooted and got the same results: first an error message, next nothing appears to happen.

Revision history for this message
Phillip Susi (psusi) wrote :

Can you try running blkid under strace?

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Attached an example with strace.

blkid returns nothing line 795
strace blkid from line 872.

hope this helps.

description: updated
Revision history for this message
Phillip Susi (psusi) wrote :

Ahh, so it is crashing. Can you run it under gdb and get a backtrace when it crashes?

Revision history for this message
YannUbuntu (yannubuntu) wrote :

These 3 Boot-Repair logs are not from my own computer, but from some users I don't personally know. Is there is a non-interactive way to get the backtrace you need? if yes, then please describe it and I will implement it in Boot-Repair's PPA so that the backtrace will appear automatically in the next log they generate via Boot-Repair. Else, please describe the procedure step-by-step and I will ask the users to follow it.

Revision history for this message
Phillip Susi (psusi) wrote :

Damn.. for some reason there seem to be no debug symbols for blkid so it isn't possible to get a backtrace. The only other way I can think of to proceed is to get a disk image of the offending partition ( sda1 ) and try to reproduce it locally.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in util-linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

Come to think of it, if it is crashing, apport should automatically pop up and ask to submit a bug report. Also I did find the debug symbols. Are you still seeing this and not getting the apport request to submit a bug report?

Changed in util-linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.]

Changed in util-linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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