LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 12-26-2016, 06:55 AM   #1
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Rep: Reputation: 4
debian 8.1 won't install wine-devel due to unmet dependencies


Background: I need to be able to run TomTom Home in order to update the TomTom XL navigator. I used to use my wife's Win 7 machine, but Win 7 died with unrecoverable errors. It didn't take much persuasion to convince my wife to switch to linux (in her case Ubuntu 16.04). TomTom Home doesn't have a Lunux version, however. I find that a bit rude, but that's unfortunately the way it is.

The logical solution, when you don't have a Win machine, is to try installing the required software with wine. I'm not too keen to dabble with the Ubuntu O/S if I can avoid it. So I'd like to do this with Debian Jessie 8.6 (that's what I use on my laptop). Using the stable packages I get wine 1.6.20. This allows TomTom Home to install, but it won't run. It just results in a meaningless "An error occurred" message.

So I checked the WineHQ Site and found that TTH will run OK (bronze rating) with wine 1.7.42 or better.

After scouring some forums I somewhat naiively added two new files to my /etc/apt/sources.list.d:
Code:
:/etc/apt/sources.list.d$ cat wine.list.jessie 
deb https://dl.winehq.org/wine-builds/debian/ jessie main

:/etc/apt/sources.list.d$ cat wine.list.stretch 
deb https://dl.winehq.org/wine-builds/debian/ stretch main
After firing up synaptic I noticed that the wine version had not changed. However, there were now a number of winehq packages like wine-devel 2.0-rc2-stretch. These are development versions and not the latest stable release, as I understand it. But the latest stable release is not listed under Synaptic.

Working on the assumption that the development package might just be what I need, I tried installing it. That is when I get unmet dependencies. In this case I used aptitude, because it gives slightly better diagnostic messages:
Code:
:/etc/apt/sources.list.d$ aptitude install wine-devel
The following NEW packages will be installed:
  libcapi20-3{a} libcapi20-3:i386{a} libexif12:i386{a} libgd3:i386{a} libgphoto2-6:i386{a} libgphoto2-port10:i386{a} 
  libgphoto2-port12{a} libgphoto2-port12:i386{a} libieee1284-3:i386{a} libltdl7:i386{a} libodbc1:i386{a} libosmesa6{a} 
  libosmesa6:i386{a} libpcap0.8:i386{a} libsane:i386{a} libsane-extras:i386{a} libusb-1.0-0:i386{a} libv4l-0:i386{a} 
  libv4lconvert0:i386{a} libxcomposite1:i386{a} libxinerama1:i386{a} libxpm4:i386{a} libxrandr2:i386{a} libxslt1.1:i386{a} wine-devel 
  wine-devel-amd64{ab} wine-devel-i386:i386{ab} 
0 packages upgraded, 27 newly installed, 0 to remove and 67 not upgraded.
Need to get 47.5 MB of archives. After unpacking 398 MB will be used.
The following packages have unmet dependencies:
 wine-devel-i386:i386 : Depends: libc6:i386 (>= 2.23) but 2.19-18+deb8u6 is installed.
                        Depends: libgphoto2-6:i386 (>= 2.5.10) but 2.5.4-1.1+b2 is to be installed.
 wine-devel-amd64 : Depends: libc6 (>= 2.23) but 2.19-18+deb8u6 is installed.
                    Depends: libgphoto2-6 (>= 2.5.10) but 2.5.4-1.1+b2 is installed.
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     wine-devel [Not Installed]                         
2)     wine-devel-amd64 [Not Installed]                   
3)     wine-devel-i386:i386 [Not Installed]
The suggestion from aptitude as to how this might be resolved is less than helpful.

I'm not at all sure that I'm going the right way about this. Can anybody set me straight? I really do need to update the navigator soon and wineseems to be my only option.
 
Old 12-26-2016, 07:24 AM   #2
snowday
Senior Member
 
Registered: Feb 2009
Posts: 4,667

