Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: Sashank999 on August 08, 2020, 04:36:26 AM
-
Hi !
I just now installed Gedit in the hope of getting a good GUI Text Editor with line number and syntax highlighting. But Gedit isn't working when I open a shell script in it. I get the followng error when I open the attached file.
(gedit:8624): Gdk-WARNING **: 08:31:33.801: The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 3930 error_code 2 request_code 139 (RENDER) minor_code 34)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Any ideas what to do to solve ?
If this is a bug in the program, can anyone suggest me another GUI text editor that has syntax highlighting and line numbers ?
-
Which version and architecture are you using - CorePure64-11.x?
If you're using Xfbdev try Xorg-7.7, if you're using Xorg-7.7 try Xorg-7.7-3d.
-
I quite like geany for line numbers and colours
BTW gedit for me runs on sway but with a different set of messages
gedit # space truncated by me
** (gedit:20790): WARNING **: 09:30:30.670: Could not load Gedit repository: Typelib file for namespace 'Gedit', version '3.0' not found
** (gedit:20790): WARNING **: 09:30:30.670: Could not load Peas repository: Typelib file for namespace 'Peas', version '1.0' not found
** (gedit:20790): WARNING **: 09:30:30.670: Could not load PeasGtk repository: Typelib file for namespace 'PeasGtk', version '1.0' not found
I just happened to be in sway when I read this post. I do not expect people to run sway.
-
Those messages will disappear if you load gedit-gir.
-
@Juanito I am on Corepure64 v11.1.
I normally use Xfbdev. Now confirming that it works on Xorg-7.7. But it is as slow as heck. What do I do ?
@aus9 Even I got those messages. But those got away with loading of -girs of the said tczs in the error messages. Hence I didn't report them.
-
Xorg-7.7 is slow (perhaps you need a driver, look at /var/log/Xorg.0.log) or gedit is slow (what hardware do you have)?
-
My hardware - A BIOS Laptop with Intel Core i3, 2GB DDR3 RAM(found DDR3 by lshw command), No Graphics Card but there is "Intel Integrated Grpahics Controller".
Xorg-7.7 is slow. I can say that. Now, after examining /var/log/Xorg.0.log with :
grep -in "(WW)" /var/log/Xorg.0.logand then found that it requires intel_drv.so. Downloaded and installed it via xf86-video-intel.tcz and it now works faster than Xfbdev ;D.
-
If you're only using gedit and other gtk3 apps wayland/weston or sway might be faster still.
-
But I heard that WMs get struck in Wayland.
-
eh?
There are only two wayland compositors in the repo at the moment - weston and sway - read the info files first.
There's also mutter/gnome-session, but I would not recommend that without more serious hardware.
-
Oops, not the WMs but some apps that work very good under Xorg are known to break under Wayland. I don't know if it is true or not but now. Also, I have many other apps that are not gtk3. I already have a working and fast enough desktop. Thanks for the suggestion !
When I add the gedit.tcz to onboot.lst, I get 2 gedit icons on wbar and 2 "New Document" entries in the jwm right-click menu.
-
Hi Sashank999
That sounds like the same problem reported for epiphany.tcz here:
http://forum.tinycorelinux.net/index.php/topic,23933.msg150766.html#msg150766
The problem is that gedit.tcz contains 2 desktop files:
/usr/local/share/applications/gedit.desktop
/usr/local/share/applications/org.gnome.gedit.desktopand both of them are getting loaded.
-
The problem is that gnome-session requires a desktop file of the form org.gnome.gedit.desktop and wbar will not display a desktop file of this form if the X gui is already started (it is not a problem in wayland).
If the extension is loaded from the console and the X gui started, then two icons appear.
-
Oops, not the WMs but some apps that work very good under Xorg are known to break under Wayland.
In case you are interested is....Wayland can have desktops, we do not call them window managers on Wayland..they are called compositors...and they either support xwayland or not.
sway was built with xwayland compiled support but has a config for those who wish to disable it. Other desktops that run on Wayland may or may not have xwayland support.
Hope that helps.