Bugzilla – Bug 527283
Update hangs when entering screensaver, and cannot be restarted. (no retry button.)
Last modified: 2009-09-03 17:25:23 UTC
During a major update, 2,5 GB, i left the system alone. When i came back, the screen was black. I was able to come into the password dialog, and entered the password. Then i found the update had stopped in the middle of a download of openct, with 1.78 GB to go:530 pkgs. ( where over a thousand.) At this point ther was no routeractivity anymore, and the two balls were turning. Continue was greyed out, so there is no way to get the update going again. Cancel seems still useable, but at this moment i have not tried it. I hope i can get it going without problems, else i fear for a wrecked system. I am going to try to cancel after submitting this bug.
Yast realy hangs. Cancel does not reakt. Before taking this update, i updated all of yast and rebooted: all fine. Than i updated all pkgs, kept the old kernel, because there seemed to be a problem with the new one, and okular would be uninstalled. When installing k3b earlier, to find out if bug# https://bugzilla.novell.com/show_bug.cgi?id=521325 was still active, a lot of new pkgs had to be pulled in.
Created attachment 309769 [details] exact state where yast hangs...
I am not able to close the update window. I will try to log off, and continue the update after logging back in.
The yast module seems trange: a slider to the right, and all options are in the same window. I try to restart the update, but the amount of pkgs to update has changed.has changed. Yast hangs when trying to install the first pkg.
Created attachment 309772 [details] yasthangs1.png
Also this time, there is no normal way to interrupt or cancel the proces. I will close down, and see what happens tomorrow.
Atm the update can be performed. I am doing: 'update everything in the list when update is available' 448 pkgs to go: 1.80GB.
The update finished without errors, except very much kernel dep warnings and FATAl Warnings about non existing kernel modules, but it finished and a ll seems fine. I am going to reboot, and if i am not reporting back the warnings were true ;)
M4 started.. :)
Robby,could you please attach y2logs according to http://en.opensuse.org/Bugs/YaST? Thanks!
Created attachment 312173 [details] yast logs.
Found in y2log-1.gz: 2009-07-31 21:28:51 [zypp++] ExternalProgram.cc(start_program):210 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--force' '--nodeps ' '--' '/var/cache/zypp/packages/openSUSE 11.2-0/suse/x86_64/openct-0.6.15-7.5.x86_64.rpm' [zypp++] ExternalProgram.cc(start_program):355 pid 10621 launched 2009-07-31 23:11:42 [qt-ui] YQMainWinDock.cc(closeEvent):297 Caught window manager close event - returning with YCancelEvent ... 2009-07-31 23:19:24 [qt-ui] YQUI.cc(qMessageHandler):709 <libqt-warning> YaST2: Fatal IO error: client killed [qt-ui] YQUI.cc(qMessageHandler):724 Client killed. Possibly caused by X server shutdown or crash. I don't see anything related to installation or update.
Nothing related to kernel either.
Don't see how KDE is to blame :-)...
Would it be possible to provide the required information according to our HOWTO http://en.opensuse.org/Bugs:X for reporting X11 related bugs? Please set the Status back to ASSIGNED after providing all the required information. Thanks.
I had similar problems with installing the openct package happen back when the package was released, only while using command line zypper dup from factory. I assumed that either the package was at fault, or perhaps it was a problem with zypper's use of aria2c on a broken metalink. My current test systems are doing fine after several zypper dup's using "export ZYPP_ARIA2C=0" (just my two cents.)
Reading the commments again I have no idea, why this bugreport has been assigned to X.Org component. Back to YaST.
Again, now when updating all pkgs, the installer keeps on trying to install bundle-lang-gnome-nl-, which seems to be impossible. The first time it shows many attempts, and the possibility to retry or continue, but after retry, there is no possibility to stop the attempts. No way to exit yast2 normal way: ctrl-alt-backspace(x2) killed the desktop and relogged. I am going to try again now.
Same happened. I am going to disable the pkg from updating.
Now the update continues. The fact that the process cann't be stopped other than killing the desktop, disturbs me.
Created attachment 315860 [details] Yast log Rob Verberne
despite the fact that i protected the old pkg, the new pkg wants to install, and keeps retrying, even after the 'skip' button has been pressed. So ending up with the same situation. Do i have to file seperate bugs for this?
sorry, my mistake, now the nl pkg skipped (was protected though), but the en pkg gives the same troubles.
Skipping the bundle-lang-gnome-en, after many retries to download it, worked. Updating continues... I presume both pkgs, (and maybe all the other languages too) are broken.
It seems that problem is in openct package. See comment #12
Can you try /etc/init.d/openct start and /etc/init.d/openct restart manually? Does it also hang? Does hang also: /usr/sbin/openct-control shutdown /usr/sbin/openct-control init If it hangs: Do you have any crypto hardware (smart card reader, crypto token, SIM card reader,...)? Could you strace the commands above and attach the output?
The pkgs donot exist in the clean M6 install: oddball@AMD64x2-SFN1:~> /etc/init.d/openct start bash: /etc/init.d/openct: Bestand of map bestaat niet oddball@AMD64x2-SFN1:~> su Wachtwoord: AMD64x2-SFN1:/home/oddball # /etc/init.d/openct start bash: /etc/init.d/openct: Bestand of map bestaat niet AMD64x2-SFN1:/home/oddball # I do indeed have a smartcardreader 35 in 1. Dear stanislav, i am afraid i cannot help you atm. What i can do is install the openct pkg and look what happens than, but that would be later this evening, or tomorrow morning.
Bestand of map bestaat niet = No such file or directory Package openct was not installed on your system, but I am not sure, in which phase of installation it died. In %pre phase (before installation of package files), openct tries to install new UID and GID. Do you see scard UID and GID in your /etc/passwd and /etc/group? To ZYPP people: What will happen, if installation fails due to hand in the %post? Will the package be removed or the installation will continue? --- If your smart card reader is the 35 in 1 that I had a chance to test (a standard memory card reader with a SIM slot with ID 04cf:9920 Myson Century, Inc. CS8819A3-116 or similar), then its SIM slot is not supported by Linux. The reader is recognized in linux just like a simple mass storage memory card reader. Regarding the openct package: This package should not be installed by default (but it was installed in past). It should be installed only on a system with supported hardware (reader that conforms ISO 7816 Smart Card reader standard and which has a driver in Linux).
(In reply to comment #29) > Bestand of map bestaat niet = No such file or directory Correct > > Package openct was not installed on your system, but I am not sure, in which > phase of installation it died. I was updating all pkgs that have newer version, in Yast_sw Single. Yast downloads, and immediately installs the pkgs. On the picture in Comment#2 , is visible that the install hangs on 50%.. > In %pre phase (before installation of package files), openct tries to install > new UID and GID. Do you see scard UID and GID in your /etc/passwd and > /etc/group? Nope...! > > To ZYPP people: What will happen, if installation fails due to hand in the > %post? Will the package be removed or the installation will continue? > > --- > > If your smart card reader is the 35 in 1 that I had a chance to test (a > standard memory card reader with a SIM slot with ID 04cf:9920 Myson Century, > Inc. CS8819A3-116 or similar), then its SIM slot is not supported by Linux. > The > reader is recognized in linux just like a simple mass storage memory card > reader. It is a Hama usb 2.0 Card Reader, And the simcard slot need an adapter to use it, but i never did. > > Regarding the openct package: > > This package should not be installed by default (but it was installed in past). > It should be installed only on a system with supported hardware (reader that > conforms ISO 7816 Smart Card reader standard and which has a driver in Linux). Meaning that there were differences between hwdetection, and ct? Hwdetection called upon ct, and ct did not find the device it should serve?
Well, it seems, that the installation was waiting in useradd. This bug was already reported as bug 510788 and should be already fixed. Regarding the card reader: openct does no hardware detection. It knows USB IDs and USB interface classes of device that can be handled. If any is found, it handles it. I cannof decide, whether you reader is supported or not without further information (e. g. lsusb, lshal or hwinfo). If it is based on Myson Century chipset like many other cheap memory+SIM card readers, then it is not supported and probably never will be (it contains a proprietary 8 bit microcontroller and its ISO 7816 is not documented nor supported in Linux). If it is based on a different hardware (e. g. CCID standard reader), then it may be supported. *** This bug has been marked as a duplicate of bug 510788 ***
oddball@AMD64x2-SFN1:~> lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1307:0330 Transcend Information, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub oddball@AMD64x2-SFN1:~> Which parts of lshal are of interest for you the usb parts? udi = '/org/freedesktop/Hal/devices/usb_device_1d6b_2_0000_00_02_1' info.linux.driver = 'usb' (string) info.parent = '/org/freedesktop/Hal/devices/pci_10de_3f2' (string) info.product = '2.0 root hub' (string) info.subsystem = 'usb_device' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_1d6b_2_0000_00_02_1' (string) info.vendor = 'Linux Foundation' (string) linux.device_file = '/dev/bus/usb/001/001' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'usb' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.1/usb1' (string) usb_device.bus_number = 1 (0x1) (int) usb_device.can_wake_up = true (bool) usb_device.configuration_value = 1 (0x1) (int) usb_device.device_class = 9 (0x9) (int) usb_device.device_protocol = 0 (0x0) (int) usb_device.device_revision_bcd = 518 (0x206) (int) usb_device.device_subclass = 0 (0x0) (int) usb_device.is_self_powered = true (bool) usb_device.linux.device_number = 1 (0x1) (int) usb_device.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.1/usb1' (string) usb_device.max_power = 0 (0x0) (int) usb_device.num_configurations = 1 (0x1) (int) usb_device.num_interfaces = 1 (0x1) (int) usb_device.num_ports = 8 (0x8) (int) usb_device.product = '2.0 root hub' (string) usb_device.product_id = 2 (0x2) (int) usb_device.serial = '0000:00:02.1' (string) usb_device.speed = 480.0 (480) (double) usb_device.vendor = 'Linux Foundation' (string) usb_device.vendor_id = 7531 (0x1d6b) (int) usb_device.version = 2.0 (2) (double) udi = '/org/freedesktop/Hal/devices/usb_device_1307_330_000000000000100' info.linux.driver = 'usb' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_2_0000_00_02_1' (string) info.product = 'Mass Storage Device' (string) info.subsystem = 'usb_device' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_1307_330_000000000000100' (string) info.vendor = 'Transcend Information, Inc.' (string) linux.device_file = '/dev/bus/usb/001/002' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'usb' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.1/usb1/1-1' (string) usb_device.bus_number = 1 (0x1) (int) usb_device.can_wake_up = false (bool) usb_device.configuration_value = 1 (0x1) (int) usb_device.device_class = 0 (0x0) (int) usb_device.device_protocol = 0 (0x0) (int) usb_device.device_revision_bcd = 256 (0x100) (int) usb_device.device_subclass = 0 (0x0) (int) usb_device.is_self_powered = false (bool) usb_device.linux.device_number = 2 (0x2) (int) usb_device.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.1/usb1/1-1' (string) usb_device.max_power = 500 (0x1f4) (int) usb_device.num_configurations = 1 (0x1) (int) usb_device.num_interfaces = 1 (0x1) (int) usb_device.num_ports = 0 (0x0) (int) usb_device.product = 'Mass Storage Device' (string) usb_device.product_id = 816 (0x330) (int) usb_device.serial = '000000000000100' (string) usb_device.speed = 480.0 (480) (double) usb_device.vendor = 'Transcend Information, Inc.' (string) usb_device.vendor_id = 4871 (0x1307) (int) usb_device.version = 2.0 (2) (double) udi = '/org/freedesktop/Hal/devices/usb_device_1307_330_000000000000100_if0' info.linux.driver = 'usb-storage' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_1307_330_000000000000100' (string) info.product = 'USB Mass Storage Interface' (string) info.subsystem = 'usb' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_1307_330_000000000000100_if0' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'usb' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0' (string) usb.bus_number = 1 (0x1) (int) usb.can_wake_up = false (bool) usb.configuration_value = 1 (0x1) (int) usb.device_class = 0 (0x0) (int) usb.device_protocol = 0 (0x0) (int) usb.device_revision_bcd = 256 (0x100) (int) usb.device_subclass = 0 (0x0) (int) usb.interface.class = 8 (0x8) (int) usb.interface.number = 0 (0x0) (int) usb.interface.protocol = 80 (0x50) (int) usb.interface.subclass = 6 (0x6) (int) usb.is_self_powered = false (bool) usb.linux.device_number = 2 (0x2) (int) usb.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.1/usb1/1-1/1-1:1.0' (string) usb.max_power = 500 (0x1f4) (int) usb.num_configurations = 1 (0x1) (int) usb.num_interfaces = 1 (0x1) (int) usb.num_ports = 0 (0x0) (int) usb.product = 'USB Mass Storage Interface' (string) usb.product_id = 816 (0x330) (int) usb.serial = '000000000000100' (string) usb.speed = 480.0 (480) (double) usb.vendor = 'Transcend Information, Inc.' (string) usb.vendor_id = 4871 (0x1307) (int) usb.version = 2.0 (2) (double)
None. usb_device.device_class = 9 (0x9) (int) CCID devices use 0xb. All other devices need a driver from the manufacturer or a complete documentation and a PC/SC familiar person willing to spend days or weeks on this task. I am not aware of any such person.
Me neither. Besides that if i needed the device for such purpose, i probably would have met these shortcomings, and would have looked for a device, or os, that was able to fullfill my needs... But..! I am very glad you shared this info, and like to thank you for it..:) I totaly was not aware of these things....