Rep: Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409
Code:
:/etc/apt/sources.list.d$ cat wine.list.jessie 
deb https://dl.winehq.org/wine-builds/debian/ jessie main

:/etc/apt/sources.list.d$ cat wine.list.stretch 
deb https://dl.winehq.org/wine-builds/debian/ stretch main
You are running Debian "Jessie" so the packages from Debian "Stretch" repository are not compatible with your system. You should probably delete /etc/apt/sources.list.d/wine.list.stretch immediately.

However, there may be a better way! (I haven't tried it personally, I'm not a Debian user, but I trust their wiki.)

https://wiki.debian.org/Wine

According to the wiki:

Quote:
Since Debian Jessie you can choose between two sets of Wine packages: wine and wine-development.

wine tracks the stable releases from winehq.org (e.g. version 1.6.2), and wine-development the development releases (e.g. version 1.7.29).

Despite its name wine-development is also intended to be used by regular users. Do not mix this up with the *-dev packages which contain the header files and development libraries.

You can either install both sets at the same time, or only one of them.
It may be that 1.7.29 is new enough for "tom tom" to run as Bronze status (i.e. the app will run, but not all features will work). If you need newer still, then you can use "jessie-backports" repository to get even newer (1.8.5 or thereabouts at the time of this writing). The packages are called 'wine32' (32-bit version) or 'wine64' (64-bit version).

