Excellent, thanks Danilo for the super fast fix! ⭐
--
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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- ren
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
Exact same fix uploaded to -proposed SRU review queue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2040488
Title:
loading lvm2 module crashes: udisks_module_lvm2_new: assertion
'
** Description changed:
[Impact]
Trying to load the lvm2 module crashes udisks immediately:
busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager
org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true
udisksd[5709]: cannot register existing type 'UDisksDaemo
add165ccc46008a17163f8
+
ProblemType: Crash
Architecture: amd64
Date: Wed Oct 25 12:13:14 2023
DistroRelease: Ubuntu 23.10
ExecutablePath: /usr/libexec/udisks2/udisksd
Package: udisks2 2.10.1-1ubuntu1
** Changed in: udisks2 (Ubuntu Mantic)
Status: New => In Progr
** Changed in: udisks2 (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: udisks2 (Ubuntu)
Status: New => Fix Committed
** Changed in: udisks2 (Ubuntu)
Importance: Undecided => High
** Changed in: udisks2 (Ubuntu Mantic)
Importance: Undecide
It's not related to the configure arguments, but to the linker flags.
The Ubuntu package build sets
LDFLAGS="-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects
-Wl,-z,relro -Wl,-z,now"
while Debian uses
LDFLAGS="-Wl,-z,relro -Wl,-z,now"
lto seems to work, but dropping the "-Wl,-Bsymbolic
Interesting! when I check out the source package, and build with the
above patch and like this:
./configure CFLAGS="-g -O0" --disable-gtk-docs --enable-lvm2
make -j4
sudo src/udisksd -rd --force-load-modules
then it loads the module just fine:
(udisksd:17050): udisks-WARNING **: 14:52:41.1
Comparing with Debian testing: Running
# /usr/libexec/udisks2/udisksd --debug --force-load-modules
udisks-Message: 10:34:44.696: udisks daemon version 2.10.1 starting
udisks-Message: 10:34:44.724: Acquired the name org.freedesktop.UDisks2 on the
system message bus
udisks-Message: 10:34:44.729: Lo
It's a bit easier to investigate with
/usr/libexec/udisks2/udisksd --debug --force-load-modules
There I've1 also seen it fail on the btrfs module, so it's not specific
to the LVM one.
It also happens with rebuilding the udisks source package (so not just
changed ABI)
I tried building upstre
Confirmed on current noble, same udisks2 version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2040488
Title:
loading lvm2 module crashes: udisks_module_lvm2_new: assertion
'UDISK
Public bug reported:
I tried to do this with `apport-cli
/var/crash/_usr_libexec_udisks2_udisksd.0.crash`, but 's'ending doesn't
do anything obvious. I run this from a cloud image over ssh, I really
don't have any GUI. So filing this manually.
Trying to load the lvm2 module crashes udisks immedia
*** This bug is a duplicate of bug 1856799 ***
https://bugs.launchpad.net/bugs/1856799
** This bug has been marked a duplicate of bug 1856799
vitrage-ml run error
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
h
** Package changed: libssh (Ubuntu) => openstack (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1856799
Title:
vitrage-ml run error
Status in openstack package in Ubuntu:
N
Sorry, this isn't something that can be fixed in libssh, but some
bug/issue with dpkg, possibly a faulty disk, etc. Closing as
inactionable.
** Changed in: libssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is s
> Xorg -config tests/xorg-dummy.conf -logfile /tmp/log -once :5
The -once was an attempt to work around this, but it doesn't help, nor
change the behaviour of this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubunt
umockdev's test suite now started to see this crash in current Ubuntu
jammy. Simple reproducer:
$ cat tests/xorg-dummy.conf
Section "Device"
Identifier "test"
Driver "dummy"
EndSection
$ Xorg -config tests/xorg-dummy.conf -logfile /tmp/log -once :5
Then, run at least one query
Christian, as I write above I believe this really needs to be fixed in
bolt's tests. The umockdev change was a bug fix which bolt's tests
(incorrectly) worked around. So I hope you don't mind that I flipped the
affected package around? I am in contact with Christian now, and hope to
sort this out s
I installed udisks2 2.9.2-1ubuntu1 from hirsute-proposed, and confirm
that both the manual test case above as well as cockpit's automatic
TestStorageFormat.testFormatTypes now succeed. Thank you Sebastien and
Robie!
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: ve
Argh indeed, forgot about that one already -- I even looked at that
before, it's tracked here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=983751
But you knew that as well, in comment #4 -- So I hope this didn't take
too much time to track down. Merci beaucoup !
** Bug watch added: Debian
Direct mkfs works:
# mkfs.vfat -I -n label /dev/vdb
mkfs.fat 4.2 (2021-01-31)
mkfs.fat: Warning: lowercase labels might not work properly on some systems
# blkid -p /dev/vdb
/dev/vdb: PTUUID="892240dd" PTTYPE="dos"
** Changed in: udisks2 (Ubuntu)
Status: Incomplete => New
--
You receive
Reproducer from scratch:
# download current cloud image
curl -L -O
https://cloud-images.ubuntu.com/daily/server/hirsute/current/hirsute-server-cloudimg-amd64.img
# nothing fancy, just admin:foobar and root:foobar
curl -L -O
https://github.com/cockpit-project/bots/raw/master/machine/cloud-init.is
I tried to run it in the foreground with
G_MESSAGES_DEBUG=all /usr/libexec/udisks2/udisksd
but still no messages aside from the timeout.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bu
Forgot to mention, there is nothing useful in the journal. The only
message is this when the timeout happens:
Apr 23 15:12:35 ubuntu udisksd[3116]: Error synchronizing after
formatting with type `vfat': Timed out waiting for object
** Description changed:
There is a regression somewhere betwe
Public bug reported:
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}'
FTR, I would strongly advise against that, see
https://github.com/martinpitt/umockdev/issues/110#issuecomment-736224503
. You want the tests to work independently on the hardware it's running
on, so that you can run it on e.g. standard autopkgtest infra.
You could create /sys/firmware/efi/efivars/
Nevermind then, this is working well enough for a stable release.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.laun
I confirm that using a valid IP works better:
In the config:
route1=fe80:2::/60,fe80::99,42
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
fe80:2::/60 via fe80::99 proto static metric 42 pref medium
It's still missing the
The journal says why:
NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure
to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No
route to host (113)
NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply
manual IPv6 configuration
Appa
Public bug reported:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac
Wow, thanks Marc, this was super-fast!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1805348
Title:
Recent security update broke server-side keyboard-interactive
authentication
Sta
Public bug reported:
0.8.4 and the backported fixes for CVE-2018-10933 cause server-side
keyboard-interactive authentication to completely break. See
https://bugs.libssh.org/T117 for details and a reproducer.
This was fixed upstream as part of the 0.8.5 release, so disco is fine.
For 16.04/18.04/
I installed libssh-4 0.8.1-1ubuntu0.2 from cosmic-proposed, and confirm
that the manual ssh connection with "cockpit-ssh" as well as all the
integration tests that involve talking to remote machines through ssh
now work.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added
s. So overall, I
think this is bearable for an SRU, especially as the impact is quite high.
[1]
http://api.libssh.org/master/group__libssh__session.html#gac%20bc5d04fe66beee863a0c61a93fdf765
[2] https://github.com/cockpit-project/cockpit/pull/10357
[3]
https://fedorapeople.org/groups/cockpit
ld get included:
https://git.libssh.org/projects/libssh.git/commit/?id=35a64554899f142a2b8b68c79007ad9c3ce00cb1
https://git.libssh.org/projects/libssh.git/commit/?id=c1a8c41c5daf79e37aa5fde67dd94c8596e81102
https://git.libssh.org/projects/libssh.git/commit/?id=893b69d82b4435973ec4d15aaec
Added SRU information and uploaded SRU to unapproved queue.
** Description changed:
Ubuntu 18.10's libssh 0.8.1 regresses parsing of known_hosts. This
happens (sometimes) if there are multiple known_host key types (e. g.
ssh-rsa and ssh-ed25519), then it can happen that
ssh_session_is_kno
@Robie: It's been a while since I dabbled with this, but to me this is
not really "wishlist", it's an actual bug. Surely pg_wrapper doesn't
document that it looks at the explicitly specified port, but it
certainly ought to. This case was just plain forgotten.
So the patch certainly needs some mass
FTR, I don't want to blame the NetworkManager 1.2.6 SRU to xenial - that
new upstream version now evades the version test in the postinst, but of
course it's still that version test which is at fault. I don't see how
we can use a simple version test to determine the situation that we want
(one-time
Is that any better with the fix in bug 1690992? That sounds very much
like a duplicate?
--
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/1716034
Title:
Network manager stops man
I'm sorry, I mean bug 1676547.
--
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/1716034
Title:
Network manager stops managing Ethernet links after upgrade
Status in network-man
Blaisorblade [2017-03-15 15:03 -]:
> Another corner case seems to be binaries linked against musl libc, since
> they do not use NSS.
Note that this is generally broken and cannot be supported, regardless of the
DNS resolver. These binaries could also not resolve winbind host names, YP,
LDAP, A
Carlos Garnacho [2017-03-01 10:59 -]:
> > - Is it acceptable to have approximate search results if the indexing isn't
> > (yet) up to date?
>
> If tracker-miner-fs is not paused/throttled down, it will pick up
> changes in monitored folders just as fast as any other app, there is
> very littl
> To summarize, I see 2 performance questions:
I'd add:
- Is it acceptable to have approximate search results if the indexing isn't
(yet) up to date?
- Does it significantly affect battery life?
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
Hello Carlos,
Carlos [2017-02-28 13:58 -]:
> Just wanted to mention I disagree with your statements and that I have
> the opposite experience and feedback from users (we agree we disagree,
> which is fine of course :)).
Yep :-) (I'm not making the call anyway). Thanks for sharing your
perspec
Carlos [2017-02-28 12:08 -]:
> "Tracker imposes a huge cost due to always indexing everything"
> As long as is low priority and the kernel scheduler works fine it shouldn't
> be an issue.
This isn't true. This will use a lot more CPU and disk cycles, thus decreasing
battery life. Or, if you d
So all of this tells me that tracker isn't a replacement for typeahead
search. They have two entirely different use cases:
* Typeahead search only affects the currently displayed directory (or
should anyway -- you search through what you see, not through the
entirety of the file system). It is fa
Yes, there, see "man resolved.conf". But I'd recommend a separate file
to avoid changing the package-provided conffile:
sudo mkdir -p /etc/systemd/resolved.conf.d
printf "[Resolve]\nDNSSEC=no\n" | sudo tee
/etc/systemd/resolved.conf.d/no-dnssec.conf
--
You received this bug notification because
Note: We keep DNSSEC=allow-downgrade during development to collect
feedback, but switch it off for stable releases (we did so in yakkety
and should do so again in zesty). So if you have some trouble which is
DNSSEC related, it would be good to get a debug output of resolved while
it's failing to re
Fixed upstream:
https://github.com/systemd/systemd/commit/e8d23f92b50a97bb3
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.l
Till Kamppeter [2016-12-19 16:48 -]:
> Then edit the file /lib/systemd/system/cups.path adding a line
> "PartOf=cups.service" to the [Unit] section, so that the file looks like
> this:
>
> --
> [Unit]
> Description=CUPS Scheduler
> PartOf=cups.service
I suppose that cups.path is only
Ah, so you didn't have resolvconf installed (and therefore also not
ubuntu-minimal), that's a good data point, thank you! This should be
part of this bug -- NM should get along with this better.
Do you see the search domain in "systemd-resolve --status"?
--
You received this bug notification bec
What does "systemctl status resolvconf" say? is it not running for you?
--
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/1647133
Title:
dns=dnsmasq does not work any more
Statu
** Tags added: resolved
--
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/1647133
Title:
dns=dnsmasq does not work any more
Status in network-manager package in Ubuntu:
Triage
> # Generated by NetworkManager
> nameserver 127.0.1.1
OK, that's definitively unexpected. It looks like NM is still using a
different plugin for managing /etc/resolv.conf and that thinks it's
using the dnsmasq plugin (127.0.1.1) while not actually starting
dnsmasq. That part is understood and wha
OK, thanks. I'm afraid I need the NM log and /etc/resolv.conf with NM
1.4.2-2ubuntu4 without "dns=dnsmasq".
--
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/1647133
Title:
dns=d
> dns=dnsmasq
Ah -- please remove that from /etc/NetworkManager/NetworkManager.conf,
this is not currently working (this is known, this needs to be fixed in
a better way).
** Summary changed:
- Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)
+ dns=dnsmasq does not work any more
Can you please attach your /etc/NetworkManager/NetworkManager.conf ? NM
is not supposed to create /etc/resolv.conf any more, so I suppose
something else is going on. Can you please reproduce the failed state
and then do
cat /etc/resolv.conf
and copy&paste the output, and run
journalctl -u Ne
> In CUPS everything is OK and as intended.
No -- as above, the maintainer scripts need to stop cups.{socket,path}
first before stopping cups.service. Also, as it seems you can entirely
drop that .path unit as it's fairly useless -- we don't start cups on
demand, but it always starts on boot (in a
Till's log shows that cups.path triggers after cups got stopped:
Dec 02 10:59:15 till-x1carbon systemd[1]: cups.path: Got notified about unit
deactivation.
Dec 02 10:59:15 till-x1carbon systemd[1]: cups.path: Changed running -> waiting
Dec 02 10:59:15 till-x1carbon systemd[1]: cups.socket: Change
Hello Harry,
Harry [2016-12-03 15:02 -]:
> Please note, that in my setup, the network is lost immediately after
> rebooting with the new network-manager (1.4.2-2ubuntu4).
Thanks for filing bug 1647133, tracking that issue there.
--
You received this bug notification because you are a member
> Requires=cups.service in /lib/systemd/system/cups-browsed.service the
shutdown of CUPS should shutdown cups-browsed first.
No -- Requires/Wants start/stop other units, but they *do not imply
ordering*. If you need to order services against each other you must
additionally specify Before/After=.
> Interestingly, "cups.service: Start request repeated too quickly."
appears on a successful run.
This would usually happen if you try things in a loop, (5 or more
restarts in 10s); run "systemctl reset-failed " in between to
reset the counter.
The journal shows an obvious loop, and at that point
I tried this on zesty, and in comment #20 Robie tried on xenial, and we
both get:
> Warning: Stopping cups.service, but it can still be activated by:
> cups.path
(I additionally get cups.socket there too). Thus:
> However, in the real world failure case, cups.path is stopped before
> cups.servi
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 failed to install/upgrade: triggers loopi
I didn't reproduce this yet, answering Till's questions first.
> Does systemd care about keepalive files?
No, there is no such concept. You can certainly build such a thing using
path units and others, but no Linux init system kills processes willy-
nilly from the outside (except on shutdown, of
FTR:
-r 1 root root 0 Feb 11 2015 /var/cache/cups/org.cups.cupsd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to instal
Sorry, wrong commit:
https://cgit.freedesktop.org/udisks/commit/?id=f641062
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1585382
Title:
test_internal_fs_allowed crashes with SIGABRT
Silly me! Should be fixed with
https://cgit.freedesktop.org/udisks/commit/?id=054d9c4201f
** Changed in: udisks2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
http
http://autopkgtest.ubuntu.com/packages/udisks2/zesty/i386 now has two
failures with core dumps. I extracted the stack trace from the topmost
one.
This one is interesting:
f = Frame 0xb662ccec, for file src/tests/test_polkitd.py, line
184, in spawn (allowed_actions=['org.freedesktop.udisks
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1645631
Title:
Sending files fails because obex not loaded
Status in bluez package in Ub
https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local-
resolver has the two outstanding issues to switch NM over to resolved
too. These are unblocked now: the new resolved DNS plugin is in upstream
master since around September, and NM 1.4 landed in zesty-proposed
yesterday. Let's land
** Changed in: network-manager (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
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/1615044
Title:
"unmanaged
> Curiously I do not see this when running the tests on my laptop
And of course in the minute I write this it does happen again (I ran the
test maybe 20 times today, and only just now it happened):
[11359.569157] INFO: task systemd-udevd:341 blocked for more than 120 seconds.
[11359.569163]
I also see this with exfat, so it rather seems to be related to fuse (as
both ntfs-3g and exfat use fuse). Curiously I do not see this when
running the tests on my laptop or on the Scalingstack cloud infra, just
when I run them in QEMU.
--
You received this bug notification because you are a memb
I ran it five times on the production infrastructure and it does not
reproduce there either, so a nasty heisenbug :-(
I instead changed the test to archive a core dump if the test crashes,
so that this can be debugged post-mortem:
https://anonscm.debian.org/cgit/pkg-
utopia/udisks2.git/commit/?id=
This does not reproduce locally or with autopkgtest-virt-qemu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1585382
Title:
test_internal_fs_allowed crashes with SIGABRT
Status in u
** Changed in: udisks2 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1585382
Title:
test_internal_fs_allowed crashes with SIGABRT
Stat
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Will, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help us
Hello Kyle, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help us
https://cgit.freedesktop.org/udisks/commit/?id=e168e59f
https://cgit.freedesktop.org/udisks/commit/?id=554daa4b
I tried this with an USB stick; I do get the wipefs failure pretty
consistently, and with this creating the partition and FS seems to work
reliably. I think we ought to SRU this into xen
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1460602
Title:
Erasing disk failed: Error wiping newly created partition
snapd-glib accepted into xenial. Please upload the corresponding gnome-
software SRU.
** Changed in: snapd-glib (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubu
** Changed in: lightdm (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1637758
Title:
lightdm greeter session not properly shut dow
** Changed in: pulseaudio (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1574324
Title:
pulseaudio crashes when connecting to bl
The verification of the Stable Release Update for pulseaudio 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 encounte
Comment #123 provided verification in yakkety.
** Tags removed: verification-done-xenial verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.ne
The verification of the Stable Release Update for pulseaudio 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 encounte
The version of duplicity in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Desktop
Pac
The version of duplicity in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Desktop
Pac
The version of duplicity in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: duplicity (Ubuntu Trusty)
Status: Fix Committed => Won't
I don't see anythign left to sponsor here, so unsubscribing sponsors
now. Please re-subscribe when you upload further patches.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/
Sponsored the xenial update, unsubscribing sponsors now. Thanks!
** Also affects: im-config (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.lau
The verification of the Stable Release Update for ubiquity 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
unity8 tests have always been brittle; the autopilot ones (which use X)
succeeded, while the QML ones (which don't use X) didn't, so this
appears unrelated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bu
The verification of the Stable Release Update for xorg-server 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 encount
I changed the overrides of all the gir* packages in zesty, so that the
archive now has the correct ones. The sources should still be updated to
follow suit at some point, though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsignon-g
> I'm a bit confused. I thought that the section information was stored
in debian/control, but I see that while I have had (since 2014)
"Section: introspection" in libaccounts-glib's debian/control [1], "apt-
cache show" claims that the section is "libs".
No, you don't. debian/control says
Packag
1 - 100 of 3912 matches
Mail list logo
