I finally managed to get it to install (using minimal) on the 6th try. The
only thing I did differently was watch the logs and not click any buttons
if the logs showed that something was in progress.
On Mon, Sep 6, 2021, 3:40 PM Malachi de AElfweald <
1942...@bugs.launchpad.net>
** Attachment added: "These are the auto-generated partitions"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1942803/+attachment/5523321/+files/disks.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Public bug reported:
This machine was previously running 18.04. I decided to replace it with
21.04 (using the ISO via USB) rather than doing an in-place upgrade.
The Ubiquiti installer gets to the grub-install step then fails with:
```
Executing grub-install /dev/nvme2n1 failed
This is a fatal er
I think we can close this one
On Fri, Jul 26, 2019, 4:59 AM Paul White <1002...@bugs.launchpad.net>
wrote:
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. This bug was reported some time ago
> and there have been many changes in Ubuntu sinc
Unfortunately, the system is unusable this morning. Still trying to
recover it. May have to flatline it again.
It seems I have gotten myself stuck in a loop:
1. try to reboot and that causes kernel panic
2. after that happens a few times, the NVME needs fsck'd because of corrupt
group descriptor
Let me see if I can figure out how to do it without breaking the system
this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765822
Title:
BUG: Bad page map in process Compositor pte:2
Public bug reported:
Booted. Started firefox. A couple seconds later it was back on the lock
screen. Logged in again and it hung.
This is a fresh "Erase disk and reinstall" of minimal from yesterdays
bionic iso
Ubuntu 4.15.0-15.16-generic 4.15.15
ProblemType: KernelOops
DistroRelease: Ubuntu 18
Public bug reported:
This showed up after Chrome started crashing.
Ubuntu 4.15.0-15.16-generic 4.15.15
This is a fresh "Erase disk and reinstall" of minimal from yesterdays
bionic iso
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVer
Public bug reported:
update-grub hangs entire system at found initrd indefinitely.
If I temporarily hard-reboot and add `acpi=off` to kernel params, update-grub
finishes.
This is a fresh "Erase disk and Reinstall" of a Minimal from yesterdays
bionic iso
Description:Ubuntu Bionic Beaver (dev
Just had this happen twice on today's bionic iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277717
Title:
Sausy grub-efi amd64 signed package failed to install into /target/
To manage notificat
For example, this is from the most recent crash
[ 988.304175] traps: php7.2[7903] general protection ip:7f68dbf29ca3
sp:7ffdfcf7b640 error:0 in ld-2.27.so[7f68dbf1d000+27000]
[ 1719.219737] traps: sudo[9244] general protection ip:7f5ffbc5e9fb
sp:7ffc9fa60f30 error:0 in ld-2.27.so[7f5ffbc52000+2
I have downloaded Memtest86-7.5.iso but haven't yet got the 40_custom
entry correct to launch it via loopback. I guess I could burn it to
USB/CD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764521
I've been getting a ton of faults in ld; even after a 'Erase disk and
reinstall Ubuntu' from a new live usb. It's not the only one, of course
- just a common one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
Apport reported in conjunction with
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1764521
malachid@odin:~$ lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
malachid@odin:~$ apt-cache policy libopencore-amrwb0
libopencore-amrwb0:
In
`sudo valgrind apt-get install --only-upgrade libudev1` completed successfully
so I tried the apt upgrade again
It mostly completed (hung the system at the shim-signed)
but got past the previous failure.
I think we can close this.
--
You received this bug notification because you are a member of
Hmm
malachid@odin:~$ sudo apt install valgrind
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
ca-certificates-java
Use 'sudo apt autoremove' to remove it.
Suggested packa
I was able to get valgrind to install after a reboot. Hold on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763756
Title:
apt upgrade fails with Illegal instruction
To manage notifications about
I also see this in dmesg
[ 695.712618] traps: apt[8483] trap invalid opcode ip:7f531b425254
sp:7ffd31536338 error:0 in liblzma.so.5.2.2[7f531b418000+24000]
[ 722.097041] traps: apt[8757] trap invalid opcode ip:7f8d3ac98254
sp:7ffe28c10908 error:0 in liblzma.so.5.2.2[7f8d3ac8b000+24000]
[ 739.
Public bug reported:
Update worked. Upgrade was working, then died with Illegal instruction.
Restarting the upgrade with -V shed no light on the problem. dpkg
--configure -a saw nothing to do. Apport tried to report but failed
because packages were out of date.
malachid@odin:~$ sudo apt -V up
libudev1 is the one it wants upgraded before apport will work; however
`sudo apt-get install --only-upgrade libudev1` also crashed with Illegal
instruction.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Pratik -
If you don't see the boot menu (Try Ubuntu, Install Ubuntu, etc) - hold
the shift button when booting until you do see it. I wasn't sure which
button it was, so I was alternating between shift and F6, but I am
pretty sure it is shift.
Once you see the menu, you will have a short delay b
Hi Joseph,
I was having a similar bug; see 1759865, 1760461, 1759947
I tried getting that kernel installed. Without nvidia driver, I
couldn't get the system booted. With it, I couldn't get the kernel to
install. After some time, grub-install no longer worked, even from
liveusb or recovery. I
Public bug reported:
gnome-system-monitor, wget and firefox were running while I was away
from the machine. Came back and the machine showed a Firefox crash
popup. Before I could check what happened the machine was locked up
requiring hard reboot.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762237/+attachment/5107183/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762237
T
Tried quite a few options and those two were both required to get a
Normal install to go through with today's daily ISO 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/1762009
Title:
ubiquity
Finally managed to get through the installer:
kernel params `pcie_aspm=off` and `acpi=off`
NOTE: Screen is HUGE - ubiquity installer is larger than the screen itself
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
A brand new Kingston Elite USB, fresh out of the package, is exhibiting
the same problems - so I don't think it is the flash drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762009
Title:
ubiqu
I see this in dmesg:
[ 127.380987] SQUASHFS error: zlib decompression failed, data probably corrupt
[ 127.380991] SQUASHFS error: squashfs_read_data failed to read block 0xadd7e8
[ 127.381982] SQUASHFS error: zlib decompression failed, data probably corrupt
[ 127.381984] SQUASHFS error: squashf
Public bug reported:
My 18.04 system was so unstable, I decided to try flatlining and starting over.
ubiquity crashed while trying to install.
In the last 22 attempts, it usually hard hung either after the network
connected or after creating the papersize. This time, however, it crashed
causing
Will try another USB just in case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762009
Title:
ubiquity crashed on Ubuntu 18.04 LTS Beta 2 ISO from USB while
entering new credentials
To manage n
I am seeing the same thing in Ubuntu 18.04 w/ the Classic Gnome login.
I do not see it with the Ubuntu login.
malachid@odin:~$ env | grep -i session
GNOME_SHELL_SESSION_MODE=classic
XDG_SESSION_ID=3
DESKTOP_SESSION=gnome-classic
XDG_SESSION_TYPE=x11
XDG_SESSION_DESKTOP=gnome-classic
GDMSESSION=gno
I managed to get the upstream kernel onto the grub configuration - but
was unable to boot (probably one of the other drivers I failed to
remove).. will have to try again with various kernel params.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
They are being ignored (apparently incorrectly) in 18.04
Apr 03 13:17:58 odin systemd-tmpfiles[1033]: [/usr/lib/tmpfiles.d/var.conf:14]
Duplicate line for path "/var/log", ignoring.
Apr 03 13:32:59 odin systemd[1]: systemd-tmpfiles-clean.service: Main process
exited, code=dumped, status=11/SEGV
I'm not sure about the fix. This is in 18.04
Apr 03 13:17:58 odin systemd-tmpfiles[1033]: [/usr/lib/tmpfiles.d/var.conf:14]
Duplicate line for path "/var/log", ignoring.
Apr 03 13:32:59 odin systemd[1]: systemd-tmpfiles-clean.service: Main process
exited, code=dumped, status=11/SEGV
Apr 03 13:3
Also trying to see if I can get the updated kernel into a live usb
environment so I can test that without corruption from any local
configured setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17604
I did a fresh install on new hardware on 3/26. Been trying to get it
stable since (which meant a lot of apt updates and dpkg --configure). I
tried to install kernel 4.16.0-041600rc7 this weekend, but it needs me
to disable nvidia,etc so still trying to get that to work.
--
You received this bug
This has been happening since fresh install on new hardware.
Tried to do 4.16.0-041600rc7 this weekend, but couldn't get it to install.
Trying to figure out how to determine what all has to be uninstalled for it to
work.
--
You received this bug notification because you are a member of Ubuntu
B
I was trying to test out the upstream kernel this weekend. One of the
steps is to disable 3rd party libraries (like nvidia). Is there any way
to identify all the libraries that have to be disabled? Or better yet -
any way to install the kernel into a live usb image?
--
You received this bug no
** Attachment added: "This shows the zombie qemu under sd-pam"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760461/+attachment/5098149/+files/zombies-in-pstree.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Public bug reported:
Autogenerated bug - might be dupe of 1759865 and 1759947
QEMU hung. Couldn't close window. kill -9'd the processes, but window
remained. xkill'd the window, but zombie remained - owned by systemd-
pam.
Apport tried to report it, but hung machine in the process.
As a side no
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760461/+attachment/5098148/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760461
T
This is turning out to be a bit more tricky. Switching drivers in
'Software & Updates' did appear to work, but nvidia module was still
reporting in the logs. I purged nvidia, then the system wouldn't boot.
I tried a few of the boot params; but eventually the only way I was able
to get the system
I have been running with that in my GRUB_CMDLINE_LINUX for a couple days
now. It's unclear whether it is having an impact. Crash rate does not
seem to be reduced, and I am often unable to see the logs after it
hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Might be the same as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760163
Title:
BUG: unable to handle kernel NULL pointer dereference a
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760163/+attachment/5096319/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760163
T
Public bug reported:
Chrome hung. Then the rest of the machine hung.
Might be related to the other bugs recently auto-reported.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname:
Doesn't look like switching out the video driver was enough; I'll
continue with the kernel change after work tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759865
Title:
general protection
Sure - trying it now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759947
Title:
BUG: unable to handle kernel paging request at 2020
To manage notifications about this bug go to:
http
The first step in trying the other kernel was to disable the nvidia
driver. I have switched it to nouveau and am letting it run for a
little to see if that makes any difference before I swap out the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759947/+attachment/5095360/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759947
T
Public bug reported:
Unclear what happened. It said chrome was dying, but then nothing
including mouse and keyboard worked.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Lin
It's a fresh install on new hardware. No previous versions on this
hardware.
I'll try out the upstream kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759865
Title:
general protection fault:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759865/+attachment/5094968/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759865
T
Public bug reported:
I was using chrome and saw the update-notifier warn me of ""
Went to the command line to try to figure out what the problem was. Most
commands just core dumped (including apt and su) however I was able to get this
from dmesg
[ 693.573723] cron[5576]: segfault at 7fff19647
I was just able to fix it on 17.10 by opening 'NVIDIA X Server
Settings', going to 'X Screen 0':'OpenGL Settings' and unchecking
'Allow Flipping'.
Problem immediately stopped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I just upgraded to 17.10 and am seeing the same problem with
0.9.13.1+17.04.20170109-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/269904
Title:
Screen refresh problems with nvidia cards
T
I believe I have fixed mine. Perhaps someone else can test the fix on theirs?
>From this
>http://unix.stackexchange.com/questions/91027/how-to-disable-usb-autosuspend-on-kernel-3-7-10-or-above
Edit the /etc/default/grub file and append to the GRUB_CMDLINE_LINUX_DEFAULT
line:
usbcore.autosuspend=
Could be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1012291
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371233
Title:
USB 3.0 connection is unreliable + xHCI xhci_drop_endpoi
Regarding comment #37
If I plug an Android phone (HTC One m7 GPe) to the same port instead of the
USB3 Hub, it stays connected.
If I connect the USB hub instead, I get this problem.
If I connect the phone through the USB hub, I loose access to the phone rather
quickly during one of the drop cycl
Bug did not go away with 15.10 / 4.2.0-16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371233
Title:
USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with
disabled ep
To manage
I see the same problem with a hub plugged in and nothing attached to it.
This happens repeatedly. I've reported it to them as well, but it seems
to be more of a problem with the xhci_hcd. This is with 3.19.0-30.
[ 3323.263466] usb 2-1.1: USB disconnect, device number 103
[ 3323.284305] usb 2-1.4
I just switched from the Samsung Galaxy Note to the Google Edition of
HTC One and do not have this problem with the new device. Maybe Samsung
specific?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/88
This has started happening on my other Ubuntu box now. Turning off 'usb
debugging' makes the problem go away - of course that means no longer
using ADB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/88
I'm seeing the same thing in 13.04 w/ Samsung Galaxy Note. It used to
work fine, but after upgrading from 12.10->13.04 and from ICS->JB, this
device is unusable from Ubuntu. Dual boot to Windows and it works fine.
Linux hydra 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013
x86_64 x86
Following these instructions, I get about 50 popups but then it is connected
successfully
http://forum.xda-developers.com/showthread.php?t=2223401
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159277
I have two machines that I upgraded to 13.04. One works, the other one has this
problem. When I plug in the Samsung Galaxy Note (which used to work) I get
about 100 of these:
Unable to open MTP device '[usb:003,021]'
(with #021 increasing for each one)
At the end, it repeats and starts over.
--
Today, it was doing the failing again. I saw the update here and apt-get
upgraded. It's working again. I think that confirms the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181454
Title:
emp
rebooted - everything is working fine now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181454
Title:
empathy-accounts crashes on launch
To manage notifications about this bug go to:
https://bugs.
sudo apt-get purchase empathy
rm -rf ~/.config/Empathy
reboot
sudo apt-get install empathy
launch empathy
delete the two accounts still there
starting over. seems stable so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Preferences - told it to not autostart on boot
Managed to click the "disable account" switch
rebooted
empathy-accounts
I clicked on the other entry (I was going to disable it too) and got the same
error:
malachi@beast:~$ empathy-accounts
**
ERROR:empathy-user-info.c:252:fill_contact_info_grid: as
I rebooted and was able to launch empathy-accounts again. Both accounts were
still there. I tried to delete what I thought was the offending account, and it
crashed:
malachi@beast:~$ empathy-accounts
(empathy-accounts:2917): GLib-GObject-WARNING **: instance with invalid
(NULL) class pointer
(
malachi@beast:~$ sudo apt-cache policy empathy
empathy:
Installed: 3.6.4-0ubuntu4
Candidate: 3.6.4-0ubuntu4
Version table:
*** 3.6.4-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status
--
You received this bug notification
Went into the gnome-keyring UI and deleted all the Ubuntu Web Accounts.
malachi@beast:~/bin$ empathy-accounts
**
ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec
!= NULL)
Aborted (core dumped)
Does not appear to have made a different to Empathy.
--
You received thi
The other day, Google notified me that my password needed to be reset. I
did so. Empathy couldn't connect, so I was going to change the
password. I started having the same problem you are reporting on two
different machines both running 13.04.
>From the command line, I was able to launch empathy
I just upgraded to the beta 13 and verified the problem still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002573
Title:
FF defunct processes
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002573
Title:
FF defunct processes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1002573/+subscr
Public bug reported:
As of this morning, I have had to reboot a few times because the system
was unable to acquire memory to even fork a process.
This last time, after booting, I decided to try to figure out what it is.
It appears that as long as Firefox is running (even if not doing anything) it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797727
Title:
not retaining password
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/797727/+subscr
Public bug reported:
Binary package hint: empathy
NT password changed last week. Every boot now, it tells me my password
is incorrect and I have to re-enter/re-apply it for it to work. It is
not persisting on Apply.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: empathy 2.34.0-0ubuntu3.
79 matches
Mail list logo
