Debian Bug report logs - #449288
Syntax Highlighting dialog stays empty when choosing filetype

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Christophe Grandsire <christophe.grandsire@free.fr>

To: submit@bugs.debian.org

Subject: Syntax Highlighting dialog stays empty when choosing filetype

Date: Sun, 04 Nov 2007 20:15:03 +0100

Package: bluefish
Version: 1.0.7-3
Severity: normal

--- Please enter the report below this line. ---
When going to the syntax highlighting dialog (Edit -> Preferences -> 
Syntax highlighting) and choosing any filetype in its combo box, the 
"Pattern" list box gets filled with the various existing patterns for 
this filetype.

However, when clicking on those patterns to check them, the rest of the 
dialog stays empty: it does *not* get filled with the details of the 
chosen pattern (regexes, colour, etc.). It is the only dialog in the 
Preferences window that seems to fail, all the others seem to work 
correctly.

Despite that, syntax highlighting works correctly, and new syntax 
highlighting patterns are correctly picked up when the "highlighting" 
file in ~/.bluefish/ is directly modified. It's only the dialog itself 
that fails to work (which makes it difficult to test new syntax 
highlighting patterns quickly).

Note that the dialog worked correctly when I was still using GNOME 2.18 
(mostly, as there were times when it did fail to load details as well, 
but usually closing the Preferences window and reopening it was enough). 
Now that I finally updated my Sid installation to GNOME 2.20, the dialog 
always fails to show pattern details.

Thanks in advance for your help.

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.22-3-686

Debian Release: lenny/sid
  500 unstable        www.debian-multimedia.org
  500 unstable        ftp.nl.debian.org
  500 unstable        ftp.fr.debian.org
  500 unstable        ftp.easynet.be
  500 unstable        ftp.debian.org
  500 unstable        ftp.de.debian.org
  500 unstable        deb.opera.com

--- Package information. ---
Depends                    (Version) | Installed
====================================-+-===============
libart-2.0-2             (>= 2.3.18) | 2.3.19-3
libaspell15                (>= 0.60) | 0.60.5-1
libatk1.0-0              (>= 1.20.0) | 1.20.0-1
libbonobo2-0             (>= 2.15.0) | 2.20.1-1
libbonoboui2-0           (>= 2.15.1) | 2.20.0-1
libc6                   (>= 2.6.1-1) | 2.6.1-6
libcairo2                 (>= 1.4.0) | 1.4.10-1
libfontconfig1            (>= 2.4.0) | 2.4.91-1
libgconf2-4              (>= 2.13.5) | 2.20.1-1
libglib2.0-0             (>= 2.14.0) | 2.14.2-1
libgnome2-0              (>= 2.17.3) | 2.20.1.1-1
libgnomecanvas2-0        (>= 2.11.1) | 2.20.1.1-1
libgnomeui-0             (>= 2.17.1) | 2.20.1.1-1
libgnomevfs2-0        (>= 1:2.17.90) | 1:2.20.0-3
libgtk2.0-0              (>= 2.12.0) | 2.12.1-1
libice6                 (>= 1:1.0.0) | 2:1.0.4-1
liborbit2              (>= 1:2.14.1) | 1:2.14.7-0.1
libpango1.0-0            (>= 1.18.2) | 1.18.3-1
libpcre3                    (>= 6.0) | 7.3-2
libpopt0                   (>= 1.10) | 1.10-3
libsm6                               | 2:1.0.3-1+b1
libx11-6                             | 2:1.0.3-7
libxcomposite1          (>= 1:0.3-1) | 1:0.3.2-1+b1
libxcursor1               (>> 1.1.2) | 1:1.1.9-1
libxdamage1               (>= 1:1.1) | 1:1.1.1-3
libxext6                             | 1:1.0.3-2
libxfixes3              (>= 1:4.0.1) | 1:4.0.3-2
libxi6                               | 2:1.1.3-1
libxinerama1                         | 1:1.0.2-1
libxrandr2              (>= 2:1.2.0) | 2:1.2.2-1
libxrender1                          | 1:0.9.4-1


-- 
Christophe Grandsire-Koevoets.

Message #10 received at 449288@bugs.debian.org (full text, mbox, reply):

From: Daniel Leidert <daniel.leidert@wgdd.de>

To: 449288@bugs.debian.org

Cc: 449288-submitter@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Sun, 04 Nov 2007 22:32:30 +0100

Am Sonntag, den 04.11.2007, 20:15 +0100 schrieb Christophe Grandsire:

> When going to the syntax highlighting dialog (Edit -> Preferences -> 
> Syntax highlighting) and choosing any filetype in its combo box, the 
> "Pattern" list box gets filled with the various existing patterns for 
> this filetype.
> 
> However, when clicking on those patterns to check them, the rest of the 
> dialog stays empty: it does *not* get filled with the details of the 
> chosen pattern (regexes, colour, etc.). It is the only dialog in the 
> Preferences window that seems to fail, all the others seem to work 
> correctly.

Hm. I could think of a "corruption" of the rc_file in your users
directory (~/.bluefish/). The way the pattern are stored is not the best
(we are thinking about some improvements). Pattern can be split in this
file. You could do me a favour and test the following, if it maybe
solves your problem.

First backup your users directory ${HOME}/.bluefish.

1) you can try to reset the highlighting pattern (follow the
instructions in README.Debian)
2) remove the whole users ${HOME}/.bluefish directory and try again

Is your problem solved?

[..]
> Note that the dialog worked correctly when I was still using GNOME 2.18 
> (mostly, as there were times when it did fail to load details as well, 
> but usually closing the Preferences window and reopening it was enough). 
> Now that I finally updated my Sid installation to GNOME 2.20, the dialog 
> always fails to show pattern details.

Hm. I'm using the same GNOME version and everything works as expected.

Regards, Daniel

Message #18 received at 449288-quiet@bugs.debian.org (full text, mbox, reply):

From: Christophe Grandsire-Koevoets <christophe.grandsire@free.fr>

To: Daniel Leidert <daniel.leidert@wgdd.de>, 449288-quiet@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Mon, 05 Nov 2007 21:09:04 +0100

Selon Daniel Leidert :
> 
> Hm. I could think of a "corruption" of the rc_file in your users
> directory (~/.bluefish/). The way the pattern are stored is not the best
> (we are thinking about some improvements). Pattern can be split in this
> file. You could do me a favour and test the following, if it maybe
> solves your problem.
> 
> First backup your users directory ${HOME}/.bluefish.
> 
> 1) you can try to reset the highlighting pattern (follow the
> instructions in README.Debian)
> 2) remove the whole users ${HOME}/.bluefish directory and try again
> 
> Is your problem solved?
> 

OK, that's weird. I tried the two steps you mentioned, and neither 
helped. I still couldn't see the pattern details. Then I removed again 
the whole .bluefish folder and put back the back-up, and now it works again!

That's a weird error, and I have no idea what's causing it...

> 
> Hm. I'm using the same GNOME version and everything works as expected.
> 

It seems indeed to have no influence on the error. If it happens again I 
will look at it further...

Thanks anyway for the reply.

Regards,
-- 
Christophe Grandsire-Koevoets.

http://christophoronomicon.blogspot.com
http://rainbow.conlang.free.fr

You need a straight mind to invent a twisted conlang.

Message #23 received at 449288-quiet@bugs.debian.org (full text, mbox, reply):

From: Christophe Grandsire-Koevoets <christophe.grandsire@free.fr>

To: Daniel Leidert <daniel.leidert@wgdd.de>, 449288-quiet@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Mon, 05 Nov 2007 21:33:44 +0100

Selon Daniel Leidert :
> 
> Is your problem solved?
> 

OK, bad news. After stopping and restarting Bluefish, the problem 
reappeared, and this time doing all the steps again didn't help...

I don't understand...

Regards,
-- 
Christophe Grandsire-Koevoets.

http://christophoronomicon.blogspot.com
http://rainbow.conlang.free.fr

You need a straight mind to invent a twisted conlang.

Message #28 received at 449288-quiet@bugs.debian.org (full text, mbox, reply):

From: Daniel Leidert <daniel.leidert@wgdd.de>

To: 449288-quiet <449288-quiet@bugs.debian.org>

Cc: 449288-submitter@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Tue, 06 Nov 2007 01:03:24 +0100

Am Montag, den 05.11.2007, 21:33 +0100 schrieb Christophe
Grandsire-Koevoets:
> Selon Daniel Leidert :
> > 
> > Is your problem solved?
> > 
> 
> OK, bad news. After stopping and restarting Bluefish, the problem 
> reappeared, and this time doing all the steps again didn't help...

If you run Bluefish from the command line, do you see some Gtk warnings
or so, when you try to access the "broken" dialog?

Can you further do me a favour and send me your .bluefish directory?

Regards, Daniel

Message #36 received at 449288-quiet@bugs.debian.org (full text, mbox, reply):

From: Christophe Grandsire-Koevoets <christophe.grandsire@free.fr>

To: Daniel Leidert <daniel.leidert@wgdd.de>, 449288-quiet@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Wed, 07 Nov 2007 20:20:39 +0100

[Message part 1 (text/plain, inline)]

Selon Daniel Leidert :
> 
> If you run Bluefish from the command line, do you see some Gtk warnings
> or so, when you try to access the "broken" dialog?
> 

I tried three times, and once I did get some warnings:

(bluefish:3396): GLib-GObject-WARNING **: 
/tmp/buildd/glib2.0-2.14.2/gobject/gsignal.c:1741: instance `0x842dba8' 
has no handler with id `5265'

(bluefish:3396): GLib-GObject-WARNING **: 
/tmp/buildd/glib2.0-2.14.2/gobject/gsignal.c:1741: instance `0x842dba8' 
has no handler with id `5266'

However, I don't know exactly when they happened (I think it was when I 
clicked on a filetype in the Syntax Highlighting dialog), and it did 
that only once. The other two times I did exactly the same actions, 
without getting any warning (and still without getting the patterns 
visible).

> Can you further do me a favour and send me your .bluefish directory?
> 

I've attached it to this mail.

Thanks again for your help.

Regards,
-- 
Christophe Grandsire-Koevoets.

http://christophoronomicon.blogspot.com
http://rainbow.conlang.free.fr

You need a straight mind to invent a twisted conlang.

[bluefish.tar.gz (application/x-gzip, inline)]

Message #41 received at 449288-quiet@bugs.debian.org (full text, mbox, reply):

From: Daniel Leidert <daniel.leidert@wgdd.de>

To: 449288-quiet <449288-quiet@bugs.debian.org>

Cc: 449288-submitter@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Sat, 10 Nov 2007 22:57:26 +0100

Am Mittwoch, den 07.11.2007, 20:20 +0100 schrieb Christophe
Grandsire-Koevoets:
> Selon Daniel Leidert :
> > 
> > If you run Bluefish from the command line, do you see some Gtk warnings
> > or so, when you try to access the "broken" dialog?
> > 
> 
> I tried three times, and once I did get some warnings:
> 
> (bluefish:3396): GLib-GObject-WARNING **: 
> /tmp/buildd/glib2.0-2.14.2/gobject/gsignal.c:1741: instance `0x842dba8' 
> has no handler with id `5265'
> 
> (bluefish:3396): GLib-GObject-WARNING **: 
> /tmp/buildd/glib2.0-2.14.2/gobject/gsignal.c:1741: instance `0x842dba8' 
> has no handler with id `5266'
> 
> However, I don't know exactly when they happened (I think it was when I 
> clicked on a filetype in the Syntax Highlighting dialog), and it did 
> that only once. The other two times I did exactly the same actions, 
> without getting any warning (and still without getting the patterns 
> visible).

Hm, I tested your .bluefish directory and nothing happened. Everything
works as expected. Can you do me a favour and rebuild the bluefish
package with debugging output. This means: Get the source from the
Debian archive. Edit debian/rules and add the --enable-debugging-output
configure option, build and install the package (maybe build it with
DEB_BUILD_OPTIONS=nostrip to disable stripping of the binary). Then
simply run bluefish and pipe all (debugging) output (2>&1) to a file and
attach this file to your report.

BTW: Are you running Bluefish under C locale?

Regards, Daniel

Message #53 received at 449288-quiet@bugs.debian.org (full text, mbox, reply):

From: Daniel Leidert <daniel.leidert@wgdd.de>

To: 449288-quiet <449288-quiet@bugs.debian.org>, control <control@bugs.debian.org>

Cc: 449288-submitter@bugs.debian.org

Subject: Re: Bug#449288: Syntax Highlighting dialog stays empty when choosing filetype

Date: Tue, 27 Nov 2007 05:28:57 +0100

tags 449288 + confirmed
forwarded 449288 http://bugzilla.gnome.org/show_bug.cgi?id=498954
thanks

Am Montag, den 05.11.2007, 21:09 +0100 schrieb Christophe Grandsire-Koevoets:
> Selon Daniel Leidert :
> > 
> > Hm. I could think of a "corruption" of the rc_file in your users
> > directory (~/.bluefish/).

No corruption. I can now reproduce the issue. Unfortunately there is no
output that tells, what could go wrong here (but I guess it's caused by
the new GTK). Now that I'm able to reproduce the issue I will try to
examine the cause and fix it.

Regards, Daniel

Message #63 received at 449288@bugs.debian.org (full text, mbox, reply):

From: Daniel Leidert (dale) <daniel.leidert@wgdd.de>

To: control@bugs.debian.org

Cc: 449288@bugs.debian.org

Subject: tagging 449288

Date: Fri, 25 Jan 2008 14:21:38 +0100

# Automatically generated email from bts, devscripts version 2.10.13
# A fix is available and will be uploaded ASAP.
tags 449288 + pending

Message #72 received at 449288-close@bugs.debian.org (full text, mbox, reply):

From: Daniel Leidert (dale) <daniel.leidert@wgdd.de>

To: 449288-close@bugs.debian.org

Subject: Bug#449288: fixed in bluefish 1.0.7-4

Date: Fri, 08 Feb 2008 00:17:03 +0000

Source: bluefish
Source-Version: 1.0.7-4

We believe that the bug you reported is fixed in the latest version of
bluefish, which is due to be installed in the Debian FTP archive:

bluefish_1.0.7-4.diff.gz
  to pool/main/b/bluefish/bluefish_1.0.7-4.diff.gz
bluefish_1.0.7-4.dsc
  to pool/main/b/bluefish/bluefish_1.0.7-4.dsc
bluefish_1.0.7-4_i386.deb
  to pool/main/b/bluefish/bluefish_1.0.7-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 449288@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Leidert (dale) <daniel.leidert@wgdd.de> (supplier of updated bluefish package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue, 05 Feb 2008 03:03:47 +0100
Source: bluefish
Binary: bluefish
Architecture: source i386
Version: 1.0.7-4
Distribution: unstable
Urgency: low
Maintainer: Daniel Leidert (dale) <daniel.leidert@wgdd.de>
Changed-By: Daniel Leidert (dale) <daniel.leidert@wgdd.de>
Description: 
 bluefish   - advanced Gtk+ HTML editor
Closes: 449288
Changes: 
 bluefish (1.0.7-4) unstable; urgency=low
 .
   * debian/control: Added DM-Upload-Allowed for DM status.
     (Standards-Version): Raised to 3.7.3.
   * debian/rules: Added LDFLAGS to drop useless dependencies (should be safe
     here). Make sure, there are no unresolved symbols.
   * debian/patches/04_fix_maximization_state_save.dpatch: Added.
     - Fixes a long-time-standing bug, that prevents bluefish from saving the
       maximization state, if people quit with File > Quit.
   * debian/patches/05_fix_449288_hlt_pattern_dialog.dpatch: Added.
     - Fixes the empty highlighting pattern dialog (closes: #449288). Thanks to
       Jim Hayward for the patch.
   * debian/patches/00list: Adjusted.
Files: 
 31a97d401497daae15c65c3a621d2494 785 web optional bluefish_1.0.7-4.dsc
 1f1c0f49bb4197841ca09372b5732fc2 31342 web optional bluefish_1.0.7-4.diff.gz
 51721abc8e509a7048aef749cf046b39 1608114 web optional bluefish_1.0.7-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFHq52hmHaJYZ7RAb8RAhvxAJ9Nu50HN+NeguhbwY4IJu0ZDZC69QCgyaD9
0+2F+AYjX5tTfnC1aeqzc6c=
=SHbX
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.