Public bug reported:
Not sure for which package to report this bug, as it shows up in
multiple applications.
Ubuntu 20.04 came with a newer GhostScript, which swapped the Nimbus-L
series of fonts (e.g. Nimbus Mono L, format PostScript Type 1) for a
Nimbus-PS series (e.g. Nimbus Mono PS, format
Installed packages don't matter if their content isn't in use. It does
matter whether you run an X11 or a Wayland session.
To switch between both, log out to get to the login screen. There is a
gears icon right above the password entry field, click on it. This
should open a menu allowing to
If you're running on Wayland it might be related to this:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510
It looks like a busy gnome-shell (or -extension) can eat mouse movement
events, so it might eat keystrokes as well. Second way to reproduce the
issue (for testing whether you
When putting emphasis on a stable system, staying with Xorg is probably
a good idea for the time being. While I use Xwayland daily now, it
definitely comes with a number of quirks.
- Transparency comes and goes. For example, moving a window to near the
top of the screen makes the top menu bar
I can confirm that upgrading to 18.10 solves this issue. While there are
still a few caveats (e.g. toolbar becoming intransparent when launching
an application), the hardware which failed before can now log into
'Ubuntu' as well as 'Ubuntu on Wayland'.
Well done, Ubuntu, thank you very much!
--
Great news! Thank you for your work.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Login screen never appears on early generation Intel GPUs (Core2 and
Atom etc)
Oh, Ubuntu does boot on such hardware just fine. And seeing how well it
works I'd feel guilty of wasting money and polluting the environment
when buying newer hardware.
It does not boot all up into native Wayland. Nevertheless, one can run
X11 just fine.
How to turn Wayland off? Key is to
With 18.04 the situation got worse. Apparently, the login screen tries
to run now on Wayland as well, so the opportunity to turn it off is
gone. Booting simply stops at the Ubuntu logo, with the first of these
five dots filled.
Booting in recovery mode, then choosing 'continue'(?) gives a black
> explain yourselves Ubuntu
Never seen Ubuntu explaining anything, helping people with debugging or
something like this in the last five years. Eventually the problem will
go away some way or another, but even this event most likely won't get
reported. So, don't expect too much.
That said,
Even on a desktop, gnome-software not running all the time makes hardly
a distinction. Searches for software may take a second longer (probably
gnome-software startup time), still it works perfectly fine.
One can try this by killing gnome-software, then searching for something
using the
> "cannot open display" either means ...
Thank you! This is valuable information.
So far I thought that the bug is about gnome-shell not starting. With
this solved, it's now mutter. Well, interesting adventure game :-)
--
You received this bug notification because you are a member of Ubuntu
Daniel, your current efforts apparently put much emphasis on alienating
users capable of fixing bugs. Also on getting rid of allies for low end
hardware support.
I really wish you had put half as much efforts into explaining the
software situation a bit. For example, what does this "cannot open
Success, part II:
When attempting a Wayland session, the relevant syslog section grew from
107 lines to 396 lines. 'gnome-shell' messages are gone, it looks like a
session gets actually started. And then there are now a lot of messages
like this one:
Oct 31 18:08:01 piccard
Success! Applying the attached Diff keeps gnome-shell working for Xorg,
still makes these shader compilation errors going away. More of this
success see next comment here.
This Diff is not a solution, of course, but it should narrow down the
problematic area a lot.
** Patch added:
Great to see you're into supporting "old" hardware. I'm pretty sure the
times when people bought new hardware every other year are long gone.
This G33 PC is a Core2Duo 2.1 GHz and it's perfectly up to speed for all
the daily tasks, including software development.
"Older" hardware also comes with
Intel integrated graphics is probably the most widely used PC graphics
on this planet. The problem is apparently that shaders are called
without being present, which applies to many most recent hardware
platforms as well. Calling it High is more than accurate.
Instead of trying to discuss the
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996315/+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.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996317/+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.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996318/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected artful package-from-proposed third-
party-packages
** Description changed:
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
Upgraded from 17.04 today.
Steps to reproduce:
- Start the PC or log out/end
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1727356/+attachment/4996316/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This one sounds similar: https://bugs.launchpad.net/ubuntu/+bug/1727356
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1726192
Title:
17.10 Login To Wayland Fails Unless
-- This shouldn't be wishlist, as it's actually a regression from
Ubuntu 11.04. Dragging to bookmarks worked with the older Nautilus just
fine.
-- At least for me, this applies to self-made bookmarks only. Dragging
to the predefined bookmarks (Desktop, Pictures, Music, ...) works just
fine. Too
There's another Gnome bug tracking this:
https://bugzilla.gnome.org/show_bug.cgi?id=645353
Diagnosis: instead of making a working feature dummy-proof, they removed
the feature because it's not dummy-proof.
OUCH!
** Bug watch added: GNOME Bug Tracker #645353
They are kidding, aren't they? .xession or .xsessionrc files are in
existence and well documented for some 20 years and now they want
distros to craft their own flavour? Sligthly different for each distro?
--
The new gdm doesn't give an option to use .xsession
OK, so the problem is, the US layout is added each time I boot.
The outputs as requested right after booting:
m...@piccard:~/Desktop$ grep ^X /etc/default/console-setup
XKBMODEL=pc105
XKBLAYOUT=us,de
XKBVARIANT=,
XKBOPTIONS=grp:alts_toggle
m...@piccard:~/Desktop$ gconftool -R
For getting me started: does somebody know where these settings are
stored and which the intended behaviour is? Is an US keyboard layout
always present?
--
Insisting on US keyboard layout
https://bugs.launchpad.net/bugs/459067
You received this bug notification because you are a member of Ubuntu
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34249712/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34249713/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/34249714/ProcStatus.txt
--
Insisting
Public bug reported:
Binary package hint: gnome-control-center
Since upgrading to Karmic beta from Karmic alpha as of one day earlier,
Ubuntu refuses to accept using the german keyboard layout. The only way
to get umlauts back is to delete the US keyboard layout in gnome-
keyboard-properties.
Public bug reported:
Binary package hint: gnome-session
Since X moved to a more system wide layer (early Karmic alphas) and
isn't started for each session separately, $HOME/.xsession is simply
ignored. This prohibits custom X settings like a per-user gamma value or
per-user screen resolutions.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34251781/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34251782/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/34251783/ProcStatus.txt
** Attachment
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/31110336/Dependencies.txt
--
Folder sharing informative text unclear
https://bugs.launchpad.net/bugs/422442
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus
Public bug reported:
Binary package hint: nautilus
Attempting to share a folder outside my Home I get this message:
»net usershare« gab den Fehler 255 zurück: net usershare add: cannot
share path /media/Archiv as we are restricted to only sharing
directories we own. Ask the administrator to add
I get it about every second time.
--
gnome-display-properties crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/286503
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Setting to confirmed as a duplicate was found.
** Changed in: gnome-control-center (Ubuntu)
Status: New = Confirmed
--
gnome-display-properties crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/286503
You received this bug notification because you are a member of Ubuntu
Thanks a lot for the fix, James Michael.
When I just tried to confirm the fix, I finally ended up with
https://bugs.launchpad.net/ubuntu/+bug/297379 :-/
--
gnome-display-properties crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/269595
You received this bug notification
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/17567638/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/17567639/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/17567640/Disassembly.txt
** Attachment
# sudo apt-get install evince-dbgsym=2.23.6-0ubuntu1
# [...]
# E: Konnte Paket evince-dbgsym nicht finden
Translation: couldn't find package evince-dbgsym
Google and Ubuntu Packages don't find this package either. How could I
find it, if it even exists?
Thanks, Markus
--
evince crashed with
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/17037435/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/17037436/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/17037437/Disassembly.txt
** Attachment
The document shown in ProcCmdline is a document I was viewing before
clicking on the web link. It's a public document and avialable here:
http://www.easa.eu.int/ws_prod/g/doc/Regulation/reg_216_2008/BR216_2008_DE.pdf
--
evince crashed with SIGSEGV in FcFontSetSort()
The issue appears to be solved, apparently the packages' dependency was
changed from 2.12.9-3ubuntu2 to 2.12.9-3ubuntu4.
Please close this bug.
** Changed in: gtk+2.0 (Ubuntu)
Assignee: (unassigned) = Traumflug (mah-jump-ing)
** Changed in: gtk+2.0 (Ubuntu)
Status: New = Fix
Public bug reported:
Binary package hint: libgtk2.0-dev
Well, I think the transscript pretty much says everything:
- - - - - - -
$ sudo apt-get install libgtk2.0-dev
[sudo] password for xxx:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some
42 matches
Mail list logo
