UP - 01/10/2014 [TESTING] [DONE]

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
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: UP - 01/10/2014 [TESTING]

Postby fleabus » 30 Sep 2014 22:35

Schoelje wrote:I've updated the pre-up script which now handles the libavformat55 package correctly...
And sorry for the earlier confusion! I finally fell out for a while, I had previously been up for two days... :mrgreen:

All good now.

Code: Select all

dv7-1270us fleabus # apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

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

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 01 Oct 2014 13:08

I just finished upgrading SolydX32 from a 201401 ISO which includes the DMO repository.
Totally uneventful: no issues whatsoever.

I had to update the update manager: it didn't list kernel packages if they were still available in one of the repositories. In this case, the 3.14 packages were still in the security repository and UM didn't list them if you wanted to remove the old kernel.

Tomorrow I'm going to test on metal with Nvidia. I still have several old installs. Let's see if I can brake those.


SolydXK needs you!
Development | Testing | Translations

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

Re: UP - 01/10/2014 [TESTING]

Postby fleabus » 01 Oct 2014 15:54

Schoelje wrote:I just finished upgrading SolydX32 from a 201401 ISO which includes the DMO repository.
Totally uneventful: no issues whatsoever.
Did you remove DMO in the process?

Curious because I have a couple of old X32 installs from 2013-09 and -11 on old machines that I was going to experiment on....

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

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 01 Oct 2014 16:39

zerozero wrote:had to re-install virtualbox-guest-dkms in K-64 to have proper screen resolution, full-screen and correct mouse integration

Code: Select all

-------- Uninstall Beginning --------
Module:  virtualbox-guest
Version: 4.3.14
Kernel:  3.16-2-amd64 (x86_64)
-------------------------------------

Status: This module version was INACTIVE for this kernel.
depmod............

DKMS: uninstall completed.

------------------------------
Deleting module version: 4.3.14
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-guest-dkms (4.3.14-dfsg-1) over (4.3.14-dfsg-1) ...
Preparing to unpack .../virtualbox-guest-utils_4.3.14-dfsg-1_amd64.deb ...
Unpacking virtualbox-guest-utils (4.3.14-dfsg-1) over (4.3.14-dfsg-1) ...
Preparing to unpack .../virtualbox-guest-x11_4.3.14-dfsg-1_amd64.deb ...
Unpacking virtualbox-guest-x11 (4.3.14-dfsg-1) over (4.3.14-dfsg-1) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up virtualbox-guest-utils (4.3.14-dfsg-1) ...
Setting up virtualbox-guest-dkms (4.3.14-dfsg-1) ...
Loading new virtualbox-guest-4.3.14 DKMS files...
Building only for 3.16-2-amd64
Building initial module for 3.16-2-amd64
Done.

vboxguest:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16-2-amd64/updates/

vboxsf.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16-2-amd64/updates/

vboxvideo.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16-2-amd64/updates/

sed: -e expression #1, char 6: unknown command: `m'
depmod....

DKMS: install completed.
Setting up virtualbox-guest-x11 (4.3.14-dfsg-1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
this was most probably user error :lol: because i couldn't replicate it in the upgrade i did today of X-64.
bliss of ignorance

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

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 01 Oct 2014 17:01

in the X-64 i mentioned in the post above the update was smooth and with no dramas (as we like it :lol: ) apart from a few packages held back (but this is an older install and with some customization.

Code: Select all

The following packages have been kept back:
  bzr python-bzrlib systemd-shim
as for bzr and python-bzrlib the solution is somehow simple

Code: Select all

zerozero@x64-vb:~$ apt install bzr
[sudo] password for zerozero: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cgmanager libavresample1 libavutil53 libcgmanager0 libinput0 liblivemedia32
  libmbim-glib0 libnih-dbus1 libnih1 libpoppler44 libqmi-glib0 libx265-21
  python-ecdsa
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  python-bzrlib
Suggested packages:
  bzr-doc bzrtools python-bzrlib.tests python-bzrlib-dbg python-kerberos
The following packages will be REMOVED:
  python-paramiko
The following packages will be upgraded:
  bzr python-bzrlib
2 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 1,655 kB of archives.
After this operation, 765 kB disk space will be freed.
it wants to remove python-paramiko that was automatically installed with bzr

Code: Select all

zerozero@x64-vb:~$ aptitude why python-paramiko
i   bzr-builddeb  Depends    bzr (>= 2.1~)                     
i A bzr           Depends    python-bzrlib (>= 2.6.0+bzr6595-1)
i A python-bzrlib Recommends python-paramiko   
===
systemd-shim (already discussed in this topic -i think-) has to be dropped

Code: Select all

 zerozero@x64-vb:~$ apt install systemd-shim
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libavresample1 libavutil53 libinput0 liblivemedia32 libmbim-glib0 libndp0
  libpoppler44 libqmi-glib0 libteamdctl0 libx265-21
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  sysvinit-core
The following packages will be REMOVED:
  aptdaemon colord gufw gvfs gvfs-backends gvfs-daemons hplip libpam-systemd
  network-manager network-manager-gnome packagekit packagekit-tools
  policykit-1 policykit-1-gnome printer-driver-postscript-hp systemd
  systemd-sysv udisks2
The following NEW packages will be installed:
  sysvinit-core
The following packages will be upgraded:
  systemd-shim
1 upgraded, 1 newly installed, 18 to remove and 2 not upgraded.
Need to get 147 kB of archives.
After this operation, 34.7 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
bliss of ignorance

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

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 01 Oct 2014 17:22

@fleabus
I left the DMO repository to see how that would go.

@zerozero
I've added package handling for bzr in the pre-up script.
systemd-shim is removed by the pre-up script when systemd-sysv is installed.
You can check the script here, if you want: http://repository.solydxk.nl/umfiles/ts ... 2014.10.15


SolydXK needs you!
Development | Testing | Translations

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

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 01 Oct 2014 17:41

Schoelje

regarding bzr i don't know if it needs a special rule in the pre-update script, it's not a common package to have installed (it comes as dependency of packaging-dev) but i believe it won't hurt having it there.

Code: Select all

zerozero@x64-vb:~$ aptitude why bzr
i   bzr-builddeb Depends bzr (>= 2.1~)
zerozero@x64-vb:~$ aptitude why bzr-builddeb
i   packaging-dev Recommends bzr-builddeb
systemd-shim is not handled (was not in this situation and as far as i can see is not either in the update i'm doing now in the laptop) because

Code: Select all

pck_isinstalled 'systemd-sysv'
if $PCKINSTALLED; then
  handle_pck 'systemd-shim' 'purge' 'all'
the problem is that at that time systems-sysv is not installed yet (it will be during the update)
this would work as a post-upgrade rule

Code: Select all

zerozero@x64-vb:~$ apt purge systemd-shim
[sudo] password for zerozero: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cgmanager libavresample1 libavutil53 libcgmanager0 libinput0 liblivemedia32
  libmbim-glib0 libnih-dbus1 libnih1 libpoppler44 libqmi-glib0 libx265-21
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  systemd-shim*
0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
After this operation, 94.2 kB disk space will be freed.
Do you want to continue? [Y/n] 
EDIT: the pre-up script as-is works well with the 2014.07 isos that are already converted to systemd but the problem i described will be visible for systems that come from the april-UP.
bliss of ignorance

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

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 01 Oct 2014 18:33

shim handling moved to post-up script.


SolydXK needs you!
Development | Testing | Translations

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

Re: UP - 01/10/2014 [TESTING]

Postby fleabus » 01 Oct 2014 18:52

Schoelje wrote:@fleabus
I left the DMO repository to see how that would go.
I also have two older installs here on my main/test machine. They are both 64bit (unlike the ones in my back room), and from the same dates as the back room machines, (2013-09 and -11). Fwiw, Both of these 64bit installs have been moved in and out of DMO a couple of times using solydfixes without issue... :mrgreen:

At this point I'm going to stay with SysV on these two old 64bit installs -- as a <cough> purely educational exercise of course.... ;)

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

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 01 Oct 2014 19:22

updated one install in the amd laptop and fglrx behaved very well :mrgreen:
no need for post-update driver reinstallation

Code: Select all

zerozero@x-test:~$ inxi -Fzx
System:    Host: x-test Kernel: 3.16-2-amd64 x86_64 (64 bit gcc: 4.8.3)
           Desktop: Xfce 4.10.2 (Gtk 2.24.18) Distro: SolydXK 1 testing
Machine:   System: LENOVO product: Lenovo G585 v: Lenovo G585
           Mobo: LENOVO model: Lenovo G585 v: 31900003WIN8 STD MLT
           Bios: LENOVO v: 6CCN88WW(V8.01) date: 08/22/2012
CPU:       Dual core AMD E2-1800 APU with Radeon HD Graphics (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4a ssse3 svm) bmips: 6787
           clock speeds: max: 1700 MHz 1: 1360 MHz 2: 850 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 7340]
           bus-ID: 00:01.0
           Display Server: X.Org 1.16.1 driver: fglrx
           Resolution: 1366x768@60.00hz
           GLX Renderer: AMD Radeon HD 7340 Graphics
           GLX Version: 4.4.12968 - CPC 14.10.1006.1001 Direct Rendering: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
           driver: snd_hda_intel bus-ID: 00:14.2
           Card-2 Advanced Micro Devices [AMD/ATI] Wrestler HDMI Audio
           driver: snd_hda_intel bus-ID: 00:01.1
           Sound: Advanced Linux Sound Architecture v: k3.16-2-amd64
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 2000 bus-ID: 02:00.0
           IF: eth0 state: down mac: <filter>
           Card-2: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express)
           driver: ath9k bus-ID: 06:00.0
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 320.1GB (3.6% used)
           ID-1: /dev/sda model: WDC_WD3200BPVT size: 320.1GB temp: 43C
Partition: ID-1: / size: 54G used: 7.2G (14%) fs: ext4 dev: /dev/sda6
           ID-2: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
Sensors:   System Temperatures: cpu: 45.0C mobo: N/A gpu: 45.00C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 157 Uptime: 10 min Memory: 536.5/3534.4MB
           Init: systemd runlevel: 5 Gcc sys: 4.9.1
           Client: Shell (bash 4.3.251) inxi: 2.2.14 
zerozero@x-test:~$ 
bliss of ignorance

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 01 Oct 2014 21:50

Updated two 32 bit installs on my old laptop: K & X, both based on 2014-07 ISO, i.e. with systemd already present and no dmo.
Except for the pixbuf messages and another set of warnings about missing icons, no issues during the update, but two oddities afterwards:
- SolydK had lost it's wireless keyword (had to be re-entered)
- SolydX had lost the panel's battery plugin (had to be re-installed)

Both had issues when I wanted to reboot, but that's a known problem. I've now seen three variations of this:
- only logoff available and every option greyed out in LightDM (SolydX 64 - required terminal to reboot)
- only logoff available but reboot possible from LightDM (SolydX 32)
- reboot available but not actually functional (jumped to LightDM) - reboot possible from LightDM (SolydK 32)
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: UP - 01/10/2014 [TESTING]

Postby Snap » 01 Oct 2014 22:08

- only logoff available but reboot possible from LightDM (SolydX 32)
That was my case twice.
This likely means that your installation is broken. -Mr Pixbuf.

Image

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

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 02 Oct 2014 05:06

@grizzler
These packages you had to re-install, were they installed by default?
What were their actual package names?


SolydXK needs you!
Development | Testing | Translations

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 02 Oct 2014 06:28

Schoelje wrote:@grizzler
These packages you had to re-install, were they installed by default?
One package: the battery monitor on the panel. No, I don't think so. I don't see it in any of the SolydX VMs, but that could be because there's no battery to monitor there. However, it was present on the laptop before the upgrade.
What were their actual package names?
Good question. I'll let you know as soon as I've managed to find out.
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
grizzler
Posts: 2217
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: UP - 01/10/2014 [TESTING]

Postby grizzler » 02 Oct 2014 08:31

grizzler wrote:
Schoelje wrote:
What were their actual package names?
Good question. I'll let you know as soon as I've managed to find out.
The package appears to be called xfce4-battery-plugin and it seems to be installed by default, but that doesn't mean the plugin is actually present on the panel (it isn't on my main system or in the VMs). I don't think this is something that can easily be coded in a pre- or post-up script. Maybe just add a warning that the plugin may be missing from the panel after the upgrade? It should still be installed in package management.
Frank

