I am having a problem with Dolphin where if I am trying to view the files in an extra partition I have mounted it crashes. It only does it on partitions not usually mounted at start up. The error it gives is:
Executable: kdeinit4 PID: 6209 Signal: Aborted (6)
I am running fully updated openSUSE 11.4
Is this kde as shipped with 11.4 or have you added kde46?
What format is the partition?
Is it the only partition that does this?
On 06/12/2011 07:36 PM, hito kiri wrote:
>
> I am having a problem with Dolphin where if I am trying to view the
> files in an extra partition I have mounted it crashes. It only does it
> on partitions not usually mounted at start up. The error it gives is:
>
> Executable: kdeinit4 PID: 6209 Signal: Aborted (6)
>
> I am running fully updated openSUSE 11.4
>
>
that is strange!
how are you mounting this extra partition?
what is the file system of the extra partition?
is it on the hard drive you boot from?
or a different one? where is that different hard drive?
inside your computer?
on a USB cord?
on some other type connection?
on another computer in the local net?
on some other computer in a far away place, via the internet?
if not on your machine, what protocol and clients are you using to
access? (tcp/ip, samba, ssh, ftp, etc etc etc)
has your 11.4 always had this problem, or did it suddenly begin having it?
what version of KDE4 are you using?
you say your 11.4 is “fully updated”, what does that mean exactly: that
is are you updating from factory, tumbleweed, playground,
stable/unstable community repos?
or do you mean fully updated from oss, non-oss, update and packman only?
–
dd CAVEAT: http://is.gd/bpoMD
via NNTP openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10
Acer Aspire One D255, 1.66 GHz Atom, 1 GB RAM, Intel Pineview graphics
First, by fully updated I mean fully updated from oss non oss, update, and packman. I am using the KDE that comes with 11.4, so 4.6.0. The partition is an ext4 partition, and yes it appears to be the only one that it does it to. The hard drive it is on is not the boot hard drive, and yes it is internal. the strange thing is that it tends not to crash if I browse other files for a while, it seems to only crash when I open Dolphin and immediately try to view that partition. Also, this problem just started a day or two ago, and I don’t believe I had any recent KDE or Dolphin updates.
You might want to do a check on that partition
On 06/13/2011 06:06 AM, caf4926 wrote:
>
> You might want to do a check on that partition
i agree with that!..
something strange somewhere…
i’d say to boot to run level three, unmount that partition and fsck
it… see man fsck if you need to know which switches…or ask…
and, if that partition has problems that fsck fixes, i’d run it against
all linux partitions on that disk…
and, check the drive using s.m.a.r.t.
OH! if you are running any raid, LVM or reiser–forget everything i just
wrote because i know nothing about those file systems (except they
introduce a high level of complexity with little benefit, for me.) and
remind you to read my sig’s caveat…
this may have come from a update, and you may have uncovered a software
bug, but it sounds like a scary hardware problem to me…you might
wanna mount that (those) partition(s) read only and copy the data off as
your first step! just to be sure fsck doesn’t help you lose it all…
if fsck and smart says it is a healthy drive maybe we can help you find
the software problem to report (maybe not)…
(of course, we all know you probably already have a good backup, so i
just mention it in passing…)
–
dd
http://is.gd/bpoMD
Yep I do have a backup, and e2fsck seems to believe the drive is fine. tried using smartctl but it doesn’t seem to do much. I may be using it wrong.
Create a new test user
Try there and see if it’s different behaviour
On 06/14/2011 09:36 AM, hito kiri wrote:
> I may be using it wrong.
sudo /usr/sbin/smartctl -a /dev/sd[X]
man smartctl
–
dd
http://is.gd/bpoMD
Yep, I left off the -a on smartctl. But it reports that the drive seems to be fine. Also, tried logging in with a different user and had no problems.
Then you have crud in your .kde4
I would try this
Delete these files / folders:
.kde4/share/apps/dolphin (folder)
.kde4/share/config/dolphinrc (file)
On 06/15/2011 06:36 AM, caf4926 wrote:
>
>> Also, tried logging in with a different user and had no problems.
> Then you have crud in your .kde4
agree! thanks for helping Carl.
–
dd
http://is.gd/bpoMD