Bug 531343
| Summary: | [abrt] crash detected in wallpapoz-0.4.1-11.svn92_trunk.fc12 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ROMAN <roman.zubko> | ||||||
| Component: | wallpapoz | Assignee: | Mamoru TASAKA <mtasaka> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 12 | CC: | aa.borba, acitti, adrruiz, albarsalan.86, alexsurender, ambijat, anross, bartlett_adrian, benoit.alary, be, bugzilla, celiohermoso, christopher, comhal, cursor, dora-earth, drown_rat, dtdraganov, edosurina, etheban, fegasi, filemon, flywyvern, freddaggs, gcc.pro, gidmantas, gmclark, granata.giovanni, iptin, irc.smithsonian, jcmj, jsmeade, kethorse, linux, manuelmongeg, marco, mbruegge73, mdmpsyd, michael, mirkoszlikovski, mrblack, mtasaka, narf, noah.swint, oakeymini, plarsen, postVictor, prabhatmaurya, qau_zahid, rdurham25, redhat, redhat, register, relaxcold, remstereo555, rob.d.wills, sergiovl, soma-sk8, sorkan, tc, teapot2, theiceman.ice, tribby21, twilson, uckelman, valent.turkovic, vladimir.atanackovic, vsardavids, walrus, xtg05 | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:1732a30b | ||||||||
| Fixed In Version: | wallpapoz-0.4.1-15.svn92_trunk.fc12 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-02-18 22:19:41 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
ROMAN
2009-10-27 19:29:59 UTC
Created attachment 366330 [details]
File: backtrace
Would you please - write the details how to reproduce this issue - tell me what desktop environment you are using (and whether some additional desktop effects like compiz are enabled or not) - attach ~/.wallpapoz/wallpapoz.xml - write the result of "$ xprop -root _NET_CURRENT_DESKTOP" ? Also would you tell me - how many workspaces does your desktop has? (In reply to comment #2) > Would you please > - write the details how to reproduce this issue > - tell me what desktop environment you are using > (and whether some additional desktop effects like compiz are enabled > or not) > - attach ~/.wallpapoz/wallpapoz.xml > - write the result of "$ xprop -root _NET_CURRENT_DESKTOP" > ? 1.I'm using GNOME desktop. Additional desktop effects not enable. 2. wallpapoz.xml: <!DOCTYPE Wallpapoz> <wallpapoz interval="5" random="0" style="2" type="workspace"> <workspace name="rename this" no="1"> <file> /home/ROMA/Картинки/ABSTRACT-Burning_1600x1200.jpg </file> </workspace> </wallpapoz> 3. result of "$ xprop -root _NET_CURRENT_DESKTOP" "_NET_CURRENT_DESKTOP(CARDINAL) = 0" I have 4 workspace And this issue is still reproducible? If so would you tell me how to reproduce it? Well, would you "attach" (not copy and paste) wallpapoz.xml file? Created attachment 367018 [details]
/.wallpapoz/wallpapoz.xml
(In reply to comment #6) > And this issue is still reproducible? If so would you > tell me how to reproduce it? I'm sorry? but i dont know how to reproduce it Well, for now I guess that in both cases (i.e. both on bug 531342 and bug 531343) when wallpapoz crashed "xprop" (in xorg-x11-utils) returned unexpected result, so this may be a bug in X packages or the desktop environment being used, however I am not sure... When you recounter this bug, please let me know it. I have this issue a few times a day. Not 100% reproducible, but seems to be related to an X-crash (that is not detected by abrtd) happening when viewing some random website in firefox. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Once closing this bug as the reporter says this bug is not reproducible. I had this problem with a F12 install (upgrade from F11). It's not rawhide only. I have got this problem (reported by "abrt") after a F12 install (upgrade from F11) also. (In reply to comment #15) > I have got this problem (reported by "abrt") after a F12 install (upgrade from > F11) also. This bug is already closed as the original reporter says that the bug reported was not reproducible. Even if you see wallpapoz crash, it does not mean that you and the original reporter are seeing the same issue. If the crash you see is reproducible, please file another bug report, then I will triage it. Again: This bug is already closed as the original reporter says that the bug reported was not reproducible. Even if you see wallpapoz crash, it does not mean that you and the original reporter are seeing the same issue. If the crash you see is reproducible, please file another bug report, then I will triage it. My guess is that these Cc-s are added by abrt (like mine). I also guess that what the original reporter ment was that he can not reliably reproduce the problem himself, not that the problem had gone away. In my case abrt reported this bug when X crashed. But if it was wallpapoz that made X crash or vice versa is impossible for me to tell. In any case, as long as abrt continues to add more people to this bug, I think it needs a closer look. The problem is: - "Abrt reported that this was a bug in wallpapoz" does not mean that a bug is really in wallpapoz. For example see bug 531342 comment 6. And I already have another cases in which abrt reported a bug to wallpapoz but the real bug was in nspluginwrapper and the contents of the bug really had no relation with wallpapoz. So please note that abrt itself may have a bug. That there are not a few people included in the CC list of this bug may be also due to a bug in abrt. So without any further information I cannot understand what is happening any more. By the way I don't think people are installing wallpapoz by default because wallpapoz is not included in F-12 installation DVD. Now this issue is reproducible to me, reopening. wallpapoz-0.4.1-12.svn92_trunk.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-12.svn92_trunk.fc12 wallpapoz-0.4.1-12.svn92_trunk.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-12.svn92_trunk.fc11 wallpapoz-0.4.1-12.svn92_trunk.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update wallpapoz'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1483 wallpapoz-0.4.1-15.svn92_trunk.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-15.svn92_trunk.fc12 wallpapoz-0.4.1-15.svn92_trunk.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-15.svn92_trunk.fc11 wallpapoz-0.4.1-15.svn92_trunk.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update wallpapoz'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1687 wallpapoz-0.4.1-15.svn92_trunk.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. wallpapoz-0.4.1-15.svn92_trunk.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |