[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.
On 2020-10-30 02:29, Gunnar Hjalmarsson wrote:
> Is that what we want to do?
Probably not.
https://gitlab.gnome.org/GNOME/pango/-/issues/483#note_949138
Matthias' gtk commits seem to fix it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3338
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3338
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3338
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-desktop3 (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.
** Package changed: gnome-desktop (Ubuntu) => gnome-desktop3 (Ubuntu)
** Changed in: gnome-desktop3 (Ubuntu)
Status: New => Triaged
** Changed in: gnome-desktop3 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Oddly, confirmed. Only when in Sound settings...
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1841 dan 20 0 1125668 168248 120056 S 12.9 1.0 103:17.70 Xorg
1984 dan 20 0 5481060 435396
Given gnome-shell is also affected it seems the problem is gnome-
control-center doing some kind of constant, invisible rendering when in
the Sound panel.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
** Changed in: gnome-control-center (Ubuntu)
Importance:
The login GUI is gnome-shell...
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
--
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/1902018
Title:
Fingerprint: "scan your
Thanks. I think xrandr.txt is the most important file there but it looks
like you didn't have any scaling set at the time.
Please enable fractional scaling, even if it is too big, and then run:
xrandr --verbose > xrandr2.txt
journalctl -b0 > journal2.txt
and attach the resulting text file
You have been subscribed to a public bug:
Several days ago I found huge lags over all system on my Ubuntu 20.04.1
LTS. Today I think found the problem, but not the reason. So when I open
Settings -> Sound menu, the CPU usage comes to about 100%. If I close
Settings window or go to other tab, it
geez,
That's a common mistake... When we ask people to test a mutter update we
actually mean 'libmutter' that's used by gnome-shell.
** Also affects: mutter (Ubuntu Hirsute)
Importance: High
Status: In Progress
** Also affects: snapd (Ubuntu Hirsute)
Importance: High
Status:
As geez did above, I installed libmutter-7-0, mutter, and mutter-common
from groovy-proposed. Zoom now opens and seems to run fine, which is
the snap that, for me, previously did not open. There seems to be a
draw issue that I have never had before though. When I close the
application, the
Now we know from the upstream pango issue which commit caused this bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/e5c0b4f5
I confirmed that reversing that commit fixes it:
https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-terminal
Is that what we want to do?
--
You received
ok, this is what happens in journalctl when an ISO successfully is
mounted:
```
Oct 29 18:02:06 boxxy kernel: loop1: p1 p2
Oct 29 18:02:06 boxxy kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Oct 29 18:02:06 boxxy kernel: ISO 9660 Extensions: RRIP_1991A
Oct 29 18:02:06 boxxy
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being 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
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being 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
This bug was fixed in the package gnome-control-center -
1:3.36.4-0ubuntu2
---
gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium
* debian/patches/git_useraccount_segfault.patch:
- don't segfault trying to get the user initials when accountsservice
is not
This bug was fixed in the package gnome-control-center -
1:3.36.4-0ubuntu2
---
gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium
* debian/patches/git_useraccount_segfault.patch:
- don't segfault trying to get the user initials when accountsservice
is not
This bug was fixed in the package gnome-control-center -
1:3.36.4-0ubuntu2
---
gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium
* debian/patches/git_useraccount_segfault.patch:
- don't segfault trying to get the user initials when accountsservice
is not
This bug was fixed in the package gnome-control-center -
1:3.36.4-0ubuntu2
---
gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium
* debian/patches/git_useraccount_segfault.patch:
- don't segfault trying to get the user initials when accountsservice
is not
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being 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
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being 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
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being 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
This bug was fixed in the package gnome-control-center -
1:3.36.4-0ubuntu2
---
gnome-control-center (1:3.36.4-0ubuntu2) focal; urgency=medium
* debian/patches/git_useraccount_segfault.patch:
- don't segfault trying to get the user initials when accountsservice
is not
here are the requested files.
** Attachment added: "bug1900873.zip"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+attachment/5429161/+files/bug1900873.zip
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** No longer affects: openjdk-7 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1226962
Title:
Keyboard shortcuts (hotkeys) not functional in some cases in
The problem was more with sssd than gnome.
Not sure of the exact source of the problem with SSSD, but applying the
following worked as a workaround :
- Run `sudo systemctl edit sssd.service` and add the following:
[Service]
RuntimeMaxSec=1800
Restart=on-failure
- Restart SSSD:
$ sudo
The bug affects me, too. I just installed the three above mentioned
mutter packages (libmutter-7-0 mutter mutter-common) and now Chromium is
working again. Thanks for the fix!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** No longer affects: openjdk-7 (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1226962
Title:
Keyboard shortcuts (hotkeys) not functional in some
I do not have tracker-miner-fs.service at all. My instance of gvfsd is
started by either ibus-daemon, or "systemd --user". Please see the
controversy at
https://gitlab.gnome.org/GNOME/gvfs/-/issues/481#note_948506
--
You received this bug notification because you are a member of Ubuntu
Desktop
If this is the same problem I'm having
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1901279)
Then a workaround that works for me is to set the display with
`xsetwacom` using coords or HEAD-1 (VGA-1 and DP-3 type identifiers
aren't working)
$ xsetwacom --set "Wacom Intuos
this is just going in circles. i don't understand the details but it seems that:
* it's quite ok to have a monospace filter built into the gnome-terminal font
selector
* this job is really delegated to the pango lib, which uses the first fc result
to determine the spacing for the *whole* family
The update works fine and there is no report for >= 1:3.36.4-0ubuntu2 on
e.u.c, marking as verified
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
The 1:3.36.4-0ubuntu2 update works as documented
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The update works fine and there is no report for >= 1:3.36.4-0ubuntu2 on
e.u.c, marking as verified
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Unsubscribing field high as desktop isn't covered under the Field SLA.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1901552
Title:
Unrecoverable failure in
Seeing as the issue was solved for two other people, I had another go -
this time explicitly installing all mutter-related packages from
-proposed (and not just 'mutter'):
$ aptitude upgrade libmutter-7-0 mutter mutter-common
Lo and behold, the socket showed up:
$ sudo ss -xlp | grep Xwayland
I was running libmutter-7-0 3.38.1-1ubuntu1. I could reproduce the
initial bug of not being able to launch Chromium from the snap. After
upgrading to 3.38.1-2ubuntu1, now I can launch it fine.
Additionally, ss shows that Xwayland is listening on the abstract socket
too.
laney@nightingale> ss
The upstream bug got reopened now, could you try disabling the tracker
service and see if it resolves the issue for you?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890
Title:
Thank you for your bug report, could you take a photo showing the issue
and add the 'journalctl -b 0' log after triggering the problem?
** Package changed: gnome-control-center (Ubuntu) => gdm3 (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Low
--
You received this bug
Trying with https://fedorapeople.org/groups/virt/virtio-win/direct-
downloads/archive-virtio/virtio-win-0.1.185-1/virtio-win-0.1.185.iso it
mounts fine here
Could you do
$ journalctl -f
try to mount and see if the log has any output? here it writes
udisksd[1519]: Set up loop device /dev/loop61
Hum, which viewer did you use?
Opening the log in gedit it displays
'Resolving wks.cie.com failed: No DNS record of the requested type for
“_kerberos._udp.wks.cie.com”'
the string uses utf quotes
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: xf86-input-wacom
Status: Unknown => 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/1900908
Title:
Mutter doesn't apply gsettings appropriately to Wacom
** Also affects: vscode
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1226962
Title:
Keyboard shortcuts (hotkeys) not
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1902018/+attachment/5428917/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1902018/+attachment/5428919/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Public bug reported:
OS: Ubuntu 20.10 version
Test sequence:
Fingeprint is enrolled
Win+L: At login screen, earlier in 20.04 version, it used to display "scan your
finger", it is not displayed in 20.10 version, but fingerprint identify is
working fine.
---
ProblemType: Bug
ApportVersion:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1902018/+attachment/5428918/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Sounds like more votes/testers are required.
** Tags removed: verification-failed-groovy
** Tags added: verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I have the updated mutter package (3.38.1-2ubuntu1) and chromium snap is
working fine again.
Open sockets:
u_str LISTEN 0 1 @/tmp/.X11-unix/X0
64514* 0 users:(("Xwayland",pid=4667,fd=4))
Same problem on the fresh released Fedora 33, GNOME desktop on Wayland.
I think this is a Wayland related issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
** Also affects: xserver-xorg-input-wacom (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/linuxwacom/xf86-input-wacom/issues #148
https://github.com/linuxwacom/xf86-input-wacom/issues/148
** Also affects: xf86-input-wacom via
Can also confirm on Ubuntu 20.04.1 LTS. Didn't find the process so I
couldn't kill this annoying window. It popped when I started to install
dependancies within pycharm.
Alt+F2 + "r" worked for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1900908 ***
https://bugs.launchpad.net/bugs/1900908
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1900908, so it is being marked as such. Please
Additional info, when mapping buttons, if I set a Wacom tablet button to
"Switch Monitor", when I tap that button all three of my monitors
display the same Wacom Intuos BT M popup. Presumably this is because all
three are mapped, not just one. If it were properly mapping a single
monitor, that
This doesn't seem limited only to Nvidia drivers. I'm using a Lenovo
Thinkpad X1 Carbon, 6th Gen with Ubuntu 20.10. Sometimes the map to
monitor setting works, other times it is completely ignored. When it is
ignored, the relative vs absolute setting in the Settings | Wacom |
Tablet gnome settings
57 matches
Mail list logo
