Bug 247431 - Bug-Buddy doesn't work
Summary: Bug-Buddy doesn't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 7
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-09 09:57 UTC by markm
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-07-09 10:05:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Bug-buddy started from the Menu. (14.49 KB, image/png)
2007-07-09 09:57 UTC, markm
no flags Details

Description markm 2007-07-09 09:57:36 UTC
Description of problem:

OpenOffice crashed and gave me nicely formated debug information, so I wanted to
paste it into bug buddy report, but... bug buddy doesn't work - it keeps asking
about application name or package name, when I give app name, it asks about pid
number... when I give package name it says bug buddy didn't know how to send a
report for this particular application.

The bug buddy behaviour is very user unfriendly and as I am not able to send a
report, how anyone can send it? :)

Version-Release number of selected component (if applicable):

bug-buddy 1:2.18.0-2.fc7@i386

How reproducible:

everytime

Steps to Reproduce:
1. just start bug-buddy from the menu
  
Actual results:

ask about command line parameters

Expected results:

user friendly wizard style dialog box which allows you to choose an application,
version etc.

Comment 1 markm 2007-07-09 09:57:36 UTC
Created attachment 158752 [details]
Bug-buddy started from the Menu.

Comment 2 Caolan McNamara 2007-07-09 10:05:05 UTC
OOo doesn't use bug-buddy as it's not a GNOME app. So instead of logging a bug
about using bug-buddy (which isn't a bad idea, just one we haven't implemented)
log a bug here in bugzilla against OOo, just like you did for this issue, and
instead attach the "cut and paste me" output to that new bug ;-)

We do need a way to automate the process, we're thinking about it.




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