Thanks, Pedro, but without the hard facts it is difficult to ascertain
whether this is a bug. Namely,
whoami; stat /tmp /tmp/.X11-unix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bu
** Summary changed:
- gnome-shell crashed with SIGABRT:
ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state
== SHELL_APP_STATE_STOPPED)
+ gnome-shell crashed with SIGABRT: ERROR:../src/shell-app.c:shell_app_dispose:
assertion failed: (app->state == SHELL_APP_STATE_STO
Looks like it's still a common issue:
https://errors.ubuntu.com/?package=systemd&period=week
but we'd need the crash ID or the machine's whoopsie ID to tell which
instance this is.
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Inco
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2078280
Title:
System Crash on reboot/screen lockout: systemd-logind crashed with
SIGABRT in
You have been subscribed to a public bug:
Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
A
I've extended the test plan to mention the particular hardware required.
As for testing multiple Nvidia driver versions, that's not required.
Because the phantom monitor comes from simpledrm and not from nvidia.
There are no separate per-driver fixes. Although it's always advisable
you're starting
i386 has been enabled by default on amd64 for quite some time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2077232
Title:
Security update 42.9-0ubuntu2.2 uninstalls GDM
Sta
Touch sensors are independent devices from the displays they're glued
to. But that said, Mutter should already have a good idea of which
display it has associated the touch sensor with. So it should be smart
enough to disable it in this case.
** Package changed: gnome-shell (Ubuntu) => mutter (Ubu
> Why is there a warning that is about overwriting a binding keysym with
the exact same value? Can't that warning be skipped.
I had the same thought. The new binding having a different callback
might explain it.
--
You received this bug notification because you are a member of Desktop
Packages,
https://launchpadlibrarian.net/746352003/mutter_46.2-1ubuntu0.24.04.2_source.changes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2077746
Title:
GNOME Shell crashes when recording a
https://launchpadlibrarian.net/746352003/mutter_46.2-1ubuntu0.24.04.2_source.changes
** Changed in: mutter (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bug
https://launchpadlibrarian.net/746352003/mutter_46.2-1ubuntu0.24.04.2_source.changes
** Changed in: mutter (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bug
> The only thing is, installing updates through the GUI default upgrader
is NOT supposed to accept solutions that require removing packages.
If having multiple architectures enabled was a factor here then surely
we're already outside the realm of a bug that can be reached through GUI
interactions
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2078284/+attachment/5810212/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https:/
apport information
** Tags added: apport-collected
** Description changed:
Important logs:
19:55:29 gdm-session-wor: gkr-pam: unable to locate daemon control file
19:55:19 systemd: Failed to start fluidsynth.service - FluidSynth Daemon.
19:55:19 (uidsynth): fluidsynth.service: Failed
Public bug reported:
Important logs:
19:55:29 gdm-session-wor: gkr-pam: unable to locate daemon control file
19:55:19 systemd: Failed to start fluidsynth.service - FluidSynth Daemon.
19:55:19 (uidsynth): fluidsynth.service: Failed to drop capabilities: Operation
not permitted
19:33:37 systemd: F
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.7.8
---
ubuntu-drivers-common (1:0.9.7.8) oracular; urgency=medium
[ Kuba Pawlak ]
* Revert "Change maximum open files limit for the shell" (LP: #2077646)
-- Timo Aaltonen Wed, 28 Aug 2024 21:42:02 +0300
** Chang
** Changed in: pppconfig (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pppconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2078254
Title:
ftbfs: UTF-8 "\xAB" does not map to Unicode at
/usr/s
I have just installed the latest 6.8.0-41.41 kernel (and rebooted too),
but the issue persists.
Trying to suspend, turns the screen blank for one second, and then shows
the GDM/ login screen (my user is still logged in and I can continue my
session from where I left off prior to suspend.
Any tips
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2077918
Title:
librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing
dependencies
Sta
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/pppconfig/+git/pppconfig/+merge/472165
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/po4a/+git/po4a/+merge/472166
--
You received this bug notification because you are a member
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Invalid
** Description changed:
[ Impact ]
- ADT testing fails on arm builders
+ ADT testing fails on arm builders due to a racy test
+
+ [Fix]
+
+ Split the test avoiding the race.
[ Test Plan ]
Run ADT tests in PPA o
for oracular this is committed to git
** Changed in: ubuntu-drivers-common (Ubuntu Oracular)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bu
Allesandro, subscribing you to this bug because of your PR at
https://github.com/mquinson/po4a/pull/515
I'm willing to upload pppconfig with the debdiff you provided in the
debian bug, and also po4a with the patch in your github PR[2], to
unblock this FTBFS in Oracular. I can do follow-up uploads
Hello, I'm having same error but with another package reported in here
but with packages bleachbit and rhythmbox because updating the packages
today with Python 3.12.
https://ubuntuforums.org/showthread.php?t=2500273&p=14202717#post14202717
Regards
Fran
--
You received this bug notification be
Probably needs Fix (debdiff) proposed in Debb #1072606
** Bug watch added: Debian Bug tracker #1072606
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072606
** Also affects: pppconfig (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072606
Importance: Unknown
St
Public bug reported:
>From the oracular archive rebuild ppa:
https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular-
amd64.pppconfig_2.3.28_BUILDING.txt.gz
...
UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line
353, <$fh> line 464.
UTF-8 "\xE9" does not m
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2077232
Title:
Security update 42.9-0ubuntu2.2 uninstalls GDM
Status in gnome-shell package in U
The only thing is, installing updates through the GUI default upgrader
is NOT supposed to accept solutions that require removing packages. So
this really needs to be tracked down and fixed. I don't think there's
anything further to be done in gnome-shell.
** Also affects: gnome-software (Ubuntu)
Public bug reported:
[placeholder for https://github.com/ubuntu/adsys/pull/1070]
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.la
Public bug reported:
[placeholder for https://github.com/ubuntu/adsys/pull/1079]
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.la
Public bug reported:
[placeholder for https://warthogs.atlassian.net/browse/UDENG-4314]
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- username overwritten during rewrite from / to @
+ rewrite from / to @ formats overwrites usernames
--
You re
Just to let you know, my problem was a slight different message: "Failed to
start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"
And the "/tmp/.X11-unix" directory had the right permissions.
Turns out the message is quite misleading in my case because the problem was
actually in "/tmp"
I disabled the test as there are some races there between different scenarios
in one context.
I just tested that splitting this one big test so each smaller test only checks
one thing, make all of them pass.
Instead of disabling it, refactor it.
--
You received this bug notification because you
OK, but how does this relate to the upload in Jammy unapproved that
disables the test outright?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2077654
Title:
Race condit
In the case that /tmp is owned by ourselves and it matches 0200 but not
0022, it is still writable but it would fail with the present error.
I do not know if this is actually an intended blockage and thus the
description is just not clear enough or if this is an edge case to
consider.
Nor do we k
Why is there a warning that is about overwriting a binding keysym with
the exact same value? Can't that warning be skipped. Or is that
"(keycode NN)" part important here?
I don't like unnecessary syslog messages.
--
You received this bug notification because you are a member of Desktop
Packages,
the test origiannly was testing 6 different scenarios by injecting dependency
in a separate file.
I split this test into 6 scenarios, each testing one thing only. for now it
seems to work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This comes from ensure_x11_unix_perms, which is determining that the
/tmp/.X11-unix does not have at least permission bits 022:
--->
static gboolean
ensure_x11_unix_perms (GError **error)
{
/* Try to detect systems on which /tmp/.X11-unix is owned by neither root nor
* ourselves because in t
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2078069
Title:
package firefox 129.0.2+build1-0ubuntu0.20.04.1 failed to
install/upgrade: new fi
Public bug reported:
Failed during do-release-upgrade to Jammy from Focal
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 129.0.2+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-193.213-generic 5.4.278
Uname: Linux 5.4.0-193-generic x86_64
NonfreeKernelModules: nvidia
Hi Robie,
the test is failing 100% on arm builder in PPA. It sometimes fails for amd64
too.
This issue was already there when the previous version of this package was
introduced and it was also retried until it passed somehow. I could not make it
pass myself.
--
You received this bug notifica
** Attachment added: "Screenshot of gnome-system-monitor when copying had
finished"
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2078065/+attachment/5810082/+files/Screenshot%20from%202024-08-28%2016-12-25.png
--
You received this bug notification because you are a mem
Public bug reported:
Gnome System Monitor on Ubuntu 24.04 shows completely wrong network
(Receiving) transfer speed and Total Received values.
Hardware: Framework Laptop 13 _AMD Ryzen 7040Series
- Laptop is connected via ethernet (framework network expansion card) to a 1
Gbps switch
- copying a
Public bug reported:
I connected the ThinkPad T14 G3 AMD to an external screen with the lid
open, turned off the internal screen, and to my surprise when my cat
walked over the screen she moved the windows on the external screen. 🙀
Now this may be useful and I am not sure it is a bug, I'll let ot
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2078060
Title:
gnome-control-center 47~beta-1ubuntu2 does not accept fractional
scales
St
Public bug reported:
Fractional scale support seems broken, it says the configuration cannot
be applied due to "hardware limitations". If you already have configured
fractional scaling; any changes to the output essentially can't be
saved.
e.g. you can't switch to external-only (with fractionally
Public bug reported:
Observed:
I access Teams from Firefox and it works as far as I can tell, including live
meetings. Occasionally though, when I try to share my screen (it is always a
specific window I'm sharing), others in the meeting see that I'm sharing
something, but they don't see the wi
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
I'm rejecting two uploads for Noble because they collide between bug
2077746 and bug 2025006 (amongst others). Please coordinate and re-
upload just one SRU at once (possibly squashing multiple fixes together
as you wish).
** Changed in: mutter (Ubuntu Noble)
Status: In Progress => Triaged
An upload of libmbim to noble-proposed has been rejected from the upload
queue for the following reason: "Rejecting as agreed with @kchsieh,
pending the full SRU.".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https:
Public bug reported:
Starting with the librsvg 2.59 series (2.58.9*), librsvg requires
cargo-c to build. cargo-c comes from the Debian source rust-cargo-c.
The issue is that librsvg needs to be built on i386, but rust-cargo-c is
not currently built for i386. The list of Build-Depends is kinda lon
From IRC (#ubuntu-release):
13:14 tjaalton: for bug 2060268, are there any cases where the
udev rule would be triggered but is the wrong thing to do? How certain
are we on that point?
13:14 tjaalton: presumably the Test Plan should specify testing
on particular hardware? That needs adjusting. B
SRU review: it looks like the test being disabled was first introduced
in 1:0.9.5.1 and was related to an FTBFS fix. However, it doesn't seem
to be testing the actual payload, but its own test setup. I don't see a
way that disabling this test would cause a false negative, so it appears
to be a no-o
> +# Race condition may happen and the test fails. This only happens in
> Jammy containers.
> +# Disable the test for now.
> +return
I don't think it's appropriate to disable a test without an analysis
that considers what it was testing, how to mitigate the gap created by
** Changed in: kubuntu-meta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2068612
Title:
Please remove wireless-tools from oracular
S
** Also affects: kubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-gnome-meta (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal unlinked:
https://cod
I suppose we *could* do the same in Jammy and Noble updates. But again
that only prevents the issue from recurring and doesn't fix the
brokenness if it's already in that state.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell i
I'm going to declare this done for Oracular, but we can't fix the hard
dependencies that already exist up to and including Noble. Because those
dependencies are already on peoples' hard disks.
https://salsa.debian.org/gnome-team/gnome-
shell/-/commit/40849f7efd55e48346ecb9ed3e171ae1ad75adb0
No lo
24.04.01 LTS - Same bug with the difference that the icons (using candy-
icons) reverts only when selecting the "Appearance" section in Settings.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs
** Changed in: librsvg (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2077918
Title:
librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fai
61 matches
Mail list logo
