Thank you! I didn't know that this package existed. It's working now.
Should this bug marked as fixed?
--
binary nvidia 1.0.9631 crashes X on startup
https://bugs.launchpad.net/bugs/105928
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
ok. i've opened bug 105928
--
nvidia-glx-legacy driver crashes xorg on startup
https://bugs.launchpad.net/bugs/89290
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubunt
dmesg output
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/7301627/dmesg.log
--
binary nvidia 1.0.9631 crashes X on startup
https://bugs.launchpad.net/bugs/105928
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
xorg.conf
driver is changed to nv at the moment
** Attachment added: "xorg.conf"
http://librarian.launchpad.net/7301620/xorg.conf
--
binary nvidia 1.0.9631 crashes X on startup
https://bugs.launchpad.net/bugs/105928
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: linux-restricted-modules-2.6.20-14-generic
As suggested in bug 89290, I open a new report:
In march I had problems with a crashing X when using the binary nvidia driver
version 1.0.9631.
This was fixed when linux-restricted-modules dependency changed to
xorg log
** Attachment added: "Xorg.0.log.old"
http://librarian.launchpad.net/7301578/Xorg.0.log.old
--
binary nvidia 1.0.9631 crashes X on startup
https://bugs.launchpad.net/bugs/105928
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
Well the crash has reappeared with the update of linux-restricted-modules.
excerpt from aptitude.log:
[AKTUALISIERUNG] linux-restricted-modules-2.6.20-14-generic 2.6.20.4-14.15 ->
2.6.20.5-14.18
in the Changelog the downgrade of nvidia driver to version 1.0.9631 was
mentioned (before: 1.0.9755).
is fixed for me with today's xorg/nvidia related updates, don't know
which one. Excerpt from /var/log/aptitude (sorry in german):
Aptitude 0.4.4: Protokoll
Di, Mär 27 2007 19:49:50 +0200
WICHTIG: Dieses Protokoll zeigt nur geplante Aktionen an. Aktionen, die wegen
dpkg-Problemen fehlschlagen, sin
Same crash for me. I have nvidia-glx installed (no legacy).
X is working with the nv driver.
--
nvidia-glx-legacy driver crashes xorg on startup
https://launchpad.net/bugs/89290
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm on Kubuntu 6.10 with amarok 1.4.4.
My collection is on a local partition (reiserfs), so I guess it is not file
system dependant.
In the past moving (as in mv) the added files around triggered sometimes
an update. But at the moment I have no luck with this trick.
--
amarok: "Watch
Does not work for me.
I still have to run `sudo touch /var/cache/apt-index-watcher/*` every time I
notice the spikes in CPU load.
--
apt-index-watcher uses way too much system ressources
https://launchpad.net/bugs/64531
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
for me there is no syslog message from apt-index-watcher and the debtags
package is installed.
So this is no solution for me.
I run `sudo touch /var/cache/apt-index-watcher/*` every time I notice the
spikes in CPU load and this stops it. Very inconvenient.
--
apt-index-watcher uses way too much
see bug #69997 for new packages.
--
Attached file crashes OOWriter 2.0.4
https://launchpad.net/bugs/68219
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm, with these packages the crash doesn't occur anymore.
--
Openoffice becomes unstable with PNG images
https://launchpad.net/bugs/69997
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
For me too OpenOffice crashes when selecting pictures. I can confirm the crash
for the file attached by carsten.
In carsten's blog (http://cniehaus.livejournal.com/28878.html) someone
suggested to disable klipper, this does the trick, but is a rather bad
workaround for me, because I use klipper
I can confirm the regular peaks in CPU usage caused by apt-index-watcher. After
starting adept and closing it again (doing nothing with it) the peaks vanish.
If I can/should provide more information, let me know.
--
apt-index-watcher uses way too much system ressources
https://launchpad.net/bugs
Thank you, worked for me too.
--
Hang with 100% CPU usage while loading resources
https://launchpad.net/bugs/52105
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've installed edgy and I can confirm printing is not working in ECP mode.
Following message is repeated several times (from dmesg):
lp0: ECP mode
Apart from that nothing unusual in the logs.
--
HP LJ 1100 prints in EPP mode but not in ECP mode of the parallel port
https://launchpad.net/bugs/3312
18 matches
Mail list logo
