Fix works for me (I opened duplicate #1815152): I apt upgraded to linux-
modules-4.18.0-15-generic 4.18.0-15.16, and now my system boots
just fine. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1814555 ***
https://bugs.launchpad.net/bugs/1814555
Bug fixed! I apt upgraded to linux-image-4.18.0-15-generic 4.18.0-15.16
as usual, and my system boots happily again.
Thank you ~smb for the quick followup.
--
You received this bug notification because
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236898/+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/1815152
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236897/+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/1815152
Title:
apport information
** Tags added: apport-collected cosmic
** Description changed:
A few days ago, I let update-manager upgrade my kernel from 4.18.0-13 to
4.18.0-14. Since then, my system is unable to boot. It freezes after
printing
fb: switching to inteldrmfb from VESA VGA
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236902/+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/1815152
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236896/+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/1815152
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236899/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236903/+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/1815152
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236904/+files/WifiSyslog.txt
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236895/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236900/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815152
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236894/+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/1815152
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1815152/+attachment/5236901/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Results with mainline kernels:
* linux-image-unsigned-4.18.20-041820-generic: bug present, same behaviour as
in linux-image-4.18.0-14-generic
* linux-image-unsigned-4.20.7-042007-generic: bug fixed!
One other interesting factoid: after the failed modeset, the system
isn't _completely_ dead. I
** Attachment added: "happy boot sequence with previous build (4.18.0-13)"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1815152/+attachment/5236892/+files/happy-kernel.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A few days ago, I let update-manager upgrade my kernel from 4.18.0-13 to
4.18.0-14. Since then, my system is unable to boot. It freezes after
printing
fb: switching to inteldrmfb from VESA VGA
but before it gets around to asking me the passphrase for my encrypted
main
Public bug reported:
gnumeric crashes loading some files (but not others). The best stack
trace I've been able to get so far is:
#0 0x7f8f75536c85 in ?? () from /usr/lib/libspreadsheet-1.12.6.so
#1 0x7f8f7552def6 in sv_update () from /usr/lib/libspreadsheet-1.12.6.so
#2
OK, I managed to strip down a real-life spreadsheet to repro the bug
without leaking sensitive personal information. Attached. Note that
there is no content remaining in this spreadsheet, just whatever stuff
was left behind after I deleted all the content. Note also that I had to
do some of that
...and it looks like the bug is also fixed in
gnumeric_1.12.6-2_amd64.deb, which I downloaded from trusty. So fixing
this should be *really* easy! ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I successfully downloaded and booted http://cdimage.ubuntu.com/daily-
live/current/saucy-desktop-amd64.iso dated 05-Aug-2013 09:02. Video
works.
Not sure what the point of this was, since everything has been fine
since I upgraded to raring (as the original quantal upgrade had no
apparent fix or
Sorry for the delay. Here are the requested log files in a tarball:
lp1169004-logs/normal/dmesg
lp1169004-logs/normal/Xorg.0.log
- logs from a normal boot, where X works just fine
lp1169004-logs/failsafe/dmesg
lp1169004-logs/failsafe/Xorg.failsafe.log
- logs from a recovery boot with
** Summary changed:
- friendly-recovery: failsafeX dialog is completely unusable
+ friendly-recovery: failsafeX dialog is keyboard-hostile (sometimes completely
unusable)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update from testing mainline kernels...
1) to confirm that the bug is still present in the mainline kernel
corresponding to Ubuntu's 3.5.0-27.46 (which definitely exhibits the
bug), I downloaded and installed linux-
image-3.5.7-03050707-generic_3.5.7-03050707.201303040535_amd64.deb (and
the
Workaround #1:
I guess I'll repartition and try installing raring in the new
partition.
success! the bug has been fixed in Ubuntu 13.04. This is still an update
regression with 12.10; my ThinkPad T500 worked just fine on March 31 and
video stopped working on April 13. But at least the next
Update on 12.10: it's not just keyboard-unusable, it's also mouse-
unusable. I just tried failsafe-x on my desktop system running 12.10,
and it is completely unusable. X works perfectly on this system, my
mouse is hooked up and working fine, everything is good. Details...
Steps to reproduce:
1)
I've recently installed 13.04 on my laptop, so I'll try it there next.
Good: failsafe-x is no longer completely broken in 13.04. It can now be
controlled with the mouse and keyboard. Hooray!
It still has several bugs, though, which I'll report separately.
--
You received this bug notification
This is starting to look very much like a kernel bug, although I'm still
confused about several things. My main evidence is that I'm having
similar problems with System Rescue CD, a Gentoo-based rescue distro
that boots from CD or USB stick.
In particular, System Rescue CD 3.4.1 (kernel 3.4.32)
H: if I disable my encrypted swap partition (by modifying
/etc/fstab), this problem goes away. Definitely seems like friendly-
recovery has problems with encrypted swap.
** Summary changed:
- friendly-recovery tool hangs trying to do almost anything (e.g. Enable
networking)
+
** Tags added: regression-update
** Summary changed:
- no video after upgrading kernel, mesa, libc, and several other packages
+ regression: no video after upgrading kernel, mesa, libc, and several other
packages (ThinkPad T500)
--
You received this bug notification because you are a member
Public bug reported:
Steps to reproduce:
1) on 2013-03-31, shutdown laptop for a 2-week vacation
2) on 2013-04-13, return from vacation, boot laptop, and apply pending updates
with update-manager
3) reboot laptop
Expected result: Ubuntu boots just as it did before the update (it
worked fine on
** Attachment added: screenshot of the initial hang (after fsck quickly
succeeds)
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1168974/+attachment/3644234/+files/recovery-mode-hang.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Steps to reproduce:
1. boot into recovery mode
2. from the Recovery Menu, select Enable networking
3. when warned that continuing will remount / in read/write mode,
select Yes
Expected behaviour:
- system runs fsck on root FS, which quickly succeeds (because the
FS is
** Attachment added: screenshot after I hit Ctrl-C, which hints that encrypted
swap might be involved
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1168974/+attachment/3644235/+files/recovery-hang-encrypted-swap.png
--
You received this bug notification because you are a
Public bug reported:
1. boot my laptop into recovery mode with no external mouse connected
(only the laptop's builtin trackpad)
2. from the Recovery Menu, select failsafeX
(This is a Lenovo ThinkPad T500 with Synaptics trackpad -- pretty
vanilla hardware that normally works perfectly with
This is by design. Reading Mercurial config files owned by
random/unknown/untrusted users would be a security risk, because those
untrusted users can install malicious hooks that run with your
privileges on certain Mercurial operations (e.g. commit).
You can add to the set of trusted users with
I have been having this problem too, and like other posters the bug has
persisted to 0.8.3.1-1. So now I'm trying the packages from Lionel's
PPA (0.8.3.1-1ubuntu1~test2). I'll keep an eye open for more crashes...
--
xfce4-power-manager 0.8.2-1 crashed with signal 5 in
Public bug reported:
Binary package hint: mercurial
There appears to be an incompatibility between mercurial 1.0.1-2~hardy1
and python-subversion 1.5.1dfsg1-1ubuntu2 (both in hardy-backports).
Converting an svn repository to hg blows up:
$ hg convert /tmp/vchacks.svn /tmp/vchacks.hg
scanning
Workaround: download and install the Mercurial packages from intrepid:
wget
http://gulus.usherbrooke.ca/pub/distro/ubuntu/pool/universe/m/mercurial/mercurial-common_1.0.1-5.1_all.deb
wget
http://gulus.usherbrooke.ca/pub/distro/ubuntu/pool/universe/m/mercurial/mercurial_1.0.1-5.1_i386.deb
sudo
It looks like this is fixed in intrepid (1.0.1-5.1), while hardy would
still benefit from Suggests: python-subversion.
--
hg convert on Subversion repository fails (almost) silently unless
python-subversion installed
https://bugs.launchpad.net/bugs/233878
You received this bug notification
** Attachment added: proposed patch which simply tweaks the wording of the
offending comment in /etc/login.defs
http://launchpadlibrarian.net/16187244/ubuntu-bug-245210.patch
--
login.defs references libpam-umask which is a obsolete package
https://bugs.launchpad.net/bugs/245210
You
Public bug reported:
Binary package hint: mercurial
Using hg convert to convert a Subversion repository to Mercurial
requires python-subversion, but this requirement is not documented.
Example:
$ sudo apt-get remove python-subversion
[...]
$ svnadmin create /tmp/repo1
$ hg convert /tmp/repo1
FWIW, things have improved upstream: Mercurial 1.0 is now a bit more
verbose and reports that it cannot load the Python Subversion bindings
without --debug.
So IMHO all that needs doing to the Ubuntu package of Mercurial 0.9.5 is
add Suggests: python-subversion. That would certainly help.
--
Public bug reported:
Binary package hint: mail-notification
Attempting to install mail-notification fails like this:
# apt-get install mail-notification
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This
Public bug reported:
Binary package hint: slocate
I get this email from cron every morning:
From: Anacron [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Anacron job 'cron.daily' on gollum
Date: Tue, 05 Feb 2008 07:38:56 -0500
/etc/cron.daily/slocate: slocate: fatal error: load_file: Could
Same problem here: I installed hardy alpha 3 around 2008-01-13 20:30
+0500, and shortly after first booting and logging in, got the error
described above. My apt.log file ends with the line
ERROR:root:Dist-upgrade failed: 'E:Unable to correct problems, you have
held broken packages.'
which the
Easy workaround: as root, run apt-get dist-upgrade. That seems to
have successfully done the upgrade for me.
--
update-manager could not calculate the upgrade
https://bugs.launchpad.net/bugs/182703
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
47 matches
Mail list logo
