This bug is still present in a fresh install of Ubuntu 20.04.1 LTS on a
Lenovo T510.
Nvidia driver is 340.108
The work-around mentioned in #73 is working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I got xsane running by copying the content of /usr/lib/x86_64-linux-
gnu/sane from the old Ubuntu 14.04 (64 bit) installation to the same
location in my Ubuntu 17.10 (64 bit) install.
According to
sane-config --version
the "old" libraries are from the release 1.0.23. (And the naming of the
see 2nd entry
** Package changed: xsane (Ubuntu) => sane-backends (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756201
Title:
xsane not aquiring images from Lide 30
To manage
Public bug reported:
Ubuntu 17.10, xsane 0.999
During the "searching for devices" phase I can hear the "usual" tick from the
scanner.
When I try to scan the error "Failed to start scanner: Error during
device I/O" occurs.
I can dual-boot my machine into Ubuntu 14.04 LTS with xsane 0.998.
I can also confirm the bug in Lucid.
I can connect (XP - Ubuntu 10.04) via an unencrypted or nearly
unencrypted (WEP) Ad-Hoc connection.
I noticed how the following fact, which might hint to the source of the
problem:
When I switch to WPA, the Ad-Hoc network an XP machine is listed as
A new variant of the bug is present in the CD install of 10.04 LTS:
On a freshly installed system, with the first user having an encrypted
home directory, the drop down list in Login Screen Settings for the
auto-login user is indeed blanked.
If a second user is added - also with an encrypted
I now have a definitve answer. I found the Maintanance and Service
Guide for my laptop. It reads: 32 MB of discrete video memory.
At least it shows, that lspci does not report the actual video memory,
and if the Xorg log doesn't report it either, answering this question is
non trivial.
The bug
I'm not sure where to look for the video ram size. I didn't find anything in
the Xorg log file.
lspci -v reports:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW
[Radeon Mobility 7500]
Subsystem: Compaq Computer Corporation Device 00b7
Flags: bus
Similar problem with blender 3D (2.49 and 2.50 alpha):
*WARN_ONCE*
File radeon_tcl.c function radeon_run_tcl_render line 499
Rendering was 138 commands larger than predicted size. We might overflow
command buffer.
*** This bug is a duplicate of bug 416001 ***
https://bugs.launchpad.net/bugs/416001
** This bug has been marked a duplicate of bug 416001
Notification and similar dialogs are displaying corrupted after update on
Karmic
--
gnome-system-monitor and notification area not readable without
Public bug reported:
Binary package hint: gnome-system-monitor
The first time I noticed that bug was during the pop-ups of the
notifier (connected to network, etc.). The attached file shows what
that looks like.
I get a similar pattern when I try to open the gnome-system-monitor.
When I
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36746138/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/36746139/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/36746140/ProcStatus.txt
** Attachment
** Attachment added: Notification area without compiz
http://launchpadlibrarian.net/36746428/notifier.png
--
gnome-system-monitor and notification area not readable without compiz
https://bugs.launchpad.net/bugs/496214
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 446632 ***
https://bugs.launchpad.net/bugs/446632
** This bug has been marked a duplicate of bug 446632
blender-bin crashed with SIGSEGV in GPU_state_init()
--
inkscape crashed with SIGSEGV in GC_malloc()
https://bugs.launchpad.net/bugs/492886
You
** Visibility changed to: Public
--
inkscape crashed with SIGSEGV in GC_malloc()
https://bugs.launchpad.net/bugs/492886
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I applied both patches against upstream version mesa_7_6.
Blender seems to work fine now.
Yeah!
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
No luck here. This patch is for r200 only. My laptop uses the radeon
driver.
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I have been told that there is no Ubuntu-Git repository, so the
bisection has been done against the mesa upstream repository
(http://cgit.freedesktop.org/mesa/mesa /
git://anongit.freedesktop.org/mesa/mesa).
As reported earlier the first bad commit is the
bfbad4fbb7420d3b5e8761c08d197574bfcd44b2
The analysis of the core dump did not look very informative (no
symbols). So I let blender-bin crash inside gdb. (The file named
blender is a shell script executing blender-bin).
Looks like the same bug to me.
There were new packages from xorg-edgers, today. This analysis was
performed using
Result of bisecting:
bfbad4fbb7420d3b5e8761c08d197574bfcd44b2 is first bad commit
commit bfbad4fbb7420d3b5e8761c08d197574bfcd44b2
Author: Pauli Nieminen suok...@gmail.com
Date: Fri Aug 28 04:58:50 2009 +0300
r100/r200: Share PolygonStripple code.
:04 04
Architecture: i386
DistroRelease: Ubuntu 9.10
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq Evo N610c (DD502A#AK8)
Package:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/36232628/BootDmesg.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/36232630/CurrentDmesg.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/36232631/Lspci.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/36232632/PciDisplay.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/36232633/ProcCpuinfo.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/36232634/ProcInterrupts.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/36232636/ProcModules.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/36232637/UdevDb.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: XorgConf.txt
http://launchpadlibrarian.net/36232639/XorgConf.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/36232640/XorgLog.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/36232638/UdevLog.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xrandr.txt
http://launchpadlibrarian.net/36232663/Xrandr.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: glxinfo.txt
http://launchpadlibrarian.net/36232664/glxinfo.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: XorgLogOld.txt
http://launchpadlibrarian.net/36232658/XorgLogOld.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: setxkbmap.txt
http://launchpadlibrarian.net/36232666/setxkbmap.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: xdpyinfo.txt
http://launchpadlibrarian.net/36232667/xdpyinfo.txt
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: xkbcomp.txt
http://launchpadlibrarian.net/36232669/xkbcomp.txt
** Tags added: apport-collected
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that downgrading helps.
I installed the following packages from the very first karmic versions
of mesa, skipping the binaries from the mesa packages that were not
already installed on my system:
libgl1-mesa-dri_7.4-0ubuntu3_i386.deb
libgl1-mesa-glx_7.4-0ubuntu3_i386.deb
Another blender version
** Attachment added: Blender 2.50, Karmic, ATI card
http://launchpadlibrarian.net/36199705/Bildschirmfoto-1.png
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member
Some sudo restart gdm later.
The latest version of mesa that Blender can run under is:
7.6.0~git20090817.7c422387-0ubuntu8
Window decoration looks ok now; still problems with notifier pop-ups.
Starting from 7.6.0-1ubuntu1 the segfault occurs.
--
blender-bin crashed with SIGSEGV in
I Installed the xorg-edgers pakets. No luck with blender. Still
segfaulting.
The onboard graphics card is a: ATI Technologies Inc Radeon Mobility M7
LW [Radeon Mobility 7500]
Is there a simple way to confirm which driver version is currently
running?
--
blender-bin crashed with SIGSEGV in
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/36128773/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36128774/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/36128775/Disassembly.txt
** Attachment
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/36129672/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36129673/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/36129674/Disassembly.txt
** Attachment
*** This bug is a duplicate of bug 488986 ***
https://bugs.launchpad.net/bugs/488986
** This bug has been marked a duplicate of bug 488986
inkscape crashed with SIGSEGV in GC_malloc()
--
inkscape crashed with SIGSEGV in GC_malloc()
https://bugs.launchpad.net/bugs/488974
You received this
Hi,
Apport retracing service schrieb:
tzdata: installed version 2009r-0ubuntu9.10, latest version:
2009s-0ubuntu0.9.10
x11-common: installed version 1:7.4+3ubuntu7, latest version: 1:7.4+3ubuntu10
Please upgrade your system to the latest package versions. If you still
How can I get
Same problem over here. Inkscape stopped working after update from 8.10
- 9.04.
I de-installed and re-installed inkscape - no change.
As you can see in the output of ldd, this is not the only library that
is missing
libMagick++.so.10 = not found
libWand.so.10 = not found
This would have been to good to be true.
No crash yet, but it seems that I can't enter RGB values 245 any
longer :(
So, this work-around is not even that... I hope it points at least to
the source of the problem.
--
[jaunty] libMagick++.so.10: cannot open...
Here is the word document that was used to create the screen shot.
** Attachment added: Word document with simple table
http://launchpadlibrarian.net/27378437/Test.doc
--
OOo Writer 3.01 und 3.1 do not read tables from MS word documents
https://bugs.launchpad.net/bugs/377989
You received
Same problem here. The bug is present in the 32 and 64 bit version of
Jaunty.
--
Broken package
https://bugs.launchpad.net/bugs/345208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: openoffice.org
After a recent update to Ubuntu Jaunty I discovered that tables from
Word documents were missing.
A search in this bug tracker revealed that there were various bugs
concerning WRITING tables in MS-Word format, this one is about READING
** Attachment added: tablegone.png
http://launchpadlibrarian.net/26902880/tablegone.png
--
OOo Writer 3.01 und 3.1 do not read tables from MS word documents
https://bugs.launchpad.net/bugs/377989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
I use a GPS mouse which sends its data in ASCII format via a bluetooth
serial link to my laptop. The bluetooth capability is provided by an USB
dongle. This worked under Hardy, it stopped working under Intrepid.
(Intrepid) Kernel: 2.6.27-7-generic #1 SMP
lsusb of the dongle:
This very much looks like a bug in the Linux graphics driver.
I.e. using a newer Blender version from blender.org might not help, but it's
worth a try.
But I'm happy to report, that since updating to Hardy Heron, this bug is
gone.
--
blender crashes on camera view
I can confirm this bug (freeze on camera view) under a non-beta Gutsy.
System here is a Compqa Evo N610c.
blender2.44-2ubuntu2
kernel: 2.6.22-14-generic
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW
[Radeon Mobility 7500] (prog-if 00 [VGA])
Subsystem:
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions
56 matches
Mail list logo
