Public bug reported:

Please consider a less dramatic end-user notification for "problem"
notifications.

I'm transitioning long-time Microsoft Windows and some Apple Mac users
to Ubuntu. Often, they are "change resistant" -- looking for any reason
to claim that Ubuntu(Linux) is not "as good", etc..

Please consider changing the user-facing crash dialogs with wording such
as:

<b>Correcting for system anomaly</b>

Submitting report to authors.

      [  Continue  ]

Then, silently gather report data and submit to maintainers/developers.

More often then not, in my experience, these crashes are recoverable and
deal with things like:  cups-browsed, hpps, Xorg, etc. which are foreign
concepts to end-users anyway.

Make the current developer/technician friendly notifications an opt-in
config from an 'update-alternatives' or similar post-install process.

Thank you for your consideration in making Ubuntu an easier transition
for non-technical end-users and their sysadmins.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: apport-gtk 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportLog:

ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CrashReports:
 600:111:119:0:2017-05-09 19:57:34.728573229 -0500:2017-05-09 
19:57:34.728573229 -0500:/var/crash/_usr_sbin_cups-browsed.0.uploaded
 640:0:119:975906:2017-05-09 19:57:29.201163768 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.crash
 644:0:119:0:2017-05-09 19:57:32.328877937 -0500:2017-05-09 19:57:32.328877937 
-0500:/var/crash/_usr_sbin_cups-browsed.0.upload
CurrentDesktop: GNOME
Date: Thu May 11 07:33:43 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-05-09 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug zesty

** Description changed:

  Please consider a less dramatic end-user notification for "problem"
  notifications.
  
  I'm transitioning long-time Microsoft Windows and some Apple Mac users
  to Ubuntu. Often, they are "change resistant" -- looking for any reason
  to claim that Ubuntu(Linux) is not "as good", etc..
  
  Please consider changing the user-facing crash dialogs with wording such
  as:
  
  "Correcting for system anomaly
  Submitting report to authors"
  
-       [  Continue  ]
- 
+       [  Continue  ]
  
  Then, silently gather report data and submit to maintainers/developers.
  
  More often then not, in my experience, these crashes are recoverable and
  deal with things like:  cups-browsed, hpps, Xorg, etc. which are foreign
  concepts to end-users anyway.
  
  Make the current developer/technician friendly notifications an opt-in
- config from a 'update-alternatives' or similar post-install process.
+ config from an 'update-alternatives' or similar post-install process.
  
- 
- Thank you for your consideration in making Ubuntu an easier transition for 
non-technical end-users and their sysadmins.
+ Thank you for your consideration in making Ubuntu an easier transition
+ for non-technical end-users and their sysadmins.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportLog:
-  
+ 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports:
-  600:111:119:0:2017-05-09 19:57:34.728573229 -0500:2017-05-09 
19:57:34.728573229 -0500:/var/crash/_usr_sbin_cups-browsed.0.uploaded
-  640:0:119:975906:2017-05-09 19:57:29.201163768 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.crash
-  644:0:119:0:2017-05-09 19:57:32.328877937 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.upload
+  600:111:119:0:2017-05-09 19:57:34.728573229 -0500:2017-05-09 
19:57:34.728573229 -0500:/var/crash/_usr_sbin_cups-browsed.0.uploaded
+  640:0:119:975906:2017-05-09 19:57:29.201163768 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.crash
+  644:0:119:0:2017-05-09 19:57:32.328877937 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.upload
  CurrentDesktop: GNOME
  Date: Thu May 11 07:33:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Please consider a less dramatic end-user notification for "problem"
  notifications.
  
  I'm transitioning long-time Microsoft Windows and some Apple Mac users
  to Ubuntu. Often, they are "change resistant" -- looking for any reason
  to claim that Ubuntu(Linux) is not "as good", etc..
  
  Please consider changing the user-facing crash dialogs with wording such
  as:
  
- "Correcting for system anomaly
- Submitting report to authors"
+ [b]Correcting for system anomaly[/b]
+ 
+ Submitting report to authors.
+ 
  
        [  Continue  ]
+ 
  
  Then, silently gather report data and submit to maintainers/developers.
  
  More often then not, in my experience, these crashes are recoverable and
  deal with things like:  cups-browsed, hpps, Xorg, etc. which are foreign
  concepts to end-users anyway.
  
  Make the current developer/technician friendly notifications an opt-in
  config from an 'update-alternatives' or similar post-install process.
  
  Thank you for your consideration in making Ubuntu an easier transition
  for non-technical end-users and their sysadmins.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportLog:
  
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports:
   600:111:119:0:2017-05-09 19:57:34.728573229 -0500:2017-05-09 
19:57:34.728573229 -0500:/var/crash/_usr_sbin_cups-browsed.0.uploaded
   640:0:119:975906:2017-05-09 19:57:29.201163768 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.crash
   644:0:119:0:2017-05-09 19:57:32.328877937 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.upload
  CurrentDesktop: GNOME
  Date: Thu May 11 07:33:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Please consider a less dramatic end-user notification for "problem"
  notifications.
  
  I'm transitioning long-time Microsoft Windows and some Apple Mac users
  to Ubuntu. Often, they are "change resistant" -- looking for any reason
  to claim that Ubuntu(Linux) is not "as good", etc..
  
  Please consider changing the user-facing crash dialogs with wording such
  as:
  
- [b]Correcting for system anomaly[/b]
+ <b>Correcting for system anomaly</b>
  
  Submitting report to authors.
  
- 
        [  Continue  ]
- 
  
  Then, silently gather report data and submit to maintainers/developers.
  
  More often then not, in my experience, these crashes are recoverable and
  deal with things like:  cups-browsed, hpps, Xorg, etc. which are foreign
  concepts to end-users anyway.
  
  Make the current developer/technician friendly notifications an opt-in
  config from an 'update-alternatives' or similar post-install process.
  
  Thank you for your consideration in making Ubuntu an easier transition
  for non-technical end-users and their sysadmins.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportLog:
  
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports:
   600:111:119:0:2017-05-09 19:57:34.728573229 -0500:2017-05-09 
19:57:34.728573229 -0500:/var/crash/_usr_sbin_cups-browsed.0.uploaded
   640:0:119:975906:2017-05-09 19:57:29.201163768 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.crash
   644:0:119:0:2017-05-09 19:57:32.328877937 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.upload
  CurrentDesktop: GNOME
  Date: Thu May 11 07:33:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1690143

Title:
  More end-user friendly dialogs on crash notifications

Status in apport package in Ubuntu:
  New

Bug description:
  Please consider a less dramatic end-user notification for "problem"
  notifications.

  I'm transitioning long-time Microsoft Windows and some Apple Mac users
  to Ubuntu. Often, they are "change resistant" -- looking for any
  reason to claim that Ubuntu(Linux) is not "as good", etc..

  Please consider changing the user-facing crash dialogs with wording
  such as:

  <b>Correcting for system anomaly</b>

  Submitting report to authors.

        [  Continue  ]

  Then, silently gather report data and submit to
  maintainers/developers.

  More often then not, in my experience, these crashes are recoverable
  and deal with things like:  cups-browsed, hpps, Xorg, etc. which are
  foreign concepts to end-users anyway.

  Make the current developer/technician friendly notifications an opt-in
  config from an 'update-alternatives' or similar post-install process.

  Thank you for your consideration in making Ubuntu an easier transition
  for non-technical end-users and their sysadmins.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportLog:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports:
   600:111:119:0:2017-05-09 19:57:34.728573229 -0500:2017-05-09 
19:57:34.728573229 -0500:/var/crash/_usr_sbin_cups-browsed.0.uploaded
   640:0:119:975906:2017-05-09 19:57:29.201163768 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.crash
   644:0:119:0:2017-05-09 19:57:32.328877937 -0500:2017-05-09 
19:57:32.328877937 -0500:/var/crash/_usr_sbin_cups-browsed.0.upload
  CurrentDesktop: GNOME
  Date: Thu May 11 07:33:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1690143/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to