This bug is no longer relevant as beryl has been replaced by compiz-
fusion.
Adam Niedling wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is thi
anks aOliNeX.
>
> nixnoob, since you are the original bug reporter, can you confirm if
> this is resolved for you with the newer Intrepid kerenl? Intrepid's
> Beta release came out today -
> http://www.ubuntu.com/testing/intrepid/beta . Thanks.
>
>
--
X won't start in Feist
After hitting Close on the window, having finished the report, I tried
to open Add/Remove Programs from the Kmenu, and got a window with the
following: Another process is using the packaging systme database
(probably some other Adept application or apt-get or aptitude). It asked
me if I would like
Public bug reported:
Binary package hint: update-manager
I am using Kubuntu 7.10, with the 2.6.22-14-generic kernel. I am dual
booting Kubuntu along with Widows XP on my HP dv5020us laptop, and just
recently upgraded via dvd from Feisty. While attempting to upgrade to
the new 8.04 Beta, following
** Attachment added: "lsb-release, apt.log, main.log"
http://launchpadlibrarian.net/12828705/update_crash.log
--
Upgrade Tool Crashed
https://bugs.launchpad.net/bugs/205672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
can you guys try commenting out eth0 from /etc/network/interfaces on my
system I get the lockup if I bring up whilel eth0 is already up, if I
down eth0 and bring up ra0 it does not crash.
--
kernel lockup on feisty because of rt61 driver
https://bugs.launchpad.net/bugs/91192
You received this bug
possibly related to my issue, if eth0 is up and ra0 is brought up the
system get soft lockup, try removing either of these entries from
/etc/network/interfaces and see if the crashing persists.
--
[rt61] Lockups running Feisty on x86-64
https://bugs.launchpad.net/bugs/90243
You received this bug
I've determined the source of the crash... the crash comes from the rt61
driver, if eth0 and ra0 are both up at the same time the system crashes.
because network-manager attempts to bring up both interfaces for
configuration (assumption) it causes the same crash.
--
X won't start in Feisty, MS-10
Public bug reported:
Binary package hint: beryl-plugins-unsupported
beryl-plugins-unsupported is broken
sudo apt-get install beryl-plugins-unsupported #returns the following
error:
[EMAIL PROTECTED]:~$ sudo apt-get install beryl-plugins-unsupported
Password:
Reading package lists... Done
Build
Also, now that I've found the solution and setup my system I would like
to avoid breaking it further by reinstalling the problem package if at
all possible. On the other hand I would love to be helpful I just want
to make sure that the log file will actually be there in this situation
so I don't c
Would /var/log/kern.log or dmesg contain any significant information
after a failed boot? The only way for me to do this would be to
reinstall network-manager and reboot. I would then get the crash and
would be forced to power the box down physically with the hard button
and boot into recovery mo
Removing network-manager completely solved my problem, the alternate
login screen I was getting was my own fault there must be a problem
with that package... tenthconcept, judging by the log file in your post
I doubt that our problems are related, but I'm no expert
--
X won't start in Feisty,
Update: removing network-manager allows some sort of graphical login,
however its asking for a host? I'm not sure what this is and how to get
the normal login screen? Ctrl+Alt+F1 allows me to drop to console and
startx... only after stopping gdm...What is this new hell I'm in?
--
X won't start
I was just thinking, maybe since Edgy worked and single user mode works
in Feisty perhaps its an issue with the new X and permissions?
--
X won't start in Feisty, MS-1039 Laptop
https://bugs.launchpad.net/bugs/106626
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
X won't start on my MS-1039 laptop with Feisty. Both the x86 and a64
beta live CD's of Feisty produce the same problem: Just before X
starts I get "Soft Lockup Detected on CPU#0". Furthermore, I get the
same problem with the daily live CD. Even furthermore upgrading Edgy
15 matches
Mail list logo
