On some blog I found a workaround(?) for this:
In my xorg.conf I had the line
Option "BackingStore" "1"
which I edited to
Option "BackingStore" "0"
and now everything is fine.
You might give it a try.
--
system tray widget on desktop, icons disappear
https://bugs.lau
I see the same behaviour. I want to have the systray in an additional
Panel on the right side of the window. When I first inserted the control
there, everything was fine. But with the next login the trayicons don't
appear anywhere.
--
system tray widget on desktop, icons disappear
https://bugs.la
I can confirm this problem.
When logging in using KDE3 moneyplex works without a problem. It start's
up quite fast.
When logging in using KDE4 (same user) it takes a _long_ time to start
and all fonts are striked out in the login-screen (same as in that
bugreport on the Novell-Bugzilla).
I don't
I have the same problem with the upgrade to Kubuntu 7.10.
I noticed, that the segfault happend right after my memoryusage
skyrockets.
I have 1 GB of RAM. Right before the error-message the memory-usage
jumps from approx. 250MB to >1GB (using at least 250MB of swap).
I have two crash-log-files in
@Mike:
I just finished upgrading via the "aptitude -v dist-upgrade" path.
I had similarly longish outputs by aptitude, and I had to run "aptitude
dist-upgrade" 3 or 4 times, but now my system is up and running Gutsy.
Only problem I had was, that I had to reinstall the restricted-modules
as the nv
@Mike
This update comes from the gutsy-proposed repository which you had to
enable to do the upgrade.
If you disable this, the proposed (as in "not yet finalized") updates
won't be installed.
So this is probably not really connected to the problem with the
"existing but not really existing" up
Public bug reported:
Binary package hint: kdelibs
Apport informed me of this crash after logging into KDE. Was probably on
shutdown, but I'm not sure of this.
ProblemType: Crash
Architecture: i386
Date: Thu Apr 12 12:55:18 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/kdeinit
Package:
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/7316832/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7316833/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/7316834/Disassembly.txt
** Attachm
The last upgrade I did was 25th november. Actually it was my father who
finally got the message that theres an upgrade available. He startet the
upgrade. Fortunately I saw what he was doing and kept an eye on the
upgrade-process. Because as with every other Kubuntu I upgraded, this
debconf-bug
Public bug reported:
Binary package hint: grub
I had this Setup:
/dev/hda1-> Windows XP
/dev/hda2-> leftover /boot from an old Gentoo
/dev/hda3-> Swap
/dev/hda4-> / of a Kubuntu 7.04 (originally 5.10, continually updated)
I needed to reinstall Windows. After that I wanted to rein
Just seconds after posting this bug, a friend had the right idea (which
I seem to remember having read somewhere else before but ignored):
Instead of running
install (hd0)
doing
install --force-lba (hd0)
did the trick.
I'm 100% sure that I never needed to do this before, but the last gr
** Changed in: grub (Ubuntu)
Status: Unconfirmed => Rejected
--
Grub not reinstallable after installing Windows
https://bugs.launchpad.net/bugs/120020
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
I'm sorry, I cannot say much more than what I wrote in the original
report.
It's possible, that Kontact was running, and as I only use
IMAP4-Accounts that would confirm your guess.
Other than that I don't know anything helpful.
--
[apport] kdeinit crashed with SIGSEGV in
QValueListPrivate::~QV
So this is the reason for mdadm being installed?
I kept wondering why I have to have a raid-manager when I don't have or
plan on having a raid in my system. :/
What is the reason for this dependency? Why does every user, with or
without raid-systems, get this? These
W: mdadm: /etc/mdadm/mdadm.co
Ok, the problem with the missing restricted modules was fixed over night
(german time). So I'm running a working and finished Edgy Eft Beta 3
system now.
All in all: The upgrade-tools worked like a charm. _VERY_ nice that
ya'll thought of us "kde-latest"-users. :)
Here now my list of things I not
I'd advise to run a few cycles through "get updates" and "full upgrade"
in adept. This fixed it for me.
--
SRU: updates necessary for Kubuntu Upgrade Tool in Edgy
https://launchpad.net/bugs/84717
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
I did an update on my laptop today, which went more or less smoothly. I
had a few comments, which I conveniently left on my desk at work.
What I do remember is, that the kernel was upgraded to 2.6.20-13 which
caused unresolvable errors with the restricted-modules package. That
only exists in versi
As far as I could see today there are no restricted drivers for the
linux-image 2.6.20-13. Only 2.6.20-12 does exist.
This doesn't happen for the first time (not all kernel-packages updated
at the same time). How can this slip?
--
7.04 beta upgrade: proprietary driver in use, but not upgraded ->
Public bug reported:
This bug behaves similar to #538524 but happens with the released
version.
After the upgrade from 9.10 to 10.04 everything was ok at first. But
after a few reboots the system did not come past the splash screen
anymore.
[ctrl]-[alt]-[F1] doesn't do anything. [ctrl]-[alt]-[de
I have no idea when it was fixed. Neither do I know what fixed it. But
today I just tried booting with "quiet splash" switches. And it worked.
I hope this is not just "by chance".
--
Boot hangs at splashscreen, KDM doesn't show up
https://bugs.launchpad.net/bugs/573216
You received this bug noti
Problem is so old. I have no idea if the above mentioned fix was the
cure, or something else. Should be closed as fixed.
** Changed in: intrepid-backports
Status: New => Fix Released
--
moneyplex does not start under KDE4.1
https://bugs.launchpad.net/bugs/255870
You received this bug noti
I just had this very same issue after installing Jaunty from the
alternate disk and afterwards switching to grub (I hate LILO).
I just today found that there were these two lines missing in the file
/etc/kernel-img.conf:
postinst_hook = update-grub
postrm_hook = update-grub
I have no idea where
So, since the r8168-dkms package that is shipped with 14.10 does not
work with the kernel shipped with 14.10, is there any chance, that this
package will be updated to a working version?
Since the r8169 module continuously crashes when handling heavy load
(and I've experienced this behaviour with
This bug caused my machine to be completely offline after upgrading to
13.04. Thanks to the patch posted by tomcsi I could at least manually
enter the changes (reading them from my phone).
How could this bug not be a blocker for 13.04? The r8168-dkms package
worked in 12.10, now it plain doesn't.
*** This bug is a duplicate of bug 1108068 ***
https://bugs.launchpad.net/bugs/1108068
** This bug has been marked a duplicate of bug 1108068
r8168 fails to install in kernel 3.8.0-1 and 3.8.0-2 [error: expected ‘=’,
‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘rtl8168_init_board’]
--
You
This bug left my system without network access after the upgrade to
13.04. Lucky me, that I had a phone with wich I found bug #1156283 and
the patch attached there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I'm using Kubuntu 10.04 with the backports-ppa (KDE SC 4.5.1). kopete-
gcall is not installed as either a dependency for kdenetwrok or for
kopete. I needed to install it manually.
After manual installation of kopete-gcall I could find googletalk-call
in /usr/bin.
What I find disturbing is, that k
I'm currently seeing this issue on my fathers computer.
After starting 4.18.0-14 the screen goes blank and nothing seems to
happen anymore. Booting wiht 4.18.0-13 works without issues.
I noticed, that after some time I can SSH into the machine. So I dumped
dmesg with 4.18.0-14 and 4.18.0-13. I'll
** Attachment added: "dmesg output for working kernel 4.18.0-13"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5236563/+files/dmesg_4.18.0-13.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Uhm... Sorry for that, I seem to have triggered some keyboard shortcut.
To continue:
1. Additional line in 4.18.0-14
Line 355: [0.034459] Spectre V2 : Spectre v2 cross-process SMT mitigation:
Enabling STIBP
2. Additional line in 4.18.0-14
Line 590: [0.124079] pci :00:02.0: BIOS left
** Attachment added: "dmesg output for failing kernel 4.18.0-14"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5236564/+files/dmesg_4.18.0-14.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
@Khaled El Mously: I could try your kernels tomorrow (I hope). Can you
please tell me which packages I'd need to install? That's quite a list
of files there. ;)
I'm currently guessing the packages with these "base-names":
linux-headers-4.18.0-14
linux-headers-4.18.0-14-generic
linux-image-unsigned
I just stumbled across Bug #1814555
That looks like the exact same problem (i915 driver causing the boot to
fail). They even identified the same source commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I just stumbled across this relic. This bug is so old, it's petrified.
So it should probably be closed. How can I do that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968543
Title:
nepomukservices
@Stefan Bader: I just installed the kernel from comment #8 and can
confirm that it boots without issues.
I'm looking forward for this to hit the repositories, because currently
apt won't install anything anymore until I fix the "broken installs"
(reinstall the official kernel).
--
You received t
Sorry for this OT discussion, just to explain my comment:
I had to "dpkg --force-depends -r linux-image-4.18.0-14-generic" because
otherwise dpkg did not allow me to install the "unsigned" package from
the link above. Now apt tells me, that the dependencies are borked and I
need to use "--fix-brok
36 matches
Mail list logo
