Seahorse Not Displaying Password Tab

Bug #407063 reported by tekstr1der
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
seahorse
Fix Released
Undecided
Unassigned
seahorse (Fedora)
Fix Released
Medium
seahorse (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Binary package hint: seahorse

Seahorse 2.27.5 is not displaying the password tab and thus I am unable to view or delete network passwords or wireless secrets. Launching seahorse from the terminal results in the following related errors:

$ seahorse

** (seahorse:3910): WARNING **: DNS-SD initialization failed: Daemon not running
** Message: init gpgme version 1.1.8

** (seahorse:3910): WARNING **: could not find widget password-tab for seahorse-key-manager.xml

** (seahorse:3910): CRITICAL **: initialize_tab: assertion `self->pv->tabs[tabid].widget != NULL' failed

ProblemType: Bug
Architecture: i386
Date: Thu Jul 30 15:05:48 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: seahorse 2.27.5-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SourcePackage: seahorse
Uname: Linux 2.6.31-4-generic i686

Related branches

Revision history for this message
tekstr1der (tekstr1der) wrote :
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: http://bugzilla.gnome.org/show_bug.cgi?id=590331

Changed in seahorse (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → High
status: New → Triaged
Changed in seahorse:
status: Unknown → New
Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Created attachment 356040
Screenshow showing missing tabs (2.27.5-1.fc12)

Description of problem:
After updating from seahorse-2.27.1-2.fc12.x86_64 to seahorse-2.27.5-1.fc12.x86_64, seahorse no longer displays "Passwords" and "Trusted Keys" tabs.

See this when running seahorse, first 2.27.1-2 and then 2.27.5-1:

[tbl@tlondon ~]$ seahorse
** Message: init gpgme version 1.1.8
[tbl@tlondon ~]$
[tbl@tlondon ~]$ seahorse
** Message: init gpgme version 1.1.8

** (seahorse:5146): WARNING **: could not find widget password-tab for seahorse-key-manager.xml

** (seahorse:5146): CRITICAL **: initialize_tab: assertion `self->pv->tabs[tabid].widget != NULL' failed
[tbl@tlondon ~]$

I'll attach 2 screenshots: the first showing seahorse-2.27.5-1.fc12.x86_64, the second showing seahorse-2.27.1-2.fc12.x86_64.

Version-Release number of selected component (if applicable):
seahorse-2.27.5-1.fc12.x86_64

How reproducible:
Every time.....

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Created attachment 356042
Screenshot showing "older" seahorse display (2.27.1-2.fc12.x86_64)

This one shows "Passwords" and "Trusted Keys"

Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :
Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Thanks. I cc'ed myself on that BZ.

I'm always in a bit of a quandary whether to file here or upstream...

In the future, would it be helpful if I did the upstream searching first?

Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :

I don't care if you do it before or after, but getting the information upstream is valuable...

Revision history for this message
dobey (dobey) wrote :

Doing a cherry pick reverse patch of http://git.gnome.org/cgit/seahorse/commit/?id=6b7d1de066011d04db35548217f0b64e607abe4b should fix the problem I think...

Changed in seahorse (Fedora):
status: Unknown → Confirmed
Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Upstream reports:

 Comment #2 from Rodney Dawes (developer, points: 20)
2009-08-05 20:05 UTC [reply]

Reverting
http://git.gnome.org/cgit/seahorse/commit/?id=6b7d1de066011d04db35548217f0b64e607abe4b
will fix this problem, it seems. Looks like the "moving the passwords tab"
didn't quite fully happen, and instead it sort of got removed. :-/

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Created attachment 356439
Patch to revert "moving" of Passwords tab

I hand patched and then created a patch file, hacked "seahorse.spec", and then ran "rpmbuild -bb" on the 2.27.5-1 code.

With this patch, I now get "Passwords tab" back.

Had to fiddle a bit with the rpmbuild cmd to get it to accept '/lib64', etc.

Hope this helps....

Revision history for this message
C de-Avillez (hggdh2) wrote :

Stef, upstream, has just fixed this. I built GIT seahorse, and can confirm it. The update should be available for us on next sync/merge from GIT. Marking Fix Committed.

Changed in seahorse (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

New tarballs are due next week

Changed in seahorse (Fedora):
status: Confirmed → Fix Released
Revision history for this message
Neil Broadley (scaine) wrote :

Is there any chance this fix will hit the repos before the Alpha 4 freeze (4 days away)?

Revision history for this message
Sebastien Bacher (seb128) wrote :

The new tarballs are due tomorrow

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package seahorse - 2.27.90-0ubuntu1

---------------
seahorse (2.27.90-0ubuntu1) karmic; urgency=low

  * New upstream relese: (LP: #411609)
    - Fix problem with missing password tab. (LP: #407063)
    - New and updated translations

 -- Andreas Moog <email address hidden> Mon, 10 Aug 2009 21:57:41 +0200

Changed in seahorse (Ubuntu):
status: Fix Committed → Fix Released
tekstr1der (tekstr1der)
Changed in seahorse:
importance: Unknown → Undecided
status: New → Fix Released
Changed in seahorse (Fedora):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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