Ubuntu
peacock package

Crash on New File

Bug #33759 reported by Lukas Sabota
14
Affects Status Importance Assigned to Milestone
peacock (Debian)
Fix Released
Unknown
peacock (Ubuntu)
Fix Released
Medium
MOTU

Bug Description

Whenever I try to create a new HTML file, peacock will crash. These are the errors printed to the terminal:

(peacock-2:7012): Bonobo-WARNING **: Activation exception 'Failed to activate 'OAFIID:GNOME_GtkHTML_Editor:3.0''

(peacock-2:7012): Bonobo-CRITICAL **: bonobo_widget_set_property: assertion `control != NULL' failed

See original description
Revision history for this message
In , Noël Köthe (noel) wrote : Re: Bug#262440: peacock segfaults on every action

tags 262440 + upstream confirmed
forwared 262440 https://sf.net/tracker/index.php?func=detail&aid=1232366&group_id=3369&atid=103369
thanks

Am Samstag, den 31.07.2004, 02:12 +0200 schrieb Marc Lehmann:

> In short: peacock crashes on both open or new.
>
> After starting, I get a window. Hitting either New or Open + selectign a
> html file, gives me the following messages and peacock segfaults:
>
> *cerebro /tmp# peacock-2
>
> (peacock-2:10295): gtkhtml-WARNING **: Cannot create spell dictionary instance (iid:OAFIID:GNOME_Spell_Dictionary:0.3)
>
> (peacock-2:10295): GLib-GObject-WARNING **: invalid cast from `ColorCombo' to `GtkBox'
>
> (peacock-2:10295): GLib-GObject-WARNING **: invalid cast from `ColorCombo' to `GtkBox'

Yes its reproduceable.:(
I reported it to the upstream author.

thx for the report.

--
Noèl Köthe <noel debian.org>
Debian GNU/Linux, www.debian.org

Revision history for this message
In , Noël Köthe (noel) wrote : forwarded

forwarded 262440 https://sf.net/tracker/index.php?func=detail&aid=1232366&group_id=3369&atid=103369

--
Noèl Köthe <noel debian.org>
Debian GNU/Linux, www.debian.org

Revision history for this message
Lukas Sabota (punkrockguy318) wrote :

Whenever I try to create a new HTML file, peacock will crash. These are the errors printed to the terminal:

(peacock-2:7012): Bonobo-WARNING **: Activation exception 'Failed to activate 'OAFIID:GNOME_GtkHTML_Editor:3.0''

(peacock-2:7012): Bonobo-CRITICAL **: bonobo_widget_set_property: assertion `control != NULL' failed

Daniel Robitaille (robitaille)
Changed in peacock:
assignee: nobody → motu
Revision history for this message
Gauvain Pocentek (gpocentek) wrote : gdb backtrace

I confirm this issue on dapper with peacock 1.9.1-6ubuntu2.
Backtrace attached.

Changed in peacock:
status: Unconfirmed → Confirmed
Revision history for this message
Rok Ruzic (rruzic) wrote : Q&D fix

I got a quick and dirty fix for this, here is the diff that fixes the bug on dapper. See attachment.

... the patch probbaly doesn't work because the febform processing broke it, just edit the file manually

... this however is just a quick and dirty fix. The problem is, that the version of the control is hardcoded in the sources.

There are three good fixes for this one, you should just decide what to use.

1. #define should be produced by the configure script after checking the installed version of libgtkhtml at compile-time.

2. the value should be determined dynamically at run-time, by reading listing of usr/lib/bonobo/servers.

3. peacock package should depend on the proper version of libgtkhtml (this fix is the worst of the three, but it doesn't mess with upstream).

If you decide on one of these two fixes and don't have the time to code them up, please do not hesitate to contact me.

Revision history for this message
Lukas Sabota (punkrockguy318) wrote :

Any work on getting this patch committed?

Revision history for this message
Vassilis Pandis (pandisv) wrote :

The Debian maintainer has decide to go with the 3rd solution, and peacock now depends on libgtkhtml-3.8dev. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262440 for more information. This has been fixed in Edgy.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Sorry, I was wrong. This is still an issue with edgy.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

The attached Q&D fix doesn't work for me.

Bug Watch Updater (bug-watch-updater)
Changed in peacock:
status: Unknown → Confirmed
Revision history for this message
In , Øystein Gisnås (oystein-gisnas) wrote : Package peacock unusable

package peacock
severity 262440 grave
thanks

This bug renders the package completely unusable, hence is it a grave
bug according to http://www.debian.org/Bugs/Developer#severities. To
me it sounds reasonable that this bug either must be fixed or the
package not be released with etch.

Revision history for this message
In , Steve McIntyre (steve-mcintyre) wrote : Please remove peacock - clearly not fit for release

retitle 262440 RM: please remove peacock - unfit for release
reassign 262440 ftp.debian.org
thanks

I've just checked, and peacock still crashes immediately upon opening
or creating a page. No response at all from upstream, nor any recent
bug activity at all from a quick look at

  http://sourceforge.net/tracker/?atid=103369&group_id=3369&func=browse

Time to lose this package IMHO - it doesn't look like a fix is coming...

--
Steve McIntyre, Cambridge, UK. <email address hidden>
"Every time you use Tcl, God kills a kitten." -- Malcolm Ray

Revision history for this message
In , Steve Langasek (vorlon) wrote : cloning 262440, reassign -1 to peacock, severity of 262440 is normal ...

# Automatically generated email from bts, devscripts version 2.9.21
clone 262440 -1
reassign -1 peacock
severity 262440 normal
retitle -1 peacock segfaults on every action

Revision history for this message
In , Adam D. Barratt (debian-bts-adam-barratt) wrote : retitle 262440 to RM: peacock -- RoQA; unsuitable for release

# Automatically generated email from bts, devscripts version 2.9.21
retitle 262440 RM: peacock -- RoQA; unsuitable for release

Revision history for this message
In , Adam D. Barratt (debian-bts-adam-barratt) wrote : bug 262440 is not forwarded, tagging 262440

# Automatically generated email from bts, devscripts version 2.9.21
notforwarded 262440
tags 262440 =

Bug Watch Updater (bug-watch-updater)
Changed in peacock:
status: Confirmed → Unconfirmed
Revision history for this message
In , Debian Archive Maintenance (ftpmaster) wrote : Bug#262440: fixed

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   peacock | 1.9.1-7.1 | source, alpha, amd64, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System. Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
<email address hidden>.

Debian distribution maintenance software
pp.
Anthony Towns (the ftpmaster behind the curtain)

Bug Watch Updater (bug-watch-updater)
Changed in peacock:
status: Unconfirmed → Fix Released
Revision history for this message
Vassilis Pandis (pandisv) wrote :

Peacock was removed from Debian because of this bug.

Revision history for this message
William Grant (wgrant) wrote :

A bug[1] was filed with upstream 1.5 years ago. There has been no response.

[1] https://sourceforge.net/tracker/index.php?func=detail&aid=1232366&group_id=3369&atid=103369

Revision history for this message
Barry deFreese (bddebian) wrote :

Looks to me like this is a candidate for removal from the archives. Debian has dropped it and upstream seems to have been dead since 2003?

Revision history for this message
William Grant (wgrant) wrote :

Sounds good to me.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

'Fixed' in gutsy by removing it.

Changed in peacock:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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