[Bug 1906190] Re: Ubuntu 20.10 Live, debian-installer/language=de not working anymore
** Summary changed: - Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE + Ubuntu 20.10 Live, debian-installer/language=de not working anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906190 Title: Ubuntu 20.10 Live, debian-installer/language=de not working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906190] Re: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE
i also tried the both options `debian-installer/language=de debian- installer/country=DE` without success. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906190 Title: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906190] Re: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE
reading https://help.ubuntu.com/lts/installation-guide/amd64/ch05s03.html#preseed-args the option `debian-installer/language=de` should work, but it doesn't with Ubuntu 20.10 Live. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906190 Title: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906190] Re: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE
thanks to comments from Gunnar Hjalmarsson https://askubuntu.com/questions/1296105/ubuntu-20-10-live-locale-set-to-aa-dj-when-bootoption-tells-to-setup-with-loca i got it working. when using `debian-installer/locale=de_DE.UTF-8` instead of `debian-installer/language=de` the locale and language is set up 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/1906190 Title: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906190] [NEW] Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE
Public bug reported: hi, i tried to PXE boot Ubuntu 20.10 Live from ubuntu-20.10-desktop-amd64.iso (2020-10-22 14:31) but i have issues with setting the locale by using bootoptions. using the following additional boot options to setup locale and keyboard layout: debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German here the full pxe boot entries: KERNEL http://192.168.1.1/srv/nfs/ubuntu-x64/casper/vmlinuz INITRD http://192.168.1.1/srv/nfs/ubuntu-x64/casper/initrd APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-x64 ro netboot=nfs ip=dhcp file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German after sucessfull PXE boot into Ubuntu 20.10 Live, the locale is set to aa_DJ.UTF-8 LANG=aa_DJ.UTF-8 LANGUAGE= LC_CTYPE="aa_DJ.UTF-8" LC_NUMERIC="aa_DJ.UTF-8" LC_TIME="aa_DJ.UTF-8" LC_COLLATE="aa_DJ.UTF-8" LC_MONETARY="aa_DJ.UTF-8" LC_MESSAGES="aa_DJ.UTF-8" LC_PAPER="aa_DJ.UTF-8" LC_NAME="aa_DJ.UTF-8" LC_ADDRESS="aa_DJ.UTF-8" LC_TELEPHONE="aa_DJ.UTF-8" LC_MEASUREMENT="aa_DJ.UTF-8" LC_IDENTIFICATION="aa_DJ.UTF-8" LC_ALL= but the locale sould be set to de_DE.UTF-8 as expected (and as it was with ubuntu 20.04): LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= it was not an issue with Ubuntu 20.04 Live when i left out the boot options for locale settings at booting 20.10, the resulting locale is set to C.UTF-8 LANG=C.UTF-8 LANGUAGE= LC_CTYPE="C.UTF-8" LC_NUMERIC="C.UTF-8" LC_TIME="C.UTF-8" LC_COLLATE="C.UTF-8" LC_MONETARY="C.UTF-8" LC_MESSAGES="C.UTF-8" LC_PAPER="C.UTF-8" LC_NAME="C.UTF-8" LC_ADDRESS="C.UTF-8" LC_TELEPHONE="C.UTF-8" LC_MEASUREMENT="C.UTF-8" LC_IDENTIFICATION="C.UTF-8" LC_ALL= here the PXE server project i used: https://github.com/beta-tester/RPi- PXE-Server i think this is a bug. when looking to the casper.log, i can see the folowing lines: + '[' -e /conf/param.conf ] + /scripts/casper-bottom/14locales Begin: Setting up locales... ... grep: /root/usr/share/localechooser/languagelist: No such file or directory Generating locales (this might take a while)... aa_DJ.UTF-8... done Generation complete. done. looks like there is something missing. ** 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/1906190 Title: Ubuntu 20.10 Live, locale set to aa_DJ, when bootoption tells to setup to locale de_DE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857825] [NEW] LinSSID shows -110db wrongly
Public bug reported: hello, i installed LinSSID to visualize the wifi channel usage in my environment. i noticed, that a signal strenth of -110db is shown flipped downwards in the channel graph to the invisible part - only the first few pixels are visible of those -110db channel graphs. in the preferences of LinSSID, i tried to adjust the strengh min value from -100db to -110db, but the input field does not allow to enter a value less than -100. so it is not fixable for the enduser. the fix would be to remove the hardcoded strength min value or at least changing the limit from -100 down to -120 i think. OS is ubuntu 19.10 (also tried 20.04); installed version of LinSSID is 3.6 (sudo apt install linssid); ** Affects: linssid (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/1857825 Title: LinSSID shows -110db wrongly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linssid/+bug/1857825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848018] Re: PXE boot/nfsboot broken; Eoan Ermine; 19.10
okay... solved. for unknown reason i have to add ip=dhcp to the boot options now, what i didn't had in the past. sorry for that report. can be closed now. ** Changed in: casper (Ubuntu) Status: New => Invalid ** Summary changed: - PXE boot/nfsboot broken; Eoan Ermine; 19.10 + [solved] PXE boot/nfsboot broken; Eoan Ermine; 19.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848018 Title: [solved] PXE boot/nfsboot broken; Eoan Ermine; 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848018] Re: PXE boot/nfsboot broken; Eoan Ermine; 19.10
** Description changed: hello, since ubuntu 19.10 Eoan Ermine (beta & daily) PXE boot/nfsboot is broken from: http://releases.ubuntu.com/eoan/ubuntu-19.10-beta-desktop-amd64.iso and http://cdimage.ubuntu.com/daily-live/pending/eoan-desktop-amd64.iso when i use the same boot options as of ubuntu 19.04 (or 18.04 LTS), where it was working, i will get am error message now: " + ... + Begin: Loading essential drivers ... done. + Begin: Running /scripts/init-premount ... done. + Begin: Mounting root file system ... Begin: Runnint /scripts/nfs-top ... done. + Begin: Running /scripts/nfs-premount ... done. + [...] FS-Cache: Loaded + [...] RPC: Registered named UNIX socket transport module. + [...] RPC: Registered udp transport module. + [...] RPC: Registered tcp transport module. + [...] RPC: Registered tcp NFSv4.1 backchannel transport module. + [...] FS-Cache: Netfs 'nfs' registered for caching + Bebin: /scripts/casper-premount ... done. + done. Begin: Trying netboot from 192.168.1.1:/srv/nfs/ubuntu-daily-x64 ... Begin: Trying nfsmount -o nolock -o ro 192.168.1.1:/srv/nfs/ubuntu-daily-x64 /cdrom ... connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable ... " i use lpxelinux.0 as boot loader. the pxe boot menu entry looks like: LABEL ubuntu-daily-x64 MENU LABEL Ubuntu x64 Daily-Live KERNEL http://192.168.1.1/nfs/ubuntu-daily-x64/casper/vmlinuz INITRD http://192.168.1.1/nfs/ubuntu-daily-x64/casper/initrd APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT - - this ist the same as for ubuntu 19.04 Disco Dingo, and there i don't run into this error message + this ist the same as for ubuntu 19.04 Disco Dingo, and there i don't run + into this error message -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848018 Title: PXE boot/nfsboot broken; Eoan Ermine; 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848018] Re: PXE boot/nfsboot broken; Eoan Ermine; 19.10
** Summary changed: - PXE boot broken; Eoan Ermine; 19.10 + PXE boot/nfsboot broken; Eoan Ermine; 19.10 ** Description changed: hello, - since ubuntu 19.10 Eoan Ermine (beta & daily) PXE boot is broken from + since ubuntu 19.10 Eoan Ermine (beta & daily) PXE boot/nfsboot is broken from: http://releases.ubuntu.com/eoan/ubuntu-19.10-beta-desktop-amd64.iso and http://cdimage.ubuntu.com/daily-live/pending/eoan-desktop-amd64.iso - when i use the same boot options of ubuntu 19.04 (or 18.04 LTS) i will get am error message: + when i use the same boot options as of ubuntu 19.04 (or 18.04 LTS), where it was working, i will get am error message now: " Begin: Trying netboot from 192.168.1.1:/srv/nfs/ubuntu-daily-x64 ... Begin: Trying nfsmount -o nolock -o ro 192.168.1.1:/srv/nfs/ubuntu-daily-x64 /cdrom ... connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable ... " + i use lpxelinux.0 as boot loader. the pxe boot menu entry looks like: - - LABEL ubuntu-daily-x64 - MENU LABEL Ubuntu x64 Daily-Live - KERNEL http://192.168.1.1/nfs/ubuntu-daily-x64/casper/vmlinuz - INITRD http://192.168.1.1/nfs/ubuntu-daily-x64/casper/initrd - APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German - TEXT HELP - Boot to Ubuntu x64 Daily-Live - User: ubuntu - ENDTEXT + + LABEL ubuntu-daily-x64 + MENU LABEL Ubuntu x64 Daily-Live + KERNEL http://192.168.1.1/nfs/ubuntu-daily-x64/casper/vmlinuz + INITRD http://192.168.1.1/nfs/ubuntu-daily-x64/casper/initrd + APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German + TEXT HELP + Boot to Ubuntu x64 Daily-Live + User: ubuntu + ENDTEXT - this ist the same as for ubuntu 19.04 Disco Dingo, and there i don't run - into this error message + + this ist the same as for ubuntu 19.04 Disco Dingo, and there i don't run into this error message -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848018 Title: PXE boot/nfsboot broken; Eoan Ermine; 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848018] [NEW] PXE boot broken; Eoan Ermine; 19.10
Public bug reported: hello, since ubuntu 19.10 Eoan Ermine (beta & daily) PXE boot is broken from http://releases.ubuntu.com/eoan/ubuntu-19.10-beta-desktop-amd64.iso and http://cdimage.ubuntu.com/daily-live/pending/eoan-desktop-amd64.iso when i use the same boot options of ubuntu 19.04 (or 18.04 LTS) i will get am error message: " Begin: Trying netboot from 192.168.1.1:/srv/nfs/ubuntu-daily-x64 ... Begin: Trying nfsmount -o nolock -o ro 192.168.1.1:/srv/nfs/ubuntu-daily-x64 /cdrom ... connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable NFS over TCP not available from 192.168.1.1 connect: Network is unreachable connect: Network is unreachable ... " the pxe boot menu entry looks like: LABEL ubuntu-daily-x64 MENU LABEL Ubuntu x64 Daily-Live KERNEL http://192.168.1.1/nfs/ubuntu-daily-x64/casper/vmlinuz INITRD http://192.168.1.1/nfs/ubuntu-daily-x64/casper/initrd APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT this ist the same as for ubuntu 19.04 Disco Dingo, and there i don't run into this error message ** 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/1848018 Title: PXE boot broken; Eoan Ermine; 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848018] Re: PXE boot broken; Eoan Ermine; 19.10
PXE boot from ubuntu 19.04 and ubuntu 18.04 is working. since ubuntu 19.10 PXE boot is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848018 Title: PXE boot broken; Eoan Ermine; 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793894] Re: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly
Debian 10 Buster now has proper signed bootloader for 64bit UEFI and 32bit UEFI. so next step should be that ubuntu will upgrade to properly signed bootloader as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793894 Title: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1793894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765765] Re: on nfsboot 18.04 bionic, internet addresses arn't resolve properly
i never used ip=dhcp in the boot menu entries. strange i had those resolv issue with ubuntu 19.04 daily (pending) from 2019-02-14 for sure. now i tried again with ubuntu 19.04 daily (pending) from 2019-02-20, and now it seems to be not an issue. i also tried the other versions 18.10 and 18.04.2... there it is no issue with resolv anymore. the only thing i could notice now was, that resolving (ping google.de) takes a bit longer under 19.04 daily than under 18.10 / 18.04.2... or maybe it is only my mind. at the moment i can not reproduce my ony reported resolv issue. :/ pxe boot menu entries: LABEL ubuntu-daily-x64 MENU LABEL Ubuntu x64 Daily-Live KERNEL http://192.168.0.1/nfs/ubuntu-daily-x64/casper/vmlinuz INITRD http://192.168.0.1/nfs/ubuntu-daily-x64/casper/initrd APPEND nfsroot=192.168.0.1:/srv/nfs/ubuntu-daily-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT LABEL ubuntu-x64 MENU LABEL Ubuntu x64 KERNEL http://192.168.0.1/nfs/ubuntu-x64/casper/vmlinuz INITRD http://192.168.0.1/nfs/ubuntu-x64/casper/initrd APPEND nfsroot=192.168.0.1:/srv/nfs/ubuntu-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper systemd.mask=tmp.mount -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German TEXT HELP Boot to Ubuntu x64 Live User: ubuntu ENDTEXT LABEL ubuntu-lts-x64 MENU LABEL Ubuntu LTS x64 KERNEL http://192.168.0.1/nfs/ubuntu-lts-x64/casper/vmlinuz INITRD http://192.168.0.1/nfs/ubuntu-lts-x64/casper/initrd APPEND nfsroot=192.168.0.1:/srv/nfs/ubuntu-lts-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper systemd.mask=tmp.mount -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German TEXT HELP Boot to Ubuntu LTS x64 Live User: ubuntu ENDTEXT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765765 Title: on nfsboot 18.04 bionic, internet addresses arn't resolve properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793894] Re: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly
see the answer i got https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=909718 ** Bug watch added: Debian Bug tracker #909718 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909718 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793894 Title: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1793894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793894] Re: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly
the Debian one is only "Debian UEFI CA" signed and not "Microsoft Corporate UEFI CA" signed. that means, as far as i know, it is only usable then you manually add that "Debian UEFI CA" certificate/key to your UEFI certificate/key store, before you are able to boot with SecureBoot enabled. not all netbook computers are able to add certificates/key manually to do that. i don't know at the moment, if the Debian UEFI CA has a "Microfot Corporate UEFI CA" certificate in its "certificate path"... but not at the time as i was reporting that issue. and not in the Debian Live ISO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793894 Title: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1793894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
@Guillermo, i have the same issue with ubuntu 19.04 daily (pending) from 2019-02-14 (without using the workaround) when pxe booting. /var/log/syslog shows the folowing lines, when i serch for resolv: ``` Feb 14 17:53:27 ubuntu systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... Feb 14 17:53:27 ubuntu systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. Feb 14 17:53:27 ubuntu avahi-daemon[1225]: Failed to open /etc/resolv.conf: Invalid argument Feb 14 17:53:27 ubuntu kernel: [6.498832] Key type dns_resolver registered Feb 14 17:53:27 ubuntu kernel: [6.985154] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [6.985719] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [6.986106] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [6.988112] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [7.347354] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [7.357711] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:28 ubuntu sh[1400]: grep: /etc/resolv.conf: No such file or directory Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Positive Trust Anchors: Feb 14 17:53:29 ubuntu systemd-resolved[1604]: . IN DS 19036 8 2 ... Feb 14 17:53:29 ubuntu systemd-resolved[1604]: . IN DS 20326 8 2 ... Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Using system hostname 'ubuntu'. Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 14 17:53:30 ubuntu NetworkManager[1405]: [1550166810.1729] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: netplan.conf) (etc: default-wifi-powersave-on.conf) Feb 14 17:53:30 ubuntu NetworkManager[1405]: [1550166810.4138] dns-mgr[0x55dc42397170]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved Feb 14 17:54:29 ubuntu systemd-resolved[1604]: Using degraded feature set (UDP) for DNS server 192.168.0.1. ``` PS: long time ago i opened a report for that, but never got any reaction there... https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
just tried http://cdimage.ubuntu.com/daily-live/pending/disco-desktop-amd64.iso from 2019-02-08 without the workaround and it pxe boots just fine. thank you very much!!! will the Ubuntu 18.04 LTS (Bionic Beaver) receive that fix in the next point release as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
i just tried out the daily build of http://cdimage.ubuntu.com/daily-live/pending/disco-desktop-amd64.iso from 2019-01-31 07:45 to pxe boot wihout using the "systemd.mask=tmp.mount" workaround... but i still goes straight to maintenance mode. is the fix not included to the daily build yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
hello Victor (vtapia), does it mean the next comming ubuntu Live release 18.04.2 sould PXE boot without any tweak? is it already in the "Ubuntu 19.04 (Disco Dingo) Daily Build"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793894] Re: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly
today i tried Fedora 29 Workstation Live (64bit). there is a bootia32.efi that is correctly Microsoft UEFI CA signed. with that version i can boot and use Fedora 29 on all my UEFI32 + SecureBoot enabled devices successfully. i hope it will be fixed for Ubuntu as well soon... sudo /usr/bin/sbverify --list BOOTIA32.EFI warning: data remaining[839112 vs 975536]: gaps between PE/COFF sections? signature 1 image signature issuers: - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 image signature certificates: - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Windows UEFI Driver Publisher issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation Third Party Marketplace Root -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793894 Title: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1793894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
@Eric, i just tested what you suggested at your comment #31 with Ubuntu 18.10 release ... KERNEL http://pxe-server/nfs/ubuntu-x64/casper/vmlinuz INITRD http://pxe-server/nfs/ubuntu-x64/casper/initrd APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper systemd.mask=dev-hugepages.mount -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German ... but then i again run straight into emergency console. (not sure, if that information still is helpful) at the moment "systemd.mask=tmp.mount" still is the best solution. but with the issues of: - having few red "FAILED" messages at boot time; - at reboot/poweroff often run into "stop jobs" are running endless at shutting down; - or hangs for ever at "Starting Shuts down the 'live' preinstalled system clearly..."; the second best solution is "toram", there i never observed the issues of any "FAILED" message and never hat the issues at reboot/poweroff (maybe there are race conditions - "toram" nothing has to be loaded fron nfs via network). but "toram" takes a lot of time, because the whole squashfs-image has to be loaded into ram first, before it can be mounted. BTW: lununtu 18.10 shows the same behavior as ubuntu 18.10, but it does not show up the issues with reboot/poweroff hanging or endles running stop jobs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793894] Re: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly
** Tags added: bootia32.efi ** Tags added: grub-efi-ia32 secureboot uefi ** Description changed: i have a tablet/netbook with: 32bit UEFI (only), SecureBoot enabled, 32/64bit CPU, Windows 10 Pro (32bit). i can't use the 64bit version of ubuntu 18.04.1 or 18.10 (daily-beta) to boot LiveDVD or LiveUSB, because of missing bootia32.efi on the Live iso media. and when i try to add the bootia32.efi by hand, then i get a signed certificate error at boot time from UEFI i guess. why is the bootx64.efi signed properly for SecureBoot an 64bit UEFI, but bootia32.efi isn't signed properly for SecureBoot an 32bit UEFI??? and why is that bootia32.efi missing at all on the Live iso? i am not the only one, who is using that kind of tablet/netbook and want to install ubuntu 18.x 64bit on that device. i don't know if the package i told is the right one. maybe another package is more correct... - e.g. shim-signed, grub-ia32-signed, grub-amd64-signed, ... + e.g. shim-signed, grub-efi-ia32-signed, grub-efi-amd64-signed, ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793894 Title: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1793894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793894] [NEW] bootia32.efi + 32bit UEFI + SecureBoot => not signed properly
Public bug reported: i have a tablet/netbook with: 32bit UEFI (only), SecureBoot enabled, 32/64bit CPU, Windows 10 Pro (32bit). i can't use the 64bit version of ubuntu 18.04.1 or 18.10 (daily-beta) to boot LiveDVD or LiveUSB, because of missing bootia32.efi on the Live iso media. and when i try to add the bootia32.efi by hand, then i get a signed certificate error at boot time from UEFI i guess. why is the bootx64.efi signed properly for SecureBoot an 64bit UEFI, but bootia32.efi isn't signed properly for SecureBoot an 32bit UEFI??? and why is that bootia32.efi missing at all on the Live iso? i am not the only one, who is using that kind of tablet/netbook and want to install ubuntu 18.x 64bit on that device. i don't know if the package i told is the right one. maybe another package is more correct... e.g. shim-signed, grub-ia32-signed, grub-amd64-signed, ... ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Description changed: i have a tablet/netbook with: 32bit UEFI (only), SecureBoot enabled, 32/64bit CPU, Windows 10 Pro (32bit). i can't use the 64bit version of ubuntu 18.04.1 or 18.10 (daily-beta) to boot LiveDVD or LiveUSB, because of missing bootia32.efi on the Live iso media. - and when i try to add the bootia32.efi by hand, then i get a signed certificate error ar boot time from UEFI i guess. + and when i try to add the bootia32.efi by hand, then i get a signed certificate error at boot time from UEFI i guess. why is the bootx64.efi signed properly for SecureBoot an 64bit UEFI, but bootia32.efi isn't signed properly for SecureBoot an 32bit UEFI??? - and why is that bootia32.efi missing at all on the Live iso at all? + and why is that bootia32.efi missing at all on the Live iso? i am not the only one, who is using that kind of tablet/netbook and want to install ubuntu 18.x 64bit on that device. i don't know if the package i told is the right one. - maybe a similar package is more correct... + maybe another package is more correct... e.g. shim-signed, grub-ia32-signed, grub-amd64-signed, ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793894 Title: bootia32.efi + 32bit UEFI + SecureBoot => not signed properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1793894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765765] Re: on nfsboot 18.04 bionic, internet addresses arn't resolve properly
still an issue of ubuntu 18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765765 Title: on nfsboot 18.04 bionic, internet addresses arn't resolve properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
my Logitech K400 still does not react to double tap on ubuntu 18.04.1 so ubuntu 18.04.1 still got no update of libinput to version >=1.10.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
"toram" works to me and will also fix the hanging at shutdown/reboot. but "toram" takes more that twice as long to boot into the desktop (~3minutes instead of ~1minute). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
i guess Logitek K400 and Logitec K400+ have different device ids so the fix is only for my Logitek K400 and does not fix the issue for a Logitek K400+. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772486] Re: download list of Software Updater (update-manager) does not adjust height while sizing window
** Description changed: in ubuntu 18.04 LTS (Bionic Beaver) release there is still an issue with the update-manager (Software Updater). when there are updates available to download and install, then while downloading you can expand the donloading details of current downloading items list. when you then enlarge the window at the height, the list is not follow in its height. (see screenshot) - file:///home/me/Pictures/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater.png + "the issue ... download list didn't adjust the height (Step 5)" - i think to recall that this issue was already reported for ubuntu 17.10 as "follow up" of a similar issue of update-manager (https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541). + i think to recall that this issue was already reported for ubuntu 17.10 as "follow up" of a similar issue of update-manager (https://answers.launchpad.net/ubuntu/+question/663622 + -> + https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541). the main part is fixed but the part i report is still an issue. i was instructed to do a new report, so here it is... Description: Ubuntu 18.04 LTS Release: 18.04 to reproduce in ubuntu 18.04 LTS: 1. open "Software Updater" - file:///home/me/Pictures/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater%20icon.png + "the icon of "Software Updater" (step 1)" 2. when there are updates available click the button to install available updates. 3. in case there are multiple items to download and their size i big enough, that the download progress takes time, you will see a download message where you can see Downloading . under that string there is a Details region that you can expand. click on that Details to expand ans see the list of downloading items. 4. with your mouse go to thew bottom of the window of "Software Updater" and grab the lower border further down to enlarge the windows in its height. 5. you will see, that only the windows will grow, but the lit of downloading items stays as small as in its initial height. + "the issue ... download list didn't adjust the height (Step 5)" i would expect that the height of the list will grow in the same amount as the windows height does. ** Description changed: in ubuntu 18.04 LTS (Bionic Beaver) release there is still an issue with the update-manager (Software Updater). when there are updates available to download and install, then while downloading you can expand the donloading details of current downloading items list. when you then enlarge the window at the height, the list is not follow in its height. (see screenshot) "the issue ... download list didn't adjust the height (Step 5)" - i think to recall that this issue was already reported for ubuntu 17.10 as "follow up" of a similar issue of update-manager (https://answers.launchpad.net/ubuntu/+question/663622 - -> - https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541). + i think to recall that this issue was already reported for ubuntu 17.10 as "follow up" of a similar issue of update-manager (https://answers.launchpad.net/ubuntu/+question/663622 -> https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541). the main part is fixed but the part i report is still an issue. i was instructed to do a new report, so here it is... Description: Ubuntu 18.04 LTS Release: 18.04 to reproduce in ubuntu 18.04 LTS: 1. open "Software Updater" "the icon of "Software Updater" (step 1)" 2. when there are updates available click the button to install available updates. 3. in case there are multiple items to download and their size i big enough, that the download progress takes time, you will see a download message where you can see Downloading . under that string there is a Details region that you can expand. click on that Details to expand ans see the list of downloading items. 4. with your mouse go to thew bottom of the window of "Software Updater" and grab the lower border further down to enlarge the windows in its height. 5. you will see, that only the windows will grow, but the lit of downloading items stays as small as in its initial height. "the issue ... download list didn't adjust the height (Step 5)" i would expect that the height of the list will grow in the same amount as the windows height does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772486 Title: download list of Software Updater (update-manager) does not adjust height while sizing window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690541] Re: Scrolled windows in update-manager are too small to read
@Brian Murray (brian-murray) the issue i (and others) showed in screenshots were a follow up of the main issue... i thought it is the right place to put my screenshot here as well. ok, opened a new report... https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772486 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690541 Title: Scrolled windows in update-manager are too small to read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772486] [NEW] download list of Software Updater (update-manager) does not adjust height while sizing window
Public bug reported: in ubuntu 18.04 LTS (Bionic Beaver) release there is still an issue with the update-manager (Software Updater). when there are updates available to download and install, then while downloading you can expand the donloading details of current downloading items list. when you then enlarge the window at the height, the list is not follow in its height. (see screenshot) file:///home/me/Pictures/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater.png i think to recall that this issue was already reported for ubuntu 17.10 as "follow up" of a similar issue of update-manager (https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541). the main part is fixed but the part i report is still an issue. i was instructed to do a new report, so here it is... Description:Ubuntu 18.04 LTS Release:18.04 to reproduce in ubuntu 18.04 LTS: 1. open "Software Updater" file:///home/me/Pictures/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater%20icon.png 2. when there are updates available click the button to install available updates. 3. in case there are multiple items to download and their size i big enough, that the download progress takes time, you will see a download message where you can see Downloading . under that string there is a Details region that you can expand. click on that Details to expand ans see the list of downloading items. 4. with your mouse go to thew bottom of the window of "Software Updater" and grab the lower border further down to enlarge the windows in its height. 5. you will see, that only the windows will grow, but the lit of downloading items stays as small as in its initial height. i would expect that the height of the list will grow in the same amount as the windows height does. ** Affects: update-manager (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/1772486 Title: download list of Software Updater (update-manager) does not adjust height while sizing window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772486] Re: download list of update-manager does not adjust height while sizing window
** Attachment added: "the issue ... download list didn't adjust the height" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772486/+attachment/5142526/+files/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater.png ** Summary changed: - download list of update-manager does not adjust height while sizing window + download list of Software Updater (update-manager) does not adjust height while sizing window ** Description changed: - in ubuntu 18.04 LTS (Bionic Beaver) release there is still an issue with the update-manager (Software-Updater). + in ubuntu 18.04 LTS (Bionic Beaver) release there is still an issue with the update-manager (Software Updater). when there are updates available to download and install, then while downloading you can expand the donloading details of current downloading items list. when you then enlarge the window at the height, the list is not follow in its height. (see screenshot) file:///home/me/Pictures/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater.png i think to recall that this issue was already reported for ubuntu 17.10 as "follow up" of a similar issue of update-manager (https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541). the main part is fixed but the part i report is still an issue. i was instructed to do a new report, so here it is... Description: Ubuntu 18.04 LTS Release: 18.04 to reproduce in ubuntu 18.04 LTS: 1. open "Software Updater" file:///home/me/Pictures/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater%20icon.png 2. when there are updates available click the button to install available updates. 3. in case there are multiple items to download and their size i big enough, that the download progress takes time, you will see a download message where you can see Downloading . under that string there is a Details region that you can expand. click on that Details to expand ans see the list of downloading items. 4. with your mouse go to thew bottom of the window of "Software Updater" and grab the lower border further down to enlarge the windows in its height. 5. you will see, that only the windows will grow, but the lit of downloading items stays as small as in its initial height. i would expect that the height of the list will grow in the same amount as the windows height does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772486 Title: download list of Software Updater (update-manager) does not adjust height while sizing window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772486] Re: download list of update-manager does not adjust height while sizing window
** Attachment added: "the icon of "Software Updater" (step 1)" https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1772486/+attachment/5142525/+files/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater%20icon.png ** Package changed: aptdaemon (Ubuntu) => update-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772486 Title: download list of Software Updater (update-manager) does not adjust height while sizing window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1772486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690541] Re: Scrolled windows in update-manager are too small to read
same issue here... ubuntu 18.04 LTS update software screenshot. the shot is just from today (2018-05-21) ** Attachment added: "ubuntu 18.04 LTS bionic - Software Updater.png" https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541/+attachment/5142265/+files/ubuntu%2018.04%20LTS%20bionic%20-%20Software%20Updater.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690541 Title: Scrolled windows in update-manager are too small to read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
libinput10 1.10.5 does have that fix. seems to be fixed in cosmic ubuntu 18.10 daily since 2018-05-06. (double tap is working as expected) but bionic ubuntu 18.04 LTS release still uses libinput10 (1.10.4) (got no upgrade to 1.10.5 yet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
oh nooo… to 1. "Fix Released" was ticked by misstake. it is still not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
oops... 3. should be "systemd.mask=tmp.mount" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
is the status "Fix Released" from 2018-04-27 mean, that the fix is already included in release ubuntu 18.04, or will it be included to 18.04.1 the first time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
1. for pxe/nfs boot, there is stated, that there is a fix released, but i guess it will released in the first point release 18.04.1. see https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863 "netbooting the bionic live CD over NFS goes straight to maintenance mode" 2. for the resolve issue i opened a separate bug report, but there is no activity yet... see https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765 "on nfsboot 18.04 bionic, internet addresses arn't resolve properly" 3. yes, with option "systemd.mask=tmp" i am able to boot successfully into ubuntu desktop. 4. yes, when i shutdown or try to reboot, ubuntu hangs for ever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765765] Re: on nfsboot 18.04 bionic, internet addresses arn't resolve properly
there is a side note about that issue in report: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777 and i asked a question about that issue earlier, but never got a proper answer: https://answers.launchpad.net/ubuntu/+question/663724 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765765 Title: on nfsboot 18.04 bionic, internet addresses arn't resolve properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765765] [NEW] on nfsboot 18.04 bionic, internet addresses arn't resolve properly
Public bug reported: since ubuntu 17.10, 18.04, when i nfsboot into ubuntu live an internet address isn't resolved properly. i always have to put a dns server to the /etc/resolv.conf file by hand to get address resolving to work again. it wasn't an issue in ubuntu 16.04 and not an issue in ubuntu 17.04. it began to be an issue starting with ubuntu 17.10 and ist still an issue now 18.04 daily-live. the different between /etc/resolv.conf of ubuntu <=17.04 and utuntu >=17.10 is, that now only one entry is in the resolv.conf file with IP 127.0.0.53 in the erlier version there was an additional entry on top with the IP of the local DNS server(router). when i nfsboot ubuntu 18.04, adjust the /etc/resolv.conf file by hand to get internet address resolving to work, when i then install ubuntu 18.04 from that environment to the local harddrive, the networksettings on the newly installed local harddisk is always setted up to "manual" IP in the /etc/network/interfaces - so it will not get a proper IP from the router. after a new installation, i always have to set it up "dhcp" to get the IP from the router as usual. ** 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/1765765 Title: on nfsboot 18.04 bionic, internet addresses arn't resolve properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
you wrote: "after this i get normal live session except wrong dns setting, which is fixed by setting my router's dns as resolver #echo "nameserver 192.168.1.1" > /etc/resolv.conf" the issue with resolv.conf i have since ubuntu 17.10, when i nfsboot the live system. ubuntu 17.04 was the last version, where internet addresses were resolved out-of-the-box. is that already reported somewhere? or is there a fix in the queue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
PS.: confirmed as debouncing bug in libinput. https://bugs.freedesktop.org/show_bug.cgi?id=105974#c5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
watching the content of the evemu-record, the only different between double-tap on the touchpad and double-click on the mouse buttons below the touchpad i saw, is the timing. double-tap is way faster than the double-click. double-tap: 6ms..11ms between tap-release vs. double-click: 79ms..137ms between click-release going back to ubuntu 18.04 daily-live is made sligktly slower double-tap on the touchpad with the result, that some of the slower double-taps were recognized as double-click. is there somewhere a kind of "debouncing"-algorithm that let the double- tap recognized as "bouncing" and is filtered out - so it is only seen as single-click... ? ** Attachment added: "evemu-record of the device" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1762536/+attachment/5111696/+files/recording.evemu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
here the link https://bugs.freedesktop.org/show_bug.cgi?id=105974 ** Bug watch added: freedesktop.org Bugzilla #105974 https://bugs.freedesktop.org/show_bug.cgi?id=105974 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] [NEW] double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
Public bug reported: i have a Logitech K400 wireless keyboard-touchpad-combo. https://secure.logitech.com/assets/46733/19/wireless-touch-keyboard-k400r.jpg ID 046d:c52b Logitech, Inc. Unifying Receiver up to ubuntu 17.10.1, i hadn't any issues with it using ubuntu. since ubuntu 18.04 (daily-build / beta2) when do a double tap to the touchpad, it will always be recognized as single click only. i tried to use ubuntu 18.04 on my notebook and used the notebook's touchpad there. there, ubuntu 18.04 is recognizing a double tap as double click, when using the notebook's touchpad. if i connect the Logitek K400 keyboard-touchpad-combo to the notebook and use the K400's touchpad, a double tap is still recognized as single click only. i tried to change touchpad settings in the ubuntu's settings panel without getting double tap working. then i installed gnome-tweak-tools and changes touchpad settings in the gnome-tweaks settings panel. aslo without getting double tap recognized as double click. ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: ubiquity (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic
attached lsusb output of that Logitech K400 wireless keyboard-touchpad combo. ** Attachment added: "ubuntu-18-04-lsusb.txt" https://bugs.launchpad.net/ubuntu/+bug/1762536/+attachment/5108412/+files/ubuntu-18-04-lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762536 Title: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1762536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: Ubuntu 18.04 LTS fails to PXE boot
*** This bug is a duplicate of bug 1755863 *** https://bugs.launchpad.net/bugs/1755863 isn't it possible to mark this report as duplicate of more than one other report? 1754777 and 1755863 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: Ubuntu 18.04 LTS fails to PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: Ubuntu 18.04 LTS fails to PXE boot
yes, my report is a duplicate of issue https://bugs.launchpad.net/bugs/1754777 and https://bugs.launchpad.net/bugs/1755863 that's precisely the issue i have as well. the temporary workaround on bug report https://bugs.launchpad.net/bugs/1754777 works for me at the moment, to get booting into the desktop user interface. thank you Jean-Baptiste Lallement (jibel), for pointing to that report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: Ubuntu 18.04 LTS fails to PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
i have the same issue #1754828 thank you for the temporary workaround -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: Ubuntu 18.04 LTS fails to PXE boot
i just tried the daily-live from 2018-03-25 and attached the log output of dmesg and journalctl (syslog doesn't exist) and screenshots of the FAILED messages off the screen. ** Attachment added: "logs_and screenshots__issue__pxe_boot_1804_daily-live_20180325.zip" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754828/+attachment/5089803/+files/logs_and%20screenshots__issue__pxe_boot_1804_daily-live_20180325.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: Ubuntu 18.04 LTS fails to PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: fails PXE boot Ubuntu 18.04 LTS daliy-live
** Summary changed: - fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09 + fails PXE boot Ubuntu 18.04 LTS daliy-live ** Summary changed: - fails PXE boot Ubuntu 18.04 LTS daliy-live + Ubuntu 18.04 LTS daliy-live ISO fails PXE boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: Ubuntu 18.04 LTS daliy-live ISO fails PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09
not sure what package is unvolved to the pxe boot process of a live dvd so image ** Package changed: bootcd (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09
same PXE boot issue with Ubuntu 18.04 LTS daily-live 2018-03-10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] [NEW] fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09
Public bug reported: i just downloaded the daily-live image from: http://cdimage.ubuntu.com/daily-live/current/bionic-desktop-amd64.iso and added it to my PXE server project (for more information see: https://github.com/beta-tester/RPi-PXE-Server/tree/testing). when i try to PXE boot the PC or VirtualBox from that ISO daily-live image, i run into the emergency mode console. earlier ISO images of Ubuntu (16.04.04, 17.10.1) are PXE booting this way correctly to the UI on both, PC and VirtualBox. when i burm the ISO of Ubuntu 18.04 LTS daily-live to a media and boot from it, it boots correctly. this are the PXE boot menu parameters: LABEL Ubuntu x64 Daily-Live KERNEL /nfs/ubuntu-daily-x64/casper/vmlinuz.efi APPEND initrd=/nfs/ubuntu-daily-x64/casper/initrd.lz netboot=nfs nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro file=/cdrom/preseed/ubuntu.seed boot=casper -- TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT this is the log i could grab from the emergency mode console: see attached log. ** Affects: bootcd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log of journalctl -xb" https://bugs.launchpad.net/bugs/1754828/+attachment/5074937/+files/Ubuntu-18.04-LTS-2018-03-09-pxe-boot-issue.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754828] Re: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09
oops, Affects package was given wrongly. ** Package changed: aptdaemon (Ubuntu) => bootcd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: fails PXE boot Ubuntu 18.04 LTS daliy-live 2018-03-09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/1754828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690541] Re: Scrolled windows in update-manager are too small to read
here the post i made in "ask question" area, with some further description. https://answers.launchpad.net/ubuntu/+question/663622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690541 Title: Scrolled windows in update-manager are too small to read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690541] Re: Scrolled windows in update-manager are too small to read
and during installing (but there is nothing new) screenshots are from Ubuntu 17.10.1 ** Attachment added: "ubuntu17.10_SoftwareUpdater_issue_Install.png" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1690541/+attachment/5043838/+files/ubuntu17.10_SoftwareUpdater_issue_Install.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690541 Title: Scrolled windows in update-manager are too small to read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690541] Re: Scrolled windows in update-manager are too small to read
an screenshot during downloading ** Attachment added: "during downloading" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1690541/+attachment/5043837/+files/ubuntu17.10_SoftwareUpdater_issue_Download.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690541 Title: Scrolled windows in update-manager are too small to read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1690541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
** Attachment removed: AlsaInfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401926/+files/AlsaInfo.txt ** Attachment removed: CRDA.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401927/+files/CRDA.txt ** Attachment removed: WifiSyslog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401936/+files/WifiSyslog.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401928/+files/CurrentDmesg.txt ** Attachment removed: JournalErrors.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401929/+files/JournalErrors.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401935/+files/UdevDb.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401934/+files/ProcModules.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401933/+files/ProcInterrupts.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401932/+files/ProcCpuinfo.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401931/+files/Lsusb.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+attachment/4401930/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
indeed, there is RISCOS partition stuff on the same SD card. and zero'ing out that will prevent the newer kernel to mess up. so maybe i have to bounce back the issue to the raspberry pi team, that the way they prepare the NOOPS partition tables for installing and booting multiple different OS'es is problematic to newer ubuntu kernels. or is there a practical way on ubuntu site to handle these conflicts more nicer... like it was before with older kernels...? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
ok, thank you, i got it. maybe the raspberry pi NOOBS team will find a solution to create a nice separated and non-conflicting partition table setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
@Philip Susi (psusi): oops, i didn't really answered your question... the size of blocks appears on ALL systems as expected with (14,9 GiB, 15931539456 bytes, 31116288 sectors). here the outputs of the different Ubuntu versions + debian: Debian 8.0.0 LiveCD LXDE dmesg: [3.153986] scsi 8:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0 [3.156776] sd 8:0:0:0: Attached scsi generic sg3 type 0 [3.390080] sd 8:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [3.394821] sd 8:0:0:0: [sdc] Write Protect is off [3.397416] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00 [3.399569] sd 8:0:0:0: [sdc] No Caching mode page found [3.402135] sd 8:0:0:0: [sdc] Assuming drive cache: write through [3.438526] sdc: sdc1 sdc2 sdc5 sdc6 sdc7 sdc8 sdc3 [3.454048] sd 8:0:0:0: [sdc] Attached SCSI removable disk [ 35.537446] EXT4-fs (sdc8): mounted filesystem with ordered data mode. Opts: (null) [ 35.564251] FAT-fs (sdc7): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 35.597981] FAT-fs (sdc7): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 35.759060] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null) [ 35.799686] FAT-fs (sdc5): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 35.858976] FAT-fs (sdc5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 35.910946] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null) -- lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdc 8:32 1 14,9G 0 disk |-sdc1 8:33 1 118,2M 0 part |-sdc2 8:34 1 1K 0 part |-sdc3 8:35 132M 0 part /media/user/SETTINGS |-sdc5 8:37 1 160M 0 part /media/user/0332-85B5 |-sdc6 8:38 1 6,3G 0 part /media/user/b0f5d83c-52fb-4181-9165-18c086e8be4c |-sdc7 8:39 160M 0 part /media/user/boot `-sdc8 8:40 1 8,1G 0 part /media/user/root Ubuntu 12.04 LiveDVD dmesg: [5.659331] scsi 8:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0 [5.659716] sd 8:0:0:0: Attached scsi generic sg3 type 0 [5.901090] sd 8:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [5.903212] sd 8:0:0:0: [sdc] Write Protect is off [5.903214] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00 [5.905334] sd 8:0:0:0: [sdc] No Caching mode page present [5.905336] sd 8:0:0:0: [sdc] Assuming drive cache: write through [5.914826] sd 8:0:0:0: [sdc] No Caching mode page present [5.914828] sd 8:0:0:0: [sdc] Assuming drive cache: write through [5.938801] sdc: sdc1 sdc2 sdc5 sdc6 sdc7 sdc8 sdc3 [5.950926] sd 8:0:0:0: [sdc] No Caching mode page present [5.950928] sd 8:0:0:0: [sdc] Assuming drive cache: write through [5.950930] sd 8:0:0:0: [sdc] Attached SCSI removable disk [8.328996] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null) [8.793824] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null) [9.109466] EXT4-fs (sdc8): mounted filesystem with ordered data mode. Opts: (null) [ 81.374842] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null) [ 81.462819] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null) [ 81.510502] EXT4-fs (sdc8): mounted filesystem with ordered data mode. Opts: (null) -- lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdc 8:32 1 14,9G 0 disk ├─sdc1 8:33 1 118,2M 0 part ├─sdc2 8:34 1 1K 0 part ├─sdc3 8:35 132M 0 part /media/SETTINGS ├─sdc5 8:37 1 160M 0 part /media/0332-85B5 ├─sdc6 8:38 1 6,3G 0 part /media/b0f5d83c-52fb-4181-9165-18c086e8be4c ├─sdc7 8:39 160M 0 part /media/boot └─sdc8 8:40 1 8,1G 0 part /media/root Ubuntu 14.04 LiveDVD dmesg: [5.394953] scsi 8:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0 [5.395218] sd 8:0:0:0: Attached scsi generic sg3 type 0 [5.636478] sd 8:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [5.638695] sd 8:0:0:0: [sdc] Write Protect is off [5.638697] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00 [5.640943] sd 8:0:0:0: [sdc] No Caching mode page found [5.640945] sd 8:0:0:0: [sdc] Assuming drive cache: write through [5.650433] sd 8:0:0:0: [sdc] No Caching mode page found [5.650435] sd 8:0:0:0: [sdc] Assuming drive cache: write through [5.673938] sdc: sdc1 sdc2 sdc5 sdc6 sdc7 sdc8 sdc3 [5.685308] sd 8:0:0:0: [sdc] No Caching mode page found [5.685310] sd 8:0:0:0: [sdc] Assuming drive cache: write through [5.685311] sd 8:0:0:0: [sdc] Attached SCSI removable disk [ 106.588083] EXT4-fs (sdc8): recovery complete [ 106.588087] EXT4-fs (sdc8): mounted filesystem with ordered data mode. Opts: (null)
[Bug 1457526] [NEW] recognized partitions incomplete on 14.04.2 and 15.04
Public bug reported: on ubuntu 15.04, 14.04.2 the system shows me after plugging a SD card the following information (where sdc the SD card is) me@my-Linux:~$ cat /proc/partitions major minor #blocks name ... 8 32 15558144 sdc 8 333807232 sdc1 me@my-Linux:~$ sudo fdisk -l /dev/sdc Disk /dev/sdc: 14,9 GiB, 15931539456 bytes, 31116288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: ... Device BootStart End Sectors Size Id Type /dev/sdc1 2048 244140 242093 118,2M e W95 FAT16 (LBA) /dev/sdc2 245760 31050751 30804992 14,7G 85 Linux extended /dev/sdc3 31050752 311162876553632M 83 Linux /dev/sdc5 253952 581631 327680 160M c W95 FAT32 (LBA) /dev/sdc6 589824 13869055 13279232 6,3G 83 Linux /dev/sdc7 13877248 14000127 12288060M c W95 FAT32 (LBA) /dev/sdc8 14008320 31047679 17039360 8,1G 83 Linux Partition table entries are not in disk order. none of the partitions are able to mount. the exact same SD card and same USB/SD card reader but using ubuntu 14.04 or 12.04 shows me the correct information: me@my-Linux:~$ cat /proc/partitions major minor #blocks name ... 8 16 15558144 sdc 8 17 121046 sdc1 8 18 1 sdc2 8 19 32768 sdc3 8 21 163840 sdc5 8 226639616 sdc6 8 23 61440 sdc7 8 248519680 sdc8 tested environments: with that issue (wrong/incomplete partition information) ubuntu 15.04 amd64 (dist-upgraded from 14.10 to 15.04) ubuntu 15.04 liveDVD amd64 (from 2015) ubuntu 14.04.2 liveDVD amd64 (from 2015) without that issue (correct partition information) ubuntu 12.04 liveDVD amd64 ubuntu 14.04 liveDVD amd64 (~2014) debian 8.0.0 liveCD amd64 LXDE (from 2015) see here for more details: https://www.raspberrypi.org/forums/viewtopic.php?p=762666#p762666 ** Affects: ubuntu-docs (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/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401928/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401933/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401930/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401931/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] JournalErrors.txt
apport information ** Attachment added: JournalErrors.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401929/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
apport information ** Tags added: apport-collected vivid ** Description changed: on ubuntu 15.04, 14.04.2 the system shows me after plugging a SD card the following information (where sdc the SD card is) me@my-Linux:~$ cat /proc/partitions major minor #blocks name ... 8 32 15558144 sdc 8 333807232 sdc1 me@my-Linux:~$ sudo fdisk -l /dev/sdc Disk /dev/sdc: 14,9 GiB, 15931539456 bytes, 31116288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: ... Device BootStart End Sectors Size Id Type /dev/sdc1 2048 244140 242093 118,2M e W95 FAT16 (LBA) /dev/sdc2 245760 31050751 30804992 14,7G 85 Linux extended /dev/sdc3 31050752 311162876553632M 83 Linux /dev/sdc5 253952 581631 327680 160M c W95 FAT32 (LBA) /dev/sdc6 589824 13869055 13279232 6,3G 83 Linux /dev/sdc7 13877248 14000127 12288060M c W95 FAT32 (LBA) /dev/sdc8 14008320 31047679 17039360 8,1G 83 Linux Partition table entries are not in disk order. none of the partitions are able to mount. the exact same SD card and same USB/SD card reader but using ubuntu 14.04 or 12.04 shows me the correct information: me@my-Linux:~$ cat /proc/partitions major minor #blocks name ... 8 16 15558144 sdc 8 17 121046 sdc1 8 18 1 sdc2 8 19 32768 sdc3 8 21 163840 sdc5 8 226639616 sdc6 8 23 61440 sdc7 8 248519680 sdc8 tested environments: with that issue (wrong/incomplete partition information) ubuntu 15.04 amd64 (dist-upgraded from 14.10 to 15.04) ubuntu 15.04 liveDVD amd64 (from 2015) ubuntu 14.04.2 liveDVD amd64 (from 2015) without that issue (correct partition information) ubuntu 12.04 liveDVD amd64 ubuntu 14.04 liveDVD amd64 (~2014) debian 8.0.0 liveCD amd64 LXDE (from 2015) see here for more details: https://www.raspberrypi.org/forums/viewtopic.php?p=762666#p762666 + --- + ApportVersion: 2.17.2-0ubuntu1.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2149 F pulseaudio + CasperVersion: 1.360 + DistroRelease: Ubuntu 15.04 + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: initrd=/nfs/hostname/amd64/casper/initrd.lz netboot=nfs nfsroot=10.11.12.181:/srv/tftp/nfs/hostname/amd64 file=/cdrom/preseed/hostname.seed boot=casper -- debian-installer/language=de console-setup/layoutcode?=de locale=de_DE BOOT_IMAGE=/nfs/hostname/amd64/casper/vmlinuz.efi + ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.19.0-15-generic N/A + linux-backports-modules-3.19.0-15-generic N/A + linux-firmware 1.143.1 + RfKill: + + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/06/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2105 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8Z77-M PRO + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401926/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions --
[Bug 1457526] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401935/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401927/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401936/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401934/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1457526/+attachment/4401932/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
@Brad Figg (brad-figg): i called that 'apport-collect' as you can see... hopefully successfully and complete. @Phillip Susi (psusi): the plugged SD card is a 16GB SanDisk microSD. it is used for a Raspberry Pi and is partitionized by NOOBS 1.4 to severyl different partitions. the thing is, when i plugged that SD card to my Desktop PC with ubuntu 15.04 or 14.04.2 its most recent version from 2015 via LiveDVD or installed on HDD. cat /proc/partitions shows me not the partitions that are on the SD card. but fdisk -l do so - but none of the listed partitions are able to mount. when i use the exact same SD card on the exact same desktop PC, but this time using ubuntu 14.04 (from 2014) or 12.04 (from 2012) via LiveDVD, i have all partitions listed by cat /proc/partitions and fdisk -l and i am able to mount all of its partitions successfully and can access them. also other Raspberry Pi user are having similar issues with ubuntu 15.04 and 14.04.2 as i could notice -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457526] Re: recognized partitions incomplete on 14.04.2 and 15.04
oops... was done so by accident -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457526 Title: recognized partitions incomplete on 14.04.2 and 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1457526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