'wine-devel' isn't what you need at all, so don't waste your time (or risk your system's stability) installing it.

Last edited by snowday; 12-26-2016 at 07:33 AM.
 
Old 12-26-2016, 12:27 PM   #3
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Thanks for the response, snowpine.

I did as you suggested and removed the directory /etc/apt/sources.list.d. Thereafter I checked the status in synaptic. Sure enough There promptly appeared a new wine-development 1.7.29 package. All the stretch packages have disappeared (as one would expect). The wine package itself had the same old version number. I installed the new package, which also caused wine64-development 1.7.29 to be installed (amongst others), without installing the wine package. But it hasn't helped. In fact I cannot run, reinstall, or uninstall TomTom Home 2. When I try the wait symbol (I call it the washing machine) rotates away for a bout 15 seconds and then... nothing happens.

Checking in /var/log/syslog only revealed one relevant message:
Code:
Dec 26 19:43:03 ascomtux /etc/gdm3/Xsession[2179]: env: wine: No such file or directory
This suggests that I need the base wine package as well, but I'm not going to experiment any further tonight.

I do have jessie backports in my sources.list, so there should be some way to get an even newer version if I understand you correctly. Firstly, I will check out the link you sent and see if that tells me anything new.

I'll post the results of any further attempts... whether they succeed or not.
 
Old 12-27-2016, 07:04 AM   #4
snowday
Senior Member
 
Registered: Feb 2009
Posts: 4,667

Rep: Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409
Quote:
Originally Posted by achim_59 View Post
I did as you suggested and removed the directory /etc/apt/sources.list.d.
No no no no no! I hope you did not delete the entire folder /etc/apt/sources.list.d !!

It was only the one file /etc/apt/sources.list.d/wine.list.stretch that was incompatible with your Jessie system.

I apologize if my advice was confusing or misleading. Do you have backups? Or do you remember what else was in that folder?

Last edited by snowday; 12-27-2016 at 07:08 AM.
 
Old 12-28-2016, 01:42 AM   #5
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
I'm the one who should apologise.

Sorry, apparently I was more tired than I realised when I wrote that. deleting /etc/apt/sources.list.d would, of course, be nonsense. I did a copy/paste when I wrote that and didn't look too closely at what I was copying. Really, I'm very sorry to have caused you so much bother. I only deleted the file wine.list.stretch as you recommended.

I have to work some long hours this week and, therefore, I won't have time before the weekend to really tinker any further with the problem. I'll report back when I've tried some other combinations. Again, I'm really sorry about that.

How embarrassing!
 
1 members found this post helpful.
Old 12-28-2016, 01:33 PM   #6
snowday
Senior Member
 
Registered: Feb 2009
Posts: 4,667

Rep: Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409
That is a relief.
 
Old 01-01-2017, 01:21 PM   #7
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Wine 1.7.29 doesn't work either

It wasn't initially clear to me why trying to open TTH with wine wasn't doing anything. After checking some configuration files and looking at the command that was executed when TTH was run, it was obvious that a nonexistent wine was being run, and not the wine-development script. I changed that and tried reinstalling TTH. The installation ran as before, but when the app was launched the same meaningless error message as before appeared. This time I had first initiated a trace on /var/log/syslog which revealed the following:
Code:
Jan  1 20:23:08 ascomtux /etc/gdm3/Xsession[2237]: wine: Call from 0x7b839c9c to unimplemented function KERNEL32.dll.SetVolumeMountPointW, aborting
Jan  1 20:23:08 ascomtux /etc/gdm3/Xsession[2237]: wine: Unimplemented function KERNEL32.dll.SetVolumeMountPointW called at address 0x7b839c9c (thread 0063), starting debugger...
Jan  1 20:23:10 ascomtux /etc/gdm3/Xsession[2237]: wine: Call from 0x7b839c9c to unimplemented function KERNEL32.dll.SetVolumeMountPointW, aborting
Jan  1 20:23:10 ascomtux /etc/gdm3/Xsession[2237]: wine: Unimplemented function KERNEL32.dll.SetVolumeMountPointW called at address 0x7b839c9c (thread 007e), starting debugger...
Jan  1 20:24:37 ascomtux /etc/gdm3/Xsession[2237]: fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
Jan  1 20:24:37 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: meta_display_register_x_window: assertion 'g_hash_table_lookup (display->window_ids, xwindowp) == NULL' failed
Jan  1 20:25:55 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: Source ID 6047 was not found when attempting to remove it
Jan  1 20:25:57 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: Source ID 6058 was not found when attempting to remove it
Jan  1 20:26:01 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: Source ID 6076 was not found when attempting to remove it
Jan  1 20:26:03 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: Source ID 6081 was not found when attempting to remove it
Jan  1 20:26:07 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: Source ID 6192 was not found when attempting to remove it
Jan  1 20:27:36 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: Source ID 6458 was not found when attempting to remove it
Jan  1 20:28:02 ascomtux /etc/gdm3/Xsession[2237]: Window manager warning: Log level 8: meta_display_unregister_x_window: assertion 'g_hash_table_lookup (display->window_ids, &xwindow) != NULL' failed
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Unhandled exception: unimplemented function KERNEL32.dll.SetVolumeMountPointW called in 32-bit code (0x7b839c9c).
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Register dump:
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: CS:0023 SS:002b DS:002b ES:002b FS:006b GS:0063
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: EIP:7b839c9c ESP:0033f134 EBP:0033f1b8 EFLAGS:00000212(   - --  I   -A- - )
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: EAX:7b826d81 EBX:7b8b1dcc ECX:0033f160 EDX:0033f1e0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ESI:00000004 EDI:7b87edc0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Stack dump:
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x0033f134:  00000000 00440014 62739500 00134338
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x0033f144:  7bc4e1f6 0033f170 80000100 00000001
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x0033f154:  00000000 7b839c9c 00000002 7b87edc0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x0033f164:  7b87f5df 0033f2f0 7f5e3072 0033f190
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x0033f174:  7f5c8082 0033f2ec 7bcc3c98 7f4b6799
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x0033f184:  7f521e50 7f629f50 0033f2ec 0033f1d0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Backtrace:
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: =>0 0x7b839c9c in kernel32 (+0x29c9c) (0x0033f1b8)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 1 0x7b87ea77 in kernel32 (+0x6ea76) (0x0033f1f4)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 2 0x7b820d25 in kernel32 (+0x10d24) (0x0033f30c)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 3 0x00410141 in tomtomhomerunner (+0x10140) (0x0033f30c)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 4 0x0033f4c0 (0x00442858)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 5 0x005c003f (0x005c005c)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0x7b839c9c: addl#011$12,%esp
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Modules:
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Module#011Address#011#011#011Debug info#011Name (58 modules)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: PE#011  400000-  43c000#011Export          tomtomhomerunner
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117b800000-7ba58000#011Dwarf           kernel32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117b810000-7ba58000#011\               kernel32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117bc00000-7bce1000#011Deferred        ntdll<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117bc10000-7bce1000#011\               ntdll
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117bf00000-7bf04000#011Deferred        <wine-loader>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117eddc000-7ee00000#011Deferred        imm32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117ede0000-7ee00000#011\               imm32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efa8000-7efaf000#011Deferred        libxfixes.so.3
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efaf000-7efbb000#011Deferred        libxcursor.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efbb000-7efce000#011Deferred        libxi.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efce000-7efda000#011Deferred        libxrender.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efda000-7efe1000#011Deferred        libxxf86vm.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efe1000-7efe7000#011Deferred        libxdmcp.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efe7000-7efeb000#011Deferred        libxau.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117efeb000-7f011000#011Deferred        libxcb.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f011000-7f163000#011Deferred        libx11.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f163000-7f178000#011Deferred        libxext.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f19b000-7f229000#011Deferred        winex11<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f1b0000-7f229000#011\               winex11
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f2e6000-7f30f000#011Deferred        libexpat.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f30f000-7f352000#011Deferred        libfontconfig.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f352000-7f37f000#011Deferred        libpng12.so.0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f37f000-7f39c000#011Deferred        libz.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f39c000-7f44e000#011Deferred        libfreetype.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f471000-7f52e000#011Deferred        msvcr80<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f490000-7f52e000#011\               msvcr80
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f52e000-7f66b000#011Deferred        msvcp80<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f570000-7f66b000#011\               msvcp80
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f66b000-7f6d7000#011Deferred        setupapi<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f680000-7f6d7000#011\               setupapi
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f6d7000-7f755000#011Deferred        rpcrt4<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f6e0000-7f755000#011\               rpcrt4
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f755000-7f887000#011Deferred        ole32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f770000-7f887000#011\               ole32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f887000-7f8fe000#011Deferred        shlwapi<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f890000-7f8fe000#011\               shlwapi
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117f8fe000-7fb2a000#011Deferred        shell32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117f910000-7fb2a000#011\               shell32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fb2a000-7fb99000#011Deferred        advapi32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117fb40000-7fb99000#011\               advapi32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fb99000-7fcb3000#011Deferred        gdi32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117fbb0000-7fcb3000#011\               gdi32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fcb3000-7fe02000#011Deferred        user32<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117fcd0000-7fe02000#011\               user32
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fe02000-7fe0f000#011Deferred        libnss_files.so.2
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fe0f000-7fe1b000#011Deferred        libnss_nis.so.2
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fe1b000-7fe34000#011Deferred        libnsl.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#0117fe3e000-7fe57000#011Deferred        version<elf>
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: \-PE#0117fe40000-7fe57000#011\               version
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f73e2000-f7428000#011Deferred        libm.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f7428000-f742d000#011Deferred        libdl.so.2
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f742d000-f75da000#011Deferred        libc.so.6
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f75db000-f75f7000#011Deferred        libpthread.so.0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f7611000-f761a000#011Deferred        libnss_compat.so.2
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f761a000-f77d1000#011Dwarf           libwine.so.1
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f77d3000-f77d4000#011Deferred        [vdso].so
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: ELF#011f77d6000-f77f7000#011Deferred        ld-linux.so.2
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: Threads:
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: process  tid      prio (all id:s are in hex)
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000000e services.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000083    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000054    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000001c    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000014    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000010    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000000f    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000012 winedevice.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000001b    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000018    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000017    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000013    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000019 plugplay.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000001f    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000001e    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000001a    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000003f explorer.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000040    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000052 TomTomHOMEService.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000059    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000058    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000057    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000053    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000062 (D) C:\Program Files\TomTom HOME 2\TomTomHOMERunner.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000066    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000065    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000064    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000063    0 <==
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000067 rpcss.exe
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000069    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000068    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000005c    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000050    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000004a    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 00000049    0
Jan  1 20:30:51 ascomtux /etc/gdm3/Xsession[2237]: 0000002a    0
The backtrace data from the error shows something very similar. I've placed that in the attached text file. I'm not entirely sure, but it would seem to suggest, that I do need a newer version of wine than the 1.7.29 that I get from wine-development. The link that snowpine sent suggests using a 1.9.x version available from jessie-backports. Since I've already got that repository in my sources.list, I'll have to figure out how to install it, since synaptic doesn't show it. It will probably require using apt-get or apptitude.

I've run out of time for this weekend, but I might find time to try a few things in a day or two. Time to sleep before I do something silly again.

If anybody is hanging out for a solution to the problem, because they've got Win software they can't get running on their Linux machine, I can only tell you to be patient. Or maybe you can figure it out first and tell me how to do it...
Attached Files
File Type: txt tomtom_home_backtrace.txt (8.2 KB, 17 views)
 
Old 01-03-2017, 08:45 AM   #8
snowday
Senior Member
 
Registered: Feb 2009
Posts: 4,667

Rep: Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409
I believe that the wine packages from Jessie Backports repository are called 'wine32' (32-bit version) or 'wine64' (64-bit version).
 
Old 02-12-2017, 09:09 AM   #9
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Backports cause broken packages?

I'm really sorry it has taken me so long to get back to this problem. Two weeks ago I decided to make a concerted effort.

The wine64 command isn't required, after all. Apparently wine figures out for itself which version is required. Both wine and win64 packages installed on my machine.

I read up on how to install backport versions of packages in the Debian Admin Handbook. Here's what happened:
Code:
root@ascomtux:/etc/apt/sources.list.d# apt-get upgrade -t jessie-backports wine
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libegl1-mesa-drivers : Depends: libglapi-mesa (= 10.3.2-1+deb8u1) but 12.0.4-2~bpo8+1 is to be installed
 libgl1-mesa-glx : Depends: libglapi-mesa (= 10.3.2-1+deb8u1) but 12.0.4-2~bpo8+1 is to be installed
 libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.3.2-1+deb8u1) but 12.0.4-2~bpo8+1 is to be installed
