Description of problem: Unable to launch app from run box in kde Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Right click somewhere on desktop 2. Select Run Command... 3. enter konsole If you type slowly you will notice a konsole selection show up below the run box. Once that happens the run box will close and app does not run. Since I install xterm during install, typing xterm as fast as possible will still not run the application.
any errors on ~/.xsession.log ? (don't remember the exact name)
Keywords: (none) => NEEDINFO
Created attachment 3266 [details] ~/.xsession-errors Clean install of Mageia-3-beta1-x86_64-DVD.iso. Default runlevel: 3 Package Group Selection has all package groups selected except LSB and Other Graphical Desktops + updates followed with urpme --auto-orphans and reboot.
Keywords: NEEDINFO => (none)
Created attachment 3267 [details] virtualBox backtrace
Created attachment 3268 [details] ~/.xsession-errors
Attachment 3266 is obsolete: 0 => 1
again some virtual soprano and krunner stuff
CC: (none) => balcaen.johnAssignee: bugsquad => nicolas.lecureuil
*** Bug 8461 has been marked as a duplicate of this bug. ***
CC: (none) => mustafaa.alhamdaani
Priority: Normal => release_blockerSeverity: normal => majorHardware: x86_64 => All
I can't reproduce with the KDE 4 live iso on virtualbox. I'll try with the dvd install later.
Btw could you provide the list of rpm removed with the use of auto-orphans ?
I can't reproduce with the x86_64 dvd iso... I'm also decreasing the priority & the release blocker status until we can get a way to reproduce it cleary. Test was also done in virtualbox (from cauldron).
Severity: major => normalPriority: release_blocker => NormalStatus: NEW => UNCONFIRMEDEver confirmed: 1 => 0
(In reply to comment #7) >I can't reproduce with the KDE 4 live iso on virtualbox Odd, I just completed that activity to get your orphan list and tested and it still fails. (In reply to comment #8) > Btw could you provide the list of rpm removed with the use of auto-orphans I was about to but found out it is not needed. (In reply to comment #8) > I'm also decreasing the priority & the release blocker status until we can > get a way to reproduce it clearly. No problem with reduction in priority and blocker status but I thought UNCONFIRMED was poor since someone else has the problem indicated by the duplicate bug report. > I can't reproduce with the x86_64 dvd iso... Problem exists on all three of my systems and was on my 64 bit VirtualBox guest with all updates applied. I deleted the VB guest. Started a new one. Install procedure was: Clean install of Mageia-3-beta1-x86_64-DVD.iso. Default runlevel: 3 Package Group Selection screen has all package groups selected except LSB and Other Graphical Desktops. Enabled Individual package selection and added xterm from the KDE section. During partition phase, I used labels. In boot loader configuration I picked grub text, delay 5. I modified the title to have mga3_64_beta1, and removed the splash quite and resume stuff. Reboot, log into junk, startx, wait for startup music to complete, Left click on desktop, select Run Command, entered xte, search showed xterm and run box blinked out. Bug is reproducible.
Ever confirmed: 0 => 1Status: UNCONFIRMED => ASSIGNED
ASSIGNED would be mean that someone is *working* on it which is not the case. UNCONFIRMED was added since i (since i'm one of kde's packager) was not able at all to reproduce it... Anyway did you try to disable some krunner options to see if it's related to some options enable by default ? From comment #3 i would get a look@ the bookmark/webshortcut option in krunner which seems to be the culprit of the crash for you (certainly related to firefox)
(In reply to comment #11) > ASSIGNED would be mean that someone is *working* on it which is not the case. > UNCONFIRMED was added since i (since i'm one of kde's packager) was not able at > all to reproduce it... Sorry, did not know. Unconfirmed hid it from my bug query. I can see how a live cd might not create the problem and I'll guess you did not pick the same package groups that I do for the dvd install. > Anyway did you try to disable some krunner options to see if it's related to > some options enable by default ? Kinda the opposite. I was worried one of numerous changes was causing the problem. I turn off a bunch of features that I do not want or need in an attempt to speed up desktop login. > From comment #3 i would get a look@ the bookmark/webshortcut option in krunner > which seems to be the culprit of the crash for you (certainly related to > firefox) webshortcut on/off has no effect on run command abort. It fails enabled on just dvd VB guest and fails with it off, log out/in on host system.
Status: ASSIGNED => NEW
Bug is reproducible using Mageia-3-beta1-LiveDVD-KDE4-x86_64-DVD, both my systems and two VMs, just install it, with everything as the default, then try krunner, it will crash, Kickoff menu also crashes when I search for anything, I've also reported bugs at bugs.kde.org if you want to see the backtrace: https://bugs.kde.org/show_bug.cgi?id=312177 https://bugs.kde.org/show_bug.cgi?id=312180
It is reproducible even without installing, just created a new VM and booted Mageia-3-beta1-LiveDVD-KDE4-x86_64-DVD and tried krunner and it crashed.
confirmed here, Mageia-3-beta1-LiveDVD-KDE4-x86_64-DVD on vmware. it stop crashing if I deselect the bookmarks plugin
CC: (none) => tmassimi
*** Bug 8698 has been marked as a duplicate of this bug. ***
CC: (none) => shlomif
I can confirm it too, I saw it since at least a month ago but I thought it would go away with future updates.
CC: (none) => juan.baptiste
The problem is the bookmarks plugin, still affect me in M3 beta 2
Using the DVD version, it does not crash anymore, maybe a missing package in the LiveDVD version? but it should NOT crash anyway.
please make it crash again but this time install the debug packages.
(In reply to comment #20) > please make it crash again but this time install the debug packages. I already did, you can find the backtrace here: https://bugs.kde.org/show_bug.cgi?id=312177
Same problem here. To me it looks like the type-ahead feature of the "run command" dialog is broken (the following example might help to get a better understanding of what is happening): 1. Select the Run command kde menu item (that launch the small dialog window) 2. Slowly type "k" and than "f" - so far, so good 3. Type "i" - will be immediately and automatically expanded to kFileReplace (in fact, I had intended to type kfind) 4. The small dialog window disapperars - kfilereplace is evidently and wrongly being launched and ends up in the KDE crash handler. Maybe this is one bug - the type-ahead getting out of control, maybe two: (a) type-ahead galopping away on wrong assumptions and (b) the program thus launched by run-command getting badly launched.
CC: (none) => juergen.harms
Latest kde updates resolves the problem.
Status: NEW => RESOLVEDResolution: (none) => FIXED
*** Bug 9237 has been marked as a duplicate of this bug. ***
CC: (none) => dbello