Ah! I see why we have a discrepancy. I'm sorry, I was not explicit
enough with my repro steps. Following your steps, it works for me as
well.
What I am doing is the following:
- ctrl+alt+T
- $ gedit
- first line is highlighted by default
- *** open the "Ln1, Col 1" menu in the bottom right corner
Could you do a screencast/video of the issue?
Yes I just tried with a fresh ISO
- downloaded a focal desktop amd64 iso
- started it in VM on the live session
- ctrl-alt-T
$ gedit
- opened the popdown menu
- selected preferences
- unselected the checkbox for the 'highlight selected line'
I do not believe that this problem is specific to my system. I just
created a VM and did a fresh install of 20.04, and I can reproduce the
issue there as well.
Here are the steps I followed:
1. Created an Ubuntu 64 bit VM in VirtualBox
2. Downloaded the latest 20.04 image from Ubuntu.com
3.
Did you manage to reproduce it on your system or a clean installation?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1880806
Title:
Gedit unable to save preferences on 20.04
To
Yes, I start gedit with my own user. I tried with `sudo gedit`, as well
as with another, freshly created non-admin user. The issue is present
with both.
Nautilus is correctly saving preferences. I am not sure what other
applications use gsettings under the hood, so I don't know what else I
can
Weird, do you start gedit with your user? Do changes to other
applications (e.g nautilus) are correctly stored? Could you maybe try
with another user account on the same computer to see if that has the
issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
> The issue seems specific to your system.
Interesting, I assumed it was a bug with Focal. I appreciate you taking the
time to look into it!
> change the setting in gedit and see if there is a change printed
No change is printed while 'gsettings monitor' is running. Tried with other
> Out of curiosity, is this something that you are able to reproduce, or
is it just on my system?
The issue seems specific to your system.
Could you do
$ gsettings monitor org.gnome.gedit.preferences.editor display-line-numbers
change the setting in gedit and see if there is a change printed
Ah ok got you. There is absolutely nothing in those logs, apart from the
normal messages. The log snippet below was produced by following the
repro steps above.
Out of curiosity, is this something that you are able to reproduce, or
is it just on my system?
jún 04 19:47:54 balazs-thinkpad
the section when you start gedit is fine, you can do
$ journalctl -f
start gedit, change the settings
and see if anything gets printed in the journal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
There aren't any errors on the command line. Which portion of the
journalctl log would you need? The complete log from boot, or just when
I start gedit?
The reason I'm asking it that the boot logs contain some personal
information that I would need to redact if you need the whole lot.
Thanks
--
Thank you for your bug report. Do you see any error if you start gedit
from a command line? Could you add the 'journalctl -b 0' log from the
session after getting the issue?
** Changed in: gedit (Ubuntu)
Importance: Undecided => Low
** Changed in: gedit (Ubuntu)
Status: New =>
It's also worth mentioning that before upgrading to 20.04, I had both of
those gedit settings off. Then I upgraded to 20.04, and that seemed to
have enabled both those settings automatically.
I've upgraded from 19.10.
** Description changed:
Hi,
Since upgrading to Ubuntu 20.04, Gedit is
13 matches
Mail list logo
