[arch-general] Gedit startup issues
Dear fellow Archers, I'm using XFCE4 on an up-to-date Arch Linux installation I've built from the official downloadable image and by following the instructions on the Arch wiki. The system works fine, but there are still some bugs I want to zap out. First thing is: Sometimes gedit won't start when launching it over the GUI. I've installed it from the package repositories by using pacman, and it works most times, but, sometimes (I can't see any pattern in when it works and when not) it just won't start from the GUI. By GUI, I mean * The XFCE-Applications Menu * By double-clicking a text file that is associated with gedit * By clicking the gedit icon I've attached to docky I've never noticed such issues when launching gedit from the GUI. Furthermore, I didn't see any error messages in dmesg or in /var/log/Xorg.0.log. When the problem appears, it often persists until the next reboot. I have no clue on how to fix it, any ideas are greatly appreciated. It's quite annoying that I can't rely on gedit... Thanks in advance, Lukas
On Fri, 22 Apr 2016 00:08:36 +0200, L. Rose wrote:
I've never noticed such issues when launching gedit from the GUI. Furthermore, I didn't see any error messages in dmesg or in /var/log/Xorg.0.log. When the problem appears, it often persists until the next reboot.
Those are unrelated log files. Take a look at ~/.xsession-errors*. Gedit seems not to use /run/user/*/dconf/user, if it would, it could be the source of issues, at least after running gedit with root privileges. Did you test pluma? Unfortunately pluma does use /run/user/*/dconf/user, but OTOH it's based on GTK2 and closer to the old gedit, than gedit is nowadays.
Launch from the command line and see what shows up. Just a thought. On 04/21/2016 05:08 PM, L. Rose wrote:
Dear fellow Archers,
I'm using XFCE4 on an up-to-date Arch Linux installation I've built from the official downloadable image and by following the instructions on the Arch wiki. The system works fine, but there are still some bugs I want to zap out.
First thing is: Sometimes gedit won't start when launching it over the GUI. I've installed it from the package repositories by using pacman, and it works most times, but, sometimes (I can't see any pattern in when it works and when not) it just won't start from the GUI. By GUI, I mean
* The XFCE-Applications Menu * By double-clicking a text file that is associated with gedit * By clicking the gedit icon I've attached to docky
I've never noticed such issues when launching gedit from the GUI. Furthermore, I didn't see any error messages in dmesg or in /var/log/Xorg.0.log. When the problem appears, it often persists until the next reboot.
I have no clue on how to fix it, any ideas are greatly appreciated. It's quite annoying that I can't rely on gedit...
Thanks in advance,
Lukas
On Thu, 21 Apr 2016 20:05:10 -0500, Marshall Neill wrote:
Launch from the command line and see what shows up.
Just a thought.
That could help, after the issue appears when launching it by a file manager or a launcher, but not necessarily helps. The output in ~/.xsession-errors* could provide error messages from the original event, when gedit first failed by e.g. launching it, when clicking a file in a file manager. In ~/.xsession-errors* usually is the output, that you get by running an app in a terminal.
Hi,
I've been bitten by a very similar issue recently on a RedHat system. When
trying to launch from commandline no message is shown and the command
returns soon.
I did an strace of the execution and found out that gedit creates a socket
in a temporary directory (in my case was controlled by $TMPDIR) and
sometimes it wouldn't be deleted when closing gedit. On the next execution,
it would find the socket, try to connect there and close as the syscalls
failed.
If it happens again and no error appears on logs or stdout/stderr, try the
strace. You won't see it on the last line but a bit before, in my case
10-20 lines before the end.
HTH,
Miguel
El 22 abr. 2016 7:39 a. m., "Ralf Mardorf"
On Thu, 21 Apr 2016 20:05:10 -0500, Marshall Neill wrote:
Launch from the command line and see what shows up.
Just a thought.
That could help, after the issue appears when launching it by a file manager or a launcher, but not necessarily helps. The output in ~/.xsession-errors* could provide error messages from the original event, when gedit first failed by e.g. launching it, when clicking a file in a file manager. In ~/.xsession-errors* usually is the output, that you get by running an app in a terminal.
participants (4)
-
L. Rose
-
Marshall Neill
-
Miguel Bernabeu
-
Ralf Mardorf