I found that the latest drm-tip kernel for amd64 was at
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2019-11-08/ as
the more recent ones had failed to compile according to the READMEs.
The 2019-11-08 kernel (5.4.0-994-generic) boots fine, but after logging
in, running a GUI application
Public bug reported:
After upgrading from Kubuntu 19.04 to Kubuntu 19.10, when I open
articles in tabs inside Akregator, the tabs crash.
For example, when I open the URL https://www.lifesitenews.com/news
/abortionists-ripped-out-beating-hearts-for-research-baby-parts-
testimony-reveals
Reported by e-mail to recipients listed in comment 6. Here's a link to
the post in the archive of the Linux Foundation virtualization mailing
list:
https://lists.linuxfoundation.org/pipermail/virtualization/2019-August/043083.html
--
You received this bug notification because you are a member
Sorry for the spam. I'm not used to those Ubuntu bug reporting tools.
I've been running 5.2.0-050200rc1-generic ever since the suggestion to
try the mainline RC. This bug did not re-occur until now. Here is a new
dmesg.
** Attachment added: "Output of "dmesg" after the hang with mainline
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1813620/+attachment/5281284/+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/1813620
apport information
** Tags added: apport-collected disco
** Description changed:
The graphical environment seems to hang when scrolling web pages in
Firefox. Can't reliably reproduce during every scrolling, but it has
happened at least 5 times in the past 7 days. Happens in Kubuntu VM-s
Still happens with 5.1-rc7.
[175938.066756] INFO: task Xorg:903 blocked for more than 120 seconds.
[175938.074630] Not tainted 5.1.0-050100rc7-generic #201904282131
[175938.094726] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[175938.100947] XorgD
This still occurs with 19.04 (Disco Dingo) and kernel 5.0.0-13-generic,
and does not seem to be Firefox specific. I've also had this crash when
using some KDE apps. This issue seems to occurs at 2-3 times a day on
frequent use, each time requiring a forced reboot to fix (because Ubuntu
never
Public bug reported:
The graphical environment seems to hang when scrolling web pages in
Firefox. Can't reliably reproduce during every scrolling, but it has
happened at least 5 times in the past 7 days. Happens in Kubuntu VM-s
running under KVM and QEMU (3.1.0) on multiple host machines.
This
Same issue on Gentoo Linux and Kubuntu 14.04 with a Canon PIXMA MG7150
printer.
** Also affects: gentoo
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729054
which is fixed Debian.
** Bug watch added: Debian Bug tracker #729054
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729054
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729054
which is fixed Debian.
** Bug watch added: Debian Bug tracker #729054
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729054
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Ok, nevermind. This seems to be another issue. Namely for some reason
/home fails to mount at boot for some reason: The disk drive for /home
is not ready yet or not present. Continue to wait; or press s to skip
mounting or M for manual recovery. The workaround appears to be to
delete all LVM
The users complained that the issue re-occurred today. I remotely
upgraded the system yesterday (apt-get dist-upgrade), so its very likely
something in the upgrade process broke the system again. They will
transport me the machine today, so I will have physical access. If we
don't manage to fix it
I will confirm this from the logs when I get access to the machine, but
if I remember correctly, at least one of the updates was to libc, just
as the previous time this happened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried several reboots and several shutdowns all of which succeeded.
The issues started on January 20, after the system updates on January
19. I don't know how the Ubuntu startup system (Upstart) works, but my
guess is that one of those updates caused the race, and a subsequent
update caused the
The release notes of 0149 do not state any significant fixes which could
be related. Since this is a physically remote desktop machine I'm
administering, I don't have physical access to the machine before
February 4rd.
The main user of the machine is a non-technical person and has become
very
Public bug reported:
The user is sometimes also getting display corruption and kernel
panics/lockups with X (no logs saved on disk). The trace in the kernel
log seems to happen every time on boot.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-44-generic 3.13.0-44.73
** Attachment added: dpkg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302530/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Title:
** Attachment added: term.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302532/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Title:
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302531/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1412671
Title:
[14.04]
/var/log/upstart excluding the ureadahead logs which contained sensitive
information.
** Attachment added: var-log-upstart.tar.xz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412671/+attachment/4302533/+files/var-log-upstart.tar.xz
** Information type changed from Public to Private
I can attach the logs, but please note that these do not cover the
events of the unsuccessful bootups, because / was mounted as read-only
and hence no logs were saved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
One of these upgrades yesterday resulted in an unbootable system:
2015-01-19 20:32:45 upgrade libc-dev-bin:amd64 2.19-0ubuntu6.4 2.19-0ubuntu6.5
2015-01-19 20:32:47 upgrade libc6-dev:amd64 2.19-0ubuntu6.4 2.19-0ubuntu6.5
2015-01-19 20:32:48 upgrade libc6-dbg:amd64
Public bug reported:
One of these upgrades yesterday resulted in an unbootable system:
2015-01-19 20:32:45 upgrade libc-dev-bin:amd64 2.19-0ubuntu6.4 2.19-0ubuntu6.5
2015-01-19 20:32:47 upgrade libc6-dev:amd64 2.19-0ubuntu6.4 2.19-0ubuntu6.5
2015-01-19 20:32:48 upgrade libc6-dbg:amd64
I remembered that another error message during boot was something about
being unable to mount /home. Since there was nothing in the logs, I
think that the boot process failed before properly mounting filesystems
from /etc/fstab.
--
You received this bug notification because you are a member of
I can confirm that this does affect BibleTime 2.9.2 on Kubuntu 14.10
beta 2, but DOES NOT affect Sword 1.7.3 and BibleTime 2.10.1 built from
source on the same setup. Note that BibleTime 2.9.* is no longer
supported by upstream.
--
You received this bug notification because you are a member of
I just ran into a similar problem today with
libusb-0.1-4=2:0.1.12-14ubuntu0.1. The printer just stopped printing
after upgrading from libusb-0.1-4=2:0.1.12-14 and rebooting. Downgrading
to libusb-0.1-4=2:0.1.12-14 fixed this issue after reboot. Is this the
same bug?
--
after the last updates
28 matches
Mail list logo
