Public bug reported:
On both a Raspberry Pi 5 and an AMD64 PC running Ubuntu 24.10 upgraded
from 24.04 GNOME Terminal 3.54.0 fails on the command
rquint@Mrs-Lovett:~$ gnome-terminal --class=SageTerminal --
/home/rquint/Sage/sage-10.4/sage
# Failed to parse arguments: Too many arguments
Since I
apport information
** Tags added: apport-collected focal
** Description changed:
- The value for selected-color at line 153 in the gnome-shell.css files
- for Yaru and Yaru-dark is ignored by the shell. (Selected text should
- change color from dark grey to white.)
+ The value for selected-color
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1878998/+attachment/5373827/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1878998/+attachment/5373828/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1878998/+attachment/5373826/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
*** This bug is a duplicate of bug 1842886 ***
https://bugs.launchpad.net/bugs/1842886
I think this is a different issue. Up to 19.10, whether you used the
default or Yaru-dark themes, when you selected the text in an entry box
(e.g., rename, command, etc.) or were presented with some default
Public bug reported:
The value for selected-color at line 153 in the gnome-shell.css files
for Yaru and Yaru-dark is ignored by the shell. (Selected text should
change color from dark grey to white.)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You receive
How long does it take for something like glib to move from the git into
the current distribution's repository? I'm wondering if I should wait
instead of rolling my own.
--
GSettings bug on PowerPC
https://bugs.launchpad.net/bugs/663384
You received this bug notification because you are a member
I'm still getting the same
rqu...@old-imac:~$ evince
GLib-GIO-ERROR **: Settings schema 'org.gnome.Evince.Default' is not
installed
aborting...
Aborted
with everything up to date as of 1116 PDT 22Oct10. Is there any
diagnostic I can run to help pin down what the problem is?
--
GSettings bug
How does an end user fix their system? I deleted libglib2* from my
cache and then used synaptic to download and reinstall them, but that
did not fix the problem with evince--starting evince in a terminal still
yields
rqu...@old-imac:~$ evince
GLib-GIO-ERROR **: Settings schema 'org.gnome.Evince.
I've just done an upgrade of a powerpc iMac G3 from lucid to meerkat
with all additional updates as of 18.10.10. I also have this problem
with evince. Just to confirm that there is nothing in the pdf files
that is causing the problem I checked they are readable on the machine
with ghostview. Ca
11 matches
Mail list logo
