Public bug reported:
Steps to reproduce:
- Have Ubuntu installed.
- Install lightdm. This makes lightdm the active window manager, as far as I
can remember.
- Uninstall lightdm.
- Reboot.
Expected result:
- System booting another available window manager (gdm3 in this case).
- At very least an
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 AS
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 choose
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 experienc
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 intr
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 Desktop
Packages, 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)
Sta
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 disable
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
sc
> 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, clicki
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 activities
> "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 Desktop
Pa
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
di
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 gnome-screensav[2194]:
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: "remove-shader-
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 a
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 prob
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 session
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.laun
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bug
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https:/
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
Thanks for the help, @Brian. I thought about the package 'wayland', too,
but trying to report a bug against it came out like this:
$ ubuntu-bug wayland
dpkg-query: no packages found matching wayland
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
> It seems that your bug report is not filed about a specific source
package
See, Mr. Bot, if I'd knew the package, I'd report the bug not here, but
upstream.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bug
This one sounds similar: https://bugs.launchpad.net/ubuntu/+bug/1727356
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1726192
Title:
17.10 Login To Wayland Fails Unless User Lo
Public bug reported:
Just did what the bug triagers requested: 'ubuntu-bug upower' on the
command line.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: upower 0.99.3-1build2
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ub
Clickable link to the other bug:
https://bugs.launchpad.net/ubuntu/+bug/1513149
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1515998
Title:
Package specific report as requested in b
Works well indeed. Just upgraded using this PPA and Inkscape works fine
(including this bugfix).
Thank you for fixing this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1335523
Well, this "whoever runs the PPA" is actually Inkscape Developers:
https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1335523
Tit
Can report success for the Intel G33, too. Now the system menu is gone
and the dash searches forever without results - different story.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/122260
Q35 is one of the successors of the 945, too. More to the higher end, if
not the top model, of this family at some point.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1222602
Title:
[r
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
https://bugzilla.gnome.org/show_bug
-- 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
33 matches
Mail list logo
