Gedit Error
-
- Posts: 8
- Joined: 2017/09/29 19:16:24
Gedit Error
When running gedit I am prompted with the following error:
(gedit:165687): GLib-GIO-ERROR **: Settings schema 'org.gnome.gedit.preferences.editor' does not contain a key named 'background-pattern'
Trace/breakpoint trap (core dumped)
Any thoughts on how to fix this issue?
(gedit:165687): GLib-GIO-ERROR **: Settings schema 'org.gnome.gedit.preferences.editor' does not contain a key named 'background-pattern'
Trace/breakpoint trap (core dumped)
Any thoughts on how to fix this issue?
-
- Posts: 58
- Joined: 2017/02/20 01:36:15
Re: Gedit Error
Have you tried a reinstall ?
yum reinstall gedit
yum reinstall gedit
-
- Posts: 8
- Joined: 2017/09/29 19:16:24
Re: Gedit Error
Below is the results from running "yum reinstall gedit"
yum reinstall gedit
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
--> Running transaction check
---> Package gedit.x86_64 2:3.22.0-3.el7 will be an update
---> Package gedit.x86_64 2:3.22.0-3.el7 will be erased
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for gedit which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of gedit of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude gedit.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of gedit installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of gedit installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: 2:gedit-3.22.0-3.el7.x86_64 != 2:gedit-3.14.3-18.el7.x86_64
yum reinstall gedit
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
--> Running transaction check
---> Package gedit.x86_64 2:3.22.0-3.el7 will be an update
---> Package gedit.x86_64 2:3.22.0-3.el7 will be erased
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for gedit which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of gedit of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude gedit.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of gedit installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of gedit installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: 2:gedit-3.22.0-3.el7.x86_64 != 2:gedit-3.14.3-18.el7.x86_64
Re: Gedit Error
Did you try what it suggested with yum-complete-transaction ? If that doesn't work, then post the output from package-cleanup --dupes
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 8
- Joined: 2017/09/29 19:16:24
Re: Gedit Error
Results from running "yum-complete-transaction"
yum-complete-transaction
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
No unfinished transactions left.
I ran "package-cleanup --dupes"
package-cleanup --dupes
Loaded plugins: fastestmirror, langpacks
kbd-misc-1.15.5-13.el7.noarch
kbd-misc-1.15.5-12.el7.noarch
Above are 1 example of results from running "package-cleanup --dupes" I didnt post everything because there are honestly like 800 dupe packages...
I have also tried "yum-complete-transaction --cleanup" with no luck.
yum-complete-transaction
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
No unfinished transactions left.
I ran "package-cleanup --dupes"
package-cleanup --dupes
Loaded plugins: fastestmirror, langpacks
kbd-misc-1.15.5-13.el7.noarch
kbd-misc-1.15.5-12.el7.noarch
Above are 1 example of results from running "package-cleanup --dupes" I didnt post everything because there are honestly like 800 dupe packages...
I have also tried "yum-complete-transaction --cleanup" with no luck.
Re: Gedit Error
So you need to cleanup all those duplicates. To do this, use rpm -e --nodeps --justdb $package to remove each of the newer of the two versions leaving the older one alone and installed. Once you've done this for all of them, re-run yum update and it will download and install the newer ones for you. This makes sure that the newer ones are correctly installed.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 8
- Joined: 2017/09/29 19:16:24
Re: Gedit Error
What does the $package mean in this command rpm -e --nodeps --justdb $package?
Re: Gedit Error
Substitute the newer package name and version - so using your example kbd-misc-1.15.5-13.el7.noarch is newer than kbd-misc-1.15.5-12.el7.noarch so run rpm -e --nodeps --justdb kbd-misc-1.15.5-13.el7.noarch
Repeat for all duplicates. Make sure you leave the older copy installed.
Repeat for all duplicates. Make sure you leave the older copy installed.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke