UP - 30/11/2013 [TESTING][CLOSED]

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
kobros
Posts: 194
Joined: 28 Nov 2013 14:48
Location: Netherlands

Re: UP - 30/11/2013 [TESTING]

Postby kobros » 03 Dec 2013 15:54

Wrong!
Bugs in M$-products have always been 100% reproducable. In fact , it would be nearly impossible to avoid meeting them.

Not so with Linux. They're well hidden and may be triggered by one bit faling over.
With M$ it's always a rampage of misdirected bits. Not one, but millions of them - at the same time....:-)

If plasma-desktop crashes again (and it will, since it happens too in debian, mint, kubuntu, mepis too) I'll inform you....
Not surprisingly it never happened in antiX [which manages to stay away from (not my words) 'KDE-bloatware'].
Linux User #312596.
Mepis/Debian/antiX/MX/Win7

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 30/11/2013 [TESTING]

Postby fleabus » 03 Dec 2013 23:05

Schoelje wrote:Oh wait, now we can tell our users to just reboot the system if they have a problem...MS secretly took over Linux, mark my word!
:lol: Now that was priceless! Yes, let's add that to the 12-6 UP info page! :lol: :twisted: :mrgreen:
ScottQuier wrote:...the idea being that I might be able apply those smarts (I live in a state of eternal hope on this and similar points) to the problems I KNOW I will face in the future.
A great big "Me Too" on that one. Well said Scott.

User avatar
Santa
Posts: 16
Joined: 09 Jun 2013 23:39

Re: UP - 30/11/2013 [TESTING]

Postby Santa » 03 Dec 2013 23:11

Hi,

I just wanted to say that I hope KDE SC 4.11.4 will be ready soon.
Sometimes, standing for what you believe means standing alone.

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP - 30/11/2013 [TESTING]

Postby ScottQuier » 04 Dec 2013 01:15

Schoelje wrote: Oh wait, now we can tell our users to just reboot the system if they have a problem...MS secretly took over Linux, mark my word!
Them, sir, are fightin' words!
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP - 30/11/2013 [TESTING]

Postby ScottQuier » 04 Dec 2013 01:18

Santa wrote:Hi,

I just wanted to say that I hope KDE SC 4.11.4 will be ready soon.
So, you're hanging out here "wasting" your time when you could be getting the next KDE installment ready. Where's your loyality? :D :) :lol: :lol:

Just couldn't resist the urge. And, no, I'm not on drugs or drunk. But it is getting close to my bedtime. :)
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 30/11/2013 [TESTING]

Postby fleabus » 04 Dec 2013 01:22

@Scott,
Me and my bent bits.... :lol: One simply can't have any fun without 'em!
Santa wrote:I hope KDE SC 4.11.4 will be ready soon.
Hope springs eternal, echoed across the board! :D

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: UP - 30/11/2013 [TESTING]

Postby zerozero » 04 Dec 2013 02:19

fleabus wrote:RE the whole "Fix-The-UP" thing -- I'm still in the dark here... :lol:

Schoelje said "That was easy: KDE needs updating first:"

And he was all smiles! But from the output there, I was still at a loss as to what to actually do about it. I sat there reading and rereading, until zz posted:
zerozero wrote:Schoelje's solution here works for everybody?

Code: Select all

apt install libsmokebase3=4:4.11.3-1
And then I still didn't know:

"Oh so we gotta kung-foo in the correct version? Wait a minute, that's just one of them. And why that particular one?"

(Here, I started to install the correct versions of all of them, but then, on a strange impulse, tried the dist-up again after doing that first one, and it worked!)

My noob questions are:

1. How did you know in the first place that librubyqt4shared2 was the key? Simply because it was the first item in our original list of mis-behavers?

2. How did you know that kung-fooing in the correct version of one of these libs was gonna make the others form up and salute?

---------------

That was kinda humorous there. ZZ says "Are we sure?" Schoelje's solution worked for everybody?
<specifies the exact nature of The Thing to do>

Then everyone comes back: "Yeah zz!" Crystal, ZZ!" "Worked a charm here, ZZ" "All done and dusted here too" :lol: :mrgreen:

I love this forum. :lol: :lol: :lol:

Please y'all, I didn't mean to offend. Just about everyone here knows more about this stuff than I do. I simply have my curmudgeonly reputation to maintain. :mrgreen: :lol:
ScottQuier wrote:
fleabus wrote:My noob questions are:

1. How did you know in the first place that librubyqt4shared2 was the key? Simply because it was the first item in our original list of mis-behavers?

2. How did you know that kung-fooing in the correct version of one of these libs was gonna make the others form up and salute?
I think these are very good questions; they occurred to me as well a couple of days ago but I failed to post them.

Anyway zerozero, as and when you have time to educate - I would love to know how you :geek: :ugeek: figured this out, the idea being that I might be able apply those smarts (I live in a state of eternal hope on this and similar points) to the problems I KNOW I will face in the future.

Thanks!
sorry guys :mrgreen: wasn't my intention to be cryptic (tho i manage to be very often :lol: )

situations like the one we are talking about are usually only solved with trial&error;
the basic recipe goes more or less like this:
  1. identify the offended packages;
  2. try to install one by one and understand the output;
  3. act according to the previous point.
here libqtruby4shared2 was chosen because was the first of the list everybody had :lol: (if eventually that one didn't provide useful info next step would be to go to n2 and then n3 and then ...)

- but we had enough there; trying to install said package yields

Code: Select all

The following packages have unmet dependencies:
 libqtruby4shared2 : Depends: libsmokebase3 (>= 4:4.11.1) but 4:4.10.5-1~pre1+b4 is to be installed
                     Depends: libsmokeqtcore4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtdbus4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtgui4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtnetwork4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtopengl4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtsql4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtsvg4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtxml4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
E: Unable to correct problems, you have held broken packages.
so we know that we have a mismatch and the first result is

Code: Select all

libqtruby4shared2 : Depends: libsmokebase3 (>= 4:4.11.1) but 4:4.10.5-1~pre1+b4 is to be installed
so let's try that one (we might be lucky)
well :) we were. it could so happen that apt couldn't resolve the unmet dep yet and we had to go back to our list of mis-behavers

we knew one thing here (and that is both good and disturbing): the upgrade was good because it could be done in similar circumstances (with one small variation: the install iso):
so we just needed to push apt until we could find the knot and untangle the mess

HTH
bliss of ignorance

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 30/11/2013 [TESTING]

Postby fleabus » 04 Dec 2013 02:36

zerozero wrote:situations like the one we are talking about are usually only solved with trial&error;
the basic recipe goes more or less like this:
  1. identify the offended packages;
  2. try to install one by one and understand the output;
  3. act according to the previous point.
libqtruby4shared2 was chosen because was the first of the list everybody had :lol: (if eventually that one didn't provide useful info next step would be to go to n2 and then n3 and then ...)

... we just needed to push apt until we could find the knot and untangle the mess

HTH
Definitely did, helped a lot. It's good to know it's really that straightforward, just start at the top and go down. I guess I just couldn't believe it was that simple, always expecting things to be really complicated... And having those expectations met many times! :lol:

Thanks again zz. :)

User avatar
ScottQuier
Posts: 1781
Joined: 18 Jul 2013 15:55
Location: Newport News, VA

Re: UP - 30/11/2013 [TESTING]

Postby ScottQuier » 04 Dec 2013 11:37

OK - that makes a lot of sense ... once I've seen it.

Really appreciate you taking the time to educate me. :)
Scott
Quoting zerozero, "The usage of PPA's in debian-based
systems is risky at best and entails serious compatibility
problems; usually it's the best way to destroy an install"

User avatar
Cork
Posts: 12
Joined: 12 Mar 2013 14:00

Re: UP - 30/11/2013 [TESTING]

Postby Cork » 04 Dec 2013 15:32

System: HP Mini 311, Atom 270 (32-bit PAE), 3 GB RAM, nVidia Ion graphics (GeForce 9400M, essentially), Broadcom BCM43224 WiFi.

I used Update Manager to load the testing updates; during reboot, computer freezes going into the 3.11.2 686 PAE kernel at the point where the status bar end turns orange. Boots fine into 3.11.2 486 kernel, and into 3.10.3 686 PAE kernel.

I've tried the libsmokebase3 install from earlier in the thread, but no change. Let me know if you have specific commands you'd like me to explore; I'm fine just running in 3.10.3 but want to help in the limited way that I can.

Cork

toothandnail
Posts: 94
Joined: 02 Jun 2013 18:45
Location: Oxfordshire, UK

Re: UP - 30/11/2013 [TESTING]

Postby toothandnail » 04 Dec 2013 19:27

Ran the update through UM (64-bit SolydX). Went through, only oddity was this warning at the end of the update:

Code: Select all

W: Waited for dpkg --assert-multi-arch but it wasn't there - dpkgGo (10: No child processes)
Everything seems to be running smoothly. Interesting, it has solved a problem I reported a while ago (http://forums.solydxk.nl/viewtopic.php?f=13&t=1887). I was at the site where that problem was occurring today and tried printing an email from Seamonkey. Went through without problems!

Paul.

User avatar
Arjen Balfoort
Site Admin
Posts: 9279
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP - 30/11/2013 [TESTING]

Postby Arjen Balfoort » 05 Dec 2013 09:22

Gentlemen,

Santa has finished KDE 4.11.4 !

I'm running an upgrade from a clean 201311 iso now. I'll post back with the results.

I also updated the plymouth themes for SolydXK.
With my Nvidia I got the theme back (after 2 months without), but zerozero wasn't so lucky with his ATI :evil:
I hope you can test this with proprietary drivers.


SolydXK needs you!
Development | Testing | Translations

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 30/11/2013 [TESTING]

Postby fleabus » 05 Dec 2013 10:37

Returned the partition to (almost) pristine state from backup. That is:

New K64 install, from 2013-11-25 iso, no plymouth. Installed Lancelot, Ubuntu fonts, and Nvidia 319.60.

I'll let you know how it goes....

Edit: Still getting the 12 kept back, so holding off for now. Will try from an absolutely fresh install.

Edit: Pristine install same 12 kept back, so held off for now.

User avatar
Arjen Balfoort
Site Admin
Posts: 9279
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP - 30/11/2013 [TESTING]

Postby Arjen Balfoort » 05 Dec 2013 11:57

I confirm that after the KDE update, the held back packages was not solved:

Code: Select all

The following packages have been kept back:
  libqtruby4shared2 libsmokeqtcore4-3 libsmokeqtdbus4-3 libsmokeqtgui4-3
  libsmokeqtnetwork4-3 libsmokeqtopengl4-3 libsmokeqtsql4-3 libsmokeqtsvg4-3
  libsmokeqtwebkit4-3 libsmokeqtxml4-3 ruby-qt4 ruby-qt4-webkit

Code: Select all

# apt policy libsmokebase3
libsmokebase3:
  Installed: 4:4.10.5-1~pre1+b4
  Candidate: 4:4.10.5-1~pre1+b4
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-1~pre1+b4 0
        700 http://packages.solydxk.com/testing/ solydxk/kdenext amd64 Packages
        100 /var/lib/dpkg/status
You see that although libsmokebase3 is newer in debian, apt doesn't recognize it (installed and candidate version are the same old version from kdenext). I still don't understand how that is possible.
I'll try to contact Santa.


SolydXK needs you!
Development | Testing | Translations

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 30/11/2013 [TESTING]

Postby fleabus » 05 Dec 2013 12:06

Hmm. The prefs file?

Anyway, cool, I await your next... :)

User avatar
Arjen Balfoort
Site Admin
Posts: 9279
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP - 30/11/2013 [TESTING]

Postby Arjen Balfoort » 05 Dec 2013 12:14

I investigated a bit further by trying to install libqtruby4shared2:

Code: Select all

# apt-get install libqtruby4shared2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libqtruby4shared2 : Depends: libsmokebase3 (>= 4:4.11.1) but 4:4.10.5-1~pre1+b4 is to be installed
                     Depends: libsmokeqtcore4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtdbus4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtgui4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtnetwork4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtopengl4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtsql4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtsvg4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
                     Depends: libsmokeqtxml4-3 (>= 4:4.11.3) but 4:4.10.5-2 is to be installed
E: Unable to correct problems, you have held broken packages.
You see that I have broken packages, but when I run:

