I have the suspicion that the problem was caused by the theme. Could we
add adium-theme-ubuntu as an affected package, to see if its maintainers
can think of something?
I'm really sorry for this rubbish bug report. All I have is the
screenshot, with no way to reproduce it or any relevant details.
Public bug reported:
Binary package hint: mountall
This is with up-to-date i386 lucid installed afresh from alpha 3.
I have just applied the latest update to plymouth (0.8.0~-13) and
rebooted. However, mountall can't run because it can't find
libplybootclient.so.2, so the boot process just hangs
Be careful when updating. I just did, rebooted and mountall couldn't
find some libplybootclient.so.2 library, so my laptop doesn't boot. I've
reported this as bug #538298. Wait for a matching mountall update before
updating (if I'm right to think that's the problem).
--
Plymouth text-mode splash
Just a brief note outlining how to get the computer booting again, in case
someone finds it useful. I assume that the APT cache contains the previous
plymouth packages:
- Boot from a live CD/USB stick
- Mount your / partition by selecting it under the "Places" menu
- Open a terminal
- Type:
sud
*** This bug is a duplicate of bug 538292 ***
https://bugs.launchpad.net/bugs/538292
This was a short-lived problem. The mountall update is already
available.
Still, shouldn't the plymouth update have been blocked by the
unavailability of the mountall update? I.e., shouldn't mountall have
dep
The update to mountall indeed fixes the problem. It's already in the
repositories for i386, but not for amd64 just yet. If you happen to run
into the problem as I did, the steps to get a booting system are in bug
#538298. Then just wait for mountall before updating plymouth.
--
Plymouth text-mode
@Tony: see bug #538298 (a duplicate of this) for one possible solution,
if you have a live CD/USB stick at hand.
--
Latest plymouth update makes lucid stop at startup
https://bugs.launchpad.net/bugs/538292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
> The plymouth 0.8.0~-14 package will enforce this upgrade by using
> Breaks:, but we need the new mountall built on all architectures
> first before uploading that.
Regarding this, assuming this problem was foreseen and not a human error
--which is what I understand from your comment--, is it not
*** This bug is a duplicate of bug 538292 ***
https://bugs.launchpad.net/bugs/538292
@Groening: see bug #538292 (of which this is a duplicate) for
alternative ways of fixing the problem.
--
Unable to boot: mountall can't find libplybootclient.so.2
https://bugs.launchpad.net/bugs/538298
You r
> We don't have a way to stop packages hitting the mirrors whilst still
> making them available as build dependencies to other packages we're
> building.
Ok. Perhaps the ability to flag certain builds as non-public would be
something to file a bug report for? (Against Launchpad, I guess?)
I under
*** This bug is a duplicate of bug 532047 ***
https://bugs.launchpad.net/bugs/532047
** This bug has been marked a duplicate of bug 532047
Plymouth text-mode splash causes X to crash on first run due to shared tty7
--
Terminal interface before GDM boots up.
https://bugs.launchpad.net/bugs
@Claudio: does X crash as described in this bug, or does plymouth simply
drop you to VT1 (with the desktop accessible by pressing Ctrl-Alt-F7)
without any crashing on pressing "2" or "Enter"? I get this on my
laptop, although not on my desktop. This is a different problem, though,
the present bug r
What I just described is covered by bug #538214, by the way.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
@teh603: probably because beta-1 is due this Thursday and devs can't
guarantee to get it fixed in 4 days. People running beta releases should
know their way out of trouble, or at least should read the "Known
Problems" section of the release notes before jumping in.
--
Booting with the framebuffer
@matt: no, it works on 32-bit just fine. This is the sources we are
dealing with, it should (and does) work on all architectures.
--
[LUCID] EEEPC-1201N missing RTL8192SE module required for wifi card
https://bugs.launchpad.net/bugs/530275
You received this bug notification because you are a memb
Ok, the problem definitely exists and is reproducible. Simply get
somebody to send you a message over MSN with an embedded newline in it
(e.g. "1[shift-enter]2[enter]"). The comment will *not* show in the
conversation. Additionally:
- If this message starts a conversation, no messages from your co
It would be very useful if somebody other than myself could confirm this
problem. The issue appears to be one of input handling/sanitation, which
ought to be relatively straightforward to fix.
--
Conversation lines misassigned in empathy
https://bugs.launchpad.net/bugs/535455
You received this bu
*** This bug is a duplicate of bug 546338 ***
https://bugs.launchpad.net/bugs/546338
Indeed.. Thanks!
** This bug has been marked a duplicate of bug 546338
receiving messages containing a newline do not show with the ubuntu theme
--
Conversation lines misassigned in empathy
https://bugs.
I'm affected too. See
http://launchpadlibrarian.net/40660364/Screenshot.png for another
screenshot.
If any devs want to try to reproduce this problem, please make sure
there are conversation lines *before* one with a newline in it, since
there's additional weirdness going on depending on whether t
Try aMSN for the other end, I can reproduce the problem that way on one
computer using two MSN accounts.
--
receiving messages containing a newline do not show with the ubuntu theme
https://bugs.launchpad.net/bugs/546338
You received this bug notification because you are a member of Ubuntu
Bugs,
Chances of an SRU with the fix?
--
receiving messages containing a newline do not show with the ubuntu theme
https://bugs.launchpad.net/bugs/546338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
@SKid: these parameters go in /etc/default/grub. Simply do:
- Press Alt+F2, enter "gksudo gedit /etc/default/grub" and press enter
- Change the line that reads
GRUB_CMDLINE_LINUX=""
to
GRUB_CMDLINE_LINUX="acpi_osi=Linux acpi_backlight=vendor"
- Save and exit
- Press Alt+F2, enter "gksudo
> last time I checked the workaround from #30 did only fix /playback/ on
this card.
That's one important piece of information. The fix from comment #30
starts to seem like a bad idea.
> I'd even like to record through pulseaudio from time to time. That
would probably depend on #52/53.
I can conf
Public bug reported:
Binary package hint: ubiquity
This is a feature request. The behaviour is as described as of Lucid
alpha 3 (as well as earlier versions), which comes with ubiquity 2.1.27.
In the manual partitioner included with the ubiquity installer,
selecting a partition and clicking "Cha
Ubiquity should check for the existence of the user's home directory. I
always upgrade Ubuntu by means of fresh installs, formatting my /
partition and leaving my /home partition untouched. Usually I'll move
/home/pablo to /home/pablo.old before doing that, but now upgrading to
lucid alpha 3 I forg
Note: bug #302638 would be fixed if the above proposal was implemented.
--
Ubiquity manual partitioner "Edit partition" dialogue could be improved
https://bugs.launchpad.net/bugs/533618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: xorg
Xorg fails to detect the resolution of the Samsung SyncMaster 920N
monitor. This has happened since Feisty at least. Now I am at Lucid
installed afresh from alpha 3.
The native resolution of the monitor is 1280x1024. Lucid assigns it
1024x768. Earli
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40390668/BootDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40390669/Dependencies.txt
** Attachment added: "GdmLog.txt"
http://launchpadlibrarian.net/40390670/GdmLog.txt
** Attachment ad
Public bug reported:
Binary package hint: gnome-terminal
This is a feature request - or rather a request for the reinstatement of
a feature which has (perhaps by accident) disappeared.
It used to be the case that gnome-terminal (up to 2.28.*) would
interpret the use of the scroll-wheel as cursor
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40391803/Dependencies.txt
--
Scroll-wheel not causing cursor moves in gnome-terminal any more after latest
updates
https://bugs.launchpad.net/bugs/533647
You received this bug notification because you are a member of Ubunt
As of lucid alpha 3 at least, the message displayed is
"Could not display "sftp://u...@host/path/to/folder";.
Error: Host key verification failed
Please select another viewer and try again."
Should we consider this bug fixed?
--
confusing error message when connection via ssh fails, because
@EvanCaroll: that's precisely what I was trying to report when I came
across this bug. However, this bug is specifically about the message
being uninformative, with the reporter even suggesting the current
wording that nautilus/gvfs uses. I found bug #418192 which refers
exactly to the issue at han
I've upstreamed this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=612103
** Bug watch added: GNOME Bug Tracker #612103
https://bugzilla.gnome.org/show_bug.cgi?id=612103
--
Nautilus can't open sftp location if public key is changed
https://bugs.launchpad.net/bugs/418192
You received this bu
Public bug reported:
blcr does not build against the linux-rt kernel (which is at 2.6.31-10
as of up-to-date lucid installed from alpha 3), complaining that symbol
__put_task_struct has not been defined.
If I am not mistaken, this causes dkms to refuse to automatically build
other modules - pleas
** Attachment added: "DKMSBuildLog.txt"
http://launchpadlibrarian.net/40466346/DKMSBuildLog.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40466347/Dependencies.txt
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to build again
** Attachment added: "config.log from the failed build"
http://launchpadlibrarian.net/40488236/config.log
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to build against linux-rt kernel
https://bugs.launchpad.net/bugs/534175
You received this bug notificati
> BLCR can in theory build against almost any standard 2.6.X kernel. I have
> no idea what -rt changes internally though.
It changes quite a few things across the kernel, as far as I know. I've
seen symbols being renamed between -generic and -rt before (e.g. there
was a problem with building the n
Public bug reported:
This oops just happened and I'm unsure as to whether there will be
system instability as a consequence. Running lucid installed afresh from
alpha 3.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: amd64
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40489791/Dependencies.txt
** Attachment added: "OopsText.txt"
http://launchpadlibrarian.net/40489792/OopsText.txt
--
[luxid] [linux-rt] BUG: scheduling while atomic: sirq-tasklet/1/0x0001/23,
CPU#1
https://bugs.lau
Public bug reported:
Binary package hint: xorg
I have this problem on both my desktop (nvidia card with proprietary
drivers, 64-bit install, both -generic and -rt kernels) and my laptop
(intel 945 card, 32-bit install, -generic kernel), both running lucid
installed afresh from alpha 3, and config
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40493102/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40493103/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40493104/Dependencies.txt
** A
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: xorg
I have this problem on both my desktop (nvidia card with proprietary
drivers, 64-bit install, both -generic and -rt kernels) and my laptop
(intel 945 card, 32-bit install, -generic ker
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40494572/CurrentDmesg.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, wh
apport information
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40494574/Dependencies.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, wh
apport information
** Attachment added: "GdmLog.txt"
http://launchpadlibrarian.net/40494578/GdmLog.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
apport information
** Attachment added: "GdmLog1.txt"
http://launchpadlibrarian.net/40494579/GdmLog1.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "GdmLog2.txt"
http://launchpadlibrarian.net/40494580/GdmLog2.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/40494581/Lspci.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
apport information
** Attachment added: "PciDisplay.txt"
http://launchpadlibrarian.net/40494583/PciDisplay.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/40494584/ProcCpuinfo.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/40494585/ProcInterrupts.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/40494586/ProcModules.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "RelatedPackageVersions.txt"
http://launchpadlibrarian.net/40494587/RelatedPackageVersions.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a membe
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/40494588/UdevDb.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/40494592/UdevLog.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "XorgLog.txt"
http://launchpadlibrarian.net/40494593/XorgLog.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "XorgLogOld.txt"
http://launchpadlibrarian.net/40494594/XorgLogOld.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "Xrandr.txt"
http://launchpadlibrarian.net/40494595/Xrandr.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
apport information
** Attachment added: "glxinfo.txt"
http://launchpadlibrarian.net/40494596/glxinfo.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "setxkbmap.txt"
http://launchpadlibrarian.net/40494599/setxkbmap.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "xdpyinfo.txt"
http://launchpadlibrarian.net/40494601/xdpyinfo.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
apport information
** Attachment added: "xkbcomp.txt"
http://launchpadlibrarian.net/40494613/xkbcomp.txt
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
The initial batch of files (attached by apport-bug) are from my desktop,
and the latter (attached by apport-collect) are from my laptop. That
should rule out some possible system-specific causes.
--
Xorg crashes on first run after boot at entering password
https://bugs.launchpad.net/bugs/534419
Y
Public bug reported:
Binary package hint: apport
This is on up-to-date lucid installed afresh from alpha 3.
When apport-collect is run, it makes Launchpad send a series of emails
titled "[Bug ] ". The title should be
"[Bug ] ". While this might seem a pedantic point,
it does make a difference if
** Attachment added: "CrashReports.txt"
http://launchpadlibrarian.net/40497222/CrashReports.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40497224/Dependencies.txt
--
apport-collect should use the bug title, not the attachment name
https://bugs.launchpad.net/bu
On lucid I can do
sudo apt-get install dpkg-dev
apt-get source linux-image-2.6.31-10-rt
On karmic the version is 2.6.31-9. Should be nearly the same kernel, I suppose.
However if you prefer wgetting the lucid tarballs, I believe the correct files
to fetch are:
http://archive.ubuntu.com/ubu
Ok, patch tested. The module compiles and loads correctly. It doesn't
load automatically on startup (is it supposed to?) but it loads with
modprobe afterwards, along with a "blcr_imports" module it pulls in.
I applied the patch by regenerating the diff so that dpkg-buildpackage
would accept it and
I meant I only loaded them.
Trying to run "make insmod check" under /var/lib/dkms/blcr/0.8.2/build
produces
/usr/bin/make --no-print-directory -C include
make[1]: *** No targets specified and no makefile found. Stop.
make: *** [modules] Error 2
so whatever that was supposed to do does not
Sorry, I should have realized there was stuff missing in the dkms build
directory. I've run the tests now, and the module passes them correctly:
PASS: atomics
SKIP: bug2524
PASS: cr_run
PASS: cr_targ
PASS: cr_targ2
PASS: cr_omit
PASS: dlopen
PASS: bug2003
PASS: run_on
PASS: save_exe
PASS: save_pri
> Alan is the Debian maintainer for the blcr package, but if he commits
> changes there they may not make it into Lucid this late, right?
I think he referred to the Debian freeze for 6.0, not the Ubuntu freeze
for 10.04, no?
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel mod
The bug is basically that when there is something to notify about multiple
contacts simultaneously or in quick succession, the pictures in the
notification bubble change but the contact names do not.
So, is it possible that the bug could actually be in the notify-osd Ubuntu
package? If I remember
> Probably there is a quirk for your monitor in the xserver which wasn't taken
> into the kernel.
I don't think so, my monitor was never supported correctly by the X
server either.
In trying to obtain an EDID dump with get-edid I come across this:
"The EDID data should not be trusted as the VBE
** Attachment added: "sudo get-edid 2>&1"
http://launchpadlibrarian.net/40566541/get-edid.txt
--
Samsung SyncMaster 920N monitor resolution not correctly detected
https://bugs.launchpad.net/bugs/533639
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "sudo ddcprobe"
http://launchpadlibrarian.net/40566553/ddcprobe.txt
--
Samsung SyncMaster 920N monitor resolution not correctly detected
https://bugs.launchpad.net/bugs/533639
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "sudo dmidecode"
http://launchpadlibrarian.net/40566573/dmidecode.txt
--
Samsung SyncMaster 920N monitor resolution not correctly detected
https://bugs.launchpad.net/bugs/533639
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Plus, the use of the term "Microblogging" in the messaging menu and of
"Broadcast" in the me-menu is inconsistent... The latter seems perhaps
more applicable.
--
In The Messaging Menu, a black-and-white icon should be used for the
Microblogging section
https://bugs.launchpad.net/bugs/533082
You
Public bug reported:
Binary package hint: indicator-me
This is with up-to-date lucid installed afresh from alpha 3.
The messaging menu contains the item "Microblogging" to launch gwibber,
while indicator-me contains "Broadcast accounts..." to configure
gwibber. This terminology is inconsistent.
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40569625/Dependencies.txt
--
Inconsistent terminology between indicator-me and messaging-menu:
"Microblogging" vs "Broadcast"
https://bugs.launchpad.net/bugs/534952
You received this bug notification because you are a memb
Sorry, done: bug #534952
--
In The Messaging Menu, a black-and-white icon should be used for the
Microblogging section
https://bugs.launchpad.net/bugs/533082
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
@arky: does this happen at random? Could this be bug #529229?
--
Show incorrect profile images in notifications
https://bugs.launchpad.net/bugs/522084
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
*** This bug is a duplicate of bug 529229 ***
https://bugs.launchpad.net/bugs/529229
** This bug has been marked a duplicate of bug 529229
no buddy icon or incorrect buddy icon for facebook
--
Show incorrect profile images in notifications
https://bugs.launchpad.net/bugs/522084
You receiv
*** This bug is a duplicate of bug 529229 ***
https://bugs.launchpad.net/bugs/529229
** This bug is no longer a duplicate of bug 522084
Show incorrect profile images in notifications
** This bug has been marked a duplicate of bug 529229
no buddy icon or incorrect buddy icon for facebook
I get something very similar on my laptop which has Intel 945GM
graphics. It also happens at random, but more often than not, I'm
afraid. I can switch to VT1 then to VT7, thus entering the desktop, but
if I try to use, say, update-manager, X will crash after entering the
password -- the same happen
Public bug reported:
Binary package hint: compiz
This is a feature request. Given the attention being paid to appearance
for Lucid I think it might be worth considering. I'm currently running
compiz 1:0.8.4-0ubuntu13 and I'm on 32-bit lucid installed afresh from
alpha 3.
There are two visual ele
> Can we confirm that a pristine daily-live desktop image of Lucid
> /won't/ work after modifying /usr/share/alsa/cards/ICE1712.conf as
> mentioned in comment #30 is /insufficient/ ?
I have just installed Lucid from the alpha 3 image, applied all updates and
tested the workarounds:
- The solution
> At this point we need to focus on minimizing the amount of code added to any
> upload (for easier verification), so if the additions from comment #30
> suffice by themselves, it makes more sense to use them.
My reason for preferring tweaking the udev/pulseaudio configuration over
tweaking ALSA's
The original icon looks a bit Gnome 1.x. I think it might be the black
border that makes it look odd.
Isn't there any other icon for this? E.g., a three-people icon (like the
icon for "Chat", smaller and repeated forming a triangle), or something
more suggestive of microblogging.
--
In The Messa
@Alessio: the kernel oops is not easy to trigger, it appears to happen
mostly at random, and I haven't encountered one in a couple of days.
That means that to test your kernel I would have to use it regularly for
a few days and report back if I don't see any oopses. I don't have any
problem with th
Answering myself, DKMS does take care of it, and the nvidia driver works
with this kernel.
I'll set this kernel as the default in /etc/default/grub, and I'll
report back in a few days if I don't bump into any oopses, or earlier if
I do. Thanks.
--
[luxid] [linux-rt] BUG: scheduling while atomic:
Ok, I've just had apport pop up with a "Serious kernel problem" (which I
assume is the oops) after running VirtualBox, but it would not produce a
report because it's not an official Ubuntu kernel, and I can't for the
life of me find the oops message under /var/log -- where is it supposed
to be repo
Ah, found the apport report. Attached. It was indeed the same oops, so
whatever the change is in this kernel, it's not helping. Unless you were
trying to address the tasklet problem specifically, in which case I
still haven't encountered any oopses to report.
** Attachment added: "linux-image-2.6.
> > life of me find the oops message under /var/log -- where is it supposed
> > to be reported?
>
> /var/log/kern.log
That was my first try and there was no relevant message there. What I
attached above is from /var/crash.
--
[luxid] [linux-rt] BUG: scheduling while atomic: sirq-tasklet/1/0x
I think this may have been fixed with notify-osd 0.9.27-0ubuntu1. From
the changelog "Small maintainance release to fix LP: #525546, so
appending works correctly.". Bug #525546 is about the body text of a
notification not being updated in certain situations, which would seem a
perfectly sensible re
Public bug reported:
Binary package hint: empathy
This is on up-to-date Lucid installed from alpha 3.
This bug has just happened once in several days of using empathy. See
the attached screenshot. On the left is the conversation window as it
was displayed during the conversation, and on the righ
** Attachment added: "Bug in conversation window, actual conversation in log"
http://launchpadlibrarian.net/40660364/Screenshot.png
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40659709/Dependencies.txt
--
Conversation lines misassigned in empathy
https://bugs.lau
> After a few hours use, it does appear better. I have not seen any
> incorrect buddy icons and when multiple buddies sign on/off the
> correct notification image and text are updated.
I'll flag notify-osd as fix released then.
> Facebook icons still do not always show in the notification when
>
As I said, I could not identify anything I did as a trigger.
--
Conversation lines misassigned in empathy
https://bugs.launchpad.net/bugs/535455
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Interesting.
- My Xorg.0.log.old file says that X session --which crashed-- was running on
VT7.
- The current Xorg.0.log file says the present, stable X session is running on
VT8.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/5320
The VT7 and VT8 I reported earlier were for my desktop (fresh 64-bit
install, binary nvidia driver, text-mode plymouth). My laptop (fresh
32-bit install, Intel 945GM, graphical-mode plymouth) also has VT7 for
the crashy session and VT8 for the working one according to the log
files.
Does anyone e
@ManhattanOS: not in my case. The patch sysvinit-utils received was
related to unkillable processes at shutdown, which seems unrelated. This
bug is somewhat intermittent -- how many times did you successfully
reboot cleanly into the desktop/login screen?
--
Plymouth text-mode splash causes X to c
201 - 300 of 770 matches
Mail list logo
