Page 1 of 1

[solved] Midori

Posted: 12 Oct 2013, 17:46
by donald
something strange:
I downloaded midori (ppm),as a dependency came "libvisual..",
then I clicked "update my modules",a popup said libvisual need an update > ok > next popup
libvisual is updated, now I looked into the module folder and libvisual wasn't updated, it was deleted.
But midori is still starting
any explanation?

And in midori click
menu > preferences > extensions > activate statusbar features,
it seems the icon for the "enable scripts"-button is missing.

Re: Midori

Posted: 12 Oct 2013, 18:07
by brokenman
Thanks Donald.

There was a problem with Midori not resolving all required deps which I am looking into today. Neither slackyd nor our repository update scripts picks up all the required deps for midori. I understand that midori starts for you, but can you browse to a website. Please start it from a terminal and then try to browse to a website. Do you complaints about missing deps?

On my end it requires around 20 dependencies to run properly.

Re: Midori

Posted: 12 Oct 2013, 18:38
by donald
This is written in midori,means browsing is working (also tested google)
here are the cli results:
guest@localhost:~$ midori

(midori4:2412): Gtk-WARNING **: Error loading theme icon 'text-x-javascript' for stock: Icon 'text-x-javascript' not present in theme

(midori4:2412): GLib-GObject-WARNING **: gsignal.c:2459: signal `context-menu' is invalid for instance `0x9ce9000'

....midori comes up

root@localhost:~# midori
The configuration couldn't be loaded: No such file or directory

(midori4:2480): GLib-GObject-WARNING **: gsignal.c:2459: signal `context-menu' is invalid for instance `0x883a008'

....midori comes up
---------------------------------------------------------------------
but what about libvisual, downloading,said updating but deleting??

Re: Midori

Posted: 12 Oct 2013, 18:56
by brokenman
Thanks. Looks like progress is being made.

Re: Midori

Posted: 12 Oct 2013, 20:34
by donald
some additional Info
This is what came down with midori:

geoclue-0.12.99-i486-1sl.xzm
gst-plugins-base-0.10.36-i486-2.xzm
gstreamer-0.10.36-i486-1.xzm
icu4c-49.1.2-i486-1.xzm
libtheora-1.1.1-i486-1.xzm
midori-0.5.5-x86_64-1jay.xzm
webkitgtk-1.8.3-i486-1sl.xzm
and the libvisual-0.4.0..which was deleted before midori's first start.

( I'm still using 2.0 where 007-devel.xzm is present,
I don't know if this makes any difference )

Re: Midori

Posted: 13 Oct 2013, 00:09
by brokenman
Ok I'm not sure what happened with libvisual. I only updated midori and added one other package to the repo. Having it removed is strange indeed. I'm only testing on 2.1.

Re: Midori

Posted: 13 Oct 2013, 01:08
by donald
The libvisual-mystery is splitted into two different parts

1.I got this lib whith the download of midori,and it seems not to belong to midori.

2.the part of updating all my modules with PPM.
ppm says libvisual must be updated,than libvisual is updated, but in fact it's deleted

Why does the PPM act this way? That's the interesting part.
mysterious.. :)

Re: Midori

Posted: 13 Oct 2013, 15:48
by brokenman
I had a 64bit version of midori in the repo (slaps forehead) so I have replaced it with the correct arch. Please remove any midori module from your modules folder and update PPM. I fear we may be back at square one with midori not resolving all deps.

The reason for the anomaly with libvisual is that the (borrowed) code appears to confuse libvisual with it's libvisual-plugins partner. By opening /opt/ppm/PACKAGES.TXT and removing the libvisual-plugins section the problem went away. I will review the code today and push another update as could well affect other packages with plugins. Thanks again Donald for the keen eye.

Re: Midori

Posted: 13 Oct 2013, 17:35
by brokenman
Midori fixed.
Updater fixed.

I'll push the fix for the module updater at a later time. For those that want to fix it line 182 of /opt/porteus-scripts/porteus-package-manager should be changed from:
match=`grep NAME: $OPT/$P|awk '{print$NF}'|grep "^$name-"`
to
match=`grep NAME: $OPT/$P|awk '{print$NF}'|grep "^$name-[0-9]"`

This will do until I can make something cleaner as this will not count for packages such as: package-name-r1234-i486-1sl.xzm

Re: Midori

Posted: 13 Oct 2013, 21:00
by donald
Hi brokenman

I made the changes to line 182,...it works.

but midori-0.5.5-i486-1jay.xzm (4,1KB) only contains
/opt/porteus-scripts/system-desktop-icon,....not midori.

Re: Midori

Posted: 14 Oct 2013, 14:22
by brokenman
Thanks again. Another moron moment. Fixed now. Don't have time now but will do further testing with midori tomorrow.

Re: Midori

Posted: 15 Oct 2013, 14:59
by donald
Hi brokenman

well done, midori is working, replaced ff with midori..no prob.

one little thing is left...in midori please click
"menu > preferences > extensions > then activate statusbar features" now you have
some useful features at the bottom of midori,
but the "enable/disable-scripts-button-ICON" is still missing.
I don't know if this can be fixed, but if yes, it would be perfect.

midori start in terminal:

guest@localhost:~$ midori

(midori4:2578): Gtk-WARNING **: Error loading theme icon 'text-x-javascript' for stock:
Icon 'text-x-javascript' not present in theme

(midori4:2578): GLib-GObject-WARNING **: gsignal.c:2459: signal `context-menu' is invalid for instance `0x9475010'

Re: Midori

Posted: 15 Oct 2013, 19:10
by brokenman
https://dl.dropboxusercontent.com/u/686 ... script.png

Try dropping that file into /usr/share/pixmaps or /usr/share/matefaenza/48/mimetypes.

Re: Midori

Posted: 16 Oct 2013, 04:09
by donald
Hi brokenman

putting your Icon into /usr/share/pixmaps works
another missing icon (bookmarks),choose one you like and rename it to "user-bookmarks.png"

First time activating a merged midori-module brought up a error-message " could not refresh
the panel",just click OK and ignore it,it don't came up next time.

I didn't test all build-in extensions, but don't use
"DevPet..This extension shows glib error messages in systray"
in my case midori hangs ( no messages in terminal ) empty midori window.
To get midori working again,
open /guest/.config/midori/config and delete the DevPet-line under [extensions]

no "Gtk-WARNING" anymore
the "GLib-GObject-WARNING" still persists

In general midori works and uses just 43Mb of ram

What do you think solved or not?

Re: Midori

Posted: 16 Oct 2013, 14:51
by brokenman
I'm not sure what the gobject warning is about. If you feel basic functionality is usable I would mark it solved. Thanks.