Bug 743223 - Gnome Shell crashes in application overlay when type to find
Summary: Gnome Shell crashes in application overlay when type to find
Keywords:
Status: CLOSED DUPLICATE of bug 741964
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-04 09:52 UTC by rob martin
Modified: 2011-12-16 18:30 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-12-16 18:30:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
.xsession errors (21.37 KB, text/plain)
2011-10-04 10:17 UTC, rob martin
no flags Details
Stacktrace of a gnome shell crash during search (22.46 KB, text/plain)
2011-11-09 13:57 UTC, Michael Lausch
no flags Details

Description rob martin 2011-10-04 09:52:59 UTC
Description of problem:

When in Application overlay, typing anything other than spaces results in segfault 


Version-Release number of selected component (if applicable):
gnome-shell.x86_64 0:3.2.0-2.fc16

How reproducible:
click activites, start typing, crash

Steps to Reproduce:
1.click Activities
2. start typing (spaces do not result in crash)
3.crash
  
Actual results:
crash dmesg reports
gnome-shell[1912]: segfault at 0 ip 00007f3904daa464 sp 00007fffdb7a7ca0 error 4 in libc-2.14.90.so[7f3904d0d000+1ab000]

Expected results:
search works

Additional info:

Comment 1 Elad Alfassa 2011-10-04 10:05:33 UTC
A full backtrace will be helpful. Did ABRT showed a crash alert? If so, you could use ABRT to submit the backtrace.
If it didn't, start gnome-shell in gdb to get the backtrace.

Also, please attach ~/.xsession-errors

If you need any help in getting the backtrace, don't hesitate to ask.

Elad Alfassa,
Not a GNOME developer.

Comment 2 rob martin 2011-10-04 10:17:56 UTC
Created attachment 526217 [details]
.xsession errors

Comment 3 rob martin 2011-10-04 10:19:43 UTC
Elad

ABRT didn't/doesn't see the crash.  I've tried the gdb using the instructions on the Gnome site but will have to do it again, later, off to work now :(

Rob

Comment 4 Koda 2011-10-07 16:42:12 UTC
This also effects me...  SIGSEGV is caused by typing into Activities Window 
Also GIMP, Pidgin, BOINC client
ABRT SIGSEGV when you type in the "additional information" field...

This also effects me trying Ubuntu 11.10, Linux Mint 11 with Gnome 3...

Comment 5 awellis 2011-10-17 17:02:41 UTC
I got this bug too.  Not quite sure if I did it right but I attempted to get a gdb backtrace for the crash but every time I attached the pid to gdb, gnome-shell would freeze and not do anything until I quit gdb.

Fedora 16 x64

Comment 6 Tim Lauridsen 2011-10-26 09:37:30 UTC
I see this then using a alternate gnome-shell using the user theme extension and gnome-tweak-tool to select the theme.

Comment 7 Michael Lausch 2011-11-09 13:57:49 UTC
Created attachment 532575 [details]
Stacktrace of a gnome shell crash during search

Input was aa in the search field in the upper right corner.

Comment 8 Adam Williamson 2011-11-09 20:38:27 UTC
are the other people seeing this also using alternative Shell themes, as Tim Lauridsen is?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 9 awellis 2011-11-10 18:33:55 UTC
I had the problem right after installing F16.  didn't even add any repos.

Comment 10 Harald Hoyer 2011-11-11 09:51:49 UTC
fixed with https://bugzilla.gnome.org/show_bug.cgi?id=663815

please provide updates!

Thanks!

Comment 11 Kazimieras Vaina 2011-11-11 14:11:19 UTC
for me, gnome-shell crashes with and without custom theme.

Comment 12 Kazimieras Vaina 2011-11-11 15:44:23 UTC
I can confirm that patch in https://bugzilla.gnome.org/show_bug.cgi?id=663815 works!

Comment 13 Adam Williamson 2011-11-15 00:39:14 UTC
Ooh. Fun.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 14 Andrea Santilli 2011-11-18 17:05:40 UTC
This problem arises when there are some desktop entries that do not contain both the "Name" and "Exec" keys. I did a quick search through my installed programs by doing as follows:

for file in /usr/share/applications/*.desktop; do
  [ $(egrep "^Name=|^Exec=" "$file" | wc -l) -ne 2 ] && echo "$file"
done

It showed me the faulty entries, so I just uninstalled their packages and it all went fine. I could have also edited the entries directly but I didn't mind.
I hope this can be useful as a quick workaround while this bug is being fixed.

Comment 15 Owen Taylor 2011-12-16 18:30:42 UTC
Combining with another bug that also has a bunch of duplicates

*** This bug has been marked as a duplicate of bug 741964 ***


Note You need to log in before you can comment on or make changes to this bug.