Author Topic: WINE not running at all in a clean 2010 KDE install (multiple machines)  (Read 969 times)

Offline wyolincoln

  • Jr. Member
  • **
  • Posts: 27
Have been a PCLOS user since 2004. Pre "Big Daddy" I believe...  ;D Thanks for another great release. Been patiently waiting for this one. It is worth the wait.
On that note, after a clean install of 2010 KDE, (latest kernel) I used Synaptic, did a "Reload", searched for "WINE" and waited for the download and install process to complete.
I then selected "Wine Configurator" from the main menu, and here is what happens:
A small window (Wine) tries to display, then immediately I get an error window on top of that.
This process continues until I hard reboot the machine.
I have let the process run just to see how many windows it would try to build, and once it quit at the 96th instance.)
This tells me I need to get out more among many things.  :o
I have tried using the ProcMon to kill it, but it keeps perpetually making new windows faster than I can kill them.
I also tried killing the window/process with the Ctrl-Alt-Esc death skull sequence. No joy there.  ???
CPU usage goes through the roof and I am unable to do anything else with the computer after I start Wine.
I have tried running Wine from a Konsole and get the same problem.
Have also tried all the other options in the Wine menu, and as soon as the "primary" Wine window tries to launch,
this perpetual window creation problem occurs and another reboot is in my immediate future.

BTW, it should be noted this happens on three different computers...
Here are the hardware specs of the machine I would really like to get working:

Latest Kernel (Clean PCLOS 2010 KDE CD Install, including reformatting all partitions.)
Dell Precision 330 Server
(corrected)
1.2 Ghz processor
1 Gig RAM
32 Meg Video RAM

Let me know if there any commands I can run or if I need to run an older version of Wine, or if
after searching the Forum as I already have, I just plain missed something...
I have been known to not only be the master of the obvious, but to miss the obvious as well.

Just looking for some guidance.

Thanks,
Wyo
    
« Last Edit: April 28, 2010, 03:27:10 PM by wyolincoln »
"Mistakes happen. Others will be blamed."
Paul Perves

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15310
  • ┌∩┐(◕_◕)┌∩┐
Hi wyolincoln

Quote
1.2 Ghz processor
1 Meg RAM
4 MEg Video RAM

Can you confirm those specs please.
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline wyolincoln

  • Jr. Member
  • **
  • Posts: 27
My bad.
In a hurry.

1.2 Ghz Processor
32 Meg Video RAM
1 Gig RAM

Also tried a complete removal and reinstall.
No joy.

TL
« Last Edit: April 28, 2010, 03:46:34 PM by wyolincoln »
"Mistakes happen. Others will be blamed."
Paul Perves

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3995
So, don't keep us in suspense! What does the error window say?

I get one saying it can't find a gecko application, but it goes away when I click cancel and behaves nicely.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline wyolincoln

  • Jr. Member
  • **
  • Posts: 27
I wish I could tell you. There is nothing displayed in the primary display area of the window
and the only text that appears is in the title bar that simply says, "Program Error".
Not exactly helpful.  >:(

Wyo
"Mistakes happen. Others will be blamed."
Paul Perves

Offline corazon

  • Full Member
  • ***
  • Posts: 133
I wish I could tell you. There is nothing displayed in the primary display area of the window
and the only text that appears is in the title bar that simply says, "Program Error".
Not exactly helpful.  >:(

Wyo
Hi, I would prepare to reinstall the OS, creating a separate /home partition if you don't have one. Backup /home data if needed,
and configure synaptic to save rpms in the cache. There are a bunch of wine dependencies, you can uninstall them, after
uninstalling wine and libwine, reboot, and reinstall only wine and libwine, no wine helper apps. Hopefully the flaw resides in a dependency that went rogue. If this fails, uninstall the works again, and get suse, fedora, or mandriva wine/libwine rpms that are
older than the one that won't work for you. If those also fail, reinstall the OS, wine works fine for me on minime-kde, no helper apps, athlon processor, nvidia graphics, maudio sound, and extra msoft and webcore fonts. Consider a using a different pclos than what you have, you can fill in the gaps later, or delete unused apps.
Cheers

Offline corazon

  • Full Member
  • ***
  • Posts: 133
here are most of the wine dependencies, once prepared to safely reinstall,
the fun begins  :)

libGL libGLU libICE libSM libXext libXrender gnutis freetype libexif libpthread libgphoto libresolv

If one says synaptic will need to uninstall the whole farm, move on to the next one.
Cheers

Offline wyolincoln

  • Jr. Member
  • **
  • Posts: 27
Thanks for the list of dependencies and the response.
This is what makes PCLinuxOS so grand. People willing to help others.
 
Some time in the near future I will give the dependency thing a shot first,
if that fails, I will try an older version of Wine... The older version ran flawlessly
on these boxes, so that could be the real issue.

Bests,
Wyo
"Mistakes happen. Others will be blamed."
Paul Perves

Offline corazon

  • Full Member
  • ***
  • Posts: 133
Thanks for the list of dependencies and the response.
This is what makes PCLinuxOS so grand. People willing to help others.
 
Some time in the near future I will give the dependency thing a shot first,
if that fails, I will try an older version of Wine... The older version ran flawlessly
on these boxes, so that could be the real issue.

Bests,
Wyo
Hi, I always have synaptic save rpms in the cache, and burn them to cd/dvd. This has helped
a few when fast-moving projects like wine, or apps using codecs that are in perpetual flux,
have an issue, and I now have enough to fill out specialized mini distros if needed, like
a kde3.5.10 just for creating and printing business documents. It dawned on me that by
uninstalling and reinstalling favourite apps that are system
defaults, I can harvest the rpms without needing to extract from an iso, or fetch them from a repository.
I need all the luck I can get  ;)

synaptic-->settings-->preferences-->files-->leave all downloaded files in cache
Cheers

Offline wyolincoln

  • Jr. Member
  • **
  • Posts: 27
Excellent advise.
I have been using "remasterme" to take occasional "snapshots" of my installs when I get things how I like them.
But, I can see where having certain packages available on disc would be very helpful.

Cheers,
Wyo
"Mistakes happen. Others will be blamed."
Paul Perves