E: Broken packages
That last message made my stomach turn. The last time I had something like that, it took weeks of working at it night after night. Back then I was living in hotels Mon - Fri so it wasn't so bad. Nowadays I don't have that sort of free time. Needles to say, I was fairly depressed about it.

Still, it would seem that there aren't any broken packages yet, just that the intended upgrade would cause them. I've done updates since and there's nothing amiss. Synaptic also doesn't show anything broken.

If I read those messages correctly, then I have three packages that have version 10.3.2-1-deb8u1. Each of these would need to be replaced with a newer version (12.0.4-2~bpo8+1), which would be obtained from jessie/backports. I could do that manually, I guess by upgrading the packages individually. If I use the apt-get -f option I should get the same result... but I'm not certain.

If nobody replies with admonitions like "Don't do it!" I'll give it a go this week, assuming I find the time.

I'll post again when I've taken the leap and installed the stuff. Hopefully nothing will break.

Last edited by achim_59; 02-12-2017 at 09:11 AM. Reason: grammar
 
Old 02-12-2017, 09:31 AM   #10
hydrurga
LQ Guru
 
Registered: Nov 2008
Location: Pictland
Distribution: Linux Mint 20 MATE
Posts: 8,048
Blog Entries: 5

Rep: Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916Reputation: 2916
I'm not an expert on unravelling dependencies but I have a few notes:

