Bug 739315
| Summary: | Alternative Status Menu extension triggers st_widget_get_theme_node() assertion | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> | ||||||||||||||||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||
| Version: | 18 | CC: | a.demerdzhiev, afriza.na, akees, atangrin, avagin, bedny, bfay, browning48ky, bruno, bugzilla_rhn, carlos.sepulveda, chichiiko, collura, daniele_carminati, danw, desantis.maurizio, drindt, enaut.w, forbugzilla, gbauman, ibelkov, isaac.munoz02, jalemolina, jlmeram89, jonathan.eidsness, jorgejhms, josian2200, justafedorauser, kmaraas, krum.boy4ev, martin.wilck, maxamillion, michael.faille, neogan74, nikolayboychev, nobodie0, old.uncle.z, otaylor, patrick.guio, pc7graf, perfectop, rebus, roignac, samkraju, sanjay.ankur, spetreolle, spinus1, tadej.j, thexman, uckelman, uraeus, vladimir.travalja, vondruch, walters | ||||||||||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||
| Whiteboard: | abrt_hash:7651ff7d2ef4bde64a312de0b57ac6ca843631c3 | ||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2014-02-05 11:49:49 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
Charles R. Anderson
2011-09-17 13:59:23 UTC
Created attachment 523712 [details]
File: dso_list
Created attachment 523713 [details]
File: maps
Created attachment 523714 [details]
File: backtrace
Package: gnome-shell-3.2.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I wasn't do anthing special. I just logged in and opened Firefox. Package: gnome-shell-3.2.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I wasn't do anthing special. I just logged in and opened Firefox. Package: gnome-shell-3.2.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- i don't know Package: gnome-shell-3.2.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I get this when entering the shell and starting typing something. What happens is gnome-shell crashes and reloads itself automatically. Everything is fine if, instead of typing something to search for application, I locate and run it via mouse clicks. I have some shell extensions installed, but all are disabled: $ rpm -qa | grep shell gnome-shell-theme-gaia-1.0-1.fc16.noarch gnome-shell-extension-alternative-status-menu-3.2.0-1.fc16.noarch gnome-shell-extension-places-menu-3.2.0-1.fc16.noarch gnome-shell-extension-workspacesmenu-0-1.fc16.noarch gnome-shell-extension-gpaste-1.6-1.fc16.noarch gnome-shell-theme-smooth-inset-1.0-1.fc16.noarch gnome-shell-extension-auto-move-windows-3.2.0-1.fc16.noarch gnome-shell-extension-native-window-placement-3.2.0-1.fc16.noarch gnome-shell-extension-presentation-mode-0-0.2.gitc3ce6b2.fc16.noarch gnome-shell-extension-remove-accessibility-icon-20110603-1.fc16.noarch gnome-shell-extension-mediaplayers-0-0.2.git1225d49.fc16.noarch gnome-shell-extension-user-theme-3.2.0-1.fc16.noarch gnome-shell-theme-dark-glass-1.0-1.fc16.noarch gnome-shell-extension-theme-selector-0.9-3.fc16.noarch gnome-shell-extension-apps-menu-3.2.0-1.fc16.noarch gnome-shell-extension-systemMonitor-3.2.0-1.fc16.noarch gnome-shell-extension-cpu-temperature-0-0.1.git712153f.fc16.noarch gnome-shell-extension-pomodoro-0-0.2.git13030cd.fc16.noarch gnome-shell-extension-common-3.2.0-1.fc16.noarch gnome-shell-3.2.0-2.fc16.x86_64 gnome-shell-extension-windowsNavigator-3.2.0-1.fc16.noarch gnome-shell-extension-icon-manager-0-0.2.gite9deb2b.fc16.noarch gnome-shell-theme-orta-1.0-1.fc16.noarch gnome-shell-extension-drive-menu-3.2.0-1.fc16.noarch Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- crash if no icon is selected in status menu and the alternative-status-menu is enabled. Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- installed and enabled gnome-shell-extension-alternative-status-menu and gnome-shell was completely crashing and refusing to let me log in. Had to log in console and uninstall extension-plugin to access desktop Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Opening places-menu extension Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Was launching a gnome-session with alternative-menu activated Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Log-in after first updating since installation (In reply to comment #12) > Package: gnome-shell-3.2.1-2.fc16 > Architecture: x86_64 > OS Release: Fedora release 16 (Verne) > > Comment > ----- > Log-in after first updating since installation The alternative-menu was active before the update. Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- startup crash Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- after packages update, system reboot and initial login gnome-shell crashed Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- 1. It crashes after login if I use alternative-status-menu gnome-shell extension. Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I don't remember *** Bug 759730 has been marked as a duplicate of this bug. *** *** Bug 758182 has been marked as a duplicate of this bug. *** *** Bug 757453 has been marked as a duplicate of this bug. *** *** Bug 759102 has been marked as a duplicate of this bug. *** Logging in. Disabling all extensions worked. backtrace_rating: 4 Package: gnome-shell-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 552268 [details]
File: backtrace
Logging in. backtrace_rating: 4 Package: gnome-shell-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne) Created attachment 552269 [details]
File: backtrace
1 go to left active conor. 2. and find app 3. g-shell freeze for long time 4. go to ctrl+alt+F2 shell and kill it backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 571307 [details]
File: backtrace
*** Bug 758635 has been marked as a duplicate of this bug. *** *** Bug 759671 has been marked as a duplicate of this bug. *** *** Bug 756469 has been marked as a duplicate of this bug. *** I was experimenting with vpnc VPN support in NetworkManager and closed the connect dialog when gnome-shell crashed. backtrace_rating: 4 Package: gnome-shell-3.4.0-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Open a existing vpn connection Enter login details Hit Enter backtrace_rating: 4 Package: gnome-shell-3.4.0-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) Trying to connect to a VPN using network manager. backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) NOTE that comments 31-33 are crashes *unrelated* to the rest of this bug. Blah, blah, ABRT, blah, blah. If someone figures out how to reproduce this reliably without any extensions installed, please find me, and we can debug this.(owen on GimpNET IRC, #fedora-desktop) Good morning Owen. You've said that mine (33) is unrelated to this bug report, any way I can get it created as a new bug report, as it is entirely re-producible, and would be great if I could get it working :) Thankfully in my case at least dropping back to the non-enhanced shell experience results in a working VPN connection via the NM applet, so it's not the end of the world, but still needs fixing. (In reply to comment #35) > Good morning Owen. > > You've said that mine (33) is unrelated to this bug report, any way I can get > it created as a new bug report, as it is entirely re-producible, and would be > great if I could get it working :) It doesn't really help to make it a different bug report, since ABRT will still be adding duplicates on this bug report :-( If it's entirely reproducible, what I need for debugging is a bit tricky. 1) Download ~/fishsoup.net/xenv.sh 2) Switch to a VT and log in 3) At the command line, do: script shell-crash.log . ~/Downloads/xenv.sh # the period is not a typo, you need it gdb --args gnome-shell --replace 4) At the gdb prompt (gdb) run 5) Switch back to the X VT, reproduce the bug 6) Switch back to the other VT 7) At the gdb prompt, (gdb) call gjs_dumpstack() (gdb) quit 8) Hit Control-D to exit the script session 9) Attach the resulting shell-crash.log here There is almost certainly a mistake or two in the above - if you hit some snag and can't figure out a way around it, let me know. Note that I'm connecting to a VPN via the shell multiple times a day without ever encountering this - it's something particular to your VPN setup. (In reply to comment #36) > 1) Download ~/fishsoup.net/xenv.sh OK, that's definitely one mistake - I meant: http://fishsoup.net/tmp/xenv.sh Created attachment 580217 [details]
My crash log :)
(In reply to comment #38) > Created attachment 580217 [details] > My crash log :) Hmmm, I was asssuming that the backtrace at least had some similarity, but it's really entirely unrelated. you missed the "call gjs_dumpstack()" step... also, does this happen the first time you try to connect to the vpn? Are you connecting over wifi? If so, does it have to prompt you for the wifi password, or is that saved? and what version of NetworkManager-glib do you have installed? I am connecting to a VPN over WIFI, the password is saved, and I am actively connected at the time of attempting to connect to the VPN. The VPN password is not saved, and I have to accept an SSL cert each time. This happens each and every single time I attempt to connect to the VPN. Name : NetworkManager-glib Epoch : 1 Version : 0.9.4.0 Release : 7.git20120403.fc17 Trying to connect to a VPN (openconnect) using NetworkManager Select the desired VPN Enter USERNAME and Password Hit Enter It happens everytime I try to connect. If use the openconnect command directly in the shell it doesn't happens. backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) Laptop was closed (with screen set to turn off, but not standby or hibernate) for a few hours with Transmission, Abiword and Nautilus running. On returning and opening the laptop, not only was the screen NOT locked as it should be (from idle time), but it was prompting me for the network key to my wifi network which is stored and has no trouble connecting to automatically. As I type this I notice the hardware wifi switch was set to "off," so that may be related to that issue (still undesirable behavior...). Anyway, when the screen came back on, I "Cancel"ed about a dozen windows asking for the wifi key, then noticed the alert about this crash. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 580617 [details]
File: backtrace
I was trying to connect to secured WiFi and in the same time I was fiddeling arount the wireless network settings. In one moment, the gnome applet was telling me "waiting for authorization", but the authorization dialog was nowhere. Therefore I tried to connect other network in attempt to get the dialog. backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) http://koji.fedoraproject.org/koji/taskinfo?taskID=4028831 has packages that should fix the crash (eg, http://koji.fedoraproject.org/koji/getfile?taskID=4028832&name=gnome-shell-3.4.1-3.1.fc17.x86_64.rpm if you're on x86_64). Assuming it does fix the crash, the next question is: do you end up with a warning in ~/.xsession-errors after trying to connect to the VPN, or does it connect without error? (Or, I guess, does it fail to connect, but not crash either...) Morning Dan. This appears to have resolved the issue, VPN is now connecting successfully, and there are no errors appearing within the .xsession-errors file. Pity there isn't a "bug" for this particular issue that can be "closed" as this bug report seems to have LOTS of unrelated issues, or may be I'm wrong :\ Eithere, much obliged. Doug Login into the secured WiFi failed and asked once more for password. I canceled the password dialog when gnome-shell crashed. backtrace_rating: 3 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) just connected to vpn backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 Alpha (Beefy Miracle) Good morning Dan I think we may have spoken to soon regarding this patch fixing the issue that I was having connecting to the VPN. I started to notice some oddities with regards to it not connecting, and now it does not connect at all. I have a suspicion that it has some thing to do with the SSL certificate interaction. Previously when connecting, it would ask me to accept the SSL cert, however that is no longer the case, and it no longer connects. There are no visual errors on screen though, and I'm unsure which logs would be of use. There was a network outing, so wifi got disconnected. A dialog asking for a password was at the screen. Meanwhile, wifi had reconnected, so I hit cancel. This causes the dialog to close, and the screen to lock (since it had been unused for a while and should be locked). When it opened, i saw the abrt applet reporting the crash. backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 (Beefy Miracle) Entered an incorrect key for a wireless network backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 583892 [details]
File: backtrace
leave the computer stand alone for one hour backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) After an unsuccessful attempt to connect to a WLAN, NetworkManager shows a dialog asking for a valid password. Clicking on "dismiss" without entering a password crashes gnome-shell maybe 1 time in 10. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) I was trying to log into the Red hat Guest network; it asked me for a password. I didn't have the key handy, so i was looking it up on my desktop (after a few wrong guesses). While I was searching for the key, the ask-for-password dialogs apparently kept piling up quite deep. As I was clicking them away, GS crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) Failed authentication to Red Hat internal wireless network--- while I was typing in the auth information--- it mysteriously popped another authentication dialog on top of the one I was filling out I clicked 'cancel' and GS crashed backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) i hate that second dialog. keep forgetting to report it. sounds like the same thing i see when i randomly loose wireless. it requires a depowering to reset something before it accepts wifi password. the wierd thing is that the 2 dialogs are offset in time and theme. the first window that pops up is the new gnome3 themed dialog but the second dialog shows up about 30s after the first and is is the old gnome2 themed dialog. its like there are 2 levels of machinations running and nomatter how many times i retype the wifi password in either dialog the wifi never reconnects until i power off and let capacitance drain (not just power cycle). ugh. the wireless password dialog appeared before the unlock screen dialog appears, then the gnome shell crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) sudo lxc-create -n name sudo lxc-start -n name opened one more terminal, crash backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) multiple wifi-password-required dialogs popped up behind one another. crash when closing the second one by clicking abort. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) leaving laptop alone for hours, network-manager lost wifi, displaying an annoying prompt asking for the WPA key, after returning to laptop clicked ok on that, _then_ screen saver kicked in (hours late) and gnome-shell crashed backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Try to connect to DSL, failed. A window gnome-shell prompts you to enter a login and password. Pressed cancel. Shell hanging, missing panels and all controls, leaving only the wallpaper. Error consistently repeated rebooting does not help. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) gnome-shell crash backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) NetworkManager is trying to reconnect to my WiFi and requesting a password; It's prompting for the password several times, i.e. once with a "dark window" and one or more times with a "light colored window". Since I'm not near the laptop, I do not answer the prompt. The screen dims after a while. When I return to the laptop and try to reactive the screen, I get the prompts for the WiFi password before I get the prompt for the screen lock password. After unlocking the screen it is clear that Gnome Shell has crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) This was after hibernate my Laptop backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) I was trying to connect to wifi backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle) I've installed several Gnome Shell extensions...one or some of them are frequently crashing...and gnome shell automatically disables all the extensions: this time some process of the shell crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) This happened when after I tried to activate a WLAN connection in the NetworkManager-applet. The first time the gnome shell was simply restarted. I tried to connect again, and the gnome shell crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-6.fc17 OS Release: Fedora release 17 (Beefy Miracle) Probably caused by using dash-to-dock extension branch gnome-3.6-wip backtrace_rating: 4 Package: gnome-shell-3.6.1-3.fc18 OS Release: Fedora release 18 (Spherical Cow) Leaving laptop alone for hours, network-manager lost wifi. Mmultiple wifi-password-required dialogs popped up behind one another. Crash when closing all of them. I don't know exactly what happened, but it was very similar to comment #71: NetworkManager was trying to re-connect to a WiFi network and it asked for a password. Then gnome-shell crashed. ABRT directed me to this bug report. Version: gnome-shell-3.4.1-6.fc17.x86_64 This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I want to add banshee in to favorites aplication on the left panel. backtrace_rating: 4 Package: gnome-shell-3.6.2-6.fc18 OS Release: Fedora release 18 (Spherical Cow) Bumping version to F-18 since it is still relevant (see comment #74) Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Re-opened since it appears to be still relevant in F-18 (see comment #74). This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |