I am testing a box with opensuse 13.1 64 bit. The install went well and I installed some software via yast. I closed yast, then decided to reopen yast and found that after loading the repositories, it would just hang. A reboot did not fix it and I would have to use 'kill pid xxx' to close the yast software installer. Every other yast module works. Then I tried zypper and had the same problem. Zypper stopped at 'reading installed packages...'

I tried 'rpmdb --rebuilddb'

I have used 13.1 since it came out and never had this problem. Does it sound like a corrupt data base and how can I trouble shoot it?

How old is the "box"? Is it older than the date 13.1 was released? If not, you can expect lack of hardware support.

Try zypper clean before trying to do anything else with yast software or zypper.

Killing a package management process can leave a hanging lock that must be removed before proceeding with more package management.

Stopped how? What does the journal have to say about the stoppage?

1 members found this post helpful.

linux-7eep:~ # zypper clean
PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
Tell PackageKit to quit? [yes/no] (no): yes
PackageKit is still running (probably busy).
Try again? [yes/no] (no):


linux-7eep:~ # ps -A
PID TTY TIME CMD
1 ? 00:00:01 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 ksoftirqd/0
5 ? 00:00:00 kworker/0:0H
7 ? 00:00:00 migration/0
8 ? 00:00:00 rcuc/0
9 ? 00:00:00 rcub/0
10 ? 00:00:00 rcu_preempt
11 ? 00:00:00 rcuop/0
12 ? 00:00:00 rcuop/1
13 ? 00:00:00 rcu_bh
14 ? 00:00:00 rcuob/0
15 ? 00:00:00 rcuob/1
16 ? 00:00:00 rcu_sched
17 ? 00:00:00 rcuos/0
18 ? 00:00:00 rcuos/1
19 ? 00:00:00 watchdog/0
20 ? 00:00:00 khelper
21 ? 00:00:00 kdevtmpfs
22 ? 00:00:00 netns
23 ? 00:00:00 perf
24 ? 00:00:00 writeback
25 ? 00:00:00 kintegrityd
26 ? 00:00:00 bioset
27 ? 00:00:00 crypto
28 ? 00:00:00 kblockd
29 ? 00:00:00 ata_sff
30 ? 00:00:00 khubd
31 ? 00:00:00 md
32 ? 00:00:00 kworker/0:1
33 ? 00:00:00 khungtaskd
34 ? 00:00:00 kswapd0
35 ? 00:00:00 ksmd
36 ? 00:00:00 khugepaged
37 ? 00:00:00 fsnotify_mark
44 ? 00:00:00 kthrotld
45 ? 00:00:00 kpsmoused
47 ? 00:00:00 print/0
48 ? 00:00:00 print/1
49 ? 00:00:00 deferwq
50 ? 00:00:00 kworker/u4:1
51 ? 00:00:00 kworker/0:3
87 ? 00:00:00 kmpath_aluad
90 ? 00:00:00 kmpath_rdacd
110 ? 00:00:00 scsi_eh_0
111 ? 00:00:00 scsi_tmf_0
112 ? 00:00:00 scsi_eh_1
113 ? 00:00:00 scsi_tmf_1
135 ? 00:00:00 kworker/0:1H
191 ? 00:00:00 jbd2/sda2-8
192 ? 00:00:00 ext4-rsv-conver
229 ? 00:00:00 systemd-journal
230 ? 00:00:00 kauditd
261 ? 00:00:00 systemd-udevd
298 ? 00:00:00 scsi_eh_2
299 ? 00:00:00 scsi_tmf_2
300 ? 00:00:00 scsi_eh_3
301 ? 00:00:00 scsi_tmf_3
302 ? 00:00:00 scsi_eh_4
303 ? 00:00:00 scsi_tmf_4
304 ? 00:00:00 scsi_eh_5
305 ? 00:00:00 scsi_tmf_5
306 ? 00:00:00 kworker/u4:5
307 ? 00:00:00 scsi_eh_6
308 ? 00:00:00 scsi_tmf_6
309 ? 00:00:00 scsi_eh_7
311 ? 00:00:00 scsi_tmf_7
317 ? 00:00:00 edac-poller
375 ? 00:00:00 jbd2/sda3-8
376 ? 00:00:00 ext4-rsv-conver
544 ? 00:00:00 dbus-daemon
549 ? 00:00:00 avahi-daemon
550 ? 00:00:00 nscd
560 ? 00:00:00 ModemManager
565 ? 00:00:00 wpa_supplicant
570 ? 00:00:00 systemd-logind
580 ? 00:00:00 rsyslogd
587 ? 00:00:00 polkitd
606 ? 00:00:00 kdm
652 ? 00:00:00 iprt
1203 tty7 00:00:57 Xorg
1577 ? 00:00:00 dhclient6
1616 ? 00:00:00 kdm
1654 ? 00:00:00 systemd
1655 ? 00:00:00 (sd-pam)
1656 ? 00:00:00 startkde
1768 ? 00:00:00 dbus-launch
1769 ? 00:00:00 dbus-daemon
1836 ? 00:00:00 start_kdeinit
1855 ? 00:00:00 kdeinit4
2068 ? 00:00:00 klauncher
2097 ? 00:00:01 kded4
2284 ? 00:00:00 kglobalaccel
2341 ? 00:00:00 kwalletd
2389 ? 00:00:00 kactivitymanage
2390 ? 00:00:00 upowerd
2478 ? 00:00:00 udisksd
2558 ? 00:00:00 kwrapper4
2559 ? 00:00:00 ksmserver
2594 ? 00:00:11 kwin
2703 ? 00:00:43 plasma-desktop
2837 ? 00:00:00 knotify4
2928 ? 00:00:00 ksysguardd
3004 ? 00:00:00 kuiserver
3135 ? 00:00:00 nepomukserver
3147 ? 00:00:00 nepomukstorage
3169 ? 00:00:00 pulseaudio
3170 ? 00:00:00 rtkit-daemon
3177 ? 00:00:01 krunner
3190 ? 00:00:00 bluetoothd
3212 ? 00:00:00 kmix
3300 ? 00:00:00 polkit-kde-auth
3301 ? 00:00:00 klipper
3508 ? 00:00:03 virtuoso-t
3623 tty1 00:00:00 agetty
3787 ? 00:00:00 master
3798 ? 00:00:00 cron
3802 ? 00:00:00 pickup
3803 ? 00:00:00 qmgr
3872 ? 00:00:00 avahi-autoipd
3873 ? 00:00:00 avahi-autoipd
3931 ? 00:00:00 dhcpcd
3932 ? 00:00:00 nepomukfilewatc
3958 ? 00:07:12 packagekitd
3995 ? 00:01:40 firefox
4006 ? 00:00:00 gvfsd
4011 ? 00:00:00 gvfsd-fuse
4029 ? 00:00:00 at-spi-bus-laun
4036 ? 00:00:00 kmozillahelper
4049 ? 00:00:00 systemd
4050 ? 00:00:00 (sd-pam)
4090 ? 00:00:00 kworker/0:2
4110 ? 00:00:01 konsole
4112 pts/1 00:00:00 bash
4133 pts/1 00:00:00 su
4136 pts/1 00:00:00 bash
4207 ? 00:00:00 kworker/0:0
4218 pts/1 00:00:00 ps
linux-7eep:~ #


I did not see packagekitd when I ran ps -A so I am not sure what update app is loading during boot.

1 members found this post helpful.

linux-7eep:~ # kill pid 3958
-bash: kill: pid: arguments must be process or job IDs
linux-7eep:~ #

oops, I missed it in my last post, however bash complained. I am using the proper syntax?

1 members found this post helpful.

Append a 3 to the end of the linu line after striking the E key at the Grub menu, then proceed to boot to shell prompt. Login as root to run zypper. PackageKit shouldn't be running without any X session running. If that fails too, try a 1 instead of a 3.

1 members found this post helpful.

I followed your instruction and booted into run level 3 and was able to see all the available packages in the repositories and what was installed was flagged. That was encouraging. I need to read up on zypper. I do not think I am invoking the install properly, however this is progress.

1 members found this post helpful.

The question is why 13.1, long out of support? Leap 15.1 is the currently supported stable release, with 15.2 in beta since last month.

you are aware the support for 13.1( evergreen) has ended
https://en.opensuse.org/Lifetime
mirrors will be disappearing

zypper will have to time out on each mirror( that has been removed) that is in the old mirrorlist
this will make it look like it is freezing

it is time to upgrade this box

1 members found this post helpful.

My first thought was that zypper was hanging because the repositories were unavailable. The dialogue boxes that pop up to point this out normally don't take very long to appear.

1 members found this post helpful.

This error occurred right after I used yast to do a software install. In the yast software module, I should see the packages that are installed after it downloads the repository data. Zypper in <package name> hangs when 'reading installed packages'. At this point, I am considering doing an os update from its install disk (13.1 update to 13.1) to fix the problem. I searched yast and zypper usage and issues and have not found this type of yast/zypper issue. I can install .run files in the system, but .rpm files are another matter.

After rereading the posts a second time, I disabled the opensuse update repositories and found that yast software module is working very well. Thank you to all who pointed me in that direction. My reasoning for using 13.1 is that is works well with my hardware and I understand the limitations of not upgrading. I am considering building a new box that will be compatible with current drivers, etc.

Every 64bit PC I ever had 13.1 installed on, except possibly one, still has it, but also has newer versions, as well. That number is in excess of 20. Every single one of them has the current 15.1 release working. There is very little old hardware that 15.1 doesn't support at all, mostly ancient PCI and AGP GPUs that were new before 64bit PCs became commonplace, and some ancient CPUs that don't support SSE2.

Exactly what hardware do you have that makes you fearful of upgrading and staying secure?

1 members found this post helpful.

If I have to upgrade a video card because of lack of driver support, then my hardware is slowly not being supported, which means that the other hard drives that I use in the box would have to have their configurations changed to support the newer card. I have 15.1 on a another drive that runs 3d ok, but has rips in the video in 2d. However it runs well with 2d drivers and thats ok with what I use 15.1 for. I would have to enable/disable nvidia on boot depending on what I wanted to use 15.1 for.

My hardware:

A8V-E SE motherboard
amd 3000+ cpu
4 gig ram
nvidia 6200 pci express w/turbo cache