(i) Check your list of existing repos before anything else (inxi -r is a useful command to list all your repos if you have inxi installed) and always run apt-get update before any other apt or apt-get command. I'm sorry that this is obvious but I should include it for anyone else reading.

(ii) Your upgrade command doesn't do what you think it does. apt-get upgrade always upgrades all packages that need upgrading (unless they're held back) - you can't use it to upgrade a single package. If you want to do that, use apt-get install package - if there is a newer version available in the repos then you will be prompted to upgrade to that version.

(iii) You should possibly throw an apt-get check at your current system to see if there are any existing dependency problems.

(iv) For most apt-get commands, you can include an -s option to run the command as a simulation - it will show you what would be changed if the command were to run but won't actually do it. Can prove pretty useful.
 
Old 02-12-2017, 09:33 AM   #11
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 4,137
Blog Entries: 1

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
What's your apt-get sources.list look like? Here's mine without backports.

Code:
deb http://security.debian.org           jessie/updates  main contrib non-free
deb http://ftp.us.debian.org/debian   jessie          main contrib non-free
deb http://ftp.us.debian.org/debian   jessie-updates  main contrib non-free
deb-src http://ftp.us.debian.org/debian  jessie          main contrib non-free
deb-src http://ftp.us.debian.org/debian  jessie-updates  main contrib non-free
 
