[Bug 1466150] Re: grub-install breaks when ESP is on raid
Corresponding bug report on Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765740 This Ubuntu support for multiple ESPs has not been upstreamed to Debian Bullseye. Is someone working on upstreaming to Debian? I hope so! ** Bug watch added: Debian Bug tracker #765740 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765740 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600060] Re: ZFS "partially filled holes lose birth time"
17.04 has ZFS 0.6.5.7 that works around this bug using /sys/module/zfs/parameters/ignore_hole_birth tunable. Will a backport of this bugfix to 16.04 LTS be forthcoming? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600060 Title: ZFS "partially filled holes lose birth time" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1600060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703440] [NEW] xenial fio 2.2.10 randwrite: "random" data NOT random, highly compressible -> highly misleading output
Public bug reported: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 Package: fio (2.2.10-1ubuntu1) [universe] I've been using fio to look at the effect of zfs recordsize on random writes to a zfs dataset. After wasting the better part of a day trying to understand fio's unrealistically high reported bandwidth I finally used hexcurse to have a look at one of the files that fio allocated before doing its randwrite benchmark. I discovered that chunks that were supposed to be random data were in fact highly non-random; each "random" chunk was identical (or nearly so) to the previous "random" chunk. In case the zfs dataset uses compression (lz4 is on by default) the data end up being highly compressed before writing to disk, severely distorting the reported benchmark results. For example, for this fio command: fio \ --name=random-writers \ --ioengine=sync \ --direct=0 \ --rw=randwrite \ --bs=512k \ --refill_buffers \ --scramble_buffers=0 \ --buffer_compress_percentage=50 \ --buffer_compress_chunk=512 \ --size=2g \ --time_based \ --runtime=20 \ --randrepeat=0 \ --norandommap \ --random_generator=lfsr \ --numjobs=8 \ --group_reporting xenial's fio 2.2.10 reported an aggregate bandwidth of 3315 MB/s (for an SATA 3.1 SSD) due to the highly compressible data: # zfs get written,logicalused,compressratio tank/test NAME PROPERTY VALUESOURCE tank/test written2.03G- tank/test logicalused16.0G- tank/test compressratio 7.94x- Not all of the above fio parameters (in particular, --random_generator) are required in order to see the problem; this was the final command I wound up with trying to fix the non-random "random" data. I finally gave up and compiled fio 2.21 from source: https://github.com/axboe/fio/releases Running the exact same command on the same zfs dataset on the same hardware, fio 2.21 reports a believable aggregate bandwidth of 808 MiB/s (848 MB/s) and zfs reports compressratio 1.59x, in line with what I'd expect for data that is "50% random" as requested by the fio command. Using hexcurse to look at a file fio generated before starting the benchmark, the "random" file chunks now appear truly random; there is no longer any obvious pattern repeated among successive "random" chunks. So this fio bug has been fixed upstream somewhere between 2.2.11 - 2.21. Short changelogs are available from: http://brick.kernel.dk/snaps/ I was unable to determine when exactly the bug was fixed. But wanted to issue a public service announcement: DO NOT rely on Xenial's fio 2.2.10 to use truly random data. Until a more recent fio is available for Xenial, in repo or as PPA, I recommend compiling fio from source. The bug reported here is fixed in fio 2.21 (and probably some earlier versions). ** Affects: fio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703440 Title: xenial fio 2.2.10 randwrite: "random" data NOT random, highly compressible -> highly misleading output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fio/+bug/1703440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534884] Re: /etc/pam.d/kimchi permission broken
I had much better luck with the upstream packages: http://kimchi-project.github.io/kimchi/downloads/ Newer version with more features, works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534884 Title: /etc/pam.d/kimchi permission broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kimchi/+bug/1534884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534884] Re: /etc/pam.d/kimchi permission broken
Bit me today. OP correctly notes that group name is incorrect for Ubuntu. Attaching a patch that implements his fix, which works for me. ** Attachment added: "kimchi_pam_patch" https://bugs.launchpad.net/ubuntu/+source/kimchi/+bug/1534884/+attachment/4638205/+files/kimchi_pam_patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534884 Title: /etc/pam.d/kimchi permission broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kimchi/+bug/1534884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534882] Re: systemd service file dependancy is broken
This bit me yesterday. OP's fix works. Surprised that 3 months later this bug hasn't been fixed -- is this package even maintained? In case it helps, I'm attaching a patch that does the same thing as OP's workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534882 Title: systemd service file dependancy is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kimchi/+bug/1534882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534882] Re: systemd service file dependancy is broken
** Attachment added: "kimchi service patch" https://bugs.launchpad.net/ubuntu/+source/kimchi/+bug/1534882/+attachment/4638204/+files/kimchi_service_patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534882 Title: systemd service file dependancy is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kimchi/+bug/1534882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 886734] Re: [Kubuntu 11.10] LibreOffice icons are missing from taskbar
Same problem on my AMD64 machines after upgrading to Oneiric. FWIW, the OP noted that this appears to be a Kubuntu-specific bug, not a bug in Plasma: https://bugs.kde.org/show_bug.cgi?id=284015 ** Bug watch added: KDE Bug Tracking System #284015 http://bugs.kde.org/show_bug.cgi?id=284015 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/886734 Title: [Kubuntu 11.10] LibreOffice icons are missing from taskbar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/886734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)
Marc, thank you so much for pointing to loop-aes-utils as the culprit. I can confirm that after removing the loop-aes-utils package from my Maverick AMD64 system, and re-installing the latest libfuse and fuse- utils updates, I can mount sshfs and TrueCrypt volumes. @Søren Weber: losetup -a will show you the loop devices set up on your system. For example: # losetup -a /dev/loop5: [000e]:14986 (/dev/md1) offset=4096 encryption=AES128 multi-key-v3 /dev/loop7: [000e]:14954 (/dev/md0) offset=4096 encryption=AES128 multi-key-v3 shows 2 loop-aes devices in use. You can tell they are are loop-aes devices because of the encryption=AES128 string. In case you see such devices, you need to keep loop-aes-utils. As a counter-example, on my system using 1 TrueCrypt volume and no loop-aes devices: # losetup -a /dev/loop0: [0902]:20 (/mnt/sdc1/encrypted.tc) Much more info about loop-aes is available in the README files at http://loop-aes.sourceforge.net/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727220 Title: Command fuse returned error 1 (with TrueCrypt) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)
Marc, thank you for looking into this. I'm using Maverick, not Lucid, but do have loop-aes-utils package installed. I've stopped using loop-aes, though, so could try removing loop-aes-utils if that helps to troubleshoot. As far as setting up TrueCrypt, I just followed instructions at http://www.truecrypt.org/docs/ (click on Beginner's Tutorial). As I noted earlier, this bug also prevents me from mounting sshfs volumes, maybe that would be easier for you to test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727220 Title: Command fuse returned error 1 (with TrueCrypt) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656279] Re: NVRM: os_raise_smp_barrier(), invalid context!
I'm pleased to report that since upgrading from nvidia-current (270.18-0ubuntu1~maverick~xup1) to 270.29-0ubuntu1~maverick~xup2 the pesky NVRM: os_raise_smp_barrier(), invalid context! no longer appear in my system log. @Ivan Kravchenko: I also experienced the error messages with the 260.19.06 driver. You can get the latest stable nvidia driver from the Ubuntu-X team, add the PPA from: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656279 Title: NVRM: os_raise_smp_barrier(), invalid context! -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)
Just built a new custom 2.6.37.2 kernel with CONFIG_FUSE_FS=y rather than CONFIG_FUSE_FS=m as I'd been using. It didn't make a difference whether FUSE is compiled into the kernel or as a module. # apt-cache showpkg libfuse2 Package: libfuse2 Versions: 2.8.4-1ubuntu1.3 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick-updates_main_binary-amd64_Packages) (/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_maverick-security_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick-updates_main_binary-amd64_Packages MD5: 5d223263b75b2a98a7218dd5a0a8aaa7 2.8.4-1ubuntu1 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick_main_binary-amd64_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick_main_binary-amd64_Packages MD5: 5d223263b75b2a98a7218dd5a0a8aaa7 The latest 2.8.4-1ubuntu1.3 package fails in both cases, while the older 2.8.4-1ubuntu1 package works in both. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727220 Title: Command fuse returned error 1 (with TrueCrypt) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727220] Re: Command fuse returned error 1 (with TrueCrypt)
Same problem after updating fuse-utils (2.8.4-1ubuntu1.2) to 2.8.4-1ubuntu1.3 libfuse2 (2.8.4-1ubuntu1.2) to 2.8.4-1ubuntu1.3 yesterday. Maverick AMD64 with custom kernel, fuse built as module. The bug affects sshfs as well as TrueCrypt: trying to mount ssh filesystem gave error: fusermount: failed to access mountpoint [mount_point]: Transport endpoint is not connected Reverting libfuse2 and fuse-utils solved the problem: apt-get install libfuse2=2.8.4-1ubuntu1 fuse-utils=2.8.4-1ubuntu1 Thanks to the above posters for saving me time working around this crippling bug (I rely on sshfs and TrueCrypt). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727220 Title: Command fuse returned error 1 (with TrueCrypt) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656279] Re: NVRM: os_raise_smp_barrier(), invalid context!
I can confirm Øyvind Stegard's report above: Since upgrading my Maverick AMD64 G210 system yesterday from nvidia-current (260.19.29-0ubuntu1~xup~maverick3) to 270.18-0ubuntu1~maverick~xup1 my log file is full of the NVRM: os_raise_smp_barrier(), invalid context! messages. I haven't noticed any other ill effects, and in particular my system still suspends to and resumes from RAM without problems. But the log full of error messages is irritating and somewhat worrisome. I originally started using the Ubuntu-X packages to get rid of such errors that the Maverick Nvidia package caused. I wonder why the Ubuntu-X community decided to package this *beta* 270.18 release rather than the current stable 260.19.36? This decision seems to violate the stated purpose of Ubuntu-X: https://launchpad.net/~ubuntu-x-swat/+archive/x-update This PPA is for stable upstream releases of X.org components. If you're looking for something even more bleeding-edge, please see the xorg-edgers PPA. IOW, it would seem that 270.18 should have gone to xorg-edgers, and Ubuntu-X should have gone to 260.19.36 (or simply remained at the previously-released 260.19.29). I guess there's a reason I'm unaware of that Ubuntu-X went straight to the beta 270.18. But it would be nice if they could somehow indicate that it is a *beta* release so that we end- users would be more cautious than usual about upgrading. Could the release be called something like 270.18-0beta-ubuntu1~maverick~xup1? It would also be nice if Ubuntu-X could keep 2 versions of released drivers: the current one, and the previous one. That would help people roll back in case of problems like the above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656279 Title: NVRM: os_raise_smp_barrier(), invalid context! -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214891] Re: nedit: segfault on copy
Same problem here. Running nedit on AMD64 Hardy, forwarded through ssh to i386 Gutsy xserver. Ctrl+c segfaults 100% of time. -- nedit: segfault on copy https://bugs.launchpad.net/bugs/214891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75423] Re: pcmciautils should include driver firmware from pcmcia-cs
I have a hard time understanding why this bug is still New/Undecided more than a year after it was reported, and with a working solution supplied by the reporter. I was bitten by the same bug today when I inserted a SOHOware ND5120 NE2K pcmcia card only to be greeted with error loading '/lib/firmware/NE2K.cis' for deice '/class/firmware/0.0' with driver '(unknown)' Thanks to Daniel Brownless, I installed the deprecated pcmcia-cs package and copied /etc/pcmcia/cis/NE2K.dat to /lib/firmware/NE2K.cis then purged pcmcia-cs, and voila, the card works with pcmciautils. I suggest that the pcmciautils maintainer simply copy the contents of pcmcia-cs /etc/pcmcia/cis/ to /lib/firmware/ (changing the file extensions from *.dat to *.cis) and include it in the pcmciautils package. Maybe that's a hack, but it's certainly better than the current situation where some cards fail to work, that has persisted for over a year. I'm changing the status of this bug to Confirmed to hopefully get some attention. ** Changed in: pcmciautils (Ubuntu) Status: New = Confirmed -- pcmciautils should include driver firmware from pcmcia-cs https://bugs.launchpad.net/bugs/75423 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 196292] [NEW] knetworkconf fails to find non-generically-named network interfaces
Public bug reported:
Binary package hint: knetworkconf
% cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION=Ubuntu 7.10
Package: knetworkconf
Section: kde
Maintainer: Ubuntu Core Developers [EMAIL PROTECTED]
Architecture: i386
Source: kdeadmin
Version: 4:3.5.8-0ubuntu1
If I name my LAN interface the way I want by putting the following line in
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM==net, DRIVERS==?*, ATTRS{address}==00:10:4b:e3:23:ef, NAME=lan
and have the following in /etc/network/interfaces:
auto lo lan
iface lan inet static
address 10.0.0.17
netmask 255.255.255.128
network 10.0.0.0
broadcast 10.0.0.127
gateway 10.0.0.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.0.0.1
then ifup and ifdown work perfectly but KNetworkConf can't even find the
lan interface.
If I keep exactly the same configuration, except change the name lan
to eth0, KNetworkConf works.
** Affects: knetworkconf (Ubuntu)
Importance: Undecided
Status: New
--
knetworkconf fails to find non-generically-named network interfaces
https://bugs.launchpad.net/bugs/196292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192302] Re: pm-utils hooks run twice on suspend resume
Um, the above patch is for the file: /usr/lib/pm-utils/functions Sorry about stripping off the leading path. -- pm-utils hooks run twice on suspend resume https://bugs.launchpad.net/bugs/192302 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192302] [NEW] pm-utils hooks run twice on suspend resume
Public bug reported:
Binary package hint: pm-utils
pm-utils 0.99.2-3ubuntu1 (hardy)
Copy any of the scripts from
/usr/lib/pm-utils/sleep.d
to
/etc/pm/sleep.d
The script in /etc/pm/sleep.d is then supposed to replace the one with the same
name in /usr/lib/pm-utils/sleep.d
Well, it does replace it... twice! Look at /var/log/pm-suspend.log after a
suspend-to-ram/resume cycle.
Crude fix:
--- functions.hardy.0.99.2-3ubuntu1 2008-01-15 18:50:51.0 -0500
+++ functions 2008-02-15 23:26:06.0 -0500
@@ -87,16 +96,24 @@
if [ $2 = reverse ]; then
filea=($files)
filen=${#filea[*]}
+ last_file=
while [ $filen -gt 0 ]; do
let filen--
file=${filea[$filen]}
- echo = $(date): running hook: $file =
- $file $1
+ if [ $file != $last_file ]; then
+ echo = $(date): running hook: $file =
+ $file $1
+ fi
+ last_file=$file
done
else
+ last_file=
for file in $files ; do
- echo = $(date): running hook: $file =
- $file $1
+ if [ $file != $last_file ]; then
+ echo = $(date): running hook: $file =
+ $file $1
+ fi
+ last_file=$file
done
fi
Upstream now compiles the list of scripts to run using a different
method that includes | uniq, that probably fixes the problem too.
** Affects: pm-utils (Ubuntu)
Importance: Undecided
Status: New
--
pm-utils hooks run twice on suspend resume
https://bugs.launchpad.net/bugs/192302
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192302] Re: pm-utils hooks run twice on suspend resume
Sorry about the ugly patch above, maybe it'll be prettier as attached below. ** Attachment added: The crude but prettier (?) patch http://launchpadlibrarian.net/12033814/mypatch.txt -- pm-utils hooks run twice on suspend resume https://bugs.launchpad.net/bugs/192302 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88595] Re: [apport] vserver-info crashed with SIGSEGV
For anyone else struggling with this bug, the following works like a charm in feisty/i386: 1) purge the feisty util-vserver package (and probably vserver- debiantools package, I don't use it) 2) download the debian stable package from http://packages.debian.org/stable/net/util-vserver 3) install the debian stable util-vserver package, which I think is built/linked against an earlier gcc: dpkg -i util-vserver_0.30.212-1_i386.deb 4) get on with your life I know this package is in universe which is unsupported. But this bug has been open for several months now with no resolution, and has caused me (and I know others) wasted hours. Can't someone simply put debian's util-vserver into the ubuntu universe repository until the problem with gcc 4.1 can be worked out? More on gcc 4.1 problem: http://irc.13thfloor.at/LOG/2006-11/LOG_2006-11-29.txt There are 6 other open bugs on util-vserver that I think are caused by the same problem: https://launchpad.net/ubuntu/+source/util-vserver/+bugs -- [apport] vserver-info crashed with SIGSEGV https://bugs.launchpad.net/bugs/88595 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