Code: Select all

# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 479 not upgraded.
You see that apt is okay.

Checking these packages:

Code: Select all

# apt policy libsmokebase3 libsmokeqtcore4-3 libsmokeqtdbus4-3 libsmokeqtgui4-3 libsmokeqtnetwork4-3 libsmokeqtopengl4-3 libsmokeqtsql4-3 libsmokeqtsvg4-3 libsmokeqtxml4-3

libsmokebase3:
  Installed: 4:4.10.5-1~pre1+b4
  Candidate: 4:4.10.5-1~pre1+b4
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-1~pre1+b4 0
        700 http://packages.solydxk.com/testing/ solydxk/kdenext amd64 Packages
        100 /var/lib/dpkg/status
libsmokeqtcore4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtdbus4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtgui4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtnetwork4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtopengl4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtsql4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtsvg4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
libsmokeqtxml4-3:
  Installed: 4:4.10.5-2
  Candidate: 4:4.11.3-1
  Version table:
     4:4.11.3-1 0
        500 http://debian.solydxk.com/testing/ testing/main amd64 Packages
 *** 4:4.10.5-2 0
        100 /var/lib/dpkg/status
You can see that libsmokebase3 is the culprit, because apt doesn't recognize the newer version in the Debian repository.

This package is the only one also available from kdenext. What if I remove libsmokebase3 from our repository?


SolydXK needs you!
Development | Testing | Translations

User avatar
stelios
Posts: 128
Joined: 28 Feb 2013 21:31
Location: Athens

Re: UP - 30/11/2013 [TESTING]

Postby stelios » 05 Dec 2013 12:36

Code: Select all

sudo apt-get -t testing dist-upgrade
Result:
617 upgraded, 52 newly installed, 2 to remove and 0 not upgraded..

Code: Select all

sudo apt-get  dist-upgrade
Result:
582 upgraded, 52 newly installed, 2 to remove and12 not upgraded.

In particular these 12 packages:
libqtruby4shared2 libsmokeqtcore4-3 libsmokeqtdbus4-3 libsmokeqtgui4-3 libsmokeqtnetwork4-3 libsmokeqtopengl4-3 libsmokeqtsql4-3 ibsmokeqtsvg4-3 libsmokeqtwebkit4-3 libsmokeqtxml4-3 ruby-qt4 ruby-qt4-webkit

So, some problem with apt-pinning perhaps?

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 30/11/2013 [TESTING]

Postby fleabus » 05 Dec 2013 12:38

I tried (briefly) dumping the prefs file, nothing held back.

Of course a whole lot more packages get upgraded too...

Going out for a while, back this afternoon...

To clarify, the above was a dry run. Ran the upgrade with the prefs file in place before I left, still had the 12 kept back.

User avatar
Cork
Posts: 12
Joined: 12 Mar 2013 14:00

Re: UP - 30/11/2013 [TESTING]

Postby Cork » 05 Dec 2013 15:19

With regard to my 3.11 686 kernel problem, I corrected by removing the kernel using the steps here:
http://forums.solydxk.com/viewtopic.php ... nels#p9724

Then with a fully updated/rebooted system (into the 3.11 486 kernel) I used Synaptic to reinstall 3.11-2-686-pae (including the source). Ran

Code: Select all

sudo update-grub2
and rebooted into the 3.11-2-686-pae kernel successfully.

Best,
Cork

User avatar
Arjen Balfoort
Site Admin
Posts: 9279
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: UP - 30/11/2013 [TESTING]

Postby Arjen Balfoort » 05 Dec 2013 15:25

Cork wrote:With regard to my 3.11 686 kernel problem, I corrected by removing the kernel using the steps here:
http://forums.solydxk.com/viewtopic.php ... nels#p9724

Then with a fully updated/rebooted system (into the 3.11 486 kernel) I used Synaptic to reinstall 3.11-2-686-pae (including the source). Ran

Code: Select all

sudo update-grub2
and rebooted into the 3.11-2-686-pae kernel successfully.

Best,
Cork
Not being able to boot into a kernel can be caused by many things, but I'm glad you solved your problem!


SolydXK needs you!
Development | Testing | Translations


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 3 guests