I took video showing the bug being reproduced on 21.04. Unfortunately
it's not the best. The video in the bug I linked above is clearer.
https://youtu.be/dSPUFTfpzZc
** Description changed:
Steps to Reproduce:
In the Settings applet choose Accessibility -> Zoom. Toggle the switch
on. Th
FWIW this is the same bug I reported in
https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870
@guiverc suggested I report a new bug after reproducing this behavior on
21.04 which I have.
Thanks in advance!
-Chris
--
You received this bug notification because you are a member of Ubu
Public bug reported:
Steps to Reproduce:
In the Settings applet choose Accessibility -> Zoom. Toggle the switch
on. This happens whether or not you actually magnify the screen.
When the mouse is moved anywhere on the screen, it leaves behind
repeated partial square trails in its path.
ProblemTy
This works great in 20.04
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1799073
Title:
Full scree
This is fixed in Ubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1799073
Title:
Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
To manage notific
Hi Will!
Just wanted to follow up with some good news and maybe something you
folks can use to help fix this one should it ever come around on the
guitar? :)
I found I was able to get Gnome to start up correctly on boot if I just
add this line to the [daemon] section of /etc/gdm3/custom.conf:
Wayl
apport information
** Tags added: apport-collected
** Description changed:
Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1
(Worked perfectly in stock 18.04) and then I was testing the 18.10 beta
and hoped it would be fixed there but it's not.
To reproduce: login t
That work-around works perfectly, thank you *SO* much!
FWIW I ran the apport command after applying the work-around you
suggested. Let me know if there's anything else I can do to help on this
one.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1799073/+attachment/5203917/+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
Hi guys! (Daniel? Since you seem to be the only one reading this :)
I fixed it! :) I added:
WaylandEnable=false
ow at les
to the [daemon] section of /etc/gdm3/custom.conf and the Gnome GUI starts right
up on login!
I feel accomplished! :)
Now at least if anyone ever has time to fix the core is
Public bug reported:
Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1
(Worked perfectly in stock 18.04) and then I was testing the 18.10 beta
and hoped it would be fixed there but it's not.
To reproduce: login to the regular Ubuntu desktop, hit Super+Alt+= (You
can validate th
Done!
https://gitlab.gnome.org/GNOME/gdm/issues/432
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1796614
Title:
Ubuntu 18.10 boots to a blank screen with a blinking cursor
To mana
** Attachment added: "Attached gdm logs from failed startup on boot. No obvious
errors leaping out at me."
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614/+attachment/5201900/+files/gdm.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
I don't know if anyone's tuned into this bug anymore, but are there any
other verbose / debug logs I could attach to help move this one closer
to resolution?
I'm totally up for doing the leg work, I just need to understand where
to start digging :)
--
You received this bug notification because y
Not sure if there's a way to mark this bug as duplicated by the upstream
Gnome one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1796614
Title:
Ubuntu 18.10 - X fails to start on lo
Hi there. Thanks for the triage. As per
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/comments/25
this bug isn't a duplicate of the bug you mention. I've removed the
duplicate notation.
In fact this bug is being tracked in upstream Gnome bug
https://gitlab.gnome.org/GNOME/gdm/issues/
Hi there! I'm looking for suggestions on further testing I can do to
disambiguate the situation I'm seeing from this bug.
I reported https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614
which was marked as a duplicate of this bug.
However, I now have this package installed (Output of apt p
17 matches
Mail list logo