Re: [Bug 370261] Re: nvram-wakeup buffer overflow detected
hi, add it to CFLAGS variable in Makefile: CFLAGS = -O2 -Wall -Wstrict-prototypes -g -pedantic $(DEFS) -D_FORTIFY_SOURCE=0 -fno-stack-protector jn On Thursday 14 of May 2009 17:35:35 raulelmagico wrote: > servus albert, > > I need some help with your workaround: > > "temporary workaround: compile with -D_FORTIFY_SOURCE=0 -fno-stack- > protector" > > I don´t know how to apply that! I guess I have to add this line somewhere > in the Makefile, but I dont know how! Im new in the Ubuntu universe, so I > would be very happy about some assistance of yours. > > thx! -- nvram-wakeup buffer overflow detected https://bugs.launchpad.net/bugs/370261 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 370261] [NEW] nvram-wakeup buffer overflow detected
Public bug reported: Binary package hint: nvram-wakeup nvram-wakeup 0.97-14lenny1 triggers buffer overflow protection (fortify?): /usr/sbin/nvram-wakeup -A -C /etc/nvram-wakeup.conf --settime 1241154840 *** buffer overflow detected ***: /usr/sbin/nvram-wakeup terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7f24da8] /lib/tls/i686/cmov/libc.so.6[0xb7f22eb0] /lib/tls/i686/cmov/libc.so.6[0xb7f225a8] /lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0xc8)[0xb7e94bb8] /lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0x6f3)[0xb7e66f23] /lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xa4)[0xb7f22654] /lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xb7f2259d] /usr/sbin/nvram-wakeup[0x80522b9] /usr/sbin/nvram-wakeup[0x80499ab] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7e3d775] /usr/sbin/nvram-wakeup[0x8048d71] === Memory map: 08048000-0805f000 r-xp 08:02 783832 /usr/sbin/nvram-wakeup 0805f000-0806 r--p 00016000 08:02 783832 /usr/sbin/nvram-wakeup 0806-08061000 rw-p 00017000 08:02 783832 /usr/sbin/nvram-wakeup 08966000-08987000 rw-p 08966000 00:00 0 [heap] b7e17000-b7e24000 r-xp 08:02 589901 /lib/libgcc_s.so.1 b7e24000-b7e25000 r--p c000 08:02 589901 /lib/libgcc_s.so.1 b7e25000-b7e26000 rw-p d000 08:02 589901 /lib/libgcc_s.so.1 b7e26000-b7e27000 rw-p b7e26000 00:00 0 b7e27000-b7f83000 r-xp 08:02 598956 /lib/tls/i686/cmov/libc-2.9.so b7f83000-b7f84000 ---p 0015c000 08:02 598956 /lib/tls/i686/cmov/libc-2.9.so b7f84000-b7f86000 r--p 0015c000 08:02 598956 /lib/tls/i686/cmov/libc-2.9.so b7f86000-b7f87000 rw-p 0015e000 08:02 598956 /lib/tls/i686/cmov/libc-2.9.so b7f87000-b7f8a000 rw-p b7f87000 00:00 0 b7f9d000-b7f9f000 rw-p b7f9d000 00:00 0 b7f9f000-b7fa r-xp b7f9f000 00:00 0 [vdso] b7fa-b7fbc000 r-xp 08:02 589858 /lib/ld-2.9.so b7fbc000-b7fbd000 r--p 0001b000 08:02 589858 /lib/ld-2.9.so b7fbd000-b7fbe000 rw-p 0001c000 08:02 589858 /lib/ld-2.9.so bfca9000-bfcbe000 rw-p bffeb000 00:00 0 [stack] Aborted temporary workaround: compile with -D_FORTIFY_SOURCE=0 -fno-stack- protector ** Affects: nvram-wakeup (Ubuntu) Importance: Undecided Status: New ** Tags: nvram-wakeup ** Tags removed: overflow -- nvram-wakeup buffer overflow detected https://bugs.launchpad.net/bugs/370261 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
Re: [Bug 370261] Re: nvram-wakeup buffer overflow detected
you are right, but after disabling fortify, you get "stack smashing detected" error , so it's necessary to disable stack protector too to get working binary. and ofcourse it's not a fix, it's just temporary workaround... *** stack smashing detected ***: ./nvram-wakeup terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb8047da8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb8047d60] ./nvram-wakeup[0x8052d0e] ./nvram-wakeup[0x8049927] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7f60775] ./nvram-wakeup[0x8048cd1] === Memory map: -- nvram-wakeup buffer overflow detected https://bugs.launchpad.net/bugs/370261 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 263139] Re: usb device invisible until lsusb command issued
it DOES work Intrepid Ibex (tested on kubuntu-8.10-beta- desktop-i386.iso) -- usb device invisible until lsusb command issued https://bugs.launchpad.net/bugs/263139 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 263139] Re: usb device invisible until lsusb command issued
it DOES work in Intrepid (tested on kubuntu-8.10-beta-desktop-i386.iso ) -- usb device invisible until lsusb command issued https://bugs.launchpad.net/bugs/263139 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 263139] Re: usb device invisible until lsusb command issued
this problem occurs every time in hardy (just after boot) on my system. But it used to work, I suspect 2.6.24.19.21 -> 2.6.24.21.23 kernel upgrade but I cannot reboot now to verify it.. ;) -- usb device invisible until lsusb command issued https://bugs.launchpad.net/bugs/263139 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 263139] Re: usb device invisible until lsusb command issued
confirmed, there is no problem with kernel 2.6.24.19.21, only with 2.6.24.21.23 -- usb device invisible until lsusb command issued https://bugs.launchpad.net/bugs/263139 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 263139] Re: usb device invisible until lsusb command issued
I have 4 port "Genesys Logic, Inc. USB-2.0 4-Port HUB", my usb devices are not detected (repeat: everytime, right after boot) when connected to hub on 2.6.24.21.23 kernel until I issue lsub. Everything works OK with 2.6.24.19.21.. my problem is NOT solved, since it DOES NOT work with latest Hardy stable kernel Andre, can you please test 2.6.24.19.21 kernel ? -- usb device invisible until lsusb command issued https://bugs.launchpad.net/bugs/263139 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 130437] Re: udev rule can fail to run ifdown, break reinserting device
the same problem with bluetooth PAN, after client disconecting, bnep0 net remove event reaches 85-ifupdown.rules without DRIVER set. fixed with: SUBSYSTEM=="net", KERNEL=="bnep?*", GOTO="net_start" SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start" GOTO="net_end" ... ... -- udev rule can fail to run ifdown, break reinserting device https://bugs.launchpad.net/bugs/130437 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 544345] Re: lucid beta 1 won't install with virtio driver on karmic host
I cannot even finish install. ext4 (ext2,ext3,xfs) on root is successfully created but is not mounted: [ 186.631794] JBD: no valid journal superblock found [ 186.631803] EXT4-fs (sda1): error loading journal [ 207.258841] JBD: no valid journal superblock found [ 207.258850] EXT4-fs (sda1): error loading journal fsck reports: fsck 1.41.10 (10-Feb-2009) Superblock has an invalid journal (inode 8). -- lucid beta 1 won't install with virtio driver on karmic host https://bugs.launchpad.net/bugs/544345 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 1876438] [NEW] INSTALLER: zfs experimental install is allowed even when not selected "install proprietary drivers"
Public bug reported: installation (xubuntu 20.04) fails if "install proprietary drivers" is disabled and "ZFS experimental" is enabled... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Sat May 2 12:20:12 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Assignee: a1bert (a1bert) Status: Invalid ** Tags: amd64 apport-bug focal ubiquity-20.04.15 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876438 Title: INSTALLER: zfs experimental install is allowed even when not selected "install proprietary drivers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876438] Re: INSTALLER: zfs experimental install is allowed even when not selected "install proprietary drivers"
invalid, probably caused by ZFS artefacts on target disc after intrrupted previos instalation ** Changed in: ubiquity (Ubuntu) Status: New => Invalid ** Changed in: ubiquity (Ubuntu) Assignee: (unassigned) => a1bert (a1bert) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876438 Title: INSTALLER: zfs experimental install is allowed even when not selected "install proprietary drivers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
today's unattended upgrade killed a lot of our hosts running xenial + upstart, please mark as critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520575] Re: casper-sn persistence fails in 14.04.3, 15.10
use casper-snapshot -c /cow/upper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520575 Title: casper-sn persistence fails in 14.04.3, 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1520575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520575] Re: casper-sn persistence fails in 14.04.3, 15.10
** Tags added: casper ** Tags added: persistent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520575 Title: casper-sn persistence fails in 14.04.3, 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1520575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520575] Re: casper-sn persistence fails in 14.04.3, 15.10
the same here, the new version of casper is not working properly:
there is not only problem with assembling root FS as reported above, but
I am also not able to boot with persistent boot cmd:
reproduce:
-syslinuxed vfat USB stick: /casper/filesystem.squashfs,initrd.gz,vmlinuz
-persistent keyword on cmdline
-boot ends up in busybox
without "persistent" keyword, system boots ok
CAUSE:
initramfs-tools/scripts/casper: find_cow_device() called from
setup_unionfs("/cdrom/casper","/root"), unmounts previously mounted
/cdrom during scanning for casper-rw; /cdrom/casper/filesystem.squashfs
is then not accessible for mount ...
** Patch added: "dirty fix"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1520575/+attachment/4588796/+files/casper-persistent-boot.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520575
Title:
casper-sn persistence fails in 14.04.3, 15.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1520575/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387010] [NEW] rdesktop radeon (ati_drv) high cpu usage
Public bug reported: when using opensource radeon driver on Radeon HD 8400, certain operation in rdesktop like scrolling "eats" whole cpu power. using -b switch (force bitmap updates) helps tested on 14.04 trusty, 14.10 utopic no such issue with fglrx ** Affects: rdesktop (Ubuntu) Importance: Undecided Status: New ** Tags: cpu rdesktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387010 Title: rdesktop radeon (ati_drv) high cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/1387010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866458] [NEW] drbd not working after kernel upgrade 5.0.x -> 5.3.x
Public bug reported: I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3) /sbin/drbdadm -v up amail drbdsetup-84 new-resource amail amail: Invalid argument Command 'drbdsetup-84 new-resource amail' terminated with exit code 20 drbdadm: new-minor amail: skipped due to earlier error it maybe this issue: https://www.mail-archive.com/openembedded- de...@lists.openembedded.org/msg64900.html but not tested by me ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: drbd-utils 8.9.10-2 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Sat Mar 7 13:39:39 2020 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libstdc++6 8.3.0-6ubuntu1~18.04.1 lsb-base 9.20170808ubuntu1 InstallationDate: Installed on 2019-10-22 (136 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: drbd-utils UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 ** Affects: drbd-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866458 Title: drbd not working after kernel upgrade 5.0.x -> 5.3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866458] Re: drbd not working after kernel upgrade 5.0.x -> 5.3.x
drbd-utils_9.5.0-1_amd64.deb does not work either.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866458 Title: drbd not working after kernel upgrade 5.0.x -> 5.3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1866458] Re: drbd not working after kernel upgrade 5.0.x -> 5.3.x
Hello, I can confirm it is working... great work thanks jn On 10. 03. 20 1:24, Rafael David Tinoco wrote: > @a1bert: please check PPA and if the fix solves your initial issue if > you can. I'm pretty confident it will as the testcase is simple and I > was able to verify on my side... anyway =). I'll wait launchpad to fix > this small issue to push the merge review into ubuntu-server upload > queue so a colleague can review it before I upload the SRU. > > Will get back to this soon... > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866458 Title: drbd not working after kernel upgrade 5.0.x -> 5.3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950450] [NEW] casper: showmounts show-cow boot parameters do not work (casper-snapshot)
Public bug reported:
lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
(custom debootstrap created filesystem.squashfs)
apt-cache policy casper
casper:
Installed: 1.445
Candidate: 1.445
Version table:
*** 1.445 100
100 /var/lib/dpkg/status
casper-snapshot is not working because /cow is not exposed when using
showmounts|show-cow boot parameters
there is no /cow directory on rootmnt when trying to move /cow:
# move /cow such that live-system can poke & debug the overlayfs layers
mount -o move /cow "${rootmnt}/cow"
error in casper.log:
mount: mounting /cow on /root/cow failed: No such file or directory
casper-snapshot:
Error: /cow is not a directory
FIX: create ${rootmnt}/cow dir before moving:
# move /cow such that live-system can poke & debug the overlayfs layers
mkdir -p "${rootmnt}/cow"
mount -o move /cow "${rootmnt}/cow"
** Affects: casper (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/1950450
Title:
casper: showmounts show-cow boot parameters do not work (casper-
snapshot)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1950450/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950450] Re: casper: showmounts show-cow boot parameters do not work (casper-snapshot)
** Tags added: casper ** Tags added: casper-snapshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950450 Title: casper: showmounts show-cow boot parameters do not work (casper- snapshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1950450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950469] [NEW] casper: zcat missing in busybox
Public bug reported: lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 (custom debootstrap created filesystem.squashfs) apt-cache policy casper casper: Installed: 1.445 Candidate: 1.445 Version table: *** 1.445 100 100 /var/lib/dpkg/status casper-snapshot restoration during boot is not working because casper is trying to use zcat but zcat is not available (not compiled in busybox) error in casper.log: /init: line 376: zcat: not found FIX: use gzip -dc ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Tags: casper casper-snapshot ** Patch added: "replace zcat with gzip -dc" https://bugs.launchpad.net/bugs/1950469/+attachment/5539574/+files/zcat2gzip.patch ** Summary changed: - caspe: zcat missing in busybox + casper: zcat missing in busybox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950469 Title: casper: zcat missing in busybox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1950469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
