Hi,
> Adding Ralf in CC, since he is experiencing the same issues.
Thanks Hugo :)
The issue I have is the same as Andreas, except that the application does not
crash for me if it uses the wrong Oxygen. It just looks ugly because the
gradient seems to have changed between KDE 4.6 (which lives in
Adding Ralf in CC, since he is experiencing the same issues.
--
This starts to get off-topic, but I see the same with zsh, as in I
started zsh
from bash and run the above tests, with : ending it works, without it
doesn't.
There's either some
Am 26.02.2012, 11:20 Uhr, schrieb Andras Mantia :
This starts to get off-topic, but I see the same with zsh, as in I
started zsh
from bash and run the above tests, with : ending it works, without it
doesn't.
There's either some weird statement in your local or global shell profile
or Qt (
On Saturday, February 25, 2012 09:47:56 PM Thomas Lübking wrote:
> Am 25.02.2012, 21:38 Uhr, schrieb Andras Mantia :
> >> What about
> >> QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins: strace kwrite --style
> >> oxygen
> >> 2>&1 | grep -i oxygen | grep open
> >>
> >>
Am 25.02.2012, 21:38 Uhr, schrieb Andras Mantia :
What about
QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins: strace kwrite --style
oxygen
2>&1 | grep -i oxygen | grep open
NOTICE the colon
^
Ouch, this also works.
-> Crappy or broken
On Saturday, February 25, 2012 09:25:36 PM Thomas Lübking wrote:
> Am 25.02.2012, 21:15 Uhr, schrieb Andras Mantia :
> > I did remove that countless times while trying to find a solution...
>
> Meaning it is /not/ there when the simple env path launch fails?
Yes.
> What about
> QT_PLUGIN_PATH=/o
Am 25.02.2012, 21:15 Uhr, schrieb Andras Mantia :
I did remove that countless times while trying to find a solution...
Meaning it is /not/ there when the simple env path launch fails?
What about
QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins: strace kwrite --style oxygen
2>&1 | grep -i oxygen |
On Saturday, February 25, 2012 09:11:08 PM Thomas Lübking wrote:
> Yupp, wild guess:
> move the Trolltech.conf away, it usually contains a lot of caching junk
> (from old Qt versions, installations ...) and try again (somewhere the
> wrong path has to derive from)
I did remove that countless t
Am 25.02.2012, 20:53 Uhr, schrieb Andras Mantia :
Now comes the weird thing:
QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins /usr/bin/kwrite
/usr/bin/kwrite: symbol lookup error:
/usr/lib64/kde4/plugins/styles/oxygen.so: undefined symbol:
_ZN6Oxygen7TileSetC1ERK7QPixmap
So it works when I
On Saturday, February 25, 2012 08:37:05 PM Thomas Lübking wrote:
> > Tell me what do I do wrongly, and I'm willing to apologize and fix my
> > system.
>
> try
> QT_PLUGIN_PATH=/opt/kde4/lib64/kde4/plugins:/usr/lib64/kde4/plugins strace
> kwrite --style oxygen 2>&1 | grep -i oxygen | grep open
>
Am 25.02.2012, 19:28 Uhr, schrieb Andras Mantia :
On Saturday, February 25, 2012 11:42:13 AM Hugo Pereira Da Costa wrote:
> I tend to think proper soversion bumping would be a good solution.
In both cases it does not fix (sorry for repeating myself) the true
issue, which is that your plugin_p
On Saturday, February 25, 2012 11:42:13 AM Hugo Pereira Da Costa wrote:
> > I tend to think proper soversion bumping would be a good solution.
>
> In both cases it does not fix (sorry for repeating myself) the true
> issue, which is that your plugin_path is not consistent with your
> LD_LIBRARY_P
Am 25.02.2012, 12:17 Uhr, schrieb Pino Toscano :
In both cases it does not fix (sorry for repeating myself) the true
issue, which is that your plugin_path is not consistent with your
LD_LIBRARY_PATH.
Which "pernicious effects"? Only the old plugin being loaded?
Using wrong ABI stable lib or
Hello,
On šeštadienis 25 Vasaris 2012 12:42:13 Hugo Pereira Da Costa wrote:
> On 02/24/12 19:38, Andras Mantia wrote:
> > On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote:
> >> On 2012-02-24, Hugo Pereira Da Costa wrote:
> >>> I understand that. The point I was trying to make, is that
Alle sabato 25 febbraio 2012, Hugo Pereira Da Costa ha scritto:
> On 02/24/12 19:38, Andras Mantia wrote:
> > On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote:
> >> On 2012-02-24, Hugo Pereira Da Costa wrote:
> >>> I understand that. The point I was trying to make, is that you
> >>> wou
On 02/24/12 19:38, Andras Mantia wrote:
On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote:
On 2012-02-24, Hugo Pereira Da Costa wrote:
I understand that. The point I was trying to make, is that you would
still get the "old" pluggin, admittingly without crashing, but which
would nonet
On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote:
> On 2012-02-24, Hugo Pereira Da Costa wrote:
> > I understand that. The point I was trying to make, is that you would
> > still get the "old" pluggin, admittingly without crashing, but which
> > would nonetheless be not correct.
>
> Wh
On Fri, Feb 24, 2012 at 11:56, Andras Mantia wrote:
> On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
> > Correct.
> >
> > Make sure that your new KDE's installation is found by the Qt plugin
> > system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
>
> I have th
On 2012-02-24, Hugo Pereira Da Costa wrote:
> I understand that. The point I was trying to make, is that you would
> still get the "old" pluggin, admittingly without crashing, but which
> would nonetheless be not correct.
Whattabout just linking liboxygenstyle static into the oxygen style?
Prob
On Friday, February 24, 2012 12:01:37 PM Hugo Pereira Da Costa wrote:
> are other applications also crashing (like, e.g. plasma workspace, or
> kwin) ? (It should)
>
> if not it might be a QtCreator specific issue.
Yes, also kde apps crash, like kdesvn, kate, etc.
Andras
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
> On 02/24/2012 12:01 PM, Pino Toscano wrote:
> > Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
> >> On 02/24/2012 11:43 AM, Pino Toscano wrote:
> >>> Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
On 02/24/2012 12:01 PM, Pino Toscano wrote:
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
On 02/24/2012 11:43 AM, Pino Toscano wrote:
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
no there is no guarantee for liboxygenstyle.so.4, and I don't plan
to guaran
On 02/24/2012 11:56 AM, Andras Mantia wrote:
On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
Correct.
Make sure that your new KDE's installation is found by the Qt plugin
system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
I have this:
printenv QT_PLUGIN_PAT
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
> On 02/24/2012 11:43 AM, Pino Toscano wrote:
> > Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
> >> no there is no guarantee for liboxygenstyle.so.4, and I don't plan
> >> to guarantee it.
> >> It is all internal t
On 02/24/2012 11:51 AM, Thiago Macieira wrote:
On sexta-feira, 24 de fevereiro de 2012 11.49.44, Hugo Pereira Da Costa wrote:
despite the fact that you have a local kde build, the pluggins that gets
loaded by Qt when running a KDE or Qt application are not the ones you
compiled. An old one is us
On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
> Correct.
>
> Make sure that your new KDE's installation is found by the Qt plugin
> system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
I have this:
printenv QT_PLUGIN_PATH
/opt/qt4/plugins:/opt/kde4/lib64/kde4/
On sexta-feira, 24 de fevereiro de 2012 11.49.44, Hugo Pereira Da Costa wrote:
> despite the fact that you have a local kde build, the pluggins that gets
> loaded by Qt when running a KDE or Qt application are not the ones you
> compiled. An old one is used instead, that is inconsistent with the
On 02/24/2012 11:43 AM, Pino Toscano wrote:
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
Then please correctly bump its SONAME, ins
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
> no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
> guarantee it.
> It is all internal to kde-workspace, and has no public api.
Then please correctly bump its SONAME, instead of using the same SONAME
(liboxygen
On Friday, February 24, 2012 11:25:13 AM Hugo Pereira Da Costa wrote:
> If I remember correctly, the recipy for getting the right pluggin path
> (and thus avoid the crashes -always-), is to edit
> $HOME/.config/Trolltech.conf, and remove (or fix) the "libraryPath"
> section in [qt].
Hm, I would
On 02/24/2012 11:25 AM, Hugo Pereira Da Costa wrote:
On 02/24/2012 11:21 AM, Hugo Pereira Da Costa wrote:
Hi Andras,
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
the fact that oxygen gets broken
On 02/24/2012 11:21 AM, Hugo Pereira Da Costa wrote:
Hi Andras,
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
the fact that oxygen gets broken for kde installed from source due to
incorrect plugi
Hi Andras,
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
the fact that oxygen gets broken for kde installed from source due to
incorrect plugin path is an issue with Qt installantion, and/or with
On Friday 24 February 2012 10:58:39 Andras Mantia wrote:
> I know this does not affect regular releases in distributions, but it is
> very bad for those working/testing KDE master.
Not only master, the same happens to me in my self-compiled KDE-4.8
environment.
Let's just fix this the BC way, b
Hi,
is there any BC guarantee for liboxygenstyle.so.4? If not, i think there
should be... It is not the first time that you cannot run application installed
by your distribution under a self-compiled KDE master, because BIC issues in
lliboxygenstyle.so. The apps from there load the oxygen.so p
35 matches
Mail list logo
