Bug 313567 - kde programs don't start anymore after upgrade to 4.10 rc3
Summary: kde programs don't start anymore after upgrade to 4.10 rc3
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-20 15:05 UTC by Gandalf Lechner
Modified: 2013-02-16 10:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gandalf Lechner 2013-01-20 15:05:40 UTC
this is a bug i encountered after upgrading to 4.10 rc3, it wasn't there in rc2.

i don't know which part of kde is relevant here (bugzilla told me to guess a component so i picked plasma which might be unrelated); the behaviour i see is this:

computer boots fine and i can log into a kde plasma desktop session as usual, the programs i used last time start (dolphin, konsole for example). but if i now want to launch other programs, either by clicking a file in dolphin, or by clicking a program icon, or from the command line, these programs simply dont start. when trying to launch from the command line, i get an error message:

QDBusCOnnection: session D-Bus connection before QCoreApplication. Application may misbehave.

i tried with vlc, kate, systemsettings, ksystemlog, digikam ... all these programs don't start, it seems to be a general thing. non-kde programs like firefox or nautilus started from the command line do work, however.

i also tried loggin into a ubuntu session with its unity desktop. from there i could launch digikam, for example.
 
i dont know which other information would be useful for tracking this bug but will look it up if someone points me in the right direction.

Reproducible: Always

Steps to Reproduce:
see above
Actual Results:  
programs dont start

Expected Results:  
programs do start
Comment 1 Martin Flöser 2013-01-20 15:43:49 UTC
This sounds more like a support issue. I recommend to contact either forum.kde.org or a distribution specific support channel. Also ensure that all packages are updated correctly.
Comment 2 Gandalf Lechner 2013-01-20 15:46:41 UTC
support issue? i did check that all packages are updated correctly. does kde keep some log file where i can see what is wrong here?
Comment 3 Jekyll Wu 2013-01-20 21:26:57 UTC
Check your ~/.xsession-errors. Or run dolphin in gdb and see where it hangs. 

Anyway,  trouble shooting should go to forum, mailing list ,irc, etc .  Bug tracker is a bad place for that kind of support.
Comment 4 Gandalf Lechner 2013-02-16 10:50:24 UTC
I now figured out it was due to a script fiddling with the nvidia settings at autostart. Not sure why it causes such weired behaviour, but this bug can be closed