WineHQ Bugzilla – Bug 24531 – Cannot browse directories in winecfg

Bugzilla

Last modified: 2010-10-04 14:59:51 UTC

Cannot browse directories in winecfg

Bug 24531 - Cannot browse directories in winecfg


Summary:	Cannot browse directories in winecfg

Status:	CLOSED INVALID

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.3.3
Hardware:	x86-64 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-09-26 15:00 UTC by darkbasic
Modified:	2010-10-04 14:59 UTC (History)
CC List:	2 users (show)

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
screenshot (39.89 KB, image/jpeg) 2010-09-26 15:01 UTC, darkbasic	Details
emerge-info (5.03 KB, text/plain) 2010-09-27 04:28 UTC, darkbasic	Details
View All Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description darkbasic 2010-09-26 15:00:46 UTC

The are some strange symbols in the name of the directories too. Please see attached screenshot.

Comment 1 darkbasic 2010-09-26 15:01:58 UTC

Created attachment 30962 [details]
screenshot

Comment 2 Austin English 2010-09-26 16:10:08 UTC

Terminal output? Have you installed any native dlls?

Comment 3 darkbasic 2010-09-27 04:11:12 UTC

niko2@laptop ~ $ mv .wine .wine2
niko2@laptop ~ $ winecfg
wine: created the configuration directory '/home/niko2/.wine'
fixme:system:SetProcessDPIAware stub!
fixme:iphlpapi:NotifyAddrChange (Handle 0x90fe914, overlapped 0x90fe918): stub
wine: configuration in '/home/niko2/.wine' has been updated.

I even removed the .wine directory, but the bug is still here.

Comment 4 Austin English 2010-09-27 04:19:28 UTC

What OS is this? Any custom cflags/missing dependencies?

Comment 5 darkbasic 2010-09-27 04:28:45 UTC

Created attachment 30967 [details]
emerge-info

Comment 6 darkbasic 2010-09-27 04:29:41 UTC

It's gentoo amd64. I attached emerge --info and here it is how I compiled wine:

laptop ~ # emerge -pv wine

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] app-emulation/wine-1.3.3  USE="X alsa cups dbus gecko jack jpeg lcms ldap mp3 ncurses opengl oss perl png pulseaudio ssl threads truetype win32 xcomposite xml (-capi) -custom-cflags (-esd) -fontconfig -gnutls (-gphoto2) -gsm (-hal) -nas -openal -samba (-scanner) -test -win64 -xinerama" 0 kB

Comment 7 Austin English 2010-09-27 05:56:28 UTC

A user reported a similar problem in #winehq earlier, and said that disabling fontconfig and custom-cflags fixed it.

Comment 8 darkbasic 2010-09-27 07:37:34 UTC

fontconfig and custom cflags are already disabled (in fact there is a '-' before them in the emerge -pv wine output).

Comment 9 darkbasic 2010-09-28 06:38:08 UTC

Someone else filed a bug on the gentoo bugtracker too:
http://bugs.gentoo.org/show_bug.cgi?id=338944

Comment 10 darkbasic 2010-09-29 18:00:41 UTC

It was gentoo specific. Closed.

Comment 11 Jeff Zaroyko 2010-09-29 19:04:16 UTC

Closing invalid.

Comment 12 Plüss Roland 2010-10-02 10:33:34 UTC

(In reply to comment #10)
> It was gentoo specific. Closed.
Can't share this comment. The bug still persists. If it's a GenToo bug or an UpStream bug I can't tell but the bug is not solved yet and wine unusable due to that. Only way to use it is to start apps with a filename as parameter but anything connected to the file dialog is not working due to the mentioned bug.

Comment 13 Jerome Leclanche 2010-10-02 10:35:18 UTC

(In reply to comment #12)
> (In reply to comment #10)
> > It was gentoo specific. Closed.
> Can't share this comment. The bug still persists. If it's a GenToo bug or an
> UpStream bug I can't tell but the bug is not solved yet and wine unusable due
> to that. Only way to use it is to start apps with a filename as parameter but
> anything connected to the file dialog is not working due to the mentioned bug.

There is nothing the Wine developers can do if it's a broken lib shipped with Gentoo. Take it here: http://bugs.gentoo.org/show_bug.cgi?id=338944

Comment 14 Plüss Roland 2010-10-03 10:46:26 UTC

(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #10)
> > > It was gentoo specific. Closed.
> > Can't share this comment. The bug still persists. If it's a GenToo bug or an
> > UpStream bug I can't tell but the bug is not solved yet and wine unusable due
> > to that. Only way to use it is to start apps with a filename as parameter but
> > anything connected to the file dialog is not working due to the mentioned bug.
> 
> There is nothing the Wine developers can do if it's a broken lib shipped with
> Gentoo. Take it here: http://bugs.gentoo.org/show_bug.cgi?id=338944

"Who" claims this is a library problem? I've not seen "any" proof that this is a library problem. Without such a proof it's not "closed" but "timebomb". Can you please provide an URL to the where this claim is staked and "what" library this is supposed to be?

Comment 15 darkbasic 2010-10-03 13:15:47 UTC

Don't know, but I upgraded openssl to 1.0.0a-r3, I did an emerge @preserved-rebuild and I rebuilded wine (and deleted the profile in ~/.wine). Then the bug was fixed.

Comment 16 Plüss Roland 2010-10-04 06:18:57 UTC

(In reply to comment #15)
> Don't know, but I upgraded openssl to 1.0.0a-r3, I did an emerge
> @preserved-rebuild and I rebuilded wine (and deleted the profile in ~/.wine).
> Then the bug was fixed.
OpenSSL hardly has anything to do with string manipulation in Wine in any way.

Comment 17 darkbasic 2010-10-04 07:34:21 UTC

Yes, but I had to rebuild *LOTS* of packages because of the openssl upgrade (revdep-rebuild).

Comment 18 Plüss Roland 2010-10-04 14:57:18 UTC

(In reply to comment #17)
> Yes, but I had to rebuild *LOTS* of packages because of the openssl upgrade
> (revdep-rebuild).
As mentioned in the other place this would mean that other applications would be affected by the same bug. Wine is though the only application affected by this bug. Unless it can be pin-pointed what library causes this the bug is in TIMEBOMB statuc, meaning it can happen again at any time and renders wine totally unusable (I still can't use it at all). The question now is only if this is an upstream bug in wine or caused by some GenToo patches.

Comment 19 Jerome Leclanche 2010-10-04 14:59:51 UTC

(In reply to comment #18)
> totally unusable (I still can't use it at all). The question now is only if
> this is an upstream bug in wine or caused by some GenToo patches.

Which, either way, moves this bug outside of Wine's scope. The Gentoo bug was filed to figure that part out and it's there you should be discussing this issue, not here.