Old 02-12-2017, 01:41 PM   #12
snowday
Senior Member
 
Registered: Feb 2009
Posts: 4,667

Rep: Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409Reputation: 1409
The problem could be as simple as your system is not up to date. I'd be curious to know the output of:

Code:
apt-get update
apt-get -s dist-upgrade
The -s flag stands for "simulate" so it won't make any changes to your system. If you are satisfied with the output (and do feel free to post it here, if you want a second set of eyes), then you can proceed with the changes by running the command again without the -s:

Code:
apt-get update
apt-get dist-upgrade
 
1 members found this post helpful.
Old 02-12-2017, 01:44 PM   #13
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, EndeavourOS
Posts: 3,661
Blog Entries: 7

Rep: Reputation: 1296Reputation: 1296Reputation: 1296Reputation: 1296Reputation: 1296Reputation: 1296Reputation: 1296Reputation: 1296Reputation: 1296
Quote:
Originally Posted by snowpine View Post
The problem could be as simple as your system is not up to date. I'd be curious to know the output of:

Code:
apt-get update
apt-get -s dist-upgrade
The -s flag stands for "simulate" so it won't make any changes to your system. If you are satisfied with the output (and do feel free to post it here, if you want a second set of eyes), then you can proceed with the changes by running the command again without the -s:

Code:
apt-get update
apt-get dist-upgrade
That's my first thought assuming it actually is still 8.1 (and not upgraded to 8.whateveriscurrent).
 
Old 02-12-2017, 02:01 PM   #14
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
@hydrurga:
  1. Thanks for the tip about inxi. I wasn't aware of it. Of course you are right - I did do an update first (with synaptic as it happens) and that's good advice for others.
  2. Oooops! guess I wasn't concentrating when I did that. Thanks for pointing out my blunder. I meant to do an install. Good thing that it didn't work, I guess.
  3. Dependency problems are shown when you do the update anyway, and no changes result. However, thanks for telling me about apt-get check.
  4. The simulation option is one I sort of knew about, but somehow forget every time I do this sort of thing (like once in blue moon). Thanks for the reminder.

@Shadow_7:
My sources.list is a bit different, since I use extra files in sources.list.d depending on what 3rd party external packages I'm currently using.
sources.list:
Code:
deb http://security.debian.org/ jessie/updates main contrib
deb-src http://security.debian.org/ jessie/updates main contrib

deb http://ftp.de.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.de.debian.org/debian/ jessie main contrib non-free

deb http://ftp.de.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.de.debian.org/debian/ jessie-updates main contrib non-free

deb http://ftp.de.debian.org/debian jessie-backports main contrib non-free
deb-src http://ftp.de.debian.org/debian jessie-backports main contrib non-free
In sources.list.d I currently only have one active list -
solaar.list:
Code:
deb http://pwr.github.io/Solaar/packages/ ./
deb-src http://pwr.github.io/Solaar/packages/ ./
 
Old 05-25-2017, 01:27 PM   #15
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
An unsatisfying solution

