Bug#547177: midori: segfaults when starting under kfreebsd-i386
package midori reassign 547177 libwebkit-1.0-2 1.2.4-1 affects 547177 + midori tags 547177 + confirmed package forcemerge 547177 559925 thanks I can confirm that this issue is caused by the webkit javascript JIT bug on kfreebsd-i386. Using webkit with the webkit-1.2.4-fix_jit_on_kfreebsd-i386-1.patch[1] applied stops midori crashing. Regards, Mike. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=69;filename=webkit-1.2.4-fix_jit_on_kfreebsd-i386-1.patch;att=1;bug=598956 signature.asc Description: OpenPGP digital signature
Bug#547177: midori: segfaults when starting under kfreebsd-i386
Hi, I have to note midori starts under kfreebsd-amd64, but it is unable to open http://www.debian.org. On the other hand it is able to load and render pages like http://www.seznam.cz/ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547177 http://packages.qa.debian.org/m/midori.html http://lists.debian.org/ and even https://buildd.debian.org/ https://buildd.debian.org/~luk/status/package.php?p=midori Petr There is a good amount of messages on the console saying that it can't find some directories under /usr/share/midori (e.g., the scripts and styles directories). It also complains that it cannot set any monitor for directories. Similarly for me: ** (midori:1493): WARNING **: could not monitor /usr/share/midori/scripts: Unable to find default local directory monitor type (midori:1493): GLib-GObject-WARNING **: invalid (NULL) pointer instance (midori:1493): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (midori:1493): WARNING **: could not monitor /usr/local/share/midori/scripts: Unable to find default local directory monitor type (midori:1493): GLib-GObject-WARNING **: invalid (NULL) pointer instance (midori:1493): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (midori:1493): WARNING **: could not monitor /root/.local/share/midori/scripts: Unable to find default local directory monitor type (midori:1493): GLib-GObject-WARNING **: invalid (NULL) pointer instance (midori:1493): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (midori:1493): WARNING **: could not monitor /usr/share/midori/styles: Unable to find default local directory monitor type (midori:1493): GLib-GObject-WARNING **: invalid (NULL) pointer instance (midori:1493): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (midori:1493): WARNING **: could not monitor /usr/local/share/midori/styles: Unable to find default local directory monitor type (midori:1493): GLib-GObject-WARNING **: invalid (NULL) pointer instance (midori:1493): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (midori:1493): WARNING **: could not monitor /root/.local/share/midori/styles: Unable to find default local directory monitor type (midori:1493): GLib-GObject-WARNING **: invalid (NULL) pointer instance (midori:1493): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (midori:1493): Gtk-WARNING **: Unable to find default local directory monitor type (midori:1493): Gtk-WARNING **: Unable to find default local directory monitor type -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547177: midori: segfaults when starting under kfreebsd-i386
Package: midori
Version: 0.1.10-1
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-CC: debian-...@lists.debian.org
Hi, Ryan Co.
Unfortunately, midori segfaults when started under kfreebsd-*.
There is a good amount of messages on the console saying that it can't
find some directories under /usr/share/midori (e.g., the scripts and
styles directories). It also complains that it cannot set any monitor
for directories.
(Sorry, I don't know any way to copy the messages here).
I installed midori-dbg and gdb, but I could not get a backtrace of the
segfault, as gdb says that Cannot access memory at address 0x5. You
can see it for yourself in a kfreebsd VM).
I could not get this reproducible on my linux-amd64 machine, though. I
have not dug in the code yet.
Perhaps what I reported above are red herrings, but they are, at least,
a start in investigating the problem.
I would like very much to have a webkit-based browser running on
kfreebsd. :-)
Thanks, Rogério Brito.
P.S.: Sorry for not providing more information, but I'm almost heading
to bed and my head is exploding.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547177: midori: segfaults when starting under kfreebsd-i386
Hi Rogério, On Thu, Sep 17, 2009 at 09:23:55AM -0300, Rogério Brito wrote: Package: midori Version: 0.1.10-1 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-CC: debian-...@lists.debian.org Hi, Ryan Co. Unfortunately, midori segfaults when started under kfreebsd-*. There is a good amount of messages on the console saying that it can't find some directories under /usr/share/midori (e.g., the scripts and styles directories). It also complains that it cannot set any monitor for directories. (Sorry, I don't know any way to copy the messages here). I installed midori-dbg and gdb, but I could not get a backtrace of the segfault, as gdb says that Cannot access memory at address 0x5. You can see it for yourself in a kfreebsd VM). I could not get this reproducible on my linux-amd64 machine, though. I have not dug in the code yet. Perhaps what I reported above are red herrings, but they are, at least, a start in investigating the problem. sure, and thanks for that. I would like very much to have a webkit-based browser running on kfreebsd. :-) okay, I'll look into it.. tho it might take some time to get a kfreebsd VM set up. Thanks, Rogério Brito. P.S.: Sorry for not providing more information, but I'm almost heading to bed and my head is exploding. I know the feeling ;) Cheers, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
