After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609907 - Talkback tool a-la Mozilla (bug-buddy should have a D-BUS server to listen to assert requests from programs which didn't crash)
Talkback tool a-la Mozilla (bug-buddy should have a D-BUS server to listen to...
Status: RESOLVED WONTFIX
Product: bug-buddy
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2010-02-14 11:49 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2018-07-16 08:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (55.29 KB, image/png)
2010-02-14 11:49 UTC, Andrés G. Aragoneses (IRC: knocte)
Details

Description Andrés G. Aragoneses (IRC: knocte) 2010-02-14 11:49:50 UTC
Created attachment 153756 [details]
screenshot

I don't know how I came up with this situation, but I'm attaching a screenshot
of the problem. The tooltip is in Spanish, but here is the translation:

"Active session, not inhibited, inactive screen. If you can see this text your
screen server is broken and you should notify it to your distributor. For more
information refer to
http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/"

I don't think it's fair to request the user to:
1) Report a bug if the system can sistematically know that it happened.
2) Visit a technical blog, to figure out... what?
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2010-02-14 11:56:33 UTC
Ok, I'll go a bit further and I'll convert this bug in a more generic one. This situation should be just an assert but that doesn't crash the whole app. An assert that gets sent automatically to the Gnome servers in some way to gather enough info to be able to fix it.

This, in other kind of software, already exists, for example the Mozilla Talkback tool (although maybe that one does only work for real crashes, not for asserts that shouldn't crash the program).

The most appealing module on gnome that would get this feature is the bug-buddy, thus I'm changing the product.
Comment 2 Andrés G. Aragoneses (IRC: knocte) 2010-02-14 11:58:57 UTC
Changing summary from "Unacceptable way of notifying a bug to the user" to "We need a talkback tool a-la Mozilla (in this case bug-buddy should have a DBUS server to listen to assert requests from programs which didn't crash)"
Comment 3 André Klapper 2010-04-26 11:45:13 UTC
What is "a talkback tool a-la Mozilla"?
Comment 4 Andrés G. Aragoneses (IRC: knocte) 2010-04-26 16:54:35 UTC
http://en.wikipedia.org/wiki/Crash_reporter#Talkback
Comment 5 André Klapper 2018-07-16 08:24:34 UTC
bug-buddy is not under active development anymore and had its last code changes
many years ago. Its codebase has been archived:
https://gitlab.gnome.org/Archive/bug-buddy/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality (see bug 796784). Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.