Problems with 13.10

[Rog132]

https://lists.ubuntu.com/archives/sa...er/009991.html

sip4 (4.15.2~snapshot-20130906-0ubuntu1) saucy; urgency=low

* New upstream snapshot to fix breakage with pykde4

https://lists.ubuntu.com/archives/sa...er/009993.html

pykde4 (4:4.11.1-0ubuntu2) saucy; urgency=low

* Add debian/patches/pykde4.11_protected_public.patch to fix breakage with
sip4 4.15/4.15.1 (LP: #1220675)

[NoWorries]

I have the same problem.
And noticed jockey is not running with some errors maybe also pointing to a Python issue.

teunis@13-10-W520:~$ jockey-kde
ERROR:root:Could not find any typelib for AppIndicator3
Traceback (most recent call last):
  File "/usr/bin/jockey-kde", line 32, in <module>
    import jockey.ui
  File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 36, in <module>
    from jockey.oslib import OSLib
  File "/usr/lib/python2.7/dist-packages/jockey/oslib.py", line 27, in <module>
    class _CapturedInstallProgress(apt.InstallProgress):
AttributeError: 'module' object has no attribute 'InstallProgress'
teunis@13-10-W520:~$

I have been putting up with exactly the same problem problem of not being able to Configure Software Sources for about a week. I get the same output as you when I enter jockey-kde. All other aspects of my system are working as before and for this reason I did not take immediate action to complain. I am glad that this problem has been reported. I have been hoping that KDE 4.11.1 would correct this, however even after many 4.11.1 packages being installed, KinfoCenter still shows that 4.11.0 is the installed version.

[NoWorries]

Since the latest updates Jockey is again functional.
In my view this distro is already smoother than 13.04 and the nVidia 3.19 driver is also working really well.

I certainly agree that this system is smoother than 13.04, BUT jockey is not running on my system and the response I get when I now try to run it after all the updates is:

~$ jockey-kde
ERROR:root:Could not find any typelib for AppIndicator3
KCrash: Application '' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/aurora/.kde/socket-basil/kdeinit4__0

[1]+  Stopped                 jockey-kde

Also, muon Configure Software Source does not give the menu but launches into updating. The window that I get to enter the password is shown in the graphic.

[NoWorries]

The past week I had to use the gtk version for configuring the repo's:

software-properties-gtk

I did try installing software-properties-gtk but that made no difference to my system.

But as said, last night's updates made everything good on this system.
Update:

Starting Jockey from a Konsole does throw the same error yet the program launches successfully.

And that makes me wonder why are there differences?
I did a fresh install, retaining my ~/home, I had to rename ~/.kde because X would crash on boot, so those configs are new too.

After I run jockey and get the errors, it is still not in my system. I tried renaming the ~/.kde and that did not fix the problem. I was surprised that when I selected the recovery option for booting and entered the root partition, I could not find my home partition.

[NoWorries]

I have just found that the latest updates have resulted in virtuoso-t taking 100% of one of my 8 CPU's. It cycles through each CPU and the system performance is sluggish. I unchecked the System Settings>Desktop Search>Basic Settings>Mepomuk Desktop File Indexer and this made no difference. I recover system performance by stopping virtuoso-t. I remember this being an old problem which seems to have resurfaced.

Edit1:
I decided to measure how long it took for Dolphin to start and my measurement was 26s on an ASUS R501VM Intel Core i7 3610QM 16GB Ram. This is what I call sluggish!!!!!!

Edit2:
Found that the latest Linux Kernel 3.11.0-7-generic is the reason for the system being sluggish. This time I booted with 3.11.0-6 and virtuoso-t was nowhere to be seen and I could not measure Dolphin startup .

So it looks like the modifications to 3.11.0-7 need to be revisited post haste.

Edit3:
Latest updates fixed slow response and is seems as though it was not the Kernel 3.11.0.-7 at fault. Muon still is not behaving as it should for me.

[nevillef]

I have been putting up with exactly the same problem problem of not being able to Configure Software Sources for about a week. I get the same output as you when I enter jockey-kde. All other aspects of my system are working as before and for this reason I did not take immediate action to complain. I am glad that this problem has been reported. I have been hoping that KDE 4.11.1 would correct this, however even after many 4.11.1 packages being installed, KinfoCenter still shows that 4.11.0 is the installed version.

The problem is not KDE 4.11 as I have that installed in my 12.04 and don't have any of these problems.

[Rog132]

The fix has been released !!!

The original problem: http://www.kubuntuforums.net/showthr...l=1#post334111

When I want to edit software sources or change update server, the "Software sources" window doesn't load. When I enter password and hit enter it goes back to the Muon window and does an action like I pressed the "Check for updates" button.
Also when I go to User Management in System Settings it asks for a password and then crashes.

Earlier - bug report: http://www.kubuntuforums.net/showthr...l=1#post334547

Earlier - new packages: http://www.kubuntuforums.net/showthr...l=1#post334911


The fixed packages are stuck in the proposed: http://irclogs.ubuntu.com/2013/09/13...el.html#t16:49

yofel hm, why's python-kde4 held back here o.O 16:49
Riddell yofel: the new one is still stuck on arm 16:52
Riddell so it's in -proposed 16:52

The proposed or pre-released updates:
- https://help.ubuntu.com/community/UbuntuUpdates
- https://wiki.ubuntu.com/Testing/EnableProposed


If you enable the proposed - then there are a new update canditate:

:~$ apt-cache policy python-kde4
python-kde4:
Installed: 4:4.11.0-0ubuntu1
Candidate: 4:4.11.1-0ubuntu2
Version table:
4:4.11.1-0ubuntu2 0
500 http://fi.archive.ubuntu.com/ubuntu/ saucy-proposed/universe amd64 Packages
*** 4:4.11.0-0ubuntu1 0
500 http://fi.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
100 /var/lib/dpkg/status

Picking only the pykde packages (picked by version):

:~$ apt-get -s dist-upgrade | grep 4:4.11.1-0ubuntu2
Inst python-kde4 [4:4.11.0-0ubuntu1] (4:4.11.1-0ubuntu2 Ubuntu:13.10/saucy-proposed [amd64])
Inst python3-pykde4 [4:4.11.0-0ubuntu1] (4:4.11.1-0ubuntu2 Ubuntu:13.10/saucy-proposed [amd64])

and updating them:

sudo apt-get install python-kde4 python3-pykde4
[sudo] password for rog132:
Reading package lists...
Building dependency tree...
Reading state information...
...
The following packages will be upgraded:
python-kde4 python3-pykde4
2 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.

After the upgrade disabling the proposed.

With the new version the Python scripts with the KDE bindings (software-properties-kde) should work - at here they are working.


Jockey et al problems

It would be easier to follow if there is one problem per thread/topic - but quoting at here:

The Jockey status: http://irclogs.ubuntu.com/2013/09/13...el.html#t18:23

lordievader ronnoc: Python-apt is updated, functions that the jockey depends on are removed from the api. 18:23
ronnoc shadeslayer: lordievader: Thanks for the update. I assume a fix will be forthcoming shortly. 18:26
=== zorael is now known as zorael^
=== zorael^ is now known as zorael
lordievader ronnoc: I'm not so sure of a fix, I heard it was unmaintained. 19:18
ronnoc lordievader: Is it a KDE-only issue, or does it affect Ubuntu as well? 19:24
lordievader ronnoc: All of Ubuntu, I fixed "jockey-text -l" couple of days ago. But the rest of "jockey-text" seems to be broken too. And on top of that, jockey-kde seems to have a heap of its own problems 19:28
ronnoc That's a sad situation to be sure. Hope i gets sorted out somehow or there will be a lot of confused users when 13.10 hits :/ 19:32

I don't have the Jockey installed so I can't say nothing of it - BUT as said: It would be easier to follow if there is a new Jockey thread.

[nevillef]

Thank you for that. Updating the 2 python files did the trick for the software sources and user management for me.
A side benefit of the update is that now running sudo apt-get update finishes in a few seconds as before it took minutes to complete.

[NoWorries]

Thanks for letting us know about the python updates. I took a slightly different approach to doing this. I edited the file /etc/apt/sources.list and added the line:

## proposed updates
deb http://archive.ubuntu.com/ubuntu saucy-proposed multiverse restricted universe main

I then took the bull by the horns and upgraded all of the packages in the proposed repository.

It is great to now have muon working. I also have found that the Startup Disk Creator package now works

[SteveRiley]

I have been living with $DISTRO-proposed enabled for quite some time now, probably ever since Lucid. Can't think of a time when it caused me a problem.

[Rog132]

...try#N...

http://irclogs.ubuntu.com/2013/09/16...el.html#t22:49

ScottK Updating pykde4 to 4.11 trunk should fix it. 22:49

http://irclogs.ubuntu.com/2013/09/17...el.html#t04:42

ScottK Hopefully fixed pykde4 uploaded. 04:42
ScottK Meh. Failed on armhf again. 05:00

https://lists.ubuntu.com/archives/sa...er/010465.html

pykde4 (4:4.11.1+git20130916-0ubuntu1) saucy; urgency=low

* Upstream snapshot to complete fix for sip4 4.15 breakage fixes
- Drop debian/patches/pykde4.11_protected_public.patch, was backported
from upstream, no longer required
- Refreshed patches

https://lists.ubuntu.com/archives/sa...er/010427.html

sip4 (4.15.2-1ubuntu1) saucy; urgency=low

* Merge from Debian Experimental. Remaining Ubuntu changes:
- Adjust Breaks versioning to match Ubuntu versioning for rebuild only
uploads