I'm not using Ubuntu but Arch and I'm affected by the same problem like Simon.
So it seems like to be an upstream bug.
I cannot reproduce the behaviour at all. It just randomly happens when
(quickly?) going through photo collections.
Picture are on the SSD with XFS. Going back and forth “fixes”
Public bug reported:
After the upgrade to 12.04, I am unable to link against the libblas.so
(and friends), libatlas.so (and friends), libcblas.so, libopenblas.so,
and other files. These are from different packages such as libblas-dev,
libatlas-base-dev, libopenblas-dev, etc. I do not know if this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993991
Title:
nm and ld cannot find symbols in libblas.so and other files
To manage notifications about this bug go to:
A few points:
1) I didn't file this bug against a specific package because I am not
able to identify the source. There are some Grub-related issues, but the
actual error message I see contains references to dbus and X11. I can
recategorize this ticket if somebody tells me where it belongs (or how
Public bug reported:
I just upgraded my system from 11.10 (running fine[1] for months, since
updating from 11.04 and 10.10 before that). The Upgrade appeared to go
fine with no obvious errors or warnings generated. However, when I
rebooted it, 12.04 would not load. I get some kind of dbus error
** Attachment added: my grub.cfg, showing Ubuntu 11.10 options
https://bugs.launchpad.net/bugs/991558/+attachment/3117719/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991558
Thanks for the confirmation, meanasspenguin! I tried a fresh install,
but the installer program did the exact same thing (randomly freezing)
three times in a row before I gave up. I've since downgraded to 9.04 for
now. If I work up the nerve to try the 9.10 upgrade again I will do a
custom kernel
It's been several days without so much as a confirmation that another
human has even read this report. In the interim, the state of my
computer has steadily decreased and is now essentially unusable. I
sincerely want to get this issue resolved not only so I can use the
system again, but so that
Here's the output of dmesg from this morning. Shows a similar event:
[ 61.044961] WARNING: at
/build/buildd/linux-2.6.31/arch/x86/kernel/check.c:134
check_for_bios_corruption+0xe5/0x100()
[ 61.044964] Hardware name: INVALID
[ 61.044965] Memory corruption detected in low memory
[
Here's my kern.log from this morning. A few interesting points:
11:02, BUG: unable to handle kernel paging request at
88008520. This started a long series of errors that say BUG:
scheduling while atomic: Xorg/1286/0x1001. Several of these popped
up between 11:02 and 11:04
11:04,
Public bug reported:
Binary package hint: ubiquity
Computer is Lenovo Y530, 64-bit Intel Core2 duo.
I upgraded to Karmic from Jaunty following the official release and my
system has become significantly less stable because of it. In Jaunty
there were absolutely no problems to speak of. Now in
I've attached my /etc/log/syslog. It contains some more information
General Timeline:
Last night (Nov 20th) the computer froze so I shut it off and went to bed. The
last entries on Nov20th should be around that time.
This morning, It froze several times, though I didn't keep track of when. This
Public bug reported:
Ubuntu 9.04 64 bit.
I have a 15 LCD screen with native resolution of 1280x800. However,
sometimes when I boot up the resolution is different. Two configurations
seem to be commonly misapplied:
1) 1 monitor with 1024x768 resolution
2) 2 monitors in Mirror Screens
Here's the log file (attached)
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/25699833/Xorg.0.log
--
Display changes resolution at bootup
https://bugs.launchpad.net/bugs/363330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
14 matches
Mail list logo