SolydX EE 64 - tracking Debian Testing

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

Re: UP - 01/10/2014 [TESTING]

Postby fleabus » 02 Oct 2014 08:42

Schoelje wrote:I just finished upgrading SolydX32 from a 201401 ISO which includes the DMO repository.
Totally uneventful: no issues whatsoever.
I upgraded the old P3 last night using the terminal (SolydX32-pae), also no issues. It has 512M of ram and a Radeon 9600SE/128. I kept DMO and purposely did not run the pre-up. So far it's doing great. I suppose no real reason to run pae, though the cpu does at least have that flag.

Code: Select all

fleabus@d815eea2:~$ uname -a
Linux d815eea2 3.16-2-686-pae #1 SMP Debian 3.16.3-2 (2014-09-20) i686 GNU/Linux
fleabus@d815eea2:~$ inxi -Fzrxxx
System:    Host: d815eea2 Kernel: 3.16-2-686-pae i686 (32 bit gcc: 4.8.3) 
           Desktop: N/A info: xfce4-panel dm: lightdm Distro: SolydXK 1 testing 
Machine:   Mobo: Intel model: D815EE2U v: AAA52399-803
           Bios: Intel v: EA81520A.86A.0039.P21.0211061753 date: 11/06/2002
CPU:       Single core Intel Pentium III family (-UP-) cache: 512 KB
           flags: (pae sse) bmips: 2789 clocked at 1394 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV350 [Radeon 9550/9600/X1050 Series]
           bus-ID: 02:00.0 chip-ID: 1002:4150
           Display Server: X.Org 1.16.1 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on ATI RV350 GLX Version: 2.1 Mesa 10.2.6 Direct Rendering: Yes
Audio:     Card Intel 82801BA/BAM AC'97 Audio Controller 
           driver: snd_intel8x0 ports: e800 ef00 bus-ID: 00:1f.5 chip-ID: 8086:2445 
           Sound: Advanced Linux Sound Architecture v: k3.16-2-686-pae
Network:   Card: Intel 82801BA/BAM/CA/CAM Ethernet Controller
           driver: e100 v: 3.5.24-k2-NAPI port: cf00 bus-ID: 01:08.0 chip-ID: 8086:2449
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 80.0GB (12.3% used)
           ID-1: /dev/sda model: WDC_WD800AAJB size: 80.0GB serial: WD-WCAV3C557217
Partition: ID-1: / size: 9.5G used: 5.5G (61%) fs: ext4 dev: /dev/sda6 
           ID-2: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 
Sensors:   None detected - is lm-sensors installed and configured?
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb http://packages.solydxk.com/testing/ solydxk main upstream import
           deb http://debian.solydxk.com/testing testing main contrib non-free
           deb http://debian.solydxk.com/security testing/updates main contrib non-free
           deb http://debian.solydxk.com/testing/multimedia testing main non-free
           deb http://community.solydxk.com/testing/ solydxk main
Info:      Processes: 136 Uptime: 6 min Memory: 166.8/499.9MB 
           Init: systemd v: 208 runlevel: 5 default: 2 Gcc sys: 4.9.1 alt: 4.6/4.7/4.8 
           Client: Shell (bash 4.3.251 running in xfce4-terminal) inxi: 2.1.28

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

Re: UP - 01/10/2014 [TESTING]

Postby Arjen Balfoort » 02 Oct 2014 08:48

@grizzler
Odd, with my upgrade of SolydX32, xfce4-battery-plugin wasn't removed.
I'll check it with SolydX64 later.

@fleabus
This promises to be a boring UP :D
In fact, I think it's that boring that I already started to build the ISOs...


SolydXK needs you!
Development | Testing | Translations

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

Re: UP - 01/10/2014 [TESTING]

Postby fleabus » 02 Oct 2014 11:34

Schoelje wrote:@fleabus
This promises to be a boring UP :D
It really is! It has been for me, at any rate. I had commented on that fact in Snap's thread here:

http://forums.solydxk.nl/viewtopic.php? ... 069#p45069

You're getting right good at this! Bravo old son! :D ;)
Schoelje wrote:In fact, I think it's that boring that I already started to build the ISOs...
Just from my own experiences with this one, I'd say go for it...
Soon as I get my greedy little hands on one I'll do some metal installs... Ain't no VBs on me! :mrgreen:

User avatar
smitty1
Posts: 256
Joined: 23 Jun 2013 13:50
Location: Pittsburgh, PA USA

Re: UP - 01/10/2014 [TESTING]

Postby smitty1 » 02 Oct 2014 18:48

Getting around to testing some seldom used apps, and I cannot get Software Manager to open, from the menu, terminal or alt-F2. Click on it and an enter password box comes up, enter password and it goes away but no software manager appears.
This happens on both SolydK 64 metal & SolydX 64 vm.

No Good Deed Goes Unpunished

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

Re: UP - 01/10/2014 [TESTING]

Postby zerozero » 02 Oct 2014 19:29

smitty1 wrote:Getting around to testing some seldom used apps, and I cannot get Software Manager to open, from the menu, terminal or alt-F2. Click on it and an enter password box comes up, enter password and it goes away but no software manager appears.
This happens on both SolydK 64 metal & SolydX 64 vm.
confirmed :cry:
and strangely enough tried 3 installs (X-64 metal, X-64 and K-64 both VM's):
softwaremanager is broken in all of them but only in K-64 i got a clue about the problem

Code: Select all

 zerozero@k64-vb ~ $ softwaremanager
Attempt to unlock mutex that was not locked
add_categories took 0.572 ms
build_matched_packages took 0.098 ms
'googleearth'
'virtualbox-nonfree'
'miro'
'vuze'
'netbeans'
'skype'
'worldofgoodemo'
'steam-launcher'
'seamonkey-browser'
'midori'
'galeon'
'prism'
'dooble'
'rekonq'
'anjal'
'prism-google-mail'
'seamonkey-mailnews'
'freepops'
'mailody'
'kcheckmail'
'skype'
'gossip'
'kadu'
'sim'
'centerim'
'cgiirc'
'naim'
'seamonkey-chatzilla'
'sirc'
'eva'
'prism-google-talk'
'qutim'
'kasablanca'
'amule'
'frostwire'
'vuze'
'foff'
'giver'
'gnunet-qt'
'gwget'
'kbluetooth'
'kepas'
'kflickr'
'kradioripper'
'miro'
'moserial'
'tork'
'tucan'
'minitunes'
'xine'
'acidrip'
'lastfm'
'k9copy'
'gnomebaker'
'listen'
'aqualung'
'mplayer-gui'
'kivio'
'kolourpaint'
'openoffice.org-draw'
'skencil'
'xaralx'
'gqview'
'f-spot'
'gpixpod'
'flegita'
'kcoloredit'
'kflickr'
'kiconedit'
'koverartist'
'opencascade-draw'
'kivio'
'kolourpaint'
'skencil'
'kcoloredit'
'kiconedit'
'koverartist'
'fontmatrix'
'openoffice.org-draw'
'pencil'
'salasaga'
'xaralx'
'gqview'
'f-spot'
'gpixpod'
'kflickr'
'luciole'
'phatch'
'rawstudio'
'flegita'
'acroread'
'epdfview'
'omaque'
'pdfedit'
'viewpdf.app'
'xpdf-reader'
'steam-launcher'
'worldofgoodemo'
'ggz-python-games'
'ggz-kde-games'
'pouetchess'
'stroq'
'open-arena'
'urban-terror'
'warsow'
'boson'
'glest'
'wormux'
'zsnes'
'uae'
'pearpc'
'pcsx-df'
'pose-skins'
'nestra'
'kxmame'
'snes9express'
'gfceu'
'dgen'
'armagetron'
'planetpenguin-racer'
'wine1.2'
'virtualbox-guest-additions'
'virtualbox-ose'
'virtualbox-3.1'
'compizconfig-settings-manager'
'ttf-telugu-fonts'
'ttf-farsiweb'
'ttf-droid'
'ttf-indic-fonts-core'
'ttf-linux-libertine'
'ttf-monapo'
'ttf-sil-gentium'
'ttf-sil-gentium-basic'
'carmetal'
'controlaula'
'drgeo'
'edubuntu-desktop-kde'
'edubuntu-desktop'
'freespeak'
'denemo'
'k3dsurf'
'kalcul'
'kayali'
'klavaro'
'lletters'
'ubuntu-edu-preschool'
'ubuntu-edu-primary'
'qucs'
'score-reading-trainer'
'ubuntu-edu-secondary'
'squeak'
'sugar-emulator-0.88'
'ubuntu-edu-tertiary'
'tipptrainer'
add_packages took 2595.528 ms
add_reviews took 483.828 ms
__init__ took 3412.344 ms
Aborted
zerozero@k64-vb ~ $ 
http://forums.solydxk.nl/viewtopic.php? ... =20#p45043
the 2 other installs don't output this error but softwaremanager is broken the same.
bliss of ignorance


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 6 guests