On Sat, Mar 3, 2012 at 8:20 AM, Sebastien Bacher <email address hidden> wrote:
> Thank you for your bug report, I can't confirm that here, could somebody
> having the issue:
> - install nautilus-dbg (and maybe the glib and gtk dbg as well)
> - run "nautilus --quit"
> - run "G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
> --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
> nautilus"
>
> trigger the issue
>
> add valgrind.log to the bug report
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/944624
>
> Title:
> nautilus crashed with SIGSEGV in mainloop_proxy_func()
>
> Status in “nautilus” package in Ubuntu:
> Confirmed
> Status in “nautilus” source package in Precise:
> Confirmed
>
> Bug description:
> This occured when coping a file from documents to UbuntuOne after
> upgradeing ubuntu 12.04 Beta this morning. One upgrade was to Nautilus, the
> copy seems to have completed (I'll know when I check my other computer
> later).
> John
>
> TEST CASE:
> 1. Launch nautilus
> 2. Select a file
> 3. Copy/Paste the file; CTRL+C/CTRL+V
>
> ACTUAL RESULT:
> This crash
>
> EXPECTED RESULT
> The file is copied without a crash
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: nautilus 1:3.3.90-0ubuntu4
> ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
> Uname: Linux 3.2.0-17-generic x86_64
> ApportVersion: 1.93-0ubuntu2
> Architecture: amd64
> Date: Fri Mar 2 08:10:59 2012
> ExecutablePath: /usr/bin/nautilus
> GsettingsChanges: org.gnome.nautilus.window-state geometry
> '800x550+53+188'
> ProcCmdline: nautilus -n
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7f3290fa43bf: mov %eax,0x8(%rbx)
> PC (0x7f3290fa43bf) ok
> source "%eax" ok
> destination "0x8(%rbx)" (0x7f3200000008) not located in a known VMA
> region (needed writable region)!
> SegvReason: writing unknown VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
> UpgradeStatus: Upgraded to precise on 2012-03-01 (0 days ago)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/944624/+subscriptions
>
On Sat, Mar 3, 2012 at 8:20 AM, Sebastien Bacher <email address hidden> wrote:
> Thank you for your bug report, I can't confirm that here, could somebody always- malloc G_DEBUG=gc-friendly valgrind -v valgrind. log /bugs.launchpad .net/bugs/ 944624 proxy_func( ) ature: Ubuntu 3.2.0-17.27-generic 3.2.6 nautilus. window- state geometry x86_64- linux-gnu/ libgio- 2.0.so. 0 context_ dispatch () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 64-linux- gnu/libglib- 2.0.so. 0 context_ iteration () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 x86_64- linux-gnu/ libgio- 2.0.so. 0 context_ dispatch( ) /bugs.launchpad .net/ubuntu/ +source/ nautilus/ +bug/944624/ +subscriptions
> having the issue:
> - install nautilus-dbg (and maybe the glib and gtk dbg as well)
> - run "nautilus --quit"
> - run "G_SLICE=
> --tool=memcheck --leak-check=full --num-callers=40 --log-file=
> nautilus"
>
> trigger the issue
>
> add valgrind.log to the bug report
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> nautilus crashed with SIGSEGV in mainloop_
>
> Status in “nautilus” package in Ubuntu:
> Confirmed
> Status in “nautilus” source package in Precise:
> Confirmed
>
> Bug description:
> This occured when coping a file from documents to UbuntuOne after
> upgradeing ubuntu 12.04 Beta this morning. One upgrade was to Nautilus, the
> copy seems to have completed (I'll know when I check my other computer
> later).
> John
>
> TEST CASE:
> 1. Launch nautilus
> 2. Select a file
> 3. Copy/Paste the file; CTRL+C/CTRL+V
>
> ACTUAL RESULT:
> This crash
>
> EXPECTED RESULT
> The file is copied without a crash
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: nautilus 1:3.3.90-0ubuntu4
> ProcVersionSign
> Uname: Linux 3.2.0-17-generic x86_64
> ApportVersion: 1.93-0ubuntu2
> Architecture: amd64
> Date: Fri Mar 2 08:10:59 2012
> ExecutablePath: /usr/bin/nautilus
> GsettingsChanges: org.gnome.
> '800x550+53+188'
> ProcCmdline: nautilus -n
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7f3290fa43bf: mov %eax,0x8(%rbx)
> PC (0x7f3290fa43bf) ok
> source "%eax" ok
> destination "0x8(%rbx)" (0x7f3200000008) not located in a known VMA
> region (needed writable region)!
> SegvReason: writing unknown VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> ?? () from /usr/lib/
> g_main_
> ?? () from /lib/x86_
> g_main_
> g_application_run () from /usr/lib/
> Title: nautilus crashed with SIGSEGV in g_main_
> UpgradeStatus: Upgraded to precise on 2012-03-01 (0 days ago)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To manage notifications about this bug go to:
>
> https:/
>
--
"Só se conseguirá a paz na ponta da lança".
Santa Joana D'Arc