Public bug reported:
I have the nvidia-smi package installed and it shows GPU info correctly.
The monitor though shows zero usage in the graph.
For a short while I was able to get it showing GPU usage, by setting lower
refresh rate, but then it stopped working again and now I can't get it working
I am facing this issue too. Is there a workaround as I have very limited
disk space and this is killing it!
Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: == Stack trace for
context 0x55c6d5f34330 ==
Aug 2 09:09:03 Bantam1 org.gnome.Shell.desktop[1532]: #0 0x7ffc8ee86540 I
resource://
This bug was fixed in the package yaru-theme - 18.10.1
---
yaru-theme (18.10.1) cosmic; urgency=medium
[ Didier Roche ]
* debian/yaru-theme-gnome-shell.postinst:
- bump priority for Yaru gdm css to 15, higher than current ubuntu
unthemed default. (LP: #1783571)
[ Marc
** Description changed:
Relying on the nouveau driver and on the vga switcheroo (to get around a
change in systemd LP: #1777099) caused increased power consumption, and
slowed down the switching process.
- Solving the problem in systemd (LP: #1777099), and adding code in gpu-
- manager an
** Also affects: gnome-software (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gnome-software (Ubuntu Bionic)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: gnome-software (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gnome-so
** Summary changed:
- Gnome Software offers installation of updates on shutdown independently from
update-manager and unattended-upgrades
+ [SRU] Gnome Software offers installation of updates on shutdown independently
from update-manager and unattended-upgrades
** Description changed:
+ [Origi
Public bug reported:
Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv
(application/vnd.rar) wird nicht unterstützt."
CBR-Files based on other rar-Types, e.g. rarv4 works fine.
** Affects: evince (Ubuntu)
Importance: Undecided
Status: New
--
You recei
Although I originally shared Daniel's doubt, I reported it to Debian and
shared the patch (bug linked above).
** Bug watch added: Debian Bug tracker #905277
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905277
** Also affects: gdm3 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.
** Changed in: libreoffice (Ubuntu Xenial)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1780996
Title:
Convert tri
Totally agree with Bruce!
I have two monitors. Let say I use LibreOffice on the left (primary) monitor
and a reference manager on the right monitor.
When I switch workspace (let say to do some programming) I don' t expect that
the reference manager keeps appearing?
This should be fixed. Or at le
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu4
---
glib2.0 (2.48.2-0ubuntu4) xenial; urgency=medium
* Add a versioned Pre-Depends for dpkg because the libglib2.0-0 -await
trigger requires a newer dpkg than the one in Ubuntu 14.04. (LP: #1784065)
-- Brian Murray
Just to follow up on this issue. I just realized that if you install
gnome-tweak tool
[sudo apt install gnome-tweak-tool] you can actually choose between coherent or
independent behavior of your multiple monitors across workspaces.
Once installed, launch tweak and then click on workspaces. then
This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
63ubuntu1
---
gnome-shell-extension-ubuntu-dock (63ubuntu1) cosmic; urgency=medium
* Merged with latest master
- Fix crash connecting/disconnecting monitors (LP: #1712661)
- showApps button label position
This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
63ubuntu1
---
gnome-shell-extension-ubuntu-dock (63ubuntu1) cosmic; urgency=medium
* Merged with latest master
- Fix crash connecting/disconnecting monitors (LP: #1712661)
- showApps button label position
** Changed in: gdm3 (Debian)
Status: Unknown => New
--
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/1782152
Title:
GDM blocks SIGUSR1 used in PAM scripts
To manage notification
** Changed in: gdm3 (Ubuntu)
Status: In Progress => Fix Committed
--
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/1778011
Title:
SRU: PRIME Power Saving mode draws too much powe
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1784065
Title:
upgrade from 14.04 to 16.04 fails due to `intere
This bug was fixed in the package ubuntu-drivers-common - 1:0.5.3
---
ubuntu-drivers-common (1:0.5.3) cosmic; urgency=medium
* gpu-manager.(c|py):
- Set automatic pci power management when the dGPU is disabled (LP:
#1778011).
- Load the nvidia modules when switching to perf
I am also having this problem. Additional notes: This happens even on
the most primitive X11 applications. Even applications like the Rosetta
Code X11 xlib application. This happens regardless of if you use
XCreate window or XCreateSimpleWindow. Additionally, even if you change
the window titl
3.18 is very old release, does this happens with 3.28?
Is there any way to reproduce this bug always? Bug description says that
it does not happen always... :(
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https:
I am experiencing this issue and it's just totally crippling. I can't
keep a session going for more than a few minutes without suddenly losing
the ability to interact with applications.
The specifics of my experience more closely match bug #1730229 -
although that is marked as a duplicate of this
This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4
---
gdm3 (3.28.2-3ubuntu4) cosmic; urgency=medium
* ubuntu_nvidia_prime.patch:
- Run scripts for Prime before and after Gdm sessions (LP: #1778011).
-- Alberto Milone Mon, 30 Jul 2018
18:31:17 +0200
** Changed in: gdm
This bug was fixed in the package gdm3 - 3.28.2-3ubuntu4
---
gdm3 (3.28.2-3ubuntu4) cosmic; urgency=medium
* ubuntu_nvidia_prime.patch:
- Run scripts for Prime before and after Gdm sessions (LP: #1778011).
-- Alberto Milone Mon, 30 Jul 2018
18:31:17 +0200
** Changed in: gdm
Thank you!
--
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/1767564
Title:
Ubuntu 18.04 Workspaces only change on primary monitor
To manage notifications about this bug go to:
h
** Description changed:
To reproduce:
-
Open a couple of windows
Press Alt+Space and keep it pressed
-
Expected results:
-
The window menu opens and nothing else happens
-
Current behavior:
-
The window menu opens
The window is minimized
The window menu of the
^ this solution doesn't work anymore
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1542519
Title:
Double menu bar
To manage notifications about this bug go to:
https://bug
** Description changed:
- Under wayland:
+ [ Description ]
+
+ Under wayland adding a monitor in cloned mode might crash g-s
+
+ See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248
+
+ [ Test case ]
+
+ Open an Ubuntu session on Wayland:
1. Attach another monitor
2. Mark
** Description changed:
+ [ Description ]
+
+ GNome shell crashes after Xorg loggin
+
+ [ Test case ]
+
+ From GDM login in a GNOME Ubuntu session (so Xorg).
+ It should start with no issues
+
+ [ Regression potential ]
+
+ We were deferencing a NULL pointer while outputting an error.
+ This
** Description changed:
+ [ Description ]
+
+ GNome shell crashes after Xorg logging
+
+ [ Test case ]
+
+ From GDM login in a GNOME Ubuntu session (so Xorg).
+ It should start with no issues
+
+ [ Regression potential ]
+
+ Nothing know, this is a safe NULL check, so no crash will happen.
+
I've not seen it yet on bionic (which uses 3.28), but it's still not
fixed on xenial's 3.18. Even though I encounter this quite frequently
there, I couldn't find a way to reproduce it in a consistent manner.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
This will be fixed in mutter (3.29.90-1)
** Description changed:
+ [ Description ]
+
gnome-control-center does not respond after we set the resolution
320x180
+
+
+ [ Test case ]
+
+ Open gnome-control-center -> Displays
+ Low resolutions (such as 320x180) should not be listed.
+
+ Tryin
** Description changed:
https://gitlab.gnome.org/GNOME/mutter/issues/130
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
+
+ [ Description ]
This happened while I was away from the computer. By the timing it
should have been well after the time it sh
** Description changed:
https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/15
- ---
+ [ Description ]
Was running 3 progr
FWIW I can't reproduce this any more either; since 18.04 in fact I've
had no problems with gnome-shell crashing. The monitor very nearly
always does wake up when it's supposed to now (some difference in the
dpms signal being sent? Previously it would always wake for windows and
just had a hard time
Public bug reported:
The nautilus closed all of a sudden
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.
StacktraceTop:
_int_malloc (av=av@entry=0x7f33dc20, bytes=bytes@entry=33) at malloc.c:3612
_int_realloc (av=av@entry=0x7f33dc20, oldp=oldp@entry=0x7f33dc042890,
oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4570
__GI___libc_realloc (oldmem=0x7f33dc0428a0, bytes=bytes@entry=32) a
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1785122/+attachment/5170925/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1785122
Ti
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1785122/+attachment/5170926/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1785122/+attachment/5170927/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1785122/+attachment/5170914/+files/CoreDump.gz
** Changed in: nautilus (Ubuntu)
Impor
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-terminal. This problem was most recently seen with package version
3.18.3-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/533baf10eb4eebaf140d791f6b612b140c44b36d
contains
Hi !
I have the same issue as I stated here :
https://askubuntu.com/questions/1061855/ubuntu-18-04-and-tracker-files-
properly-indexed-but-not-searchable-in-gs-naut
1. I installed tracker
2. I indexed all my data (as indicated on the command line by "tracker status"
/ "tracker daemon")
3. I chec
Confirming that with new glib2.0 - 2.48.2-0ubuntu4 in updates
repository, I could now easily do the 14.04 to 16.04 upgrade.
Thanks to all who made this fix happen quickly!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubu
jMyles, does your keyboard also stop responding to everything, including
the Windows key? If so then that sounds like your shell is frozen, which
is a different bug. In that case please open a new bug by running:
ubuntu-bug gnome-shell
on the machine.
--
You received this bug notification bec
Yes. The fix for this bug is in 3.28.2-3ubuntu4
--
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/1782152
Title:
GDM blocks SIGUSR1 used in PAM scripts
To manage notifications about thi
Did Alberto release the fix there and just forget to document it?
--
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/1782152
Title:
GDM blocks SIGUSR1 used in PAM scripts
To manage notif
** Also affects: gnome-control-center (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1772831
Title:
gnome-c
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1784398
Title:
Changing monitor settings
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification b
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1767956
Title:
gnome-shell crashed with
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1723615
Title:
gnome-shell crashed with SIGSEGV in
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1422253
Title:
gnome-shell crashed with
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
After a clean install of bionic, the system behaved as expected for some days.
Now, I get autologin after system boot, but have to type my password after
resume from sleep again. It happens with nvidia and nouveau driver.
** Changed in: gnome-control-center (Ubuntu)
Status: Expired => New
Public bug reported:
The same as always:
System gets to sleep (systemctl suspend), when pressing a key to resume from
sleep, the system will power up (fans and hard disk can be heard), but screens
remain dark. Not even terminals can be accessed (ctrl-alt-F2...6).
No problem with nouveau driver t
Uploaded again, thanks Marco and Robie. This time I removed the
confusing bug reference and compressed the changelog entries into one.
The version is ...18.04.2 even though this is the first release of this
upstream release to bionic, because of the aforementioned tagging error.
--
You received t
56 matches
Mail list logo
