kate does not appear anymore after a second restart; if I remove ~/.kde and restart it starts normally but after closing kate it does not show any window nor the menu bar but the kate process is still active I have a fresh ubuntu 12.04 install on a macbook pro. other kde applications work fine (kile, krusader) Reproducible: Always Steps to Reproduce: 1. sudo apt-get install kate konsole 2. start kate, open konsole; close kate 3. start kate agian Actual Results: kate inaccessable; killall kate Expected Results: show screen, etc OS: Linux (x86_64) release 3.2.0-35-generic
This also happens when I start the compiled version of kate. All windows disappear after clicking on close of the "Show tips on startup" Hence, there must be a problem with my configuration files (~.kde/) and Ubuntu 12.04.
Do you still have this issue? Sounds like Kate is running the background somehow and therefore blocking new Kate instances. Which option do you have in Configure Kate > Settings > "Sessions" > "Behavior on Application Startup"?
Yes, the issue is still there and is very annoying. Which option do you have in Configure Kate > Settings > "Sessions" > "Behavior on Application Startup"? I tested all 3 setting without success. Btw. I can start kate and get the "Tip of the day" window. Then keeping this open I am able to access the menu. But when closing the "Tip of the day" window, kate disappears in the background. Any further ideas?
Can you please follow http://kate-editor.org/get-it/ and build Kate from sources? We'd be interested if the problem then still persists. If it still persists, can you do the following: Install "gdb" and then run: ./run.sh gdb kate Then in gdb, type "run". When the problem occures, go into the gdb window and press Escape (ESC), type "bt" and press enter. Then copy the backtrace into this report.
I built kate from sources and the error persists. I think it is a config problem. Maybe also a konsole crash as it says there is another instance running Here is the backtrace: http://pastebin.com/x1mHeeYm
Ok, the gdb info doesn't help, though, unfortunately ;) Well, from my side: no idea... sorry.
I am running ubuntu 12.04 (kernel 3.2) on a macbook pro 8,2 where the graphic driver is not found (no switching of the graphic cards) Could that result in the behavior that the kate window is disappearing? However, all other programs including kile, konsole, etc work fine...
Could you temporarily delete all kate configuration files, and check, if it is indeed a configuration issue? Also, the backtrace from comment #5 is not really a crash, you simply used ^C while it ran.
I had some sucess in tracing the problem. I use a mac book pro 8,2 early 2011 with an extern screen (without being able to use the grafic card). Anyhow, when I go to Displays and mirrow them the "missing" kate window appears again. Then I can move it and access kate normal. The problem reappears after a shutdown. However, kate is the only program which has this behavior. @Christoph I tried deleting config files that but this did not help.
Adding Thomas, who better understands how to debug windows suddenly changing screens.
Cause the problem (ie. lost kate window), open konsole and run xwininfo -tree -root | grep -i kate The output will/should be sth. like 0x280006e "kate": ("kate" "Kate") 640x409+0+0 +0+0 0x2800066 "Code Completion Configuration – Kate": ("kate" "Kate") 640x409+0+0 +0+0 0x280005c "Kate": ("kate" "Kate") 640x409+0+0 +0+0 0x280000c "kate": ("kate" "Kate") 640x409+0+0 +0+0 0x2800004 "kate": ("kate" "Kate") 640x409+0+0 +0+0 0x2800028 "Untitled – Kate": ("kate" "Kate") 1920x1000+0+0 +0+39 The padded (and usually last) entry (1920x1000 in this case) is the actualy kate window and the hex number ("0x2800028") is its ID Next run xprop -id #ID > lost_kate.props xwininfo -id #ID > lost_kate.info where you replace #ID by the actual ID printed above. This will generate you two files (lost_kate.*) which you please attach to the bug. In case you're not sure that you used the proper window ID, just post the output of "xwininfo -tree -root | grep -i kate" as well and mention the #ID you ultimately used.
Created attachment 82335 [details] xprop output for lost kate window
Created attachment 82336 [details] xwininfo output for lost kate window
the window looks ok. it's mapped, on the first virtual desktop, valid position (the titlebar is 4px out on the top) two things: 1) the geometry hints look like this is a multiscreen setup. the window is quite on the upper left of the combined screens (in case you just turned off that screens power and assume the system to know about that: "no") 2) if it's not about the used screen for sure, try replacing compiz by eg. "kwin --replace" or "openbox --replace" (the window might falsely not be painted by the compositor or stacked under eg. the desktop)
correct I am using a multiscreen setup with laptop and a wide screen. when I go to displays and mirrow the screens I usually get to see the missing kate window. I can then move it around and it works fine. But after restart I'll have to do this again. I tried your suggestion with compiz --replace, but this did not help. Any ideas on how to fix this problem?
restarting compiz will certainly not work - only replacing the WM by another might expose a pot. compiz bug. the issue however seems to have its core in the MS setup. please post the output of "xrandr -q"
(In reply to comment #16) > restarting compiz will certainly not work - only replacing the WM by another > might expose a pot. compiz bug. > > the issue however seems to have its core in the MS setup. > please post the output of "xrandr -q" xrandr -q Screen 0: minimum 320 x 200, current 4240 x 1600, maximum 16384 x 16384 LVDS connected 1680x1050+0+550 (normal left inverted right x axis y axis) 331mm x 207mm 1680x1050 59.9*+ 1400x1050 60.0 1280x1024 59.9 1440x900 59.9 1280x960 59.9 1280x854 59.9 1280x800 59.8 1280x720 59.9 1152x768 59.8 1024x768 59.9 800x600 59.9 848x480 59.7 720x480 59.7 640x480 59.4 DisplayPort-0 connected 2560x1600+1680+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 59.9* 1280x800 59.9 DisplayPort-1 disconnected (normal left inverted right x axis y axis) DisplayPort-2 disconnected (normal left inverted right x axis y axis)
Well, that's the problem: The screen is: LVDS connected 1680x1050+0+550 And the window is: 700x480+57+-4 The window is only 480px high but placed at y = -4px where the visual part of the screen starts at y=550px. Not sure whether kate demands such position, but compiz should neither honor such demand (if it results in an off-any-screen position on the root window) I'll see whether kate would in general asks for a specific position, but if it was kwin and not compiz, i'd rank this a bug in kwin - iow. imo that's a compiz bug even iff kate should ask for that position.
The Kate (v3.11.0) Mainwindow does (here) not set PPosition or USPosition on its XSizeHint, nor does it send a ConfigureRequest - iow. Compiz (the WindowManager) is likely responsible for the offscreen position alone. Why this would only happen if there's a present configuration and only for kate, i can't say. Does it matter on what screen you close kate or which state (maximized? bigger than the smaller screen?) it has at that time?
At another Ubuntu 12.04 machine with two screens, the kate main window opens on a new workspace window. Which is a bit strange and might be caused by the same mechanism). This does not happen in single screen mode (just my notebooks screen).
(In reply to comment #20) > At another Ubuntu 12.04 machine with two screens, the kate main window opens > on a new workspace window. I beg your pardon, it does what? (You mean, like compiz creates a new virtual desktop and places the window there? Please notice that i do not use ubuntu/unity/compiz) I suggest to try the behavior on another windowmanager (eg. kwin, openbox, metacity) and if it doesn't behave strangely there and nicely opens the window in sight reliably, report a bug to compiz maintainers (canonical, is it?) They should be able to notice whatever in the kate startup process causes compiz to react in such ways on multiscreen setups (maybe due to the session selection modal dialog?)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Hi, I believe the bug can be closed. It worked for me. I will change status to resolved. Thanks for the help! Laub