Bugzilla – Bug 231247
printer setup of yast ends in an endless loop
Last modified: 2007-01-04 08:33:30 UTC
adding a second printer, using yast (ncurses or gui mode) never terminates. the process y2base consumes all cpu power and never terminates, for example cat /proc/7781/cmdline delivers /usr/lib/YaST2/bin/y2basemenuncurses--nothreads top - 11:53:41 up 1:39, 7 users, load average: 1.33, 1.33, 1.22 Tasks: 141 total, 5 running, 134 sleeping, 1 stopped, 1 zombie Cpu(s): 60.5%us, 39.2%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.3%hi, 0.0%si, 0.0%st Mem: 1036016k total, 886408k used, 149608k free, 83572k buffers Swap: 2104504k total, 0k used, 2104504k free, 456504k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7781 root 18 0 69316 32m 10m S 99.7 3.2 24:45.76 y2base 1 root 15 0 744 288 240 S 0.0 0.0 0:01.11 init YaST @ HUH Mit F1 kommen Sie zur Hilfe ┌──────────────────────────┐ Druckerkonfiguration wird initialisiert │Werkzeug für │ │Druckerkonfiguration │ │Sie können die │ [x] Umgebung prüfen │Einstellungen für die │ [x] Firewall-Einstellungen einlesen │Drucker im System ändern. │ => Druckerdatenbank überprüfen │Es können lokale Drucker │ - Aktuelle Einstellungen laden │und Netzwerkdrucker │ - Drucker erkennen │konfiguriert werden. │ │ │ │ │ │ │ │ ┌───────────────────────────────────────────────────┐ │ │Die Liste der installierten Treiber wurde geändert.│ │ │Die Treiberdatenbank wird aufgebaut... │ │ │ 4% │ │ └───────────────────────────────────────────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ Druckerdatenbank überprüfen... │ │ 40% │ │ │ │ └──────────────────────────┘ [Zurück] [Abbrechen]
Can you please attach y2logs. If you are in doubt please follow: en.opensuse.org/Bugs/YaST. Thanks!
the end less loop is caused by a printer on the first parallel port. the y2log gets the following lines at the end: 2007-01-02 17:13:36 <1> HUH(4750) [YCP] NetworkDevices.ycp:505 config=$["BROADCAST":"127.255.255.255", "IPADDR":"127.0.0.1", "NETMASK":"255.0.0.0", "NETWORK":"127.0.0.0", "STARTMODE":"onboot", "USERCONTROL":"no"] 2007-01-02 17:13:36 <1> HUH(4750) [YCP] SuSEFirewall.ycp:1163 Firewall init scripts are enabled 2007-01-02 17:13:36 <1> HUH(4750) [YCP] SuSEFirewall.ycp:1188 Firewall services are started 2007-01-02 17:13:36 <1> HUH(4750) [YCP] SuSEFirewall.ycp:1951 Possibly conflicting services found allowed: $["DMZ":[], "EXT":[]] 2007-01-02 17:13:36 <1> HUH(4750) [YCP] SuSEFirewall.ycp:2048 Firewall configuration has been read: $["FW_ALLOW_FW_BROADCAST_DMZ":"no", "FW_ALLOW_FW_BROADCAST_EXT":"no", "FW_ALLOW_FW_BROADCAST_INT":"no", "FW_DEV_DMZ":"", "FW_DEV_EXT":"any dsl0", "FW_DEV_INT":"eth-id-00:0d:61:a7:94:9a", "FW_FORWARD_ALWAYS_INOUT_DEV":"", "FW_FORWARD_MASQ":"", "FW_IGNORE_FW_BROADCAST_DMZ":"no", "FW_IGNORE_FW_BROADCAST_EXT":"yes", "FW_IGNORE_FW_BROADCAST_INT":"no", "FW_IPSEC_TRUST":"no", "FW_LOG_ACCEPT_ALL":"no", "FW_LOG_ACCEPT_CRIT":"yes", "FW_LOG_DROP_ALL":"no", "FW_LOG_DROP_CRIT":"yes", "FW_MASQUERADE":"no", "FW_PROTECT_FROM_INT":"no", "FW_ROUTE":"no", "FW_SERVICES_ACCEPT_DMZ":"", "FW_SERVICES_ACCEPT_EXT":"", "FW_SERVICES_ACCEPT_INT":"", "FW_SERVICES_DMZ_IP":"", "FW_SERVICES_DMZ_RPC":"", "FW_SERVICES_DMZ_TCP":"", "FW_SERVICES_DMZ_UDP":"", "FW_SERVICES_EXT_IP":"", "FW_SERVICES_EXT_RPC":"", "FW_SERVICES_EXT_TCP":"smtp ssh", "FW_SERVICES_EXT_UDP":"", "FW_SERVICES_INT_IP":"", "FW_SERVICES_INT_RPC":"", "FW_SERVICES_INT_TCP":"smtp", "FW_SERVICES_INT_UDP":"", "enable_firewall":true, "start_firewall":true]. 2007-01-02 17:13:37 <1> HUH(4750) [YCP] Printerdb.ycp:340 Checking foomatic database 2007-01-02 17:13:37 <1> HUH(4750) [YCP] Printerdb.ycp:343 Database changed 2007-01-02 17:13:37 <1> HUH(4750) [agent-ppd] PPDdb.cc(createdbThread):419 CreateDbThread started 2007-01-02 17:13:39 <1> HUH(4750) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1439 Database file parsed correctly by YCP parser 2007-01-02 17:13:39 <1> HUH(4750) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1670 Database contents is OK
workarround: delete /var/lib/YaST2/ppd_db.ycp *** This bug has been marked as a duplicate of bug 229231 ***