Author Topic: [SOLVED} Ktorren 4.3.0 segfault 11 [SOLVED]  (Read 953 times)

Offline DeBaas

  • Hero Member
  • *****
  • Posts: 1521
    • PCLinuxOS.nl
Re: Ktorren 4.3.0 segfault 11
« Reply #15 on: October 17, 2012, 01:15:23 PM »
Reinstalling the older versions ;)
I'm doing a Dutch remaster on request, so I can deliver for now ;)

Offline Archie

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8590
  • Aurum nostrum non est aurum vulgi.
Re: Ktorren 4.3.0 segfault 11
« Reply #16 on: October 17, 2012, 05:15:41 PM »
Dunno how much users are affected by the same issues you're having. Two users, especially prominent PCLinuxOS users (for me) translates to between the power of 5 to 8, and each user decides their own actions - revert to the previous working version, use an alternative app, etc.

Neal asked me what I want to do with the package in the repo. Initially, my reaction was to remove it and revert to the previous version. Neal explained to me that the repo versions were not from my build and were processed by the PCLinuxOS build server (which is now using 4.8.3). He also advised me that there are only three different reports - two with the issues and one indicating it is not a problem. He hinted that it may be a problem with the user's system.

So, I am pretty much persuaded by Neal's wisdom so unless the issue is widespread, I would leave the latest version on update. Sorry, guys.
Since 2006 | LiCo 401868 | Bare Metal | What is necessary is never unwise. --Sarek, 2258.42


Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: Ktorren 4.3.0 segfault 11
« Reply #17 on: October 17, 2012, 06:56:28 PM »
Dunno how much users are affected by the same issues you're having. Two users, especially prominent PCLinuxOS users (for me) translates to between the power of 5 to 8, and each user decides their own actions - revert to the previous working version, use an alternative app, etc.

Neal asked me what I want to do with the package in the repo. Initially, my reaction was to remove it and revert to the previous version. Neal explained to me that the repo versions were not from my build and were processed by the PCLinuxOS build server (which is now using 4.8.3). He also advised me that there are only three different reports - two with the issues and one indicating it is not a problem. He hinted that it may be a problem with the user's system.

So, I am pretty much persuaded by Neal's wisdom so unless the issue is widespread, I would leave the latest version on update. Sorry, guys.

Actually, in this thread, three people report a failure of Ktorrent 4.3.0 with KDE 4.8.3 and one reports it working on KDE 4.9.2 on the 32 bit installations. Two people report the same failure on the 64 bit system using KDE 4.8.3.

Who is the one person reporting that it works on KDE 4.8.3?
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Archie

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8590
  • Aurum nostrum non est aurum vulgi.
Re: Ktorren 4.3.0 segfault 11
« Reply #18 on: October 17, 2012, 07:15:55 PM »
The point in my last reply was: running the build on 4.9.2 did not fail with any errors. I assume that it was the same when Neal run the PCLOS build. Is it possible that the segmentation fault may be caused by something else other than the app itself? This is what I would like to know because rebuilding the app on KDE 4.8.3, which was a repeat of what Neal had already done did not seem to fix the problem.

So first thing that needed to be cleared is packaging on a 4.9.2 build environment has nothing to do with the issues. DeBaas (Ed) suggested it to be otherwise, and that idea got me needlessly concerned. We need to remember that all the packages we submit are rebuilt again using the PCLOS build server. If for any reason, a package I submit to Neal fails with an error, I would get a notification from him and we'll work it out. It is the same procedure with the other packagers.

My bad for not counting agmg and also counting JohnW's report as stable. It might look like it is a widespread issue and if it does come to that, I will not hesitate to request Neal to pull it out of the repo. How many more users can convince that it is an erroneous build ... we'll see.
Since 2006 | LiCo 401868 | Bare Metal | What is necessary is never unwise. --Sarek, 2258.42


Offline DeBaas

  • Hero Member
  • *****
  • Posts: 1521
    • PCLinuxOS.nl
Re: Ktorren 4.3.0 segfault 11
« Reply #19 on: October 18, 2012, 03:02:55 AM »
Just installed a fresh KDE 2012.08,
Updated from the nluug repo.
Checked for ktorrent version == 4.2.0-2 in the nluug repo.
Should I check with the PASS 4.3.0-1 version ?
It's a test box used to create the Dutch remaster, so it's ready to bork ;) now.

Ed

Edit: I did, I did.... and it crashed.

[off topic]
What the hell is going on with the Linuxtracker.org torrents...
Torrent not found
You're not autorized to download. Sorry...
[/off topic]
« Last Edit: October 18, 2012, 03:46:40 AM by DeBaas »

Online JohnW_57

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2130
Re: Ktorren 4.3.0 segfault 11
« Reply #20 on: October 18, 2012, 06:33:06 PM »
Quote
[off topic]
What the hell is going on with the Linuxtracker.org torrents...
Torrent not found
You're not autorized to download. Sorry...
[/off topic]

Looks like Linuxtracker.org site is too unstable at this moment and get the same issues.
There are more complains about Linuxtracker.org.

JohnW
« Last Edit: October 18, 2012, 06:52:29 PM by JohnW_57 »
PCLinuxOS 2013 KDE4 (64 bit) on: home build system:  Intel Core 2 Quad (q6700) (2.66ghz), Asus P5K motherboard, 4 gig ddr2 memory, Asus Nvidia Geforce GTS 250 1024 mb gddr3, Crucial M4 128 SSD,  2x Samsung 500 gig HDD (sata), TSSTcorp CDDVDW SH-224BB.

Offline DeBaas

  • Hero Member
  • *****
  • Posts: 1521
    • PCLinuxOS.nl
Re: Ktorren 4.3.0 segfault 11 [SOLVED]
« Reply #21 on: October 26, 2012, 05:12:32 AM »
KDE updated to 4.9.2 (PASS) problem solved.
off topic, FullMonty torrent recreated on Linuxtracker, 4 more problems to go.