On screen Keybord non responsive for "Report problem" due to update-notifier using gksu

Bug #1098235 reported by Ben
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-nexus7
Fix Released
High
Unassigned
update-notifier (Ubuntu)
Fix Released
High
Brian Murray

Bug Description

When I choose to "report a problem" via the dialog box, my password is requested, so the keyboard pops up, but, I think, due to the greying out of the all but the password request box the keyboard does not respond to touches.

After downloading and installing "raring-preinstalled-desktop-armhf+nexus7.img.gz" I find that about 10 secouds after the machine has loaded the desktop something crashes .. the dialog box asks if I want to just cancel or Report the problem .. when I choose to report the problem I exsperencie this issue mentioned above

You might want to know I am using the 32GB Nexus 7 Wifi only version, with the MultiBoot hack from XDA in place.

sorry if I have not reported enough detail or this is already known about... let me know if you want more detail.

Related branches

Revision history for this message
Oliver Grawert (ogra) wrote :

what is the content of /var/crash ?

Changed in ubuntu-nexus7:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Oliver Grawert (ogra) wrote :

apparently update-notifier still uses gksu instead of pkexec, gksu grabs the focus and suppresses other application inputs (oncluding onboard).
the code needs to be changed to use pkexec instead, which is:
a) the current standard in ubuntu to gain privileges and
b) does properly work with onscreen keyboards.

summary: - Keybord non responsive for "Report problem"
+ On screen Keybord non responsive for "Report problem" due to update-
+ notifier using gksu
Changed in ubuntu-nexus7:
status: Incomplete → Confirmed
Changed in update-notifier (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in update-notifier (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Brian Murray (brian-murray)
Changed in update-notifier (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-notifier - 0.130

---------------
update-notifier (0.130) raring; urgency=low

  [ Colin Watson ]
  * Only create a single GSettings instance for com.ubuntu.update-notifier,
    rather than several.
  * Remove unused u_abort function.
  * Make several more functions static that aren't used from other
    compilation units.
  * Correct a number of imprecise prototypes.
  * Defer instantiating GtkBuilders until the corresponding user interfaces
    actually need to be displayed, saving memory when they don't.
  * Restore code to keep a handle to crash and reboot notifications, so that
    they can be closed by later code (at least for notification-daemon
    users).
  * Fix several leaks of NotifyNotification objects.
  * Don't call show_hooks (which now includes instantiating the
    corresponding GtkBuilder) if there are no unseen hooks to show.

  [ Brian Murray ]
  * Remove calls to gnome-app-install and addon CD support (LP: #722887)
 -- Colin Watson <email address hidden> Thu, 31 Jan 2013 03:32:33 +0000

Changed in update-notifier (Ubuntu):
status: Fix Committed → Fix Released
Changed in ubuntu-nexus7:
status: Confirmed → Fix Released
Revision history for this message
Ben (bugthing) wrote :

wow! .. thanks very much.
It is amazing that I can report a bug and it gets fixed so quick .. many other OS's could take a few lessons here ;)
Ubuntu crew are supa.. thanks again and well done :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.