desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #105576
[Bug 1429852] [NEW] It is much too hard to file a bug report
Public bug reported:
Usability issue: the process of filing a bug report is too hard.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and you
want to help Ubuntu. These are the steps for a first time bug report:
(0) look through the application's menus, no hints there how to file a
bug
(1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
(4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
(5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to disagree.
(13) Scroll through a page of suggestions and click that you need a new
bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.
Observed behavior: Lots of time spent on the above procedure. Do you
have a way of knowing how many users give up?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 trusty
** Description changed:
Usability issue: the process of filing a bug report is so convoluted
that most users' goodwill is depleted along the way.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and you
- want to help Ubuntu. These are the hoops you have to jump through:
+ want to help Ubuntu. These are the steps for a first time bug report:
(0) look through the application's menus, no hints there how to file a
bug
- (1) google how to report a bug, click through 3 pages and lots of text
+ (1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
- (4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
+ (4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
- (5) figure out ubuntu-bug is a command line utility
+ (5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
- (9) Wait an unexpectedly long time at a white firefox screen while it's
+ (9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
- (12) You'd think software devs would like to make good software. But
- now, your experience gets invalidated and told that everybody else
- already knows how to work despite the bug. At least, that's what the
- search through (un)related bugs suggests from a marketing point of view.
- So you have to muster some resolve to disagree.
+ (12) You'd think software devs would like to make good software and
+ improve it. But now, your experience gets invalidated and told that
+ everybody else already knows how to work despite the bug. At least,
+ that's what the search through (un)related bug reports suggests from a
+ marketing point of view. So you have to muster some resolve to disagree.
- (13) Scroll through a page of unrelated suggestions and click that you
- need a new bug. Well, actually, I don't need a bug, I'm extending my
- goodwill to help you get rid of one.
+ (13) Scroll through a page of suggestions and click that you need a new
+ bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
+ extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
(15) Most likely, watch your bug report get deleted because most devs
are not accustomed to take usability issues seriously.
- Expected behavior: The desktop application has a button to report bugs
- somewhere in the About menu, and it should take at most 3 clicks get it
- done.
+ Expected behavior: The desktop application should have a button to
+ report bugs somewhere in the About menu, and it should take at most 3
+ clicks get it done.
- Observed behavior: Lots of time spent jumping through the hoops
- described above.
+ Observed behavior: Lots of time spent on the above procedure.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
- 664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
- 640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
- 640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
- 600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
+ 664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
+ 640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
+ 640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
+ 600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Usability issue: the process of filing a bug report is so convoluted
that most users' goodwill is depleted along the way.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and you
want to help Ubuntu. These are the steps for a first time bug report:
(0) look through the application's menus, no hints there how to file a
bug
(1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
(4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
(5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to disagree.
(13) Scroll through a page of suggestions and click that you need a new
bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
(15) Most likely, watch your bug report get deleted because most devs
are not accustomed to take usability issues seriously.
Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.
- Observed behavior: Lots of time spent on the above procedure.
+ Observed behavior: Lots of time spent on the above procedure. Do you
+ have a way of knowing how many users give up, rather than help you?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Usability issue: the process of filing a bug report is so convoluted
that most users' goodwill is depleted along the way.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and you
want to help Ubuntu. These are the steps for a first time bug report:
(0) look through the application's menus, no hints there how to file a
bug
(1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
(4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
(5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to disagree.
(13) Scroll through a page of suggestions and click that you need a new
bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
- (15) Most likely, watch your bug report get deleted because most devs
- are not accustomed to take usability issues seriously.
-
Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.
Observed behavior: Lots of time spent on the above procedure. Do you
have a way of knowing how many users give up, rather than help you?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
- Usability issue: the process of filing a bug report is so convoluted
- that most users' goodwill is depleted along the way.
+ Usability issue: the process of filing a bug report is too hard.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and you
want to help Ubuntu. These are the steps for a first time bug report:
(0) look through the application's menus, no hints there how to file a
bug
(1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
(4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
(5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to disagree.
(13) Scroll through a page of suggestions and click that you need a new
bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.
Observed behavior: Lots of time spent on the above procedure. Do you
have a way of knowing how many users give up, rather than help you?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Usability issue: the process of filing a bug report is too hard.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and you
want to help Ubuntu. These are the steps for a first time bug report:
(0) look through the application's menus, no hints there how to file a
bug
(1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
(4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
(5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to disagree.
(13) Scroll through a page of suggestions and click that you need a new
bug. (Regarding the wording: Well, actually, I don't need a bug, I'm
extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.
Observed behavior: Lots of time spent on the above procedure. Do you
- have a way of knowing how many users give up, rather than help you?
+ have a way of knowing how many users give up?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1429852
Title:
It is much too hard to file a bug report
Status in apport package in Ubuntu:
New
Bug description:
Usability issue: the process of filing a bug report is too hard.
Steps to reproduce:
Imagine your desktop application (e.g. gnucash) is misbehaving, and
you want to help Ubuntu. These are the steps for a first time bug
report:
(0) look through the application's menus, no hints there how to file a
bug
(1) google how to report a bug, get told to create an account, click through 3 pages and lots of text
https://help.ubuntu.com/community/ReportingBugs
https://help.launchpad.net/YourAccount/NewAccount
https://login.launchpad.net/
(2) wait for verification email
(3) re-type password four 4 times in total
(4) get redirected to the ubuntu-bug utility, which opens up the gnome image viewer instead of doing anything useful
(go try it on a fresh install: https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=unity-ubuntu-bug-pkgname.png)
(5) figure out that ubuntu-bug is a command line utility
(6) figure out which command line command corresponds to your
application
(7) figure out which package contains your desktop application:
$ which gnucash
$ grep -r /usr/bin/gnucash /var/lib/dpkg/info/
(8) run it: $ubuntu-bug gnucash
(9) Wait an unexpectedly long time at a white screen while firefox is
figuring out openid
(10) retype password, fifth time
(11) Type in bug summary (rejoice, finally!)
(12) You'd think software devs would like to make good software and
improve it. But now, your experience gets invalidated and told that
everybody else already knows how to work despite the bug. At least,
that's what the search through (un)related bug reports suggests from a
marketing point of view. So you have to muster some resolve to
disagree.
(13) Scroll through a page of suggestions and click that you need a
new bug. (Regarding the wording: Well, actually, I don't need a bug,
I'm extending my goodwill to help you get rid of one.)
(14) Type in the problem report in this very form here.
Expected behavior: The desktop application should have a button to
report bugs somewhere in the About menu, and it should take at most 3
clicks get it done.
Observed behavior: Lots of time spent on the above procedure. Do you
have a way of knowing how many users give up?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CrashReports:
664:1000:116:0:2015-03-02 17:51:51.797172708 +0100:2015-03-02 17:51:51.797172708 +0100:/var/crash/_usr_bin_nautilus.1000.upload
640:1000:116:6914022:2015-03-02 17:51:50.777172803 +0100:2015-03-02 17:51:51.777172803 +0100:/var/crash/_usr_bin_nautilus.1000.crash
640:1000:116:1936343:2015-03-09 01:25:54.821650091 +0100:2015-03-09 09:57:12.954563948 +0100:/var/crash/_usr_bin_workrave.1000.crash
600:109:116:0:2015-03-02 18:33:35.998493596 +0100:2015-02-25 20:56:00.564689172 +0100:/var/crash/_usr_bin_nautilus.1000.uploaded
CurrentDesktop: Unity
Date: Mon Mar 9 13:46:16 2015
InstallationDate: Installed on 2014-08-08 (212 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1429852/+subscriptions
Follow ups
References
