[Bug 25708] New: Installation problem. update-binfmts: --- Segmentation fault --- start: Job failed to start
http://bugs.winehq.org/show_bug.cgi?id=25708
Summary: Installation problem. update-binfmts: --- Segmentation fault --- start: Job failed to start Product: Wine Version: 1.2.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: gherardo@yahoo.com
Created an attachment (id=32752) --> (http://bugs.winehq.org/attachment.cgi?id=32752) The dpkg log for install and removal
I have an Ubuntu 10.04 with latest fixes. I have used wine without problems for year but a couple weeks ago' it started not working. Even winecfg has problems like this:
winecfg preloader: Warning: failed to reserve range 00010000-00110000 preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 Segmentation fault
After many tentatives I decided to wipe wine and reinstall from scratch. I tried 1.3, 1.2, 1.0 but this is what happens when I try to install Wine:
Selezionato il pacchetto winetricks. Estrazione di winetricks (da .../winetricks_0.0+20101106-0ubuntu1~lucidppa1_i386.deb)... Selezionato il pacchetto wisotool. Estrazione di wisotool (da .../wisotool_0.0+20101106~lucidppa1_i386.deb)... Elaborazione dei trigger per python-gmenu... Rebuilding /usr/share/applications/desktop.it_IT.utf8.cache... Elaborazione dei trigger per desktop-file-utils... Elaborazione dei trigger per man-db... Elaborazione dei trigger per hicolor-icon-theme... Elaborazione dei trigger per python-support... Configurazione di wine1.2 (1.2-1ubuntu1~lucidppa1)... start: Job failed to start start: Job failed to start update-binfmts: warning: current package is wine, but binary format already installed by wine1.0
Configurazione di wine1.2-gecko (1.0.0-0ubuntu4)... Configurazione di winetricks (0.0+20101106-0ubuntu1~lucidppa1)... Configurazione di wisotool (0.0+20101106~lucidppa1)... Elaborazione dei trigger per libc-bin... ldconfig deferred processing now taking place
There is something wrong in the installation that I cannot trace back. BTW, winecfg has the same problem as above and also no other program works. I also have no .wine directory...
If I try to remore wine this is what happens...
Rimozione di wine1.2... update-binfmts: warning: current package is wine, but binary format already installed by wine1.0; not removing. Eliminazione dei file di configurazione di wine1.2... start: Job failed to start Rimozione di wine1.2-gecko... Rimozione di winetricks... Rimozione di wisotool... Elaborazione dei trigger per hicolor-icon-theme... Elaborazione dei trigger per man-db... Elaborazione dei trigger per python-gmenu... Rebuilding /usr/share/applications/desktop.it_IT.utf8.cache... Elaborazione dei trigger per desktop-file-utils... Elaborazione dei trigger per libc-bin... ldconfig deferred processing now taking place Elaborazione dei trigger per python-support...
Attached is the dpkg log.
Thanks, Gherardo
http://bugs.winehq.org/show_bug.cgi?id=25708
gherardo gherardo@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gherardo@yahoo.com
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #1 from gherardo gherardo@yahoo.com 2011-01-07 12:47:44 CST --- I also did run...
dpkg -s wine Package: wine Status: unknown ok not-installed Priority: extra Section: otherosfs
http://bugs.winehq.org/show_bug.cgi?id=25708
Scott Ritchie scott@open-vote.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |scott@open-vote.org
--- Comment #2 from Scott Ritchie scott@open-vote.org 2011-01-07 20:14:59 CST --- The segfault is when you run Wine, correct? It looks like the package is uninstalling/installing cleanly.
The start error is probably on the start procps line, but that doesn't break install of the package. If you want to clean that up you can try just running start procps on a terminal and see what it says -- most likely is that there are unknown things in /etc/sysctl.d somehow, such as invalid commands. I don't know the source of those invalid commands in the conf files but I've seen them before -- it's why the package postinstall script doesn't fail on an error from start procps.
I don't know if procps properly starting is a requirement for Wine to not spew those errors, however.
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #3 from gherardo gherardo@yahoo.com 2011-01-08 09:42:59 CST --- Hi Scott this is the result:
start procps start: Rejected send message, 1 matched rules; type="method_call", sender=":1.54" (uid=1000 pid=2383 comm="start) interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply=0 destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init))
I also tried with sudo:
sudo start procps start: Job failed to start
If it's not an install problem, then I do not undertsand why .wine directory is not created and nothing works, including winecfg.
Let me know if I didn't understand correctly what you asked. Thanks
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #4 from Scott Ritchie scott@open-vote.org 2011-01-08 17:46:54 CST --- The package installed fine in the sense that all the files are there on the system. What you have is a runtime problem.
My first suspicion is cruft left over from old installs...Do you think you could put 10.10 (or 10.04) on a USB stick, boot from that, and install Wine there to retest?
If that works then you may just want to backup and reinstall.
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #5 from gherardo gherardo@yahoo.com 2011-01-09 13:48:35 CST --- Well... backing up and reinstall is HUGE. This is a work machine and would take me at least 3 days of full time work.
Cant' we check what is leftover starting from ... "update-binfmts: warning: current package is wine, but binary format already installed by wine1.0" What should I look for?
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #6 from gherardo gherardo@yahoo.com 2011-01-09 15:16:46 CST --- Another question,,, why I don't have any .wine dir?
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #7 from Scott Ritchie scott@open-vote.org 2011-01-09 18:21:17 CST --- .wine is created after Wine runs...in your case it's crashing before even getting there.
I'm not saying you should backup/reinstall immediately, I'm saying you should test booting off a stick to see if that works. If so we can rule out Wine and you can take your problem to askubuntu.com, which is better help than me.
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #8 from gherardo gherardo@yahoo.com 2011-01-10 01:55:01 CST --- I'm sure on this computer it was working till 2-3 weeks ago' so I guess it would work again from a new installation. I'm almost sure that if I involve Ubuntu they'll say is a wine matter :( and I'll be in the middle. The fact that according to you the installation is fine and winecfg doesn't work, looks to me like a wine problem. For sure is not widespread and for sure is a combination of wine and platform problem. Can't we track down in more details what's happening? Can't we re-run the start that fails checking what is the exact line that fails?
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #9 from gherardo gherardo@yahoo.com 2011-01-18 01:47:58 CST --- Thanks a lot for the support. I moved to a native linux app.
http://bugs.winehq.org/show_bug.cgi?id=25708
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #10 from Austin English austinenglish@gmail.com 2011-01-18 12:10:08 CST --- Probably a packaging bug.
http://bugs.winehq.org/show_bug.cgi?id=25708
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Severity|blocker |normal
--- Comment #11 from Nikolay Sivov bunglehead@gmail.com 2011-01-19 12:48:36 CST --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=25708
gherardo gherardo@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED Resolution|INVALID |FIXED
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #12 from gherardo gherardo@yahoo.com 2011-02-15 01:47:54 CST --- User philnice on ubuntuforum ( http://ubuntuforums.org/showthread.php?p=10459871#post10459871 ) pointed me to the answer.
He found in /var/lib/binfmts a file named "wine". Its content was (for me) the following (without -------):
----------------------- wine1.0 magic 0 MZ
/usr/bin/wine ----------------------- I moved the file elsewhere and a new wine 1.2 installation worked smoothly.
http://bugs.winehq.org/show_bug.cgi?id=25708
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Resolution|FIXED |INVALID
--- Comment #13 from Dmitry Timoshkov dmitry@codeweavers.com 2011-02-15 02:41:29 CST --- Nothing has been fixed in Wine.
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #14 from gherardo gherardo@yahoo.com 2011-02-15 02:46:42 CST --- (In reply to comment #13)
Nothing has been fixed in Wine.
You are correct. This is a workaround. Do you plan anything on the wine code to prevent the problem? If not, where is the problem?
http://bugs.winehq.org/show_bug.cgi?id=25708
--- Comment #15 from Austin English austinenglish@gmail.com 2011-02-15 12:36:37 CST --- (In reply to comment #14)
(In reply to comment #13)
Nothing has been fixed in Wine.
You are correct. This is a workaround. Do you plan anything on the wine code to prevent the problem? If not, where is the problem?
There was nothing in wine to cause that problem, it was done by whomever packaged it.
-
wine-bugs＠winehq.org