http://bugs.winehq.org/show_bug.cgi?id=14108
Summary: wine does not start at all on my clean linux/x86 laptop Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: sick_soul@yahoo.it
Since many wine versions, wine does not run at all on my amilo slackware linux laptop (x86-32bit) anymore.
On another desktop machine (another x86-32 Slackware box, but very different hardware), it works.
After installing wine (on a clean machine, no ~/.wine at all), the first time wine is launched (in this case for winecfg), it says:
"wine: created the configuration directory '/home/claudio/.wine' Could not load Mozilla. HTML rendering will be disabled."
and then it just blocks there. After a very long time I get:
"err:module:attach_process_dlls "winspool.drv" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\windows\system32\winecfg.exe" failed, status c000013a"
and I am at a prompt again. Meanwhile, the wine processes still live, and need to be killed manually (wineserver, wineboot.exe, sevices.exe, explorer.exe).
I thought it would be a good idea to inform you that at least on this machine, wine-1.0.0 does not start at all.
I noticed a somewhat similar bug report, which might or might not be related (at least the effects seem similar), but it's on NetBSD:
http://bugs.winehq.org/show_bug.cgi?id=2366
If you want some more information, I can be very responsive until at least the end of the week.
http://bugs.winehq.org/show_bug.cgi?id=14108
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-25 01:27:52 --- Not critical.
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #2 from Alexandre Julliard julliard@winehq.org 2008-06-25 02:28:54 --- Probably your CUPS setup is broken.
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #3 from Claudio sick_soul@yahoo.it 2008-06-25 06:26:47 --- (In reply to comment #2)
Probably your CUPS setup is broken.
Well in a sense it is, I have no CUPS at all, I do not need it.
I tried starting the cupsd, and indeed this lets wine run again.
Thank you for the workaround, although I still think that wine should run even though cups is not available.
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #4 from Claudio sick_soul@yahoo.it 2008-06-25 06:46:03 --- errata for clarity:
(In reply to comment #3)
(In reply to comment #2)
Probably your CUPS setup is broken.
Well in a sense it is, I have no CUPS at all, I do not need it.
I have cups installed, but I do not start the cupsd, as I do not need it.
I keep the cups package installed for the very rare cases when I do need it.
http://bugs.winehq.org/show_bug.cgi?id=14108
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|wine does not start at all |wine does not start at all |on my clean linux/x86 laptop|if cupsd is not started
--- Comment #5 from Austin English austinenglish@gmail.com 2008-06-25 10:37:13 --- austin@SERVER1:/home/austin$ sudo /etc/init.d/cupsys stop austin@SERVER1:~$ winecfg wine: created the configuration directory '/home/austin/.wine' Could not load Mozilla. HTML rendering will be disabled. wine: configuration in '/home/austin/.wine' has been updated. austin@SERVER1:~$
Works fine here.
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #6 from Lei Zhang thestig@google.com 2008-06-26 12:21:40 --- I have slackware 12, with cups installed but not running, and Wine works just fine.
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #7 from Claudio sick_soul@yahoo.it 2008-06-26 13:39:29 --- (In reply to comment #6)
I have slackware 12, with cups installed but not running, and Wine works just fine.
I think I solved: ip_tables rules, I am not accepting from 127.0.0.1 on the laptop, wine is trying to connect to 127.0.0.1:631 and sees its SYN packets dropped.
You can close this, sorry for the bogus issue report.
http://bugs.winehq.org/show_bug.cgi?id=14108
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #8 from Austin English austinenglish@gmail.com 2008-06-26 14:30:44 --- Invalid then.
http://bugs.winehq.org/show_bug.cgi?id=14108
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-26 21:36:24 --- (In reply to comment #7)
I think I solved: ip_tables rules, I am not accepting from 127.0.0.1 on the laptop, wine is trying to connect to 127.0.0.1:631 and sees its SYN packets dropped.
It's not Wine, it's cups which is doing that.
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #10 from Claudio sick_soul@yahoo.it 2008-06-27 06:18:49 --- (In reply to comment #9)
(In reply to comment #7)
I think I solved: ip_tables rules, I am not accepting from 127.0.0.1 on the laptop, wine is trying to connect to 127.0.0.1:631 and sees its SYN packets dropped.
It's not Wine, it's cups which is doing that.
It is not, no cups is running. Here's winecfg buzzing while sending SYN to 127.0.0.1:631 and blocking since its packets are dropped:
$ strace -e trace=connect winecfg [...] connect(10, {sa_family=AF_INET, sin_port=htons(631), sin_addr=inet_addr("127.0.0.1")}, 16
(other terminal): $ netstat -anc --programs | grep -e tcp -e udp
tcp 0 1 127.0.0.1:60902 127.0.0.1:631 SYN_SENT 1610/winecfg.exe
(other terminal): # while true; do iptables --list -v -n |grep INPUT; sleep 1; done Chain INPUT (policy DROP 16 packets, 960 bytes) Chain INPUT (policy DROP 17 packets, 1020 bytes) [...]
http://bugs.winehq.org/show_bug.cgi?id=14108
--- Comment #11 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-27 06:25:27 --- (In reply to comment #10)
It is not, no cups is running. Here's winecfg buzzing while sending SYN to 127.0.0.1:631 and blocking since its packets are dropped:
You are confusing cupsd and a cups client library. Wine is using the latter one, and that one communicates with cupsd via a socket at 127.0.0.1:631.