I've finally found the time to get back to the TomTom problem. I checked my debian admin handbook to make sure I was doing it right (for a change) and did the following:
Code:
apt-get update
apt-get upgrade
apt-get dist-upgrade
apt-get --reinstall -install -t jessie-backports wine64-development
apt-get --reinstall -install -t jessie-backports wine-development
This all worked as expected and subsequently I was able to reinstall TomTom Home and start it.

I then connected my TomTom XL. The software failed to detect the device. I have it installed with the option to start TomTom Home as soon as the device is connected, so I tried it that way, but TomTom Home did not start when I connected the TomTom XL. This is apparently the current state of the wine software. I checked the Wine Application DB (you need to register) and nobody seems to have achieved device detection.

I wonder if there is some way to force TomTom Home to recognise the device? My system certainly does. Checking /var/log/syslog revealed:
Code:
May 25 20:31:13 ascomtux kernel: [171722.405610] usb 1-1: new high-speed USB device number 23 using xhci_hcd
May 25 20:31:13 ascomtux mtp-probe: checking bus 1, device 23: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
May 25 20:31:13 ascomtux mtp-probe: bus: 1, device: 23 was not an MTP device
May 25 20:31:13 ascomtux kernel: [171722.534066] usb 1-1: New USB device found, idVendor=1390, idProduct=0001
May 25 20:31:13 ascomtux kernel: [171722.534070] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 25 20:31:13 ascomtux kernel: [171722.534073] usb 1-1: Product: XL
May 25 20:31:13 ascomtux kernel: [171722.534074] usb 1-1: Manufacturer: TomTom
May 25 20:31:13 ascomtux kernel: [171722.534076] usb 1-1: SerialNumber: GV4294A03054
May 25 20:31:13 ascomtux kernel: [171722.534538] usb-storage 1-1:1.0: USB Mass Storage device detected
May 25 20:31:13 ascomtux kernel: [171722.534649] scsi9 : usb-storage 1-1:1.0
May 25 20:31:14 ascomtux kernel: [171723.533390] scsi 9:0:0:0: Direct-Access     TomTom   ONE              0100 PQ: 0 ANSI: 2
May 25 20:31:14 ascomtux kernel: [171723.533930] sd 9:0:0:0: Attached scsi generic sg1 type 0
May 25 20:31:14 ascomtux kernel: [171723.535212] sd 9:0:0:0: [sdb] 7733248 512-byte logical blocks: (3.95 GB/3.68 GiB)
May 25 20:31:14 ascomtux kernel: [171723.535438] sd 9:0:0:0: [sdb] Write Protect is off
May 25 20:31:14 ascomtux kernel: [171723.535442] sd 9:0:0:0: [sdb] Mode Sense: 00 00 00 00
May 25 20:31:14 ascomtux kernel: [171723.535772] sd 9:0:0:0: [sdb] Asking for cache data failed
May 25 20:31:14 ascomtux kernel: [171723.535782] sd 9:0:0:0: [sdb] Assuming drive cache: write through
May 25 20:31:14 ascomtux kernel: [171723.539007]  sdb: sdb1
May 25 20:31:14 ascomtux kernel: [171723.540555] sd 9:0:0:0: [sdb] Attached SCSI removable disk
This is all very unsatisfying, but the problem installing and running TomTom Home is solved, so I will mark this thread as solved. What remains is a problem that might not have a solution at this stage.

Thanks to everyone who provided advice.
 
  


Reply

Tags
debian jessie, wine


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Unmet dependencies when trying to install package on Debian krofna Linux - Software 3 08-06-2012 07:22 PM
Yum won't install due to dependencies, NOT shown in deplist bonegang Linux - Newbie 6 06-27-2007 06:52 AM
can't install k3b due to unmet dependencies Mathsniper Debian 7 02-13-2006 10:02 AM
can't install k3b due to unmet dependencies Mathsniper Debian 10 01-18-2006 04:01 PM
apt-get install not working due to unmet dependencies ibrewale Debian 10 07-26-2005 12:13 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 11:53 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration