--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761039
Title:
package gir1.2-mutter-3.0 (not installed) failed to install/upgrade:
trying to overwrite '/usr/lib/mutter/Meta-3.0.typelib', which is als
Public bug reported:
Binary package hint: mutter
Auto reported.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: gir1.2-mutter-3.0 (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: am
Same problem here, confirmed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755159
Title:
Icon missing in notification area with Natty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Mysticzzz is right on target. I haven't had this problem with Ubuntu
10.04 (same router, same settings); now, upon installing the newer
release, me and a bunch of folks are getting these apt errors.
So much, for the SEVERAL people, I just talked in to installing
Maverick. I, at least thought we co
This may need to be fixed in GRUB(2), and how the kernels are complied.
Not just one.
If GRUB can get the correct UDMA mode from the drive, it needs to do
that; when it otherwise gives a "Invalid Magic Number", error.
The kernels need to be compiled with options like the older kernels(that
just w
Posted my solution over there at bug #613967.
--
[MASTER] syntax errors in /etc/default/grub break upgrades
https://bugs.launchpad.net/bugs/484499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
SOLUTION (myself) - Turn UDMA off, in my computers BIOS settings. (Dell
D8200 + Seagate 200GB PATA)
The question was, why this system, and not my other. If you're having
this problem, here's what fixed it, for me.
If not Grub (2) and not the kernel, then what's left? THE BIOS!
Once I started to
Going on 4 weeks...
1. The only action we took, was upgrading our clean-install of 10.04.
2. We expected the new kernel to boot.
3. "Invalid magic number" hangs the computer from booting to desktop,
everyday, unless the offending kernel is removed. Users must know to
select another kernel.
Whe
Thank you.
Upgrades today still leave that new kernel with the same error.
My second mission critical, AMD CPU computer, took the new kernel fine.
The subject error is on my first main computer; running a Dell P4 CPU.
Both computers are EXT4.
--
package linux-image-2.6.32-24-generic 2.6.32-24.3
Well duh!
1. Why isn't there an OPTION, for the keyring to be unlocked during an
auto-login; and that option be located anywhere where we SET up auto-
login?
2. Is this an easy to find choice, in the Administration menu?
3. Else, why isn't there an "Unlock keyring (your password database)
upon a
Now that I have grub-pc (GRUB 2) back completely, this newest kernel
(ending in -24) still will not boot (never has); yielding that latest
(original clean install 10.04) error of:
"Invalid magic number" after that GRUB 2 menu listed in selected.
Grub legacy didn't boot it either.
I'm guessing th
Are there any syntax errors here? ...-24, will not boot. ..-22
boot fine.
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
uuid8dcefa3c-cb54-4793-8fa6-e5587d9ab4ed
kernel /boot/vmlinuz-2.6.32-24-generic
root=UUID=8dcefa3c-cb54-4793-8fa6-e5587d9ab4ed ro qui
I understand and appreciate your effort, however, those guys solved
their syntax errors and that syntax error was never my problem, we just
had the same symptom. No new kernel boot. See bug #613967. I do need to
be in another bug report; besides either of these. If there's not one
already, we can s
Thank you. My post above at #2, answered those questions; as fully as possible.
This has thrown me into GRUB reinstall heck; but those failure bugs, are
another issue, accept to show that once with a working menu, this is probably
not a GRUB bug; because the new kernel still never boots (in GRUB
It's clear there was a syntax problem (this thread) and a solution that
worked; but did not work for my errors. My report, may be put back where
I started it, in another report, or in it's own. It's a separate error,
and perhaps not syntax, at all.
--
[MASTER] syntax errors in /etc/default/grub b
*** This bug is a duplicate of bug 484499 ***
https://bugs.launchpad.net/bugs/484499
I'm not seeing a syntax error and the "" one, is not the problem. Maybe
the status is wrong.
--
package linux-image-2.6.32-24-generic 2.6.32-24.39 failed to install/upgrade:
la subprocezo instalis skripton
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINU
That got me back up (from hell) through Grub (old kernel). I don't know
why changing 10 to 4 should trash Grub at is had no errors on sudo
update-grub.
My hope is, if someone can't boot at all, the last post will show them
how-to (edit with the live CD first, and then change root "update-grub"
aft
I'm coming at you from the live CD now.
I double checked /etc/default/grub and those quotes (that fix) are
already correct.
I thought I would sudo update-grub yet another time, and recheck again.
I saw that the countdown time was at 10, and I changed it to
4(preference). Yes, I am sure I did not
I see no syntax error, in grub lines, and if one has been found
somewhere(including source code), wouldn't upgrades, fix that by now?
I'm doing upgrades everyday.
--
[MASTER] syntax errors in /etc/default/grub break upgrades
https://bugs.launchpad.net/bugs/484499
You received this bug notificati
Note: fsck from live CD, was 100% OK, and still no boot, on the new
Lucid kernel.
This seems critical to me. New users would assume Ubuntu's upgrading,
just doesn't work. I fear, in 2020, we will still hear, "I tried that
stuff, in 2010 and it just crashed, with cryptic, black screen, text
message
I have package grub-pc 1.98-1ubuntu7, and still no boot on the new
kernel.
I completely removed new kernel, booted (with old one) and then
reinstalled new Kernel, linux-image, version 2.6.32-24.39. No errors
were seen.
Still, "Bad magic number"; at Grub.
It's been suggested that I do a fsck from
The newbie experience is:
"Bad magic number"
and
"load kernel first", at GRUB.
Newbie say huh?
They have to arrow down and select an older kernel, if they have one.
This looks bad. All we did was agree to the Upgrade Manger request.
--
package linux-image-2.6.32-24-generic 2.6.32-24.39 fail
I've been tracking this kind of problem for over a year. Now I'm on
Ubuntu (Gnome) 10.04 and running DigiKam upgraded. I can't seem to get
through a string of changes, in the Editor, without this manner of
crashing/lock-up; on either doing a process, Like Local Contrast, or
clicking OK to apply cha
sudo apt-get install gdm-2.20
E: Couldn't find package gdm-2.20
Didn't work; on current Ubuntu Lucid. FYI. May 1st.
--
login keyring does not get unlocked at login
https://bugs.launchpad.net/bugs/496253
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Well, now, I am testing (just upgraded) Karmic and it's Digicam. Upon
starting the "Restoration" and then immediately clicking the (try or trial)
"cancel", it acted (for a second) like it was going to freeze-up still; but
then it was fine. Maybe it has the correct libraries now, and a fix, I don't
Hey, WTH? This appears to be first filed in 2005. I also have clients
that are turning away from open software because they see this as a
serious (basic networking) OS flaw. What am I missing here?
--
Cannot create samba user with kcontrol samba module
https://bugs.launchpad.net/bugs/16575
You re
27 matches
Mail list logo