ubuntuforums-unanswered team mailing list archive

[Scott Howard <question77061@xxxxxxxxxxxxxxxxxxxxx>]

Question #77061 on gnome-power-manager in ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/77061

Scott Howard posted a new comment:
I'm happy to answer your questions:


> First, how can I reproduce it? Start working all day on the desktop cd?

Loading a liveCD and testing suspend through the GNOME logout/quit
sequence and a short timer would suffice. However, some bug reporters do
run a fully installed development version of Karmic to test for long
periods of time, which is helpful finding crashes in unique situations.


> I'm sure that if I just load it, and try to suspend everything will
> work. And what happens when I reproduce? What information will it gather
> for you to fix the issue?

Once the bug is reproducible in the development release we can gather information through the procedures outlined at: 
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager
http://projects.gnome.org/gnome-power-manager/bugs.html
When running the Karmic Development Release, Ubuntu will automatically run a tool called Apport which will collect crash stack traces and many of the necessary logs to debug and fix the bug:
https://wiki.ubuntu.com/Apport


>
> Second, I think that the comment is an attempt to brush this issue
> aside. The reason is that I did not open the bug asking for gnome-power-
> manager to be fixed, instead I asked for tools that will let me work
> around the issues that it has.

The "bugs" section at launchpad.net is used for fixing programming
errors gnome-power-manager. If you'd like tools and workarounds, please
seek support at the "answers" section of launchpad.net,
ubuntuforums.org, or #ubuntu on freenode irc
(https://help.ubuntu.com/community/InternetRelayChat).


>
> There is no reason why I should not be able to suspend my laptop in the
> same sense I should always be able to shut it down. In both cases I risk
> loosing data etc., but this is for me to decide.

That is true, suspend should just work. Bug reporting and working to
identify the cause of why you can't do that is the correct step to take.
If you'd like to suggest new features or changes to how Ubuntu is
currently working, post on the relevant developer mailing list
(https://lists.ubuntu.com/).


>
> So please, instead of asking me to reproduce a bug I did not ask to
> solve, why not focus on giving me tools to work around it (or better
> yet, analyze it, e.g., be able to say which application did not freeze)

I'm sorry, but the first step to fixing programming errors is to
recreate the bug or failure in the most up to date version of the
software. If you'd like tools and workarounds, please seek support at
the "answers" section of launchpad.net, ubuntuforums.org, or #ubuntu on
freenode irc (https://help.ubuntu.com/community/InternetRelayChat).

>
> I will not try to recreate the issue. There's no point in it.

I'm converting this bug to a question to better help the reporter and
marking as "Invalid" since there is no Karmic debugging information and
this bug is not eligible for SRU
(https://wiki.ubuntu.com/StableReleaseUpdates).

-- 
You received this question notification because you are a member of UF
Unanswered Posts Team, which is an answer contact for Ubuntu.