This is a regression for our vast majority of users using the normal
ubuntu product and quite visible one, I wouldn't put it as low.
** Changed in: gnome-shell (Ubuntu)
Importance: Low => High
** Changed in: mutter (Ubuntu)
Importance: Low => High
--
You received this bug notification
A black frame can also mean a zero FB ID, IIRC...
Can you tell if the backlight is going off?
--
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/1842009
Title:
[Wayland] Screen blanks
Regardless, please also create an upstream bug:
https://gitlab.gnome.org/GNOME/mutter/issues
--
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/1842009
Title:
[Wayland] Screen
It looks like modesetting, or at least a destructive probe of the
attached displays.
There's nothing KMS related in dmesg corresponding to the blanking, so I
don't think it's an invalid FB (I'd expect i915 to spit something in
dmesg in that case)
--
You received this bug notification because
Journal output attached
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+attachment/5285717/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
dmesg output attached
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+attachment/5285718/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
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/1841929
Title:
Volume up/down repeat keys don't work on Xorg
or
* An invalid framebuffer being accidentally flipped.
--
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/1842009
Title:
[Wayland] Screen blanks for a second whenever discrete GPU
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Can you tell if the "blanking" is either:
* The output entering sleep mode; or
* A black frame being accidentally flipped.
I guess checking if the backlight is still on would answer that.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Tags added: wayland
Let's start by checking for crashes, which can confuse and break the
console switching. Please try these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Desktop
Please do it again and instead of saving the apport just copy the link
and open it on another machine. You can then complete the new bug
creation in the browser of that other machine.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Please try:
1. Open a Terminal window and run:
journalctl -f
2. Right click on the desktop and reproduce this bug.
3. Do you see any new messages in the Terminal window?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-shell (Ubuntu)
Status: Fix Released => Invalid
--
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/1841673
Title:
GNOME Shell crashed
To manage
Thanks. That doesn't seem to show any single recurring problem though.
So it looks like log file flushing is not the explanation for this bug.
I wonder if disk performance is a factor. Can you please run:
lsblk
and
sudo hdparm -I /dev/sda
and send the output?
--
You received this bug
Public bug reported:
On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second
each time the AMD GPU is powered up. Triggers for powering up include:
launching something which loads GL such as Steam or glxinfo, loading the
Display configuration page, and so on.
This behaviour does
When running 'apport-cli --hanging $(pidof gnome-shell)' in a ssh shell,
it wants to spawn a browser to login to launchpad.net; since it did not,
I saved the apport and linked it here. After I ran the killall command
and ran the ubuntu-bug command it did not show an ID to link here.
** Attachment
This is not a dual GPU system, only the Nvidia GPU is usable.
--
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/1841679
Title:
[nvidia] Login screen never wakes after sleeping
"No errors have been reported from this system"
чт, 29 авг. 2019 г. в 04:50, Daniel van Vugt :
> Please follow the steps in comment #2, or choose one of the above bugs
> you would like this to be a duplicate of.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: Confirmed => Incomplete
>
>
After a while I have been not noticed the same problem, so I believe it
had fixed. So I think we can change the status from "Incomplete" to "Fix
released".
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a
Please, take the result.
P.S. I will try to descibe the different problems in separate apports.
Sorry for my mistakes. It's a less of my experience.
чт, 29 авг. 2019 г. в 04:45, Daniel van Vugt :
> Please be careful to only discuss one problem per bug report. If you're
> experiencing multiple
It's not quite the same as bug 1724977. This doesn't happen when moving
the cursor live, but the second copy "appears" after waking from screen
lock. My guess is that the lock screen doesn't use the same video
memory config as the desktop, but somehow they "overlap" and the cursor
gets left over
Ran a terminal with dmesg -w running.
Generated a 2gb file on my desktop, copied and pasted into home.
After "finished copying" notification I right clicked "move to trash", and
lockup.
Didn't see anything in the console output.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Did anyone try setting __GL_MaxFramesAllowed=1 as discussed in
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 ?
It helped me to get rid of the lockups on manjaro (didn't try on ubuntu though)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1202
A discussion at https://forum.manjaro.org/t/desktop-gnome-frequently-
get-frozen-few-seconds-and-works-again/81603/29 for manjaro seems to
nail down:
* It looks related to mutter (a gnome desktop component), since some guys
report that the freeze disappears when updating mutter.
* It does not
The first one (global volume) is fixed by Robert already, but the second
is not, I just reported that upstream.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #652
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/652
** Also affects: gnome-control-center via
Public bug reported:
GNOME Shell & mutter on 3.33.91
When pressing volume up or down on Xorg and keeping it pressed, only the first
key event is sent, so the volume only goes up or down once, and doesn't scale
up/down as long as you keep the button pressed.
ProblemType: Bug
DistroRelease:
Thank you for your bug report, could you report it upstream on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues
(confirmed and it does the same with Adwaita so not a theme issue)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in:
It's because it recommends rygel now which recommends gst-libav, that goes
lowered to a suggest now
https://launchpad.net/ubuntu/+source/rygel/0.38.1-2ubuntu2
** Package changed: gnome-control-center (Ubuntu) => rygel (Ubuntu)
** Changed in: rygel (Ubuntu)
Status: New => Fix Released
--
*** This bug is a duplicate of bug 1841794 ***
https://bugs.launchpad.net/bugs/1841794
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1841794, so is being marked as such.
** Tags added: rls-ee-incoming
--
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/1841794
Title:
gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from
Network connection does not die. (It appeared to first time but I think
that's just my ongoing random - and irrelevant here - avahi issues on
this machine.)
But gnome-shell is *not* running after triggering the bug, so sudo
killall on it just produces "gnome-shell: no process found". So that was
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1840675
Title:
Expose a button in the
Strange, these two extensions('sensory-percept...@harlemsquirrel.github.io',
'temperature@xtranophilist', 'gnom...@panacier.gmail.com'
) I've already uninstalled from gnome-tweaks, for a long time.
If they are available and easy to install, I think there is some problem with
gnome shell
*** This bug is a duplicate of bug 1841794 ***
https://bugs.launchpad.net/bugs/1841794
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1841794, so is being marked as such.
This might be somehow related to bug 1841873. To check that, please log
in via ssh and force a crash dump while it is unresponsive:
sudo killall -ABRT gnome-shell
Then please report that in a new bug using:
ubuntu-bug /var/crash/YOURFILE
and tell us the new bug ID.
** Changed in: gdm3
Public bug reported:
on logout the screen is black, the system is unresponsive and has to be
restarted. (Untested by me yet, but I expect ssh-ing in and restarting
gdm would work.)
I believe this may be already reported upstream here:
https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's
** Bug watch added: bugzilla.gnome.org/ #789675
https://bugzilla.gnome.org/show_bug.cgi?id=789675
** Changed in: mutter
Importance: Medium => Unknown
** Changed in: mutter
Status: Fix Released => Unknown
** Changed in: mutter
Remote watch: GNOME Bug Tracker #789675 =>
Sounds like bug 1724977, but we claim to have fixed that(?).
also...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1841894
Public bug reported:
There is no cursor on the slider in gnome-control-center (cf screenshot)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.33.90-1ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
Uname: Linux 5.2.0-13-generic x86_64
Public bug reported:
Gnome 3 desktop
Multi-monitor setup with one screen rotated right into portrait mode
*Experimental* fractional scaling on Wayland with different scaling on each
monitor. Configured using:
~~~
gsettings set org.gnome.mutter experimental-features
It doesn't look like https://gitlab.gnome.org/GNOME/mutter/issues/728.
It is about the hardware limitation that DELL DOCK - WD19 130W only supports
two external Full HD at the same time.
However mutter doesn't know the hardware limitation.
I guest mutter will try to set up external Ultra HD and
Are you able to supply apport info?
apport-collect 1841886
** Tags added: bionic
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #728
https://gitlab.gnome.org/GNOME/mutter/issues/728
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Also affects: gnome-shell-extension-dashtodock (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
Sounds like this?...
https://gitlab.gnome.org/GNOME/mutter/issues/728
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/728
Importance: Unknown
Status: Unknown
** No longer affects: mutter
--
You received this bug notification because you are a member of
Public bug reported:
[Summary] Join Displays failed when using two external monitor of one
Full HD and one Ultra HD
[Reproduce Steps]
1. Boot into the desktop environment with DELL DOCK - WD19 130W [1].
2. Connect one Ultra HD (3840x2160) external monitor and one Full HD
(1920x1080) external
Dash to Dock is currently broken as well. This branch
https://github.com/3v1n0/dash-to-dock/tree/gnome-3-34 works, but the
intelligent autohide brings down the entire gnome shell if enabled.
GNOME Pomodoro currently works, but was compiled under 3.32 from the
3.32 branch. The package has not be
49 matches
Mail list logo
