Description of problem: I was pressing the shift key when my hand on the mouse slipped, and the mouse moved over the Audacious window just as I accidentally pushed the left mouse button, resulting in a shift click. Audacious immediately crashed. Version-Release number of selected component: audacious-3.2.4-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: audacious crash_function: gtk_tree_model_get_valist kernel: 3.6.11-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (8 frames) : #0 gtk_tree_model_get_valist at gtktreemodel.c:1766 : #1 gtk_tree_model_get at gtktreemodel.c:1728 : #2 gtk_entry_completion_compute_prefix at gtkentrycompletion.c:1728 : #3 gtk_entry_completion_insert_prefix at gtkentrycompletion.c:1889 : #4 check_completion_callback at gtkentry.c:9709 : #5 source_closure_marshal_BOOLEAN__VOID at gsourceclosure.c:71 : #7 source_closure_callback at gsourceclosure.c:113 : #12 gtk_main at gtkmain.c:1161
Created attachment 679341 [details] File: core_backtrace
Created attachment 679342 [details] File: environ
Created attachment 679343 [details] File: backtrace
Created attachment 679344 [details] File: limits
Created attachment 679345 [details] File: cgroup
Created attachment 679346 [details] File: smolt_data
Created attachment 679347 [details] File: xsession_errors
Created attachment 679348 [details] File: executable
Created attachment 679349 [details] File: maps
Created attachment 679350 [details] File: dso_list
Created attachment 679351 [details] File: build_ids
Created attachment 679352 [details] File: var_log_messages
Created attachment 679353 [details] File: open_fds
Created attachment 679354 [details] File: proc_pid_status
So, what are the steps to reproduce it? Do you mean that a shift+left-click always crashes Audacious for you? The backtrace is rather short and only inside gtk3 without any context about Audacious. > #0 0x00000030654666f8 in gtk_tree_model_get_valist > (tree_model=tree_model@entry=0x2638c20, iter=iter@entry=0x7fff65e13f60, > var_args=var_args@entry=0x7fff65e13e68) at gtktreemodel.c:1766
(In reply to comment #15) > So, what are the steps to reproduce it? > Do you mean that a shift+left-click always crashes Audacious for you? No, I haven't been able to reproduce. I'm just guessing about the shift+left+click, too, as that's the last thing I noticed doing in the split second before the crash. > The backtrace is rather short and only inside gtk3 without any context about > Audacious. Well, that's odd. All around a very strange bug. I'd say just go ahead and close this bug as not reproducible. I'll reopen the bug if I ever figure out how to make it happen again.
Do give Fedora 18 a try. Don't waste time with Fedora 17. Why? GTK+ 3 has seen a lot of activity in F18 compared with F17.
Yes, I'm updating the first of my machines today. Once I get it tweaked into shape, I'll do the same to the others.