2.5 stopped working in Ubuntu Jaunty
Moderators: jesterKing, stiv
2.5 stopped working in Ubuntu Jaunty
I downloaded 2.5 on the release day and ran it several times without problem, trying to get used to the interface (I didn't use previous versions because I could never come to terms with it, but this looks to be a big improvement.)
After cosing it down this morning I tried opening it again and it just immediately shuts down. Sometimes you see an outline of a window as though trying to open but nothing ever fully appears.
Searching the Internet past problems have seemed to be video driver related though I have adjusted nothing there since I first installed Jaunty.
Steps taken to resolve.
Tried running it from the terminal - no difference
Deleted Blender folder and replaced with newly unpacked version - No difference
Re-downloaded 2.5 and started afresh - no difference
Downgraded nvidia drivers to 1.73. - no difference
Re-installed 1.8 drivers - no difference
Removed nvidia drivers altogether and relied on native drivers - no difference
Tried installing Blender 2.49 - Runs fine but 2.5 still refuses to run/
When running from the terminal I get a ';segmentation fault'
What I find strange is that it was running fine and now nothing..
Any other suggestions?
After cosing it down this morning I tried opening it again and it just immediately shuts down. Sometimes you see an outline of a window as though trying to open but nothing ever fully appears.
Searching the Internet past problems have seemed to be video driver related though I have adjusted nothing there since I first installed Jaunty.
Steps taken to resolve.
Tried running it from the terminal - no difference
Deleted Blender folder and replaced with newly unpacked version - No difference
Re-downloaded 2.5 and started afresh - no difference
Downgraded nvidia drivers to 1.73. - no difference
Re-installed 1.8 drivers - no difference
Removed nvidia drivers altogether and relied on native drivers - no difference
Tried installing Blender 2.49 - Runs fine but 2.5 still refuses to run/
When running from the terminal I get a ';segmentation fault'
What I find strange is that it was running fine and now nothing..
Any other suggestions?
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm
I have the exact same problem on Ubuntu 8.04
Downloaded, worked well a couple of times. Tried firing it up again and closed immediately. Tried starting it up wit Terminal and got a Segmentation Fult.
Still, it's looking really nice!
Cheers to all....
Downloaded, worked well a couple of times. Tried firing it up again and closed immediately. Tried starting it up wit Terminal and got a Segmentation Fult.
Still, it's looking really nice!
Cheers to all....
Joe Giampaoli
===============
Never tie a ship to a single anchor...
nor life to a single hope
===============
Never tie a ship to a single anchor...
nor life to a single hope
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm
Ok it fired up well with gdm, this is what I got from gdm (I closed blender o my own at the end):
joe@ghubuntu:~$ cd Desktop/blender-2.5-alpha0-linux-glibc27-i686/
joe@ghubuntu:~/Desktop/blender-2.5-alpha0-linux-glibc27-i686$ gdb blender
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb) run blender core
Starting program: /home/joe/Desktop/blender-2.5-alpha0-linux-glibc27-i686/blender blender core
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb67bd700 (LWP 3776)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb5f0ab90 (LWP 3779)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
found bundled python: /home/joe/Desktop/blender-2.5-alpha0-linux-glibc27-i686/.blender/python
[Thread 0xb5f0ab90 (LWP 3779) exited]
*bpy stats* - tot exec: 294, tot run: 0.0247sec, average run: 0.000084sec, tot usage 0.1143%
Saved session recovery to /tmp/quit.blend
joe@ghubuntu:~$ cd Desktop/blender-2.5-alpha0-linux-glibc27-i686/
joe@ghubuntu:~/Desktop/blender-2.5-alpha0-linux-glibc27-i686$ gdb blender
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb) run blender core
Starting program: /home/joe/Desktop/blender-2.5-alpha0-linux-glibc27-i686/blender blender core
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb67bd700 (LWP 3776)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb5f0ab90 (LWP 3779)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
found bundled python: /home/joe/Desktop/blender-2.5-alpha0-linux-glibc27-i686/.blender/python
[Thread 0xb5f0ab90 (LWP 3779) exited]
*bpy stats* - tot exec: 294, tot run: 0.0247sec, average run: 0.000084sec, tot usage 0.1143%
Saved session recovery to /tmp/quit.blend
Joe Giampaoli
===============
Never tie a ship to a single anchor...
nor life to a single hope
===============
Never tie a ship to a single anchor...
nor life to a single hope
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm
I had the same problem under Mac OSX 10.5.8
I runned Blender 2.5 for several times, I've tried to customize a bit the startup position of the windows and then, when I've tried to run it, nothing happened.. I get the colors wheel and then all close down.
The error I get in the console is:
found bundled python: /Applications/Blender/blender.app/Contents/MacOS/.blender/python
Bus error
logout
I runned Blender 2.5 for several times, I've tried to customize a bit the startup position of the windows and then, when I've tried to run it, nothing happened.. I get the colors wheel and then all close down.
The error I get in the console is:
found bundled python: /Applications/Blender/blender.app/Contents/MacOS/.blender/python
Bus error
logout
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm
This is what I get with -d:
joe@ghubuntu:~/Desktop/blender-2.5-alpha0-linux-glibc27-i686$ ./blender -d
Blender 2.50 (sub 7) Build
argv[0] = ./blender
argv[1] = -d
read file
Version 250 sub 7
ordered
OBCube
OBLamp
OBCamera
swin 1 added
swin 2 added
swin 3 added
swin 4 added
swin 5 added
swin 6 added
swin 7 added
swin 8 added
swin 9 added
swin 10 added
swin 11 added
swin 12 added
set screen
read file
Version 250 sub 0
found bundled python: /home/joe/Desktop/blender-2.5-alpha0-linux-glibc27-i686/.blender/python
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Operator'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Bone'
SRNA Subclassed: 'Context'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Mesh'
SRNA Subclassed: 'MeshEdge'
SRNA Subclassed: 'MeshFace'
SRNA Subclassed: 'Object'
SRNA Subclassed: 'PoseBone'
handle evt 0 win 0 op WM_OT_splash
Segmentation fault
joe@ghubuntu:~/Desktop/blender-2.5-alpha0-linux-glibc27-i686$
joe@ghubuntu:~/Desktop/blender-2.5-alpha0-linux-glibc27-i686$ ./blender -d
Blender 2.50 (sub 7) Build
argv[0] = ./blender
argv[1] = -d
read file
Version 250 sub 7
ordered
OBCube
OBLamp
OBCamera
swin 1 added
swin 2 added
swin 3 added
swin 4 added
swin 5 added
swin 6 added
swin 7 added
swin 8 added
swin 9 added
swin 10 added
swin 11 added
swin 12 added
set screen
read file
Version 250 sub 0
found bundled python: /home/joe/Desktop/blender-2.5-alpha0-linux-glibc27-i686/.blender/python
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Operator'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Bone'
SRNA Subclassed: 'Context'
SRNA Subclassed: 'Menu'
SRNA Subclassed: 'Mesh'
SRNA Subclassed: 'MeshEdge'
SRNA Subclassed: 'MeshFace'
SRNA Subclassed: 'Object'
SRNA Subclassed: 'PoseBone'
handle evt 0 win 0 op WM_OT_splash
Segmentation fault
joe@ghubuntu:~/Desktop/blender-2.5-alpha0-linux-glibc27-i686$
Joe Giampaoli
===============
Never tie a ship to a single anchor...
nor life to a single hope
===============
Never tie a ship to a single anchor...
nor life to a single hope
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm
Not stupid question at all, I did forget this time to copy it there, since I also have the 2.4 version, but I had alrady tried that and moving out the older .blender folder out of there. Tried again with the -d switch and all the output is the same, except for the line:
found bundled python: /home/joe/.blender/python
but still same error.
Older blender isn't installed system wide, so there should be no conflicts.
found bundled python: /home/joe/.blender/python
but still same error.
Older blender isn't installed system wide, so there should be no conflicts.
Joe Giampaoli
===============
Never tie a ship to a single anchor...
nor life to a single hope
===============
Never tie a ship to a single anchor...
nor life to a single hope
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm
I'm drawing straws ( figuratively )
1.) check your /tmp folder. erase any blend whatever files ( since it started up before it might have something to do here )
2.) try to start blender with "./blender 2>error.txt" see if anything definitive shows up in error.txt
3.) check error logs after failed start of blender. but after starting it normally without the " 2>error.txt"
4.) throw computer out the window ( use only if necessary )
1.) check your /tmp folder. erase any blend whatever files ( since it started up before it might have something to do here )
2.) try to start blender with "./blender 2>error.txt" see if anything definitive shows up in error.txt
3.) check error logs after failed start of blender. but after starting it normally without the " 2>error.txt"
4.) throw computer out the window ( use only if necessary )
-
- Posts: 0
- Joined: Sun Jul 02, 2006 10:01 pm