csant/log

And the qt4 version is static right? I need everything told twice it seems


- ØØ -

Actually I kind of liked the old ones as they had date on filename. But this works as well.

Now all we (or at least I) need is 64-bit Qt4 shared build. After this http://labs.trolltech.com/blogs/2008/05/13/introducing-qgtkstyle/ Opera is pretty much the last piece on my desktop which isn't really looking as good as it could.

+1 for a 64-bit Qt4 shared build.

Why is .9 = gcc4-qt4 requiring libqt3-mt ? That does not make sense.

1) In package "opera-9.50-1971.gcc4-qt4.i386.tar.bz2" there is lack of "static" word.
2) There isn't gcc4 + shared qt4. Please, compile that version! I hate Opera with it's own style in my nice KDE4.

Qt4 shared build would be excellent!

Qt4 shared build would be excellent!

Exactly. This is not like 64-bit build, which we could live without. KDE 4 is expected to take over, and qt4-static is as unacceptable as qt3-static was with KDE3.

csant: is this any big problem to add qt4 shared version to list of builds?

/me takes his crystal ball...

Oh, you gonna detect presence of Qt and use shared then. In other case you gonna use static.

Nice but this will increase size of package, won't it?

With opera_9.50-1971.gcc4-shared-qt3_i386.deb:

dpkg - warning: downgrading opera from 9.50-20080508.6 to 9.50.

Perhaps the date would be nice in there, so dpkg knows which version is newer? If this is taken care of in another way, just ignore me

avec le dernier version je n arrive pas a me conecter chez netvibes !

problem with the new version 10005 in www.netvibes.com

Wouldn't it be better to include the build number in the version string?
There's no way to track superseded versions if the version is only 9.50.
(at least that's what I see for the dpkg packages)

Why does this .9 version conflict with the old .9 version ("Error: Conflicts with the installed package opera-static")? Will I have to uninstall the old to get the new and will it keep my settings? Does this version support the semi-native theming as the old version did?

@remco:

AFAIK, on ubuntu you use the compare-version to check wich one is the newest.

#!/bin/bash                                                                                                                                                                         

if dpkg --compare-versions opera_static-9.50-1971.gcc4-qt4_i386.deb gt opera-static_9.50-20080508.9-static-qt_i386.deb
then
        echo "9.50-1971.gcc4-qt4 is newer"
else
         echo "9.50-20080508.9-static-qt_i386 is newer"
fi

// Outputs:
// 9.50-1971.gcc4-qt4 is newer

The reason for the conflicts looke like is because it is now named Opera, and not Opera-static anymore. So it tries to install over opera instead of Opera-static. And thats where you get your conflict.

noteme@notebuntu:~$ dpkg --info opera_static-9.50-1971.gcc4-qt4_i386.deb
 new debian package, version 2.0.
 size 10635700 bytes: control archive= 7030 bytes.
      34 bytes,     2 lines      conffiles            
    1251 bytes,    21 lines      control              
   16647 bytes,   232 lines      md5sums              
    1719 bytes,    54 lines   *  postinst             #!/bin/sh
     572 bytes,    18 lines   *  postrm               #!/bin/sh
     179 bytes,     9 lines   *  prerm                #!/bin/sh
 [COLOR=red]Package: opera[/COLOR]
 Version: 9.50
 Section: non-free/web
 Priority: optional
 Architecture: i386
 Depends: libc6 (>= 2.1.3), xlib6g (>= 3.3.6) | xlibs | libxmu6, libqt3-mt (>= 3:3.2.1)
 Suggests: flash-npapi-plugin | flashplugin-nonfree | swf-player | libflash-mozplugin | mozilla-plugin-gnash, pdf-npapi-plugin | djvulibre-plugin | mozilla-acroread, cupsys-client | lpr, sun-java6-jre | sun-java5-jre | java-gcj-compat, linux-libertine | ttf-dejavu | ttf-bitstream-vera | msttcorefonts, xine-plugin | gxineplugin | mplayerplug-in | kaffeine-mozilla | mozilla-mplayer | mozilla-helix-player | gecko-mediaplayer, mozplugger | plugger, mozilla-bonobo, aspell
 [COLOR=red]Conflicts: opera-static
 Replaces: opera-static
 Provides: opera-static, www-browser[/COLOR]
 Installed-Size: 24752
 Maintainer: Opera Packaging Team <packager@opera.com>
 Bugs: mailto:packager@opera.com
 Description: The Opera Web Browser
  Welcome to the Opera Web browser.  It is smaller, faster,
  customizable, powerful, yet user-friendly.  Opera
  eliminates sluggish performance, HTML standard violations,
  desktop domination, and instability.  This robust Web
  browser lets you navigate the Web at incredible speed and
  offers you the best Internet experience.
  The binaries were built on Debian using gcc-4.0.0.

noteme@notebuntu:~$ sudo dpkg -i opera_static-9.50-1971.gcc4-qt4_i386.deb
dpkg: considering removing opera-static in favour of opera ...
dpkg: yes, will remove opera-static in favour of opera.
(Reading database ... 109538 files and directories currently installed.)
Unpacking opera (from opera_static-9.50-1971.gcc4-qt4_i386.deb) ...
Setting up opera (9.50) ...

Then again, I am just guessing, and I am no linux expert, so if I am wrong then don't ignore ME csant


- ØØ -

Csant: I've installed gcc4 - qt4 version of Opera 9.5 build 1997 and when I start it from the command line I get this error message all the time:

"Opera: skin element not supported"
What could be wrong? is there a way to debug this issue?
Thank you in advance,
Cyro

Did you have a clean profile? Or did you have any old skins that are not updated in your profile?


BTW, are you still on Ubuntu these days? 64bit?

- ØØ -

It's not a clean profile. No old skins at all. This happens with all native skins. Non-native skins doesn't have this behavior.
Well, this problem is happening in another Ubuntu installation, a 32bit one. It's an Asus EEEPC.
I may have uninstalled something important in order to the native skin works. Any other dependencies besides qt4?
I appreciate any help you guys give me, because right now I'm clueless.

Dependencies/suggestions:


noteme@notebuntu:~$ sudo dpkg -I opera_9.50-1997.gcc4-qt4_i386.deb
new debian package, version 2.0.
size 10693654 bytes: control archive= 7026 bytes.
34 bytes, 2 lines conffiles
1227 bytes, 21 lines control
16647 bytes, 232 lines md5sums
1719 bytes, 54 lines * postinst #!/bin/sh
572 bytes, 18 lines * postrm #!/bin/sh
179 bytes, 9 lines * prerm #!/bin/sh
Package: opera
Version: 9.50
Section: non-free/web
Priority: optional
Architecture: i386
Depends: libc6 (>= 2.1.3), xlib6g (>= 3.3.6) | xlibs | libxmu6
Suggests: flash-npapi-plugin | flashplugin-nonfree | swf-player | libflash-mozplugin | mozilla-plugin-gnash, pdf-npapi-plugin | djvulibre-plugin | mozilla-acroread, cupsys-client | lpr, sun-java6-jre | sun-java5-jre | java-gcj-compat, linux-libertine | ttf-dejavu | ttf-bitstream-vera | msttcorefonts, xine-plugin | gxineplugin | mplayerplug-in | kaffeine-mozilla | mozilla-mplayer | mozilla-helix-player | gecko-mediaplayer, mozplugger | plugger, mozilla-bonobo, aspell
Conflicts: opera-static
Replaces: opera-static
Provides: opera-static, www-browser
Installed-Size: 24884
Maintainer: Opera Packaging Team
Description: The Opera Web Browser
Welcome to the Opera Web browser. It is smaller, faster,
customizable, powerful, yet user-friendly. Opera
eliminates sluggish performance, HTML standard violations,
desktop domination, and instability. This robust Web
browser lets you navigate the Web at incredible speed and
offers you the best Internet experience.
The binaries were built on Debian using gcc-4.0.0.




What happens if you rename your local opera profile folder? If the error message goes away then, you know it is something in your old profile, maybe a custom button or what ever.


- ØØ -

@NoteMe: I've double checked all the dependencies. They're all installed. I've even tried a different profile as you suggested

I can't replicate that message no matter what I do. But if I have the QT native skin on, AND the side panel open, I get the message:

opera: skin element not drawn

every time I make Opera trigger a paint event (i.e change window back and forth or press Ctrl+R). But I can't get your message displayed no matter what I do.



- ØØ -

Claudio, could you guys try to include libgtkstyle.so in the static package?
The link to the blog entry was posted by ColKilkenny above.

…as some have noticed, qt4 doesn't say "static" in the package name We have other plans…

Seems like now we see what you meant (-:E

What di he mean by that?

kriko
See comments here: http://my.opera.com/desktopteam/blog/show.dml/2592659?startidx=100#comment6121048

Where? I can't see qt4 shared builds...

Nor can you see static (-;E

As far as I remember, the idea is to have a build with shared qt4 libs in tarball. So if you have qt4 installed, Opera uses system libraries, otherwise falls back to "own"

Qt library 4.4.2 → this is sys version. It would be nice if it would display shared beside.
Why it doesn't blend into oxygen theme then?

EDIT:
OMG! Ponies!!!!!!!!!!
It has an improved save as dialog!

kriko
Can't answer you, I wait for amd64 version to use (-:E

csant, hope you don't mind but I decided it was time for an updated guide!