Public bug reported:
Automatic suspension causes the system to freeze on resume. This doesn't
happen if I suspend it manually by opening the system menu and pressing
the suspend button. Suspension works flawlessly when it is triggered
manually.
When the system resumes from automatic suspension, t
Public bug reported:
After updating firefox deb to version 88, every time I play YouTube
videos, some times in several tabs, then Wayland crashes and the system
freezes. For try workaround this crash, I've to use the magic key SysRq
(Alt + SysReq) with "REISUB" characters to safely reboot my Ubunt
Hi there!
This report page doesn't have any from reported version but it does have
the report from the previous version, version 87:
https://crash-stats.mozilla.org/report/index/09389e82-1bfb-43fe-
bd10-2b8940210408
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So, I've questions about this bug if it comes from firefox, or mutter,
or wayland because every time I try use Firefox 88 the Wayland session
freezes and nothing else works besides Magic Key to restart my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can
suspend the machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Title:
Desktop unable to Suspend when Inactive
To
Public bug reported:
I close the laptop lid and let it suspend. On resume, the whole desktop
is frozen for a while. Nothing works during this time, no CAPS LOCK
indicator LED, neither TTY switching. Then the screen goes dark and I
see the LightDM login screen. I was logged out.
This is a regressi
** Attachment added: "Journalctl logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+attachment/5298947/+files/journalctl.txt
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It
Public bug reported:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
Specs:
- Graphics: AMD
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
+ Impor
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
- Impor
No extensions were installed. Also, I'm using the native AMDGPU drivers,
not the proprietary ones.
I've tested the vanilla GNOME session as you suggested, and the bug is
there too. Due to the hover highlighting of the panel items, I had a
visual cue to test with. The highlighting does not happen a
Public bug reported:
According to this page:
https://wiki.ubuntu.com/Sound#Primary_sound_output, "if you manually
choose an output device in the “Sound” settings panel or a similar
utility, that choice should be followed". Well, despite me having
explicitly selected the headset as the output devic
Public bug reported:
I believe I've found a regression in Ubuntu 19.10 Eoan concerning a
Steam game.
Start an Ubuntu session on Xorg and try to play Counter Strike: Global
Offensive. The screen stutters, skips frames, becomes glitchy and
ultimately unresponsive. It doesn't respond to ALT+F4, does
** Attachment added: "Journalctl output of cs:go-related entries"
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1849217/+attachment/5299054/+files/journalctl-csgo.txt
** Description changed:
I believe I've found a regression in Ubuntu 19.10 Eoan concerning a
Steam game.
Start
It was already reported.
Here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
And here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1649
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
** Bug watch added:
I can reproduce this problem with a USB stick as well. I suggest
changing the title to "Removable media icon stays on the dock after
eject".
To reproduce, I've inserted my USB stick used to install Ubuntu,
automounting it; Two items appeared, one that says "Ubuntu 19.10..." and
another saying "cas
I'll create the new issue there.
I have only one monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849135
Title:
Clicking Activities in the corner doesn't work
To manage notifications about
Here's the new issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2164
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2164
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I have been trying to reproduce it in the last days, but I couldn't. I
managed to get nearly 100% use of swap space again, while simultaneously
using Nautilus and Eye of GNOME (which is what I was doing at the exact
moment the freezes began), but it didn't happen again. Nothing changed
about my wor
Public bug reported:
When you have 3 or more windows open, the overview will overflow
vertically. A piece of the bottom row is cut off from the screen. See
the screenshot, please.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSign
I have tested 'mutter' version 3.34.3-1ubuntu1~19.10.1 from eoan-
proposed on an Xorg session, and it doesn't fix the issue. Testing was
made after package installation, followed by a system reboot.
mutter/eoan-proposed,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed]
I don't know what other informa
Let me add that I also tested a GNOME session (package 'gnome-session')
and there was no difference from the results of testing the Ubuntu Xorg
session. The proposed package does NOT fix the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
It starts with very subtle stuttering that you notice when moving
windows around, then keeps getting worse and worse until it starts
freezing the UI for many seconds. I could only reproduce it twice in a
couple of days.
The applications open at the time are usually Atom, Fire
Thanks for the response. Sorry for the delay, I didn't get a
notification about this.
If by admin you mean one that has sudo privileges or a member of group
`adm`, then yes. It's the default user created by the installer.
I could reproduce this on Arch Linux and other distros IIRC. The
workaround
Public bug reported:
With CSD enabled, Firefox 66.0.4 displays white corners at the top-left
and top-right of the window.
Ubuntu version: 19.04 (fully updated)
Version: Firefox 66.0.4 (64-bits)
Desktop Environment: GNOME 3.32.1 (default)
GTK theme: Yaru (default)
GPU: Radeon RX 560 Series (POLARI
** Attachment added: "journalctl output"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+attachment/5280445/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
In the Power tab, the option "When the power button is pressed" is set
to "Suspend". However, this action is not executed on power button
press. It does nothing.
This is always reproducible on Ubuntu 19.04, while on Ubuntu 18.04.2 it
works as expected.
gnome-control-center 3
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+attachment/5280446/+files/dmesg.txt
** Description changed:
In the Power tab, the option "When the power button is pressed" is set
to "Suspend". However, this action is not exe
Public bug reported:
I've configured it so that the system would suspend after pressing the
power button. This does not happen.
How is it reproducible?
It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new
kernel, new bug. On Ubuntu 19.04, this has been reproducible since i
Public bug reported:
On shutdown, peripherals turn off (keyboard, mouse), but fans keep
spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
plymouth screen (no animations, frozen frame). The keyboard is turned
off at this point, so the only way to properly shut down the computer
** Description changed:
On shutdown, peripherals turn off (keyboard, mouse), but fans keep
spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
plymouth screen (no animations, frozen frame). The keyboard is turned
off at this point, so the only way to properly shut down th
Public bug reported:
After the screen turns off (for inactivity, screen lock, etc.), mouse or
keyboard input won't bring it back. When I come back to the computer to
resume my work, I have to wake the system up, and press the power button
on the monitor. If I don't manually bring the monitor back
I can no longer reproduce this with kernel 5.1.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830652
Title:
On shutdown, peripherals turn off, but fans keep spinning, power LED
is lit and scree
Public bug reported:
Please read this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1645553
I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
messages are still being spammed into my Xorg logs.
```
[
Let me update the description of the problem:
I launch Counter Strike: Global Offensive and the screen freezes on the
main menu. I can hear sounds from the game, I can hear feedback sounds
from hover events, and I can press buttons on the frozen interface (it
works) but I never see the frame chang
I can also reproduce this on both of my computers running Xubuntu 19.04,
a desktop and a laptop.
Just to be extra clear on what the issue is:
If the computer is left idle for 10 minutes, the screen locks. When 15
minutes have passed, it should suspend, but it never does. I unlock the
screen to in
** Description changed:
- On 16.04 (XFCE session and others) and possibly later the power-manager
- is unable to suspend the system when the user is inactive. A PK user-
- agent dialog is presented for the user to authenticate first - and as
- this action occurs specifically when the user is idle
Public bug reported:
When a file changes, or when a new file or folder is created in a
directory, and Thunar is showing that directory, changes will not be
visible until you press F5.
This is not the case for the desktop (where my wallpaper is). Changes
there are shown in real time, as expected.
I can't see any files in /var/crash/, even after applying the workaround
and reproducing the freeze again.
This time the freeze was more severe. There was no response from the
keyboard and a hard reset was the only way to recover.
--
You received this bug notification because you are a member of
I'm attaching the requested logs.
Near the end of this file you'll see the last action I performed, which
was the CTRL+ALT+PRINT+REISUB combination to reboot. You'll also see
that there is a long crash log related to AMDGPU.
Oh, and this time when it crashed I attempted to switch TTY, and then
th
I was able to reproduce this with kernel 5.0.0 too. Isn't it possible
that this is not caused by the kernel? I don't think I had this issue
back then - it's something more recent.
** Attachment added: "Logs from a previous session that crashed with kernel
5.0.0"
https://bugs.launchpad.net/ubu
Nevermind, I was running 5.8, not 5.0.0. I forgot to select 5.0.0 in the
boot menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
[amdgpu] kernel crash when resuming from automatic su
I've finished the tests, here are the results:
5.0.0: OK
5.4.0: OK
5.6.0: OK
5.7.0: BUG
5.8.0: BUG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
[amdgpu] kernel crash when resuming f
Kernel 5.6.19: OK
If I'm not mistaken, this was the last version before 5.7, so the bug
must have been introduced in 5.7.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
[amdgpu] ker
apport information
** Tags added: apport-collected
** Description changed:
Automatic suspension causes the system to freeze on resume. This doesn't
happen if I suspend it manually by opening the system menu and pressing
the suspend button. Suspension works flawlessly when it is triggered
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479057/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479058/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479059/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
[amd
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479056/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
[amdgp
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479060/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479061/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479062/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479063/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479064/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479065/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479066/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479068/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Title:
[a
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479069/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917674
Ti
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479070/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: New => Confirmed
--
You received
Public bug reported:
This extension has been updated these days and the "All" button (next to
"Frequent" button) has crash and no longer shows all applications.
Disabling Ubuntu-Dock via Extensions Panel this function works perfectly
again.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: g
Probably related to bug 1872796 too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922241
Title:
[Wayland] Dash to dock don't show all applications
To manage notifications about this bug go to:
htt
I think I can't reproduce this anymore on Xubuntu 20.04. I left the
laptop idle and after 30 minutes it was suspended as expected, without
making any fixes (clean install).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
This bug was fixed in Xubuntu 19.04, if I remember correctly. But on
later releases it became reproducible again.
I'm currently running Xubuntu 20.04, and most of the widgets on the top
panel are affected, with the exception of Whisker menu icon (sometimes),
the task switcher and the Notes widget
Public bug reported:
Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no
sound output when you plug an earphone/headset. The built-in speakers,
on the other hand, are working properly. This is a laptop, Dell Inspiron
11 3162.
I checked volume levels with alsamixer, I played w
Running amixer sset 'Capture Source' 'Internal Mic' returns error:
amixer: Unable to find simple control 'Capture Source',0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875249
Title:
[Inspiron 11
** Attachment added: "screenshot alsamixer capture"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+attachment/5361512/+files/Captura%20de%20tela_2020-04-27_06-51-37.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I have attached a screenshot of that screen, because I couldn't find any
Capture Source or Input Source there. Maybe it has a different name or
is missing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Oh, I can finally hear sound through the earphones by changing the
capture source. Too bad the change doesn't persist after I remove and
reinsert the connector. Every time that happens, I must change it to
Headset Mic, otherwise there will be no sound output.
It also works when I do it through the
I forgot to tell you that I never see any dialog when I plug the
earphone. It's a feature of some desktop environments, right? I have
never seen it in Xfce.
The capture source changes to "headphone" every time I plug the
earphone, and when that happens, there is no sound output. Changing it
to any
** Attachment added: "Screenshot of the first part of the grid"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+attachment/5365468/+files/Captura%20de%20tela%20de%202020-05-02%2019-47-31.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Public bug reported:
This bug is best explained with images. I've attached two screenshots
showing what the app grid looks like right after it's opened. A gif has
also been recorded to show a glitch in the animation as the icons slide
in.
This is not reproducible in Fedora 32 with GNOME 3.36 on t
Here's the gif showing a strange animation happening right after the app
grid is opened, which causes a displacement of the icons.
** Attachment added: "Animation showing how to reproduce the problem"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+attachment/5365469/+files
Update: this is also reproducible on Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876532
Title:
Badly positioned icons in the app grid
To manage notifications about this bug go to:
https
An observation about how to reproduce this bug:
As soon as you click the "Show Applications" button on the dock, move
your mouse to the target position of any of the icons before the sliding
animation is over. This will usually trigger the glitch.
Keeping the cursor still after you click that but
Correction:
It's not about where the cursor is placed when the animation ends, it's
about whether the cursor is moving or not.
Keep the cursor still, as I said previously, and the bug doesn't happen.
Keep the cursor moving while the sliding animation is running, and the
problem is nearly always
No change in Disco. Still missing the entry at
"com.ubuntu.desktop.pkla".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Title:
Desktop unable to Suspend when Inactive
To manage notification
*** This bug is a duplicate of bug 1795135 ***
https://bugs.launchpad.net/bugs/1795135
** This bug has been marked a duplicate of bug 1795135
XFCE window buttons are not clickable at the top of the screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Description: When session is locked either using dm-tool or light-
locker, lightdm greeter is functional (you can type your password and
press Enter to unlock the session) but screen is not turned on, and
remains turned off even when you move the mouse or press any key.
Altho
Public bug reported:
One is the alert sound chosen through GNOME's sound settings, the other
seems to be the default alert from the sound theme, which we can't
change without using dconf-editor.
When an alert sound is triggered, both sounds play at the same time
instead of one.
Things I've tried
Sorry, I'm not sure what to remove. My file is slightly different from
the one in that commit. Is it OK to comment out everything at /usr/bin
/start-pulseaudio-x11? There are other if blocks that don't seem to be
related.
I will try to comment out only the if block that references `bell.ogg`
and c
All right, that fixes it. Now I have the expected behavior. Only one
sound plays: the one selected through GNOME Settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834807
Title:
Two alert soun
The solution is right here, so simple to apply. Why is this ignored? No
one else suspends their machines? Merge the necessary polkit rule,
please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757375
Tested kernel 5.2-rc2. The issue is still reproducible.
To clarify it a bit more, let me explain that this happens when the
screen turns off by inactivity (screen locks) and also when you suspend
to RAM and then resume. The monitor will not turn back on when you press
any key.
I can continue pres
Public bug reported:
XPS L401X with Intel HD Graphics and NVIDIA 420 (Optimus) running Ubuntu
10.10
Outputs:
--
XPS L401X
Not Specified
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor
Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA
controller])
** Attachment added: "DSDT.dsl"
https://bugs.launchpad.net/bugs/707218/+attachment/1805483/+files/DSDT.dsl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/707218
Title:
DSDT.dsl file of Dell XPS L
XPS L401X with Intel HD Graphics and NVIDIA 420 (Optimus) running Ubuntu
10.10
Outputs:
--
XPS L401X
Not Specified
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor
Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA
controller])
01:00.0 VGA compatibl
*** This bug is a duplicate of bug 312756 ***
https://bugs.launchpad.net/bugs/312756
** This bug has been marked a duplicate of bug 312756
MASTER: support graphics card hot switch
* You can subscribe to bug 312756 by following this link:
https://bugs.launchpad.net/ubuntu/+source/xorg-serv
I was able to reproduce it again. The system quickly became
unresponsive, so I had to reboot with the REISUB combination. After the
system started again I collected the logs. I wasn't using Nautilus of
the image viewer this time.
** Attachment added: "journalctl -b0 after the freeze"
https://b
Apparently, the logs I collected are from after the reboot, so they're
probably not relevant. How do I collect logs from before the reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860793
Title:
The logs I attached previously only refer to the session AFTER the
system restarted. So I've collected the logs from the previous boot this
time, which will contain the relevant information.
I'm attaching the output of: `journalctl -b-1`
** Attachment added: "output of journalctl -b-1"
https:
You mean I should try an older version? Then I think I should try v5.0.x
first. As you can see, it takes time to reproduce it again. I don't know
how to intentionally reproduce it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
I've written an issue here:
https://github.com/stuartlangridge/ColourPicker/issues/63
Pick (a color picker distributed as a snap) will not launch. The creator
of the application believes this to be a problem with my system, not
with their app. Apparently, AppArmor is preventi
I have a similar netbook called Dell Inspiron 11 3162 in which this is
reproducible. Changing brightness with the FN (function) key
combinations change the gamma of the screen instead of the actual
brightness. It's a fake brightness change, like the one Redshift can do
if you're familiar with it.
Public bug reported:
I had LibreOffice Writer open at the time, but it was idle. The system
was completely unresponsive and a power reset was the only way to shut
it down. The "REISUB" command didn't work.
I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
with them.
ProblemT
** Attachment added: "dmesg log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592340/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975516
Title:
Sy
** Description changed:
I had LibreOffice Writer open at the time, but it was idle. The system
- was completely unresponsive and a power reset was the only way to shut
- it down. The "REISUB" command didn't work.
+ became completely unresponsive and a power reset was the only way to
+ shut it do
It happened again, with the laptop idle same as before.
This time the screen went dark (backlight off) and the fans were
spinning fast. I could feel the laptop was a bit hot.
I had Transmission, LibreOffice Writer and GNOME Files running at the
time.
** Attachment added: "journalctl log of the s
Public bug reported:
The video stops playing at a certain random frame, like it's been
paused. You can drag the range control and move forwards and backwards
and the frame will change as expected, but toggling play/pause does
nothing.
I can only reproduce this on Ubuntu 22.04. On Debian 11 it wor
1. I ran "totem filename.mp4" and reproduced the problem, but nothing is
logged to the console.
2. The package gstreamer1.0-vaapi is not installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197589
No, I can reproduce it with many different video files. Nothing shows up
on the cmdline. Firefox plays the videos just fine, by the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975890
Title:
1 - 100 of 115 matches
Mail list logo