Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 228632 - GQ forgets its preferences
Summary: GQ forgets its preferences
Alias: None
Product: Fedora
Classification: Fedora
Component: gq
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-14 02:51 UTC by Ian Chapman
Modified: 2009-01-09 07:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 07:04:32 UTC

Attachments (Terms of Use)

Description Ian Chapman 2007-02-14 02:51:45 UTC
Description of problem:

gq seems to just 'forget' its preference settings, particularly with regards to 
the servers list. For example if I add a few ldap servers into the preferences 
list, eventually they disappear and all I'm left with is 'localhost'.

Version-Release number of selected component (if applicable): gq-1.2.2-2.fc6

How reproducible:

Steps to Reproduce:
1. As a simple example, open up gq, go to preferences and delete the localhost 
entry, assuming a virgin run.
2. Quit gq
3. Load it again and surprisingly its back.
Actual results:
Preferences get mangled somehow, particularly with regards to storing the 
server details. Playing with the "Show Relative Distinguished Name" option, 
seems to cause servers to disappear from the preferences too.

Expected results:
Sane preference handling.

Additional info:

The following sort of messages are frequently seen on the console if launched 
from the command line.

** (gq:3601): CRITICAL **: gq_server_list_get_by_name: assertion `name 
&& *name' failed
[ian@pip ~]$ gq

** (gq:3612): CRITICAL **: is_transient_server: assertion 
`GQ_IS_SERVER(server)' failed

** (gq:3612): CRITICAL **: is_transient_server: assertion 
`GQ_IS_SERVER(server)' failed

** (gq:3612): CRITICAL **: is_transient_server: assertion 
`GQ_IS_SERVER(server)' failed

** (gq:3612): CRITICAL **: gq_server_list_get_by_name: assertion `name 
&& *name' failed

** (gq:3612): CRITICAL **: is_transient_server: assertion 
`GQ_IS_SERVER(server)' failed

** (gq:3612): CRITICAL **: is_transient_server: assertion 
`GQ_IS_SERVER(server)' failed

** (gq:3612): CRITICAL **: gq_server_list_remove: assertion 
`gq_server_list_contains(self, server)' failed

Comment 1 Terje Røsten 2007-02-19 12:38:03 UTC
Yeah, there are several problems in this area.

Upstream has several bugs: #1593645, #1593662, #1593669.
Herzi has done some hacking lately, maybe this stuff will
be better in the next stable upstream release.

Comment 2 Terje Røsten 2008-01-08 22:22:41 UTC
Sven released a gq 1.3.3 today, can you give it a try?

A srpm is available here:

rebuild on your platform with

 $ rpmbuild --rebuild gq-1.3.3-1.fc8.src.rpm

If you can't rebuild your self, I can do it for you if tell the fedora version
and arch you are running. Thanks in advance.

Comment 3 Ian Chapman 2008-01-08 22:43:00 UTC
Thanks, I'll check out the new RPM shortly :-)

Comment 4 Ian Chapman 2008-01-12 01:15:07 UTC
Ah yes, this version seems to work a lot better for me. There's also a few
things I noticed about the srpm.

1. You're missing a BR on gnome-doc-utils
2. You need a BR on /usr/bin/scrollkeeper-config (especially for F7)
3. On F7 you also need something like rm -rf %{buildroot}/var (or equivalent) to
delete the unneeded scrollkeeper crap otherwise it'll fail. This isn't needed
with F8+ because scrollkeeper stuff is handled by rarian I believe.

Thanks! :)

Comment 5 Terje Røsten 2008-01-14 20:38:23 UTC
This sounds good, will update gq to 1.4.0 when it's released.

Thanks for testing and providing feedback on the package.

Comment 6 Terje Røsten 2008-01-21 21:42:23 UTC
New srpm with more fixes available:

Comment 7 Ian Chapman 2008-02-26 15:18:15 UTC
Thanks, missed that. I'll have a look soon.

Comment 8 Ian Chapman 2008-03-19 23:56:01 UTC
(In reply to comment #6)
> New srpm with more fixes available:

Seems to work reasonably well too and builds fine in mock at least for F8 this
time. :)

Comment 9 Bug Zapper 2008-04-04 06:13:23 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 10 Terje Røsten 2008-04-04 21:22:52 UTC
Just to make it clear, comment #9 is bogus, just ignore. Sorry for the noise.

Comment 11 John Poelstra 2008-05-02 23:55:51 UTC
changing version to '8' so this bug does not get closed as part of EOL closing

Comment 12 Bug Zapper 2008-11-26 07:10:59 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

Comment 13 Bug Zapper 2009-01-09 07:04:32 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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