** 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:
** 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
@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:
[
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
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
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.
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:
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:
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.
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
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:
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:
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
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
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
@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
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
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.
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:
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
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"
@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
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
** 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)
--
** 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
** 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.
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.
"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.
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
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
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.
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
and during installing (but there is nothing new)
screenshots are from Ubuntu 17.10.1
** Attachment added: "ubuntu17.10_SoftwareUpdater_issue_Install.png"
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
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:
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
*** 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
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"
** 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
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
@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
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
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
** 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
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.
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
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
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.
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
@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
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?
--
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.
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 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
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
** 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:
** 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
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
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
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
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.
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_MEASUREM
** 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.
77 matches
Mail list logo
