You are not logged in.
Pages: 1
Hello everyone!
I experience crashes of the xfce4-terminal. I use it in drop-down mode, and the ALT+F1 key is binded to it.
Crashes means the terminal itself becomes gray. Both the, main space (where I type my commands), the tabs and the main bar (with the buttons File, Edit, View etc) are becoming gray. Rolling up and down still works. Invisible keys does not (like Ctrl+D seems unresponding). Rolling it up and down does not solve the issue. Only solution I found was to kill it from another terminal. I never experienced the issue when using non drop-down mode (truth be told, it wasn't that much...). As I can see, it happens when Remmina is also launched with a remote computer desktop. Remmina runs fullscreen on the same screen (double monitor setup), where xfce4-terminal should drop-down. This is the main monitor. It doesn't happen all the time. Unfortunately I haven't found a clear way to reproduce the problem, however it shows its ugly face once or twice a work day, which is really annoying. I switched to guake for a while (couple of months) but it lacks features I like in xfce4-terminal. Guake did not produce the issue ever.
Graphics card is nVidia Geforce GTS 450. Version of nvidia driver is 340.96-1 There is no bumblebee in action.
I run Debian stable up-to-date, xfce 4.10.1, xfce4-terminal 0.6.3-1+b1 according to dpkg. I haven't tested it with the current xfce release as I don't like the idea of messing with my production environment. As I'm writing the post, I think I will try to use remmina on the other screen (the one I don't open the terminal on) If it helps I will post it, however I would appreciate some brainstorming on the topic.
My settings are:
[Configuration]
ColorPalette1=#070736364242
ColorPalette2=#dcdc32322f2f
ColorPalette3=#858599990000
ColorPalette4=#b5b589890000
ColorPalette5=#26268b8bd2d2
ColorPalette6=#d3d336368282
ColorPalette7=#2a2aa1a19898
ColorPalette8=#eeeee8e8d5d5
ColorPalette9=#00002b2b3636
ColorPalette10=#cbcb4b4b1616
ColorPalette11=#58586e6e7575
ColorPalette12=#65657b7b8383
ColorPalette13=#838394949696
ColorPalette14=#6c6c7171c4c4
ColorPalette15=#9393a1a1a1a1
ColorPalette16=#fdfdf6f6e3e3
Term=xterm-color
DropdownKeepOpenDefault=TRUE
MiscAlwaysShowTabs=FALSE
MiscBell=FALSE
MiscBordersDefault=TRUE
MiscCursorBlinks=FALSE
MiscCursorShape=TERMINAL_CURSOR_SHAPE_BLOCK
MiscDefaultGeometry=80x24
MiscInheritGeometry=FALSE
MiscMenubarDefault=TRUE
MiscMouseAutohide=FALSE
MiscToolbarDefault=FALSE
MiscConfirmClose=TRUE
MiscCycleTabs=TRUE
MiscTabCloseButtons=TRUE
MiscTabCloseMiddleClick=TRUE
MiscTabPosition=GTK_POS_TOP
MiscHighlightUrls=TRUE
DropdownKeepAbove=FALSE
DropdownStatusIcon=FALSE
DropdownWidth=100
DropdownHeight=96
DropdownMoveToActive=FALSE
ColorPalette=#000000;#cc0000;#4e9a06;#c4a000;#3465a4;#75507b;#06989a;#d3d7cf;#555753;#ef2929;#8ae234;#fce94f;#739fcf;#ad7fa8;#34e2e2;#eeeeec
DropdownAnimationTime=200
Thank you for any help in advance!
hooger
Offline
It would be helpful if there was some logging info available. Does your distro use an ~/.xsession-errors log file and is there anything logged there, or if using systemd, is there anything in the journal?
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Thank you for your reply! Unfortunately I haven't checked those logs (partially because I haven't know of .xsession-errors which does exist in Debian as well). As soon as the crash happens again I post the logs.
hooger
Offline
Well, hello again. The crash happened again (at about 14:00, plus-minus 1 minute). 5 tabs were open, mc, top, 1 idle, 1 with bpython3 running a computation (it was a tcp socket server based on this page https://pymotw.com/2/socket/tcp.html---yeah I know, its python 2...), and another idle. Now I'm checking ~/.xsession-errors, which says nothing but paste the end of it nevertheless:
[184:184:0601/133417:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState()
weather-Message: getting http://api.yr.no/weatherapi/locationforecastlts/1.2/?lat=47.500000;lon=19.083300;msl=113
(wrapper:1105): GLib-CRITICAL **: Source ID 10457 was not found when attempting to remove it
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
nsBrowserAccess.prototype.openURI@chrome://browser/content/browser.js:15030:21
** Message: volume:65536
** Message: volume:65536
** Message: volume:65536
** Message: volume:65536
** Message: volume:65536
** Message: volume:65536
** Message: volume:65536
weather-Message: getting http://api.yr.no/weatherapi/locationforecastlts/1.2/?lat=47.500000;lon=19.083300;msl=113
I also haven't seen anything useful in the journal. User journal says nothing, using it with sudo reveals that there was dhcp request at 13:59:13 (2 dhclient logs, 9 NetworkManager logs, 2 Dbus logs, 1 nm-dispatcher log, 1 dhclient log and 9 sudo logs---I screwed up my password multiple times trying to read logs---in this order). BTW I used the following command(s):
(sudo) journalctl --since 13:55 --until 14:01
What else should I check?
Thanks in advance!
hooger
Offline
How about your Xorg.0.log file? Perhaps it's an issue with the graphics driver?
Otherwise, you may have to resort to using strace and/or gdb to debug this.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Xorg.0.log is also missing any relevant info. Now as I was experimenting (and also experiencing an uncalled for crash) I have a wild guess that it may also have something to with bpython as it was also open by the time crash happened. I will try to reproduce the bug a couple more times and see if there is really a correlation.
If anyone has any idea, please don't hesitate to post it.
Best,
hooger
Offline
Pages: 1
[ Generated in 0.013 seconds, 7 queries executed - Memory usage: 546.09 KiB (Peak: 546.94 KiB) ]