| Summary: | The panel window opens empty (not a crash). Console error: krusader(3404)/kdecore (KLibrary)... | ||
|---|---|---|---|
| Product: | [Applications] krusader | Reporter: | Alejandro Jakubi <jakubi> |
| Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | bushido76, jan_lepper, krusader-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 2.4.0-beta1 "Migration" | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/krusader/9a6e4ab904fb70fbcd449a8d596e0261ab3f39ef | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
| Attachments: |
Screenshot of Krusader panel
debug output to terminal with all kdebugdialog options set |
||
|
Description
Alejandro Jakubi
2012-07-29 08:32:43 UTC
Could you please provide a screenshot of how it looks ? Also you can get more output on the termial by enabling 'krusader' in kdebugdialog (in case you didn't do that already). Created attachment 74152 [details]
Screenshot of Krusader panel
Comment on attachment 74152 [details]
Screenshot of Krusader panel
As you see, the panel window opens empty.
Comment on attachment 74152 [details]
Screenshot of Krusader panel
As you see, the panel window opens empty.
Created attachment 74153 [details]
debug output to terminal with all kdebugdialog options set
No, I have not made any debugging with kdebugdialog yet. Actually, I have stopped using this Ubuntu installation shortly after this problem appeared (I am using Linux Mint 13 now in another partition).
On Tue, 25 Sep 2012 04:48:16 +0000 Alejandro Jakubi <jakubi@df.uba.ar> wrote: > https://bugs.kde.org/show_bug.cgi?id=304233 > > --- Comment #5 from Alejandro Jakubi <jakubi@df.uba.ar> --- > Created attachment 74153 [details] > --> https://bugs.kde.org/attachment.cgi?id=74153&action=edit > debug output to terminal with all kdebugdialog options set > > No, I have not made any debugging with kdebugdialog yet. Actually, I > have stopped using this Ubuntu installation shortly after this > problem appeared (I am using Linux Mint 13 now in another partition). > Unfortunately the debug output doesn't give any hints - although it made me aware an unrelated problem - thanks for that ;-). On the screenshot the menubar isn't shown as you said in your first comment. But if I understand you correctly, this doesn't happen anymore on your current system ? (In reply to comment #6) > But if I understand you correctly, this doesn't happen anymore on your > current system ? No, it is not correct, this problem happens right now. The screenshot and debug log were produced a few hours ago at your request. This system has several partitions with multiple boot (by grub). Ubuntu 12.04 was the first Linux distro installed in one of them. But I have stopped using it, mainly because of this problem with Krusader. So, for now, I have switched my main use to Linux Mint 13, installed in another partition (and some more distros are planed for installation). is there any other test that could be more informative? If I were to bet, I would say that it is something related to X-Windows, the .Xdefaults file, X-fonts, or something like that. But it is just a guess... On Tue, 25 Sep 2012 09:42:05 +0000 Alejandro Jakubi <jakubi@df.uba.ar> wrote: > https://bugs.kde.org/show_bug.cgi?id=304233 > > --- Comment #7 from Alejandro Jakubi <jakubi@df.uba.ar> --- > (In reply to comment #6) > > But if I understand you correctly, this doesn't happen anymore on > > your current system ? > > No, it is not correct, this problem happens right now. The screenshot > and debug log were produced a few hours ago at your request. > > This system has several partitions with multiple boot (by grub). > Ubuntu 12.04 was the first Linux distro installed in one of them. But > I have stopped using it, mainly because of this problem with > Krusader. So, for now, I have switched my main use to Linux Mint 13, > installed in another partition (and some more distros are planed for > installation). > > is there any other test that could be more informative? If I were to > bet, I would say that it is something related to X-Windows, > the .Xdefaults file, X-fonts, or something like that. But it is just > a guess... > What comes to my mind: different video driver different qt style export QT_GRAPHICSSYSTEM=raster test if it happens under a different user account I have created a fresh user account, where the Krusader panel window started OK (after the initial setting screens). It seems to me that this verification rules out graphics driver issues, while confirming that something in the configuration screwed up. Do you agree? If so, what differences would you suggest start looking at? By the way, I have not observed so far any other application affected by a similar problem. Yes, it seems to be a configuration issue. I suggest the following tests: rename ~/.kde/share/config/krusaderrc rename ~/.kde/share/apps/krusader/ rename ~/.kde/ If you haven't done so, test if other Qt(or KDE) applications misbehave too. No similar misbehavior occurs with e.g. QtOctave or KWrite. I have renamed ~/.kde/share/config/krusaderrc, started Krusader and the panel window started OK (after the initial setting screens). So, what to look at in this file? On Sat, 29 Sep 2012 01:49:03 +0000 Alejandro Jakubi <jakubi@df.uba.ar> wrote: > https://bugs.kde.org/show_bug.cgi?id=304233 > > --- Comment #12 from Alejandro Jakubi <jakubi@df.uba.ar> --- > No similar misbehavior occurs with e.g. QtOctave or KWrite. > I have renamed ~/.kde/share/config/krusaderrc, started Krusader and > the panel window started OK (after the initial setting screens). So, > what to look at in this file? > Delete the 'Startup' section (this stores which tabs were opened and their browsing history) - ignore possible warnings about the config file being binary. On Sat, 29 Sep 2012 11:40:09 +0200 jan <jan_lepper@gmx.de> wrote: > On Sat, 29 Sep 2012 01:49:03 +0000 > Alejandro Jakubi <jakubi@df.uba.ar> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=304233 > > > > --- Comment #12 from Alejandro Jakubi <jakubi@df.uba.ar> --- > > No similar misbehavior occurs with e.g. QtOctave or KWrite. > > I have renamed ~/.kde/share/config/krusaderrc, started Krusader and > > the panel window started OK (after the initial setting screens). So, > > what to look at in this file? > > > > Delete the 'Startup' section (this stores which tabs were opened and > their browsing history) - ignore possible warnings about the config > file being binary. PS: you need to delete ALL sections of the form [Startup][foo][bar]. OK. I have deleted the [Startup] and [Startup][foo][bar] sections (no warning from the nano editor, called by mc). Then, I have started Krusader and the panel window opened fine, almost as it was before this problem began (likely the diferences arising because some default is being used instead of the deleted configured items). So, what could be said about the origin of the problem at this point? On Sun, 30 Sep 2012 08:06:47 +0000 Alejandro Jakubi <jakubi@df.uba.ar> wrote: > https://bugs.kde.org/show_bug.cgi?id=304233 > > --- Comment #15 from Alejandro Jakubi <jakubi@df.uba.ar> --- > OK. I have deleted the [Startup] and [Startup][foo][bar] sections (no > warning from the nano editor, called by mc). Then, I have started > Krusader and the panel window opened fine, almost as it was before > this problem began (likely the diferences arising because some > default is being used instead of the deleted configured items). > > So, what could be said about the origin of the problem at this point? > OK, now we know something in the Startup section is at fault. Next I would try only deleting entries directly under [Startup] and leaving [Startup][...]. If that doesn't fix it, delete [Startup][Left/Right Tab Bar][Tabs][TabX] and sub-sections one after the other to identify the tab at fault. Hello, I can confirm this issue in 2.40. I experienced this problem several times in the last year. At the moment I can start krusader as root but not with my other user account. Renaming the krusaderrc file "solved" the problem. So it is definately problem in the config file or in reading the config at startup. Please tell me how could I support your analysis. It would be great to solve the problem in 2.50... ;) Tom Hello guys, I narrowed the problem down. It's caused by the config-parameter "Show Terminal Emulator=true" in the section "[Startup]". When I remove the entry in the krusaderrc-file, everything is fine again. Tom I can confirm that removing the line: Show Terminal Emulator=true from the section [Startup] solved the problem for my krusaderrc file. I guess that I have set this option while experimenting on options because of the other bug that the terminal emulator could not be set for a user action. On Wed, 03 Oct 2012 10:00:36 +0000 Alejandro Jakubi <jakubi@df.uba.ar> wrote: > https://bugs.kde.org/show_bug.cgi?id=304233 > > --- Comment #19 from Alejandro Jakubi <jakubi@df.uba.ar> --- > I can confirm that removing the line: > Show Terminal Emulator=true > from the section [Startup] solved the problem for my krusaderrc file. > > I guess that I have set this option while experimenting on options > because of the other bug that the terminal emulator could not be set > for a user action. > Sorry for the delay. I think I have nailed down the cause: different config sections are used for saving and loading of the splitter sizes. Also there is no proper check against invalid values. If you still have the config file which triggers the bug, could you please tell me the value of [Private]: "Terminal Emulator Splitter Sizes" (in case it exists) ? Git commit 9a6e4ab904fb70fbcd449a8d596e0261ab3f39ef by Jan Lepper. Committed on 27/02/2013 at 18:10. Pushed by janlepper into branch 'master'. FIXED: [ 304233 ] empty main view on startup / FIXED: main view splitter sizes are not restored use config group passed to KrusaderView::start() for loading splitter sizes instead of "Private" also add better checks against invalid values M +2 -0 ChangeLog M +15 -8 krusader/krusaderview.cpp http://commits.kde.org/krusader/9a6e4ab904fb70fbcd449a8d596e0261ab3f39ef |