I can confirm this. Installing the zodb modules basically does nothing,
as you can't use them once you have them. I tried copying the data
structure from gutsy to hardy to see if that would fix it and it
doesn't.
Annoying as this was working find in gutsy. Why change things if we are
going to c
Public bug reported:
After weeks of happily chugging along I made the gigantic mistake of
actually allowing you guys to update me again. I get burned by every
single one of these. They always break something.
So the new trick is the nvidia drivers. I was using Xinerama with dual
monitors and g
I'm running gutsy. I also reported Bug 153359 about the virtualbox update
failing. I applied the changes they recommended and then ran apt-get
upgrade. The new virtualbox install went fine and now the logout screen is
working fine.
On 10/16/07, unggnu <[EMAIL PROTECTED]> wrote:
>
> Please provi
Confirmed. This fixed the problem. Thanks!
On 10/16/07, albert <[EMAIL PROTECTED]> wrote:
>
> I had the same problem. I fixed it by editing the script
> /etc/init.d/vboxdrv and commenting out a line in the stop function:
>
> stop()
> {
> log_daemon_msg "Stopping VirtualBox kernel module" "$MOD
Public bug reported:
Binary package hint: virtualbox-ose-modules-2.6.22-14-generic
This update will not install. I get the error:
E: /var/cache/apt/archives/virtualbox-ose-
modules-2.6.22-14-generic_6_i386.deb: subprocess new pre-removal script
returned error exit status 1
I installed original
Public bug reported:
After the updates today, when I click the little running man in the top
right corner, or go to System->Quit the screen for logging out never
appears and the system completely freezes.
After that the only thing the system will respond to is a Ctrl-Alt-
Backspace to restart the
I am getting the same error. I am/was running the latest version of
gutsy everything up until this morning. I am running an intel box with
an nvidia graphics card and I receive this error running the updates
this morning:
E: /var/cache/apt/archives/virtualbox-ose-
modules-2.6.22-14-generic_6_i38
Public bug reported:
Binary package hint: gdm
I'm running with an nvidia card and 2 monitors using xinerama. After
the update to gdm it just crashes constantly saying "the launcher
crashed; attempting to use another one" or something like that. It
will just do this enlessly until I switch to a
i can confirm this bug.. its very annoying, someone please fix it
--
Can't unmount UUID= volume as a user
https://launchpad.net/bugs/71609
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 66376 ***
yes that is the entire contents of main.log
** This bug has been marked a duplicate of bug 66376
update-manager -c -d (can't find DistUpgradeViewGtk)
--
update-manager fails to upgrade from dapper to edgy
https://launchpad.net/bugs/67218
--
ubun
*** This bug is a duplicate of bug 66376 ***
Public bug reported:
I run gksu "update-manager -c -d" and it opens, checks for updates, then
tells me that edgy is available, so i click upgrade... it then begins to
download 2 files, once they are done downloading, it crashes and here is
the output:
i agree. bioapi needs to be supported and used more. also by working out
all the problems now, then once fingerprint readers are more widely
accepted, ubuntu will have full support with minimal bugs.
--
Edgy should include 'bioapi' to support fingerprint readers
https://launchpad.net/bugs/54816
same problem with ipw2915abg using knetworkmanager
it only works if iwconfig eth1 key restricted $wepkey
--
WEP Connection cannot be made
https://launchpad.net/bugs/48473
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
13 matches
Mail list logo