[Bug 1318688] Re: nautilus crashes in action_open_item_location_callback() call in nautilus-view.c when pressing Ctrl+Alt+O directy on the desktop

2014-07-15 Thread Cristian Calin
Hi,

I just installed version 3.10.1-0ubuntu9.3 and can confirm that the bug
is fixed in this version. Nautilus does no longer crash when pressing
Ctr+Alt+O on the empty desktop.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1318688

Title:
  nautilus crashes in action_open_item_location_callback() call in
  nautilus-view.c when pressing Ctrl+Alt+O directy on the desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1318688/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1318688] [NEW] nautilus crashes in action_open_item_location_callback() call in nautilus-view.c when pressing Ctrl+Alt+O directy on the desktop

2014-05-12 Thread Cristian Calin
Public bug reported:

This crash can be triggered immediately after logging in without any windows 
open or with all application windows hidden.
When you press Ctrl+Alt+O, nautilus intercepts this keybinding and crashes.

I've installed the debug packages and managed to identify the brakage in
the action_open_item_location_callback fuction in nautilus-view.c.

Full backtrace:

(gdb) backtrace
#0  0x0046766e in action_open_item_location_callback (
action=optimized out, callback_data=optimized out)
at nautilus-view.c:1147
#1  0x7f3da91713b8 in g_closure_invoke (closure=0xc86fb0, 
return_value=0x0, n_param_values=1, param_values=0x76867f80, 
invocation_hint=0x76867f20)
at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:768
#2  0x7f3da9182d3d in signal_emit_unlocked_R (node=node@entry=0xa566b0, 
detail=detail@entry=0, instance=instance@entry=0xc75eb0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x76867f80)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3551
#3  0x7f3da918aa29 in g_signal_emit_valist (instance=optimized out, 
signal_id=optimized out, detail=optimized out, 
var_args=var_args@entry=0x76868108)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3307
#4  0x7f3da918ace2 in g_signal_emit (instance=instance@entry=0xc75eb0, 
signal_id=optimized out, detail=detail@entry=0)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363
#5  0x7f3dab7519d0 in _gtk_action_emit_activate (action=0xc75eb0)
at /build/buildd/gtk+3.0-3.10.8/./gtk/deprecated/gtkaction.c:906
#6  0x7f3dab751f69 in closure_accel_activate (closure=0xc86e00, 
return_value=0x76868300, n_param_values=optimized out, 
---Type return to continue, or q return to quit---
param_values=optimized out, invocation_hint=optimized out, 
marshal_data=optimized out)
at /build/buildd/gtk+3.0-3.10.8/./gtk/deprecated/gtkaction.c:1861
#7  0x7f3da91713b8 in g_closure_invoke (closure=0xc86e00, 
return_value=0x76868300, n_param_values=4, 
param_values=0x768683b0, invocation_hint=0x76868350)
at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:768
#8  0x7f3da9182d3d in signal_emit_unlocked_R (node=node@entry=0xa334d0, 
detail=detail@entry=2786, instance=instance@entry=0xa4d8e0, 
emission_return=emission_return@entry=0x768684b0, 
instance_and_params=instance_and_params@entry=0x768683b0)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3551
#9  0x7f3da918a6f9 in g_signal_emit_valist (instance=optimized out, 
signal_id=optimized out, detail=optimized out, 
var_args=var_args@entry=0x76868578)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3317
#10 0x7f3da918ace2 in g_signal_emit (instance=instance@entry=0xa4d8e0, 
signal_id=optimized out, detail=detail@entry=2786)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363
#11 0x7f3dab783d7d in gtk_accel_group_activate (accel_group=0xa4d8e0, 
accel_quark=accel_quark@entry=2786, 
acceleratable=acceleratable@entry=0xa50320, accel_key=accel_key@entry=111, 
accel_mods=accel_mods@entry=12)
---Type return to continue, or q return to quit---
at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkaccelgroup.c:910
#12 0x7f3dab7854ed in gtk_accel_groups_activate (
object=object@entry=0xa50320, accel_key=111, accel_mods=12)
at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkaccelgroup.c:948
#13 0x7f3dab9c0dc6 in gtk_window_activate_key (
window=window@entry=0xa50320, event=event@entry=0xe34100)
at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkwindow.c:11251
#14 0x7f3dab9c0e51 in gtk_window_key_press_event (widget=0xa50320, 
event=0xe34100) at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkwindow.c:7290
#15 0x00479828 in nautilus_window_key_press_event (widget=0xa50320, 
event=0xe34100) at nautilus-window.c:1908
#16 0x7f3dab877efe in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x884420, 
return_value=0x768688a0, instance=optimized out, 
args=optimized out, marshal_data=optimized out, 
n_params=optimized out, param_types=0x884450)
at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkmarshalers.c:130
#17 0x7f3da91715e7 in _g_closure_invoke_va (closure=0x884420, 
return_value=0x768688a0, instance=0xa50320, args=0x768689a8, 
n_params=1, param_types=0x884450)
at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:831
#18 0x7f3da918a088 in g_signal_emit_valist (instance=0xa50320, 
signal_id=optimized out, detail=0, 
var_args=var_args@entry=0x768689a8)
---Type return to continue, or q return to quit---
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3215
#19 0x7f3da918ace2 in g_signal_emit (instance=instance@entry=0xa50320, 
signal_id=optimized out, detail=detail@entry=0)
at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363
#20 0x7f3dab9a0df4 in gtk_widget_event_internal 

[Bug 1318688] Re: nautilus crashes in action_open_item_location_callback() call in nautilus-view.c when pressing Ctrl+Alt+O directy on the desktop

2014-05-12 Thread Cristian Calin
When called on the empty desktop, the nautilus_view_get_selection (view)
function results in a NULL result. At that point, there is no further
need to continue the function execution and it is safe to exit as no
resources need to be released.

This patch checks for selection being NULL and returns preventing
nautilus from crashing.

Please comment on this and if appropriate merge the patch in the
nautilus package.

** Patch added: patch to fix bug #1318688
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1318688/+attachment/4110698/+files/fix_ctrl_alt_o_crash.patch

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1318688

Title:
  nautilus crashes in action_open_item_location_callback() call in
  nautilus-view.c when pressing Ctrl+Alt+O directy on the desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1318688/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 541431] Re: nautilus crashed with signal 5 in _XError()

2010-03-20 Thread Cristian Calin
Just performed a dist-upgrade (20-03-2010 21:50 EET).
Nautilus is still crashing but now it gives a more interesting message:

k...@dracula:~$ nautilus --sync
Initializing nautilus-gdu extension

Gdk-ERROR **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 1497 error_code 8 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Trace/breakpoint trap (core dumped)
k...@dracula:~$ nautilus 
Initializing nautilus-gdu extension
process 22947: arguments to dbus_message_unref() were incorrect, assertion 
message-generation == _dbus_current_generation failed in file dbus-message.c 
line 1396.
This is normally a bug in some application using the D-Bus library.

Gdk-ERROR **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 856 error_code 8 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Trace/breakpoint trap (core dumped)

-- 
nautilus crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/541431
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 541431] Re: nautilus crashed with signal 5 in _XError()

2010-03-19 Thread Cristian Calin
** Visibility changed to: Public

-- 
nautilus crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/541431
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs