OK, have manually rolled back the system to previous state (the old
versions of the packages were still available on my apt-cacher-ng
server), and run unattended-upgrades in debug mode - file attached. I
guess the key lines are:
sanity check failed for:
OK, here is dpkg.log section from one machine:
2022-03-05 14:45:14 startup archives unpack
2022-03-05 14:45:14 install libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1
2022-03-05 14:45:14 status triggers-pending libc-bin:amd64 2.31-0ubuntu9.2
2022-03-05 14:45:14 status half-installed libopengl0:amd64
Unfortunately I've already done that on the two affected machines and
didn't make a note of the output. I will try to dig out the dpkg logs.
As I said, the extra dependency on libopengl0 seemed to be the issue.
It's also just possible I took a snapshot or backup so I can roll back
and retry - I
Fixed by
https://github.com/iputils/iputils/commit/e2e9a2dd4639924614bdbee43907a49134e8da19
it seems.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1892108
Title:
ping prints ip
That would be excellent - thanks! IGLX is one of those things probably
not many people use, but those of us who do kind of really need it. It
also seems to be a thing in HPC / research circles:
https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-Potential-
Bye-Bye
FWIW, I'm now (finally)
OK, I think this is not a (huge) bug .. looking at saned code, it tries
to bind v6 and v4 sockets separately. If /proc/sys/net/ipv6/bindv6only
isn't set, binding v6 will also bind v4, making the later explicit v4
bind fail.
The second process is probably the one responsible for avahi
Still seeing this in 18.04! Gave up, disabled /etc/init.d/saned, and
used the systemd socket service - but this doesn't seem to advertise the
saned server.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
I'm seeing this in a slightly different situation .. I'm running an xpra
server which starts its own pulseaudio server; something to do with
running Chrome and attempting to play video randomly results in
everything in /dev/shm getting deleted, which leads the shm errors
reported above.
I made
Another thread relevant, at least for the gnucash aspect of this bug:
https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075769.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
Linking Jonathan's mailing list thread for reference:
https://lists.gnucash.org/pipermail/gnucash-user/2018-April/076587.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1765401
Public bug reported:
Version: 1.10.6-2ubuntu1
Ubuntu release: 18.04
I've just had a fun few minutes wondering why I couldn't disable NM
using "systemctl disable network-manager.service". Looks like the real
unit file is NetworkManager.service, and the former is a symlink.
Per systemd.unit(5),
I've hit this on Ubuntu 18.04 (xorg 1.19.6), modesetting driver. I have
opened a bug over there in case someone on that side has time to
investigate (https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1776447)
Interestingly, if I use VirtualGL as a true GLX proxy..
VGL_READBACK=sync
Public bug reported:
There's already an upstream bug report here:
https://bugs.freedesktop.org/show_bug.cgi?id=99555
Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1
I get immediate crashes e.g. with glxgear:
steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
Running
Public bug reported:
I've just spent an hour trying to understand why duplicity was not
deleting certain backup chains in remove_all_inc_of_but_n_full mode,
despite say it was. On every run, with the same parameters, it would
spit out:
Last full backup date: Tue Sep 9 16:47:20 2014
Deleting
Just been hit by this. Spent all day debugging graphics problems, only
now to discover that something has renamed my xorg.conf. I need 'Option
PageFlip false' with nouveau to get decent performance, something
decided that it knew better than me how to configure my hardware :(
Graphics card is:
Also seeing this on Ubuntu 14.04. Mixed network, have an if-up.d script
to restart minidlna - but sometimes it gets restarted after an IPv6
address has been obtained but before an IPv4 address is configured.
** Also affects: network-manager
Importance: Undecided
Status: New
** Also
Public bug reported:
I like to keep my cdrom mountpoint stable, as /media/cdrom .. in
previous Ubuntu versions this was done by adding the following (or
similar) to /etc/fstab:
/dev/cdrom /media/cdrom udf,iso9660 ro,user,noauto,exec,utf8 0
0
In 14.04, the CD-ROM gets correctly mounted on
Interesting .. should be possible to figure out the different code
paths, next time I have time to have a look...
On Wed, Mar 12, 2014 at 07:17:11PM -, Ivan Larionov wrote:
BTW it stops dhclient if I do disconnect from gnome's network-manager
menu.
--
You received this bug notification
Not sure it's an upstream bug - if you read back, there used to be
Debian-specific code wrapped in an #ifdef, which depends on a
preprocessor symbol that is no longer defined .. if you've got time you
could see if the seem problem ever existed in Debian, and if so, if/how
they fixed it ..
S.
On
OK, the commit that fixed things for me was upstream commit
52b3810b0e0d87bb47c6d77627d49fbb323d804d, fix NMPolicy/NMManager
refcounting. Not familiar with exactly how git works, but that seems to
have been cherry picked and reapplied to the main branch as
8c167c1f8f4338ccdc9906a9595e02c67fc1d9ca:
Seems that code path isn't being triggered at all for you. Interestingly,
older versions exhibit the same issue for me. Going to try to isolate the
commit that fixed things for me (binary search time!) .. hopefully then
will have some understanding of what's going on.
On 7 Mar 2014 18:01, Ivan
Interesting, your setup seems to skip a whole bunch of steps .. starting
with:
device state change: activated - disconnected
Will have a look at the source and see how that could get skipped.
Anything odd about your system - did you configure your wired connection
in n-m by hand?
--
You
Hmm, my best guess is that your connection never makes it to an
activated state .. can you grep your syslog for 'state ch.*activated'?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Color me baffled. Try adding some more debug??
diff -ur network-manager-0.9.8.8/src/nm-policy.c
network-manager-0.9.8.8.sd/src/nm-policy.c
--- network-manager-0.9.8.8/src/nm-policy.c 2014-01-26 17:37:05.0
+
+++ network-manager-0.9.8.8.sd/src/nm-policy.c 2014-03-06
Weird - I'm not seeing it here. I added some debug to n-m a while back,
will see if I can find the patch..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
OK, if you can change /etc/init/network-manager.conf so the exec line
reads:
exec NetworkManager --log-level=DEBUG
And apply the attached patch to the n-m sources, rebuild install, what
happens? (As you need syslogd to stay up to log the results, just 'sudo
stop network-manager' and have a in
Looking at this now, and getting sidetracked by RCS confusion .. what is
the difference between:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/network-
manager/trusty/files
and
http://bazaar.launchpad.net/~network-manager/network-
manager/ubuntu/files
? The latter seems to have
@oyvinst, the current NetworkManager in trusty (0.9.8.8-0ubuntu1) *does*
seem to stop dhclient:
Jan 26 17:25:02 xubuntu NetworkManager[1766]: info caught signal 15, shutting
down normally.
Jan 26 17:25:02 xubuntu NetworkManager[1766]: info (eth0): device state
change: activated - disconnected
We should probably remove the obsolete patches to avoid confusion.
** Patch added: Remove obsolete debian-specific patches that are no longer
compiled
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614/+attachment/3957801/+files/sd-nm.diff
--
You received this bug
This does seem to be getting kind of embarassing. With modern journalled
filesystems on relatively straightforward hardware configs an unclean
shutdown shouldn't be the end of the world (after all, power failures
can happen), but it's not nice either.
Unfortunately we also seem to have a hell of
On Wed, Jan 22, 2014 at 04:13:19PM -, Max wrote:
Steve Dodd:
Last time I did, my own problems were caused by dhclient and ureadahead..
It is not an ureadahead issue, it is an extra fork in upstart to launch
shell for ureadahead if more than one partition mounted.
Yes, I know - I
Public bug reported:
I'm running 12.10 on a mostly headless MK808 stick - but I believe this
bug will exist on later versions as well as the code in question hasn't
changed. Originally I had my /etc/network/interfaces configured to use
wpa_supplicant in roaming mode, and this worked correctly.
apport information
** Tags added: apport-collected quantal
** Description changed:
I'm running 12.10 on a mostly headless MK808 stick - but I believe this
bug will exist on later versions as well as the code in question hasn't
changed. Originally I had my /etc/network/interfaces
apport information
** Attachment added: modified.conffile..etc.wpa.supplicant.functions.sh.txt
https://bugs.launchpad.net/bugs/1262874/+attachment/3932845/+files/modified.conffile..etc.wpa.supplicant.functions.sh.txt
--
You received this bug notification because you are a member of Desktop
That sounds plausible - I would guess wireless connections are usually torn
down at the end of the user session (i.e. logout) whereas I assume wired
connections persist right to system shutdown??
On Oct 21, 2013 3:01 PM, Christian Niemeyer chr.nieme...@gmail.com
wrote:
It occurs that the problem
Note for those wanting to apply the above patch: network-manager uses
quilt, and the above patch only patches the patches. So do quilt pop
-a after unpacking the source, then apply the patch above, then quilt
push -a to reapply the changed patches.
--
You received this bug notification because
M4he, yes, looks like it. Does the patch above apply cleanly to n-m in
saucy? It solved things for me. If you're on x86-32 I can probably build
you a package to test easily.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
*raring, sorry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
stopped
Status in
** Tags added: saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1169614
Title:
/etc/init.d/umountroot: mount: / is busy due to dhclient is not
stopped
Status in
My problems (on current saucy) were caused by bugs in upstart (affecting
ureadahead) and network-manager. The patches in bug #1181789 and bug
#1169614 give me a clean unmount and shutdown.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I can confirm the above patch fixes the problem of dhclient still being
running on shutdown for me (once I figured out how to use quilt so I
could rebuild nm.)
Still need to a fix an upstart/ureadahead problem to get a clean
shutdown on my machine, but this is progress.
--
You received this bug
Just noticed this on 12.04 too. Looks like a difficult issue, because
there are some situations where closing the window seems to make sense,
e.g. if the window automatically opened when USB/optical media was
inserted. OTOH, if I open a nautilus window by hand, double-click a DAV
share, then eject
Discusses this from the other angle, looks like the behaviour changed
between 12.04 and 13.04:
http://ubuntuforums.org/showthread.php?t=2156088
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Public bug reported:
Getting update-alternatives: error: alternative path /usr/bin/gnome-
session-fallback doesn't exist on configuration.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: gnome-session-flashback 1:3.6.2-0ubuntu9
ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6
Public bug reported:
Possibly a dupe of bug #808776. Running saucy with all packages up-to-
date. Rebooted, logged in using GNOME Flashback/Fallback, flipped
through the menus, logged out, logged back in using Fallback (no
effects), flipped through the menus again, logged out, logged in using
45 matches
Mail list logo
