[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-06-09 Thread Apport retracing service
*** This bug is a duplicate of bug 332860 *** https://bugs.launchpad.net/bugs/332860 ** Attachment removed: CoreDump.gz http://launchpadlibrarian.net/23629274/CoreDump.gz -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received this bug

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-12 Thread Sebastien Bacher
*** This bug is a duplicate of bug 332860 *** https://bugs.launchpad.net/bugs/332860 ** This bug is no longer a duplicate of bug 334488 totem-gstreamer-video-thumbnailer crashed with SIGSEGV ** This bug has been marked a duplicate of bug 332860 nautilus crashed with SIGSEGV in

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-12 Thread SBKch
*** This bug is a duplicate of bug 332860 *** https://bugs.launchpad.net/bugs/332860 fixed -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
I can't attach backtrace and valgrind, because I don't know how to track new threads: (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] [New Thread 0xb6efe750 (LWP 20786)] [New Thread 0xb6c44b90 (LWP 20791)] Program exited normally. - gdb exits after

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
ok, adding backtrace, from attach to already running program ** Attachment added: backtrace http://launchpadlibrarian.net/23629804/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received this bug notification because you are a member

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem. ** Changed in:

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
As I said I cannot obtain valgrind for nautilus: ne...@nexem-desktop:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log nautilus ne...@nexem-desktop:~$ valgrind is exiting just after nautilus start ** Changed

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread Sebastien Bacher
that's because you have a nautilus already running, move the binary away and make a small nautilus wrapper which calls the real binary under valgrind ** Changed in: nautilus (Ubuntu) Status: New = Incomplete -- nautilus crashed with SIGSEGV in memset()

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
after long googling i was able to exit nautilus and open it with valgrind (gconf-editor-show_desktop-disable and then start valgrind) valgrind in attachment ** Attachment added: valgrind http://launchpadlibrarian.net/23631536/valgrind.log -- nautilus crashed with SIGSEGV in memset()

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
** Changed in: nautilus (Ubuntu) Status: Incomplete = New -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread Sebastien Bacher
that's a ffmpeg lib issue ==27091== Invalid write of size 1 ==27091==at 0x4028623: memset (mc_replace_strmem.c:493) ==27091==by 0x13CB999B: avcodec_default_get_buffer (string3.h:85) ==27091== Address 0x10307ebf is 0 bytes after a block of size 15 alloc'd ==27091==at 0x4024EFA:

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread Sebastien Bacher
that's a ffmpeg lib issue ==27091== Invalid write of size 1 ==27091==at 0x4028623: memset (mc_replace_strmem.c:493) ==27091==by 0x13CB999B: avcodec_default_get_buffer (string3.h:85) ==27091== Address 0x10307ebf is 0 bytes after a block of size 15 alloc'd ==27091==at 0x4024EFA:

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
That video is rather big (362mb), i will upload it on my server in few hours. I found other video that causes similar problem (crash when I try to open properties or play in totem): http://nexem.pl/filmy/efamv-rfad.mp4 -- nautilus crashed with SIGSEGV in memset()

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread Sebastien Bacher
could you read http://ffmpeg.org/bugreports.html and see if you can get a small video example to trigger the bug? -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
here is small example ** Attachment added: video example http://launchpadlibrarian.net/23659182/ffmpeg_crash_example.mp4 -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
*** This bug is a duplicate of bug 334488 *** https://bugs.launchpad.net/bugs/334488 ** This bug has been marked a duplicate of bug 334488 totem-gstreamer-video-thumbnailer crashed with SIGSEGV -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread Sebastien Bacher
*** This bug is a duplicate of bug 334488 *** https://bugs.launchpad.net/bugs/334488 do you get the crash using that small example? there is no image but not crash either using gst-launch or totem-gstreamer there -- nautilus crashed with SIGSEGV in memset()

[Bug 339854] Re: nautilus crashed with SIGSEGV in memset()

2009-03-09 Thread SBKch
*** This bug is a duplicate of bug 334488 *** https://bugs.launchpad.net/bugs/334488 yes, every time when i try to open properties of this example, or open it in totem nautilus/totem crashes -- nautilus crashed with SIGSEGV in memset() https://bugs.launchpad.net/bugs/339854 You received