| 2008-09-09 17:30:21 |
Harald Sitter |
kde4libs: statusexplanation |
|
Norbert, I rally can't follow, but it sounds mostly unrelated... anyway...
Someone please check if this still is an issue in 4.1.1. If so, please also try with a new user (or move your .kde4/.kde directory to somewhere else in order to reset your configuraitons).
Finally, if all this still leads to the described issue (or if you don't care about a new user/moving your configurations ;-):
1) Install kdebase-dbg kdebase-runtime-dbg kdebase-workspace-dbg
2) start the application kdebugdialog (via a terminal, this application is not visible in the menu)
3) click on the "Select all" button
4) click OK
5) open a terminal (e.g. konsole) and enter the following:
kquitapp kded; sleep10; kded4
6) this will make kded4 give super verbose debugging information in the terminal
7) try to trigger the issue
8) get a backtrace from the kcrash dialog and a the last few lines from the terminal attached to this report
9) start kdebugdialog again and deselect all again
The backtrace is most important since it hopefully gives us the possibility to find the crash location, the terminal output can help us find an appropriate solution. The sooner you can get the information the sooner we can fix the issue :)
Bug Triagers: This bug has to stay open until 2008-11-09! |
|
| 2008-10-10 01:12:11 |
Jonathan Thomas |
kde4libs: statusexplanation |
Norbert, I rally can't follow, but it sounds mostly unrelated... anyway...
Someone please check if this still is an issue in 4.1.1. If so, please also try with a new user (or move your .kde4/.kde directory to somewhere else in order to reset your configuraitons).
Finally, if all this still leads to the described issue (or if you don't care about a new user/moving your configurations ;-):
1) Install kdebase-dbg kdebase-runtime-dbg kdebase-workspace-dbg
2) start the application kdebugdialog (via a terminal, this application is not visible in the menu)
3) click on the "Select all" button
4) click OK
5) open a terminal (e.g. konsole) and enter the following:
kquitapp kded; sleep10; kded4
6) this will make kded4 give super verbose debugging information in the terminal
7) try to trigger the issue
8) get a backtrace from the kcrash dialog and a the last few lines from the terminal attached to this report
9) start kdebugdialog again and deselect all again
The backtrace is most important since it hopefully gives us the possibility to find the crash location, the terminal output can help us find an appropriate solution. The sooner you can get the information the sooner we can fix the issue :)
Bug Triagers: This bug has to stay open until 2008-11-09! |
Closing as it's 2008-11-09 ;-)
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|
