On Thu, 16 Jun 2011 23:06:03 +0530, sonicboy
<sonicboy@no-mx.forums.opensuse.org> wrote:
>
> It’s getting very weird :sarcastic:
>
> I renamed my .kde4 folder as you said, started with a virgin desktop,
> but guess what…
>
> when starting up any of the programes I’ve mentionned before, they
> crash again…
>
> Under my new user, everything works fine.
>
> Very strange if you ask me 
>
you are not in the habit of running (graphic) KDE as root, are you?
–
phani.
Do you mean running KDE programs as root?
If so, only very sporadically is use dolphin as root, to edit files outside my home folder or something. But I always close it immediately after this is done. I cannot recall using any other kde program as root.
On Fri, 17 Jun 2011 01:06:03 +0530, sonicboy
<sonicboy@no-mx.forums.opensuse.org> wrote:
>
> Do you mean running KDE programs as root?
>
> If so, only very sporadically is use dolphin as root, to edit files
> outside my home folder or something. But I always close it immediately
> after this is done. I cannot recall using any other kde program as root.
>
no, i meant logging as ‘root’ into the KDE GUI. doesn’t sound as if you
had been doing that. this would have been a way i could think of to mess
up ownership in your home directory. if you didn’t do that, i have no idea
what causes your trouble. in your position i would try to find out what’s
different between the new user account that works ok, and your old one
that doesn’t. and not all settings & data are saved under ~/.kde%, by the
way. there’s stuff in ~/.config, ~/.local, and ~/.cache too.
–
phani.
On Thu, 16 Jun 2011 23:06:03 +0530, sonicboy
<sonicboy@no-mx.forums.opensuse.org> wrote:
>
> It’s getting very weird :sarcastic:
>
> I renamed my .kde4 folder as you said, started with a virgin desktop,
> but guess what…
>
> when starting up any of the programes I’ve mentionned before, they
> crash again…
>
> Under my new user, everything works fine.
>
> Very strange if you ask me
>
i’m only guessing now, but perhaps you can look at the environment
variables in both the new and old user accounts (printenv), and see if &
where they differ.
–
phani.
On 2011-06-16 15:06, sonicboy wrote:
>
> @ Carl & Henk
>
> I cannot create a new user or look the programs up since both
> kpackagekit & YaST are also infected with the program, they crash
> immediately after booting them up.
Use YaST in text mode.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2011-06-16 17:06, hcvv wrote:
>
> gropiuskalle;2354135 Wrote:
>> Just a minor issue: when switching to another tty, one does not use ‘su’
>> but locks in directly as root, so no need to double-exit either.
> That is not as I outlined it above. I let him log in with the normal
> user first. I know that you can login as root directly, but that is not
> the “best practise” I want to promote.
Why would not log in as root in text mode be “best practice”? :-?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I agree there is no problem logging as root to an xterm it is logging in to a GUI as root that can cause ownership problems.
As to OP’s problem check your disk with a fsck on your home partition run from a CD or other Linux. (must be run against a non-mounted partition) You may have a corrupted file system.
Immediately after a program crash, hit Ctrl-Alt-F1, login with username and password, and do:
tail -20 .xsession-errors
post output here. The problem does not exist for a new user, so it’s in your homedir. This leads to ~/.kde4 usually, but not necessarily. There can also be settings in ~/.config . So we need to find out what crashes the programs. It would also help to start a program, known to crash, from a terminal window, then copy the output from the terminal window here, so that we can see what it crashes on.
output of **tail -20 .xsession-errors
**
"/usr/bin/nepomukservicestub(2475)" Error in thread 139873394558816 : "Invalid iterator."
"/usr/bin/dolphin(10978)" Error in thread 139993412736784 : "Invalid iterator."
"/usr/bin/dolphin(10978)" Error in thread 139993412736784 : "Invalid iterator."
[/usr/bin/nepomukservicestub] virtual void Soprano::Server::ServerConnection::run() thread done.
[/usr/bin/nepomukservicestub] void Soprano::Server::ServerCore::serverConnectionFinished()
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection
void Soprano::Server::ServerCore::serverConnectionFinished() Connection removed. Current count: 7
kdeinit4: preparing to launch /usr/lib64/kde4/kio_trash.so
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
KCrash: Application 'dolphin' crashing...
kdeinit4: preparing to launch /usr/lib64/kde4/libexec/drkonqi
[/usr/bin/nepomukservicestub] virtual void Soprano::Server::ServerConnection::run() thread done.
void Soprano::Server::ServerCore::serverConnectionFinished()
virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection
void Soprano::Server::ServerCore::serverConnectionFinished() Connection removed. Current count: 6
(I did this in terminal, not via ctrl-alt-F1, but I compared it and except for the numbers in the beginning, it was the same.
output when starting up dolphin:
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
"/usr/bin/dolphin(11900)" Error in thread 139689767626512 : "Invalid iterator."
dewouter@linux-j1ke:~> Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
KCrash: Application 'dolphin' crashing...
sock_file=/home/dewouter/.kde4/socket-linux-j1ke.site/kdeinit4__0
I’ll try an fsck this evening and see what the results are. Just booting from live cd and typing in fsck in terminal I guess? Or do i need some parameters also?
Can you explain more upon printenv commando please?
Thanx for support
On Fri, 17 Jun 2011 21:06:03 +0530, sonicboy
<sonicboy@no-mx.forums.opensuse.org> wrote:
> Can you explain more upon printenv commando please?
“Print the values of the specified environment VARIABLE(s). If no
VARIABLE is specified, print name and value pairs for them all.” – from
the manual page for printenv. (konsole: “man printenv”).
i’ve sometimes changed environment variables, only affecting one user, and
this might conceivably lead to KDE programs looking for libraries in the
wrong place…on second thought, this doesn’t appear very likely as reason
for your problems though.
–
phani.
Hi,
After being busy and unable to look to repair my problem, all of a sudden it dissapeared. I rebooted my pc to my normal account (formerly, I used the new-made account) and no program crashed. Before this, I had a small update with yast but nothing special. The problem went away like it came: without any trace…
thanx for the help