This bug seems to be intermittent. I've now rebooted 5 or 6 times the
system and I could only reproduce the issue on the first reboot. :/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
After further testing it's not a Firefox problem, other applications
have the same issue. Weirdly, gnome-shell itself doesn't have the issue,
hence my initial mistake. Gnome terminal, thunderbird, and Ubuntu
software all have the same symptoms.
Note that mouse input works fine.
Reaffecting to
Oh yes sorry, I should have done that in the initial report.
I'm using a Lenovo Yoga laptop model 710-IKB, with an AZERTY keyboard
layout. It had no external input devices plugged in. A notable HW
feature of the laptop is that it has a touchscreen.
I'll give it a few more tries later today to
Out of curiosity, would it work if you rename Vidéos into Videos?
** Also affects: glib2.0 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** Also affects: ubuntu-release-upgrader (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tracker-miners (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:
https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0
The crash occurs during the upgrade, which
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/1983859
Title:
tracker-extract crashes with SIGSYS when
So, after some fairly exhausting debugging, I kind of gave up on that
bug, but as a last ditch effort I tried a rebuild against the latest
snapshot (even though the changelog didn't seem particularly relevant),
nd... Now it builds.
I'm so tired.
--
You received this bug
** Changed in: glibc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pango1.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in Ubuntu.
I'm currently focused on cataloguing failures, but I'll try to
investigate it if nobody has picked it up by then.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2049881
Title:
Public bug reported:
Hi,
The package pango1.0 failed to build during the recent full archive test
rebuild against a snapshot of the the development branch for the
upcoming glibc 2.39, expected to land in Noble. This was subsequently
confirmed locally against a more recent snapshot.
Full logs
** Changed in: glibc (Ubuntu)
Importance: Undecided => Critical
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Tags added: foundations-todo
--
You received this bug notification be
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el,
+ s390x.
- armhf
We had a mitigation for this in glibc but the latest change from simply
denying the unshare() call to allowing it but then denying anything
requiring capabilities *presumably* broke the glibc test suite again.
I'm only basing this from looking at the test logs, as I'm temporarily
unable to run
I'm not entirely sure nautilus is the right package to assign this to,
but I'm definitely certain needrestart has nothing to do with the issue
:)
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: needrestart (Ubuntu)
Status: New => Invalid
--
The bug didn't occur after the reboot anyway so I'll keep my extensions.
I do feel like no extension should be able to lock up the shell to the point I
can't even reach the console.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
On Noble, using Gnome (not the Ubuntu desktop) + a few plugins, I had my
desktop completely unresponsive after logging in. The mouse cursor was
still moving, but the hot corner didn't work, nor did the various
keyboard shortcuts. Surprisingly, the Ctrl-Alt-Fn access to
18 matches
Mail list logo
