screem crashes when opening certain files on other partitions

[dausie]

Ubuntu 9.10
Screem crashed

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: uwe 1891 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xee240000 irq 17'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,17aa2025,00100200'
   Controls : 20
   Simple ctrls : 11
Date: Tue Nov 3 12:39:01 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=2c6cfecb-5639-4e79-8185-905190940f75
MachineType: LENOVO 195158G
OopsText: thinkpad_acpi: WARNING: sysfs attribute hotkey_enable is deprecated and will be removed. Hotkey reporting is always enabled
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=8968774a-86c9-40a6-b423-c13eda0d90b6 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: thinkpad_acpi: WARNING: sysfs attribute hotkey_enable is deprecated and will be removed. Hotkey reporting is always enabled
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 02/05/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE1WW (2.21 )
dmi.board.name: 195158G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr79ETE1WW(2.21):bd02/05/2008:svnLENOVO:pn195158G:pvrThinkPadT60:rvnLENOVO:rn195158G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 195158G
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

[WeatherGod (ben-v-root)]

dausie,

Thank you for taking the time to report this bug. To help us diagnose the problem, could you please describe what you were doing at the time of the crash?

[dausie (uwe-gelkermann)]

Hello WeatherGod,

I tried to start SCREEM. Perhaps the problems on boot have something to
do with that. Since ubuntu 9.10 (new installed on ext4 + mounted
old(ubuntu 9.04, ext3) /home partition + mounted old(win XP,
ntfs) /media/system + mounted old(Eigene Dateien, fat32) /media/eigene
the bootloader (grub beta) tells something like: waiting for /dev by
uuid ...
This message blocks the boot. Ubuntu can't mount the
"Windows"-partitions on boot but after login everything is fine ;-)

fstab is attached to this email

I'm sorry for the bad English...

Viele Grüße
Uwe

Am Dienstag, den 03.11.2009, 19:39 +0000 schrieb WeatherGod:
> dausie,
>
> Thank you for taking the time to report this bug. To help us diagnose
> the problem, could you please describe what you were doing at the time
> of the crash?
>

[WeatherGod (ben-v-root)]

Haha, silly me... I first read "I've started screem..." as "I've started to scream..."

Is this kernel crash reproducible? If Screem is set to open a particular file on one of those mounts, that might be how they could be related. If the crash is reproducible with Screem, could you see if you can force Screem open another file (from the command-line). Then, if you can find out what Screem was trying to auto-open, you could see if opening that file in another editor works.

At first glance, the fstab looks ok.

[dausie (uwe-gelkermann)]

Hello again,

the session_last.xml in /home/.screem shows exactly such a link. After
editing the xml-file, the problem is solved...

Do you have an idea, how i can solve the boot-problems? Or can I hope
for an update? ;-)

Thanks a lot
Uwe

Am Dienstag, den 03.11.2009, 20:48 +0000 schrieb WeatherGod:
> Haha, silly me... I first read "I've started screem..." as "I've started
> to scream..."
>
> Is this kernel crash reproducible? If Screem is set to open a
> particular file on one of those mounts, that might be how they could be
> related. If the crash is reproducible with Screem, could you see if you
> can force Screem open another file (from the command-line). Then, if
> you can find out what Screem was trying to auto-open, you could see if
> opening that file in another editor works.
>
> At first glance, the fstab looks ok.
>

[WeatherGod (ben-v-root)]

For the file that Screem was trying to auto-open, which partition was it on?

As for the boot problems, could you post your dmesg log file?

[dausie (uwe-gelkermann)]

...

Thank you
Uwe

Am Mittwoch, den 04.11.2009, 15:35 +0000 schrieb WeatherGod:
> For the file that Screem was trying to auto-open, which partition was it
> on?
>
> As for the boot problems, could you post your dmesg log file?
>

[dausie (uwe-gelkermann)]

sorry, I fogot the partition:

/media/eigene

Thank you
Uwe

Am Donnerstag, den 05.11.2009, 07:54 +0000 schrieb dausie:
> ...
>
> Thank you
> Uwe
>
> Am Mittwoch, den 04.11.2009, 15:35 +0000 schrieb WeatherGod:
> > For the file that Screem was trying to auto-open, which partition was it
> > on?
> >
> > As for the boot problems, could you post your dmesg log file?
> >
>
>
> ** Attachment added: "dmesg"
> http://launchpadlibrarian.net/35143490/dmesg
>

[WeatherGod (ben-v-root)]

Curious.... do you have any problems with opening and writing to other files on that partition? What happens if you open and edit the problem file using another editior like gedit?

[dausie (uwe-gelkermann)]

the file is now saved on /home/uwe ...
Opening and writing to other files without any problems.

But the boot problems afre still there. Do you have an idea?

Thanks
Uwe

Am Donnerstag, den 05.11.2009, 15:38 +0000 schrieb WeatherGod:
> Curious.... do you have any problems with opening and writing to other
> files on that partition? What happens if you open and edit the problem
> file using another editior like gedit?
>

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 430361, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[WeatherGod (ben-v-root)]

This is not a duplicate of that bug. It is merely a coincidence that the user has a similar log issue, but the bug in question is not caused by this.

[WeatherGod (ben-v-root)]

Undoing changes due to mistaken identification of duplicate

[Jeremy Foshee (jeremyfoshee)]

Hi dausie,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 472674

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[dausie (uwe-gelkermann)]

Hello,

problem is solved ;-)

Greetings
Uwe

Am Donnerstag, den 22.04.2010, 17:53 +0000 schrieb Jeremy Foshee:
> Hi dausie,
>
> This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.
>
> apport-collect -p linux 472674
>
> Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>