Public bug reported:
To Reproduce
Steps to reproduce the behavior:
Install Ubuntu 20.10 with ZFS + native encryption in the installer
Upgrade the kernel with sudo apt update && sudo apt dist-upgrade
Reboot
I've tried this with 20.10 + ZFS without encryption, and I can't reproduce the
error. So
I uploaded the logs after logging into a gnome session immediately after
a crash. If it makes a difference, I'll see if I can collect logs after
logging into another KDE session following a crash (however, I'm
experiencing rather more severe problems with my linux installation at
the moment, so
Public bug reported:
Binary package hint: kde4libs
Unlike other bugs about kded4 crashes, this does not happen when running
updates. It also has just starting happening today for me. I'm not
sure what else I can include, since it appears to happen randomly,
ending my session and booting me
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/26510593/Dependencies.txt
--
kded4 crashes randomly, causing logout
https://bugs.launchpad.net/bugs/374214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: kde4libs
This appears to have been reported upstream. The problem reported there
is that pixmaps are inverted by color presumably due to endianness
issues. In my case, I can only confirm that desktop icons are inverted,
except when moused over. A
** Attachment added: inverted_icons1.png
http://launchpadlibrarian.net/26510857/inverted_icons1.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/26510858/Dependencies.txt
** Bug watch added: KDE Bug Tracking System #163028
I'm also still experiencing this issue. I've tried compiling from
source, as I'm running ppc and there aren't any binary PPAs for powerpc,
but without success so far.
--
packagekit says: The backend took too much time to process the synchronous
request - you need to fork!
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/26511753/Xorg.0.log
--
kded4 crashes randomly, causing logout
https://bugs.launchpad.net/bugs/374214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/26511784/Xorg.0.log.old
--
kded4 crashes randomly, causing logout
https://bugs.launchpad.net/bugs/374214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I just realized what probably caused this bug, given its recent
occurance. Per a workaround in bug #345542, I changed BusType to
PCI in xorg.conf in order to get DRI working. It doesn't seem like
this should cause X to crash, though.
--
kded4 crashes randomly, causing logout
** Attachment added: lspci
http://launchpadlibrarian.net/26511747/lspci
--
kded4 crashes randomly, causing logout
https://bugs.launchpad.net/bugs/374214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Further confirmation probably isn't necessary, but I've compiled and
tested 2.6.28.8 with success. Also, I've been having stability issues
with X since I've used the BusMode workaround, but I'm not sure yet if
they're related.
--
linux-image-2.6.28-5-powerpc has ioremap fault with radeon drm
Per a previous comment, I compiled a vanilla kernel (2.6.28.10) and DRI
works fine. I can also compile and test an earlier 2.6.28 release if
that would help isolate the issue.
--
linux-image-2.6.28-5-powerpc has ioremap fault with radeon drm module
https://bugs.launchpad.net/bugs/345542
You
Should this be tagged as regression-release, given that it now affects
jaunty as released?
--
linux-image-2.6.28-5-powerpc has ioremap fault with radeon drm module
https://bugs.launchpad.net/bugs/345542
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 345542 ***
https://bugs.launchpad.net/bugs/345542
** This bug has been marked a duplicate of bug 345542
linux-image-2.6.28-5-powerpc has ioremap fault with radeon drm module
--
[rv350] DRI fails; drm module complains about agp ioremap
I'm tagging this as regression-release, per the reports in the forum
thread (http://ubuntuforums.org/showthread.php?p=7178402) which have
confirmed that this is a regression from intrepid to jaunty.
** Tags added: regression-release
--
[rv350] DRI fails; drm module complains about agp ioremap
== Regression details ==
Discovered in version: Jaunty (2.6.28-6.20): main/devel
Last known good version: Intrepid (2.6.25-2.3): main/devel
--
[rv350] DRI fails; drm module complains about agp ioremap
https://bugs.launchpad.net/bugs/359839
You received this bug notification because you are a
== Regression details ==
Discovered in version: Jaunty (2.6.28-6.20): main/devel
Last known good version: Intrepid (2.6.25-2.3): main/devel
--
[rv350] DRI fails; drm module complains about agp ioremap
https://bugs.launchpad.net/bugs/359839
You received this bug notification because you are a
To check to see if your issue is similar (it's not going to be exactly
the same because I have a radeon card, instead of intel), look in your
dmesg (type 'dmesg' into a terminal to see this) for this line (or
something similar):
[ 31.423017] [drm:radeon_do_init_cp] *ERROR* could not find
I checked Xorg.0.log and that's exactly what it reports; thanks for
looking it over and explaining the discrepancy. I don't really
understand why it's a kernel bug, though, rather than a xserver-xorg-
driver-ati bug.
Would attempting a downgrade (or reinstalling) to collect log output on
a
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/25269952/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/25269953/CurrentDmesg.txt
** Attachment added: GconfCompiz.txt
http://launchpadlibrarian.net/25269954/GconfCompiz.txt
**
Public bug reported:
Binary package hint: compiz
glxinfo reports that direct rendering is enabled, and my graphics card
(radeon rv350) is whitelisted, but compiz aborts and falls back to
software rendering with the following output:
SKIP_CHECKS=yes compiz
Checking for Xgl: not present.
xset q
I'm experiencing this problem as well. If it would help for anyone
investigating this, I can upload debug info.
** Summary changed:
- hibernate/resume failure
+ hibernate/resume failure powerbook g4
--
hibernate/resume failure powerbook g4
https://bugs.launchpad.net/bugs/342031
You received
I found this link which appeared to supply the correct firmware (I'm connected
now):
http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2
The trick is to use the file wl-apsta-mimo.o instead of wl-apsta.o, when
extracting with b43-fwcutter.
--
package b43-fwcutter 1:011-5 failed
This bug still appears to exist in Jaunty; is there a status update?
--
On Kubuntu SimDock can't load the background
https://bugs.launchpad.net/bugs/195261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
25 matches
Mail list logo
