Hello, I do not fill a bug report atm because I want to know if I'm the only one with this problem ..
I've built and installed tdelibs and tdebase from branch 3.5.13-sru on top of my 3.5.13 installation. All other packages (qt3, tqtinterface ...) are still 3.5.13 (I saw no relevant change in 3.5.13-sru for them). I've removed all my distribution-specific patches, to make sure that they cause no problem.
Now, I just open konqueror (with the quick launch icon). As soon as I do a right click inside konqueror, it segfaults immediatly. When reinstalling tdebase 3.5.13 (keeping tdelibs 3.5.13.1), konqueror works correctly.
Anybody else ?
Francois
Le 07/08/2012 22:51, François ANDRIOT a écrit :
Hello, I do not fill a bug report atm because I want to know if I'm the only one with this problem ..
I've built and installed tdelibs and tdebase from branch 3.5.13-sru on top of my 3.5.13 installation. All other packages (qt3, tqtinterface ...) are still 3.5.13 (I saw no relevant change in 3.5.13-sru for them). I've removed all my distribution-specific patches, to make sure that they cause no problem.
Now, I just open konqueror (with the quick launch icon). As soon as I do a right click inside konqueror, it segfaults immediatly. When reinstalling tdebase 3.5.13 (keeping tdelibs 3.5.13.1), konqueror works correctly.
Anybody else ?
Francois
Mmmm never mind, I've just found that it crashes with a message in terminal: "undefined symbol XXXX in some kdiff3 library ..." (I did not notice that kdiff3 had installed a konqueror plugin ...) But I already saw that upgrading tdelibs from 3.5.13 to 3.5.13-sru caused unresolved symbol in kpowersave, and even some in tdebase. I think this is due to some "q"=>"tq" renaming or vice-versa.
This leads me to the conclusion that, for packagers, the 3.5.13 => 3.5.13-sru upgrade won't be a "small update". I think that all packages, including applications, should be rebuilt to avoid such issues. TDE 3.5.13.1 looks like a major upgrade after all (from an end-user point of view, who will need to upgrade every TDE components).
Francois
On Tuesday 07 of August 2012 23:05:49 Francois Andriot wrote:
Mmmm never mind, I've just found that it crashes with a message in terminal: "undefined symbol XXXX in some kdiff3 library ..." (I did not notice that kdiff3 had installed a konqueror plugin ...) But I already saw that upgrading tdelibs from 3.5.13 to 3.5.13-sru caused unresolved symbol in kpowersave, and even some in tdebase. I think this is due to some "q"=>"tq" renaming or vice-versa.
This leads me to the conclusion that, for packagers, the 3.5.13 => 3.5.13-sru upgrade won't be a "small update". I think that all packages, including applications, should be rebuilt to avoid such issues. TDE 3.5.13.1 looks like a major upgrade after all (from an end-user point of view, who will need to upgrade every TDE components).
Francois
If I know the number of changes that are dependent on some other is not many. One is already mentioned tqaddAction/addAction => needed to update kdeaddons and kdiff3. The second is the fix in the shutdown dialog => needed to update kpowersave. The third is change in kdesu / kdesudo => needed to update kdesudo.
However, it is true that, as number of fixes => patches have increased, so I finally applied some patches to almost all packages.
Slavek --
On 08/07/2012 07:28 PM, Slávek Banko wrote:
On Tuesday 07 of August 2012 23:05:49 Francois Andriot wrote:
Mmmm never mind, I've just found that it crashes with a message in terminal: "undefined symbol XXXX in some kdiff3 library ..." (I did not notice that kdiff3 had installed a konqueror plugin ...) But I already saw that upgrading tdelibs from 3.5.13 to 3.5.13-sru caused unresolved symbol in kpowersave, and even some in tdebase. I think this is due to some "q"=>"tq" renaming or vice-versa.
This leads me to the conclusion that, for packagers, the 3.5.13 => 3.5.13-sru upgrade won't be a "small update". I think that all packages, including applications, should be rebuilt to avoid such issues. TDE 3.5.13.1 looks like a major upgrade after all (from an end-user point of view, who will need to upgrade every TDE components).
Francois
If I know the number of changes that are dependent on some other is not many. One is already mentioned tqaddAction/addAction => needed to update kdeaddons and kdiff3. The second is the fix in the shutdown dialog => needed to update kpowersave. The third is change in kdesu / kdesudo => needed to update kdesudo.
However, it is true that, as number of fixes => patches have increased, so I finally applied some patches to almost all packages.
Slavek
How long ago did this problem show up? I have 3.5.13-sru konqueror with kdiff3 integration and it is working fine. No lockups, kdiff3 working, etc.. These packages are from July 29. Here is a screenshot:
http://www.3111skyline.com/dl/dt/trinity/ss/3513-kdiff3.jpg
Do I need to try a rebuild and test?
On Wednesday 08 of August 2012 22:35:17 David C. Rankin wrote:
How long ago did this problem show up? I have 3.5.13-sru konqueror with kdiff3 integration and it is working fine. No lockups, kdiff3 working, etc.. These packages are from July 29. Here is a screenshot:
http://www.3111skyline.com/dl/dt/trinity/ss/3513-kdiff3.jpg
Do I need to try a rebuild and test?
Mentioned problem was a long time ago (around at the end of April). It is also a long time in v3.5.13-sru resolved.
Slavek --
On Tuesday 07 of August 2012 22:51:48 François ANDRIOT wrote:
Hello, I do not fill a bug report atm because I want to know if I'm the only one with this problem ..
I've built and installed tdelibs and tdebase from branch 3.5.13-sru on top of my 3.5.13 installation. All other packages (qt3, tqtinterface ...) are still 3.5.13 (I saw no relevant change in 3.5.13-sru for them). I've removed all my distribution-specific patches, to make sure that they cause no problem.
Now, I just open konqueror (with the quick launch icon). As soon as I do a right click inside konqueror, it segfaults immediatly. When reinstalling tdebase 3.5.13 (keeping tdelibs 3.5.13.1), konqueror works correctly.
Anybody else ?
Francois
François,
yes, this problem occurred and was in v3.5.13-cord resolved. It is a combination of three patches - change tqaddAction -> addAction:
1. kdebase => a34c15dc 2. kdeaddons => 4ea5634f 3. kdiff => 3f02b2be
The change I considered as useful for any further plugins from KDE3 that use addAction.
Slávek --
-
David C. Rankin -
Francois Andriot -
François ANDRIOT
-
Slávek Banko