Picasa 2.7 for Linux (release 15) does not work with Fedora 9 kernels

67 views
Skip to first unread message

Jonathan Kamens

unread,
Apr 22, 2008, 11:33:57 PM4/22/08
to Google-Labs-Picasa-for-Linux
When I attempt to use picasa-2.7.3736-15.i386 with the following Fedora 9 kernels, WINE segfaults:
kernel-2.6.25-0.218.rc8.git7.fc9.i686
kernel-2.6.25-0.234.rc9.git1.fc9.i686
kernel-2.6.25-1.fc9.i686
I couldn't get anything useful out of the core file because there is no debuginfo and I couldn't find a separate debuginfo package anywhere to install.

This suggests to me that this release of Picasa for Linux is incompatible with the soon-to-be-released Fedora 9.

  jik

dank

unread,
Apr 23, 2008, 6:40:01 AM4/23/08
to Google-Labs-Picasa-for-Linux
On Apr 22, 8:33 pm, Jonathan Kamens <j...@kamens.brookline.ma.us>
wrote:
> When I attempt to use picasa-2.7.3736-15.i386 with the following Fedora
> 9 kernels, WINE segfaults:
>
>     kernel-2.6.25-0.218.rc8.git7.fc9.i686
>     kernel-2.6.25-0.234.rc9.git1.fc9.i686
>     kernel-2.6.25-1.fc9.i686

Thanks for the report, we'll check it out.
- Dan

leiz

unread,
Apr 23, 2008, 9:28:45 PM4/23/08
to Google-Labs-Picasa-for-Linux
FC 9 Preview with kernel 2.6.25-0.234.rc9.git1.fc9.i686 works for me.

On Apr 22, 8:33 pm, Jonathan Kamens <j...@kamens.brookline.ma.us>
wrote:

Jonathan Kamens

unread,
Apr 24, 2008, 12:17:54 AM4/24/08
to Google-Labs-Picasa-for-Linux
Interesting. In that case, I guess one of the other Rawhide packages in
conjunction with the newer kernel is breaking Picasa, rather than the
kernel doing it alone. I was able to reproducibly make the problem go
away and come back by switching between the FC8 kernel and any of FC9
kernels listed below.

It would be good news if FC9 without the newer Rawhide packages is in
fact compatible with Picasa. I hope you're right!

I'd be happy to debug further if there's anything I can do to help.

jik

leiz

unread,
Apr 24, 2008, 12:35:15 AM4/24/08
to Google-Labs-Picasa-for-Linux
Do you have any security features turned on that would affect Picasa?
If you want, you can run WINEDEBUG=+tid,+seh,+relay picasa &>
relay.log, and send me the compressed log.

I'll try out the Fedora 9 release candidate when it comes out and make
sure it works out of the box on a fresh install.

On Apr 23, 9:17 pm, Jonathan Kamens <j...@kamens.brookline.ma.us>

Jonathan Kamens

unread,
Apr 24, 2008, 10:28:04 PM4/24/08
to Google-Labs-Picasa-for-Linux
On 04/24/2008 12:35 AM, leiz wrote:
> Do you have any security features turned on that would affect Picasa?
>
SELinux is disabled. Not sure what other features you have in mind.

> If you want, you can run WINEDEBUG=+tid,+seh,+relay picasa &>
> relay.log, and send me the compressed log.
>
It's quite short, it doesn't need to be compressed. It apparently
crashes very early in start-up. Here's the entire log:

/usr/bin/picasa: line 139: 4744 Segmentation fault (core dumped)
"$PIC_BINDIR"/wrapper check_dir.exe.so
/usr/bin/picasa: line 175: 4840 Segmentation fault (core dumped)
"$PIC_BINDIR/wrapper" regedit /E $registry_export
HKEY_USERS\\S-1-5-4\\Software\\Google\\Picasa\\Picasa2\\Preferences\\

Thanks,

jik
--
http://www.jews4obama.com/

leiz

unread,
Apr 24, 2008, 10:35:25 PM4/24/08
to Google-Labs-Picasa-for-Linux
Does Wine 0.9.5x or Wine 0.9.60 work on your machine with that kernel?

On Apr 24, 7:28 pm, Jonathan Kamens <j...@kamens.brookline.ma.us>
wrote:

Jonathan Kamens

unread,
Apr 24, 2008, 10:40:51 PM4/24/08
to Google-Labs-Picasa-for-Linux
On 04/24/2008 10:35 PM, leiz wrote:
> Does Wine 0.9.5x or Wine 0.9.60 work on your machine with that kernel?
>
Yup, I just installed wine-0.9.58-1.fc9.i386 from Rawhide, and "wine
winemine" works just fine.

jik
--
http://www.jews4obama.com/

luke

unread,
May 15, 2008, 12:06:52 AM5/15/08
to Google-Labs-Picasa-for-Linux
I have the same setup, and the same problem.


On Apr 24, 10:40 pm, Jonathan Kamens <j...@kamens.brookline.ma.us>
wrote:

luke

unread,
May 15, 2008, 12:09:29 AM5/15/08
to Google-Labs-Picasa-for-Linux
$ WINEDEBUG=+tid,+seh,+relay picasa
/opt/picasa/bin/wrapper: line 46: 20825 Segmentation fault "$
{WINELOADER:-wine}" regedit /E $registry_export HKEY_CURRENT_USER\
\Software\\Wine\\Fonts\\External\ Fonts
/usr/bin/picasa: line 139: 20731 Segmentation fault "$PIC_BINDIR"/
wrapper check_dir.exe.so
/opt/picasa/bin/wrapper: line 46: 20930 Segmentation fault "$
{WINELOADER:-wine}" regedit /E $registry_export HKEY_CURRENT_USER\
\Software\\Wine\\Fonts\\External\ Fonts
/usr/bin/picasa: line 175: 20834 Segmentation fault "$PIC_BINDIR/
wrapper" regedit /E $registry_export HKEY_USERS\\S-1-5-4\\Software\
\Google\\Picasa\\Picasa2\\Preferences\\
$

luke

unread,
May 15, 2008, 12:19:02 AM5/15/08
to Google-Labs-Picasa-for-Linux
Ah! Found the fix for this problem.

Recent kernels (including Fedora and Ubuntu) disable low-address page
mapping, to fix a known local root exploit. Many typical Wine apps
crash with something like:
wine: Unhandled page fault on read access to 0x00000000 at address
0xb7d3b463

To disable this security fix, as root do the following:
sysctl -w vm.mmap_min_addr=0
(Picasa should work again.)

The Wine guys know about the problem but it sounds like they haven't
figured out the best way to work around it yet, since some Windows
(and esp DOS) apps are compiled to assume pages are mapped to the low
address range:
http://wiki.winehq.org/PreloaderPageZeroProblem

This will impact Picasa usage on Linux in a serious way, because all
the mainstream distros will likely have the fix in the near future. I
hope you guys can release an updated package soon that fixes the
problem within Picasa, as this workaround is too hard to find and too
technical for the average user.

Thanks!
Luke

luke

unread,
May 15, 2008, 12:31:46 AM5/15/08
to Google-Labs-Picasa-for-Linux
Actually I spoke too soon. While the sysctl command eliminates the
segfault problem, the Picasa window never opens. I'll paste just the
last part of the relay logs here. There is an error about a non-
existent Registry key, not sure if that is causing the problem.

Sorry to paste so much straight into the message, but there's no
attachment feature...

--

0022:Call msvcrt.isspace(00000073) ret=604664df
0022:Ret msvcrt.isspace() retval=00000000 ret=604664df
0022:Call msvcrt.isspace(0000005c) ret=604664df
0022:Ret msvcrt.isspace() retval=00000000 ret=604664df
0022:Call ntdll.memcpy(0033f3d0,00114c5e,0000003e) ret=60466508
0022:Ret ntdll.memcpy() retval=0033f3d0 ret=60466508
0022:Call kernel32.GetProcessHeap() ret=60468303
0022:Ret kernel32.GetProcessHeap() retval=00110000 ret=60468303
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00000400)
ret=60468318
0022:Ret ntdll.RtlAllocateHeap() retval=0012ed30 ret=60468318
0022:Call kernel32.GetProcessHeap() ret=60468323
0022:Ret kernel32.GetProcessHeap() retval=00110000 ret=60468323
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00000400)
ret=60468338
0022:Ret ntdll.RtlAllocateHeap() retval=0012f138 ret=60468338
0022:Call kernel32.GetProcessHeap() ret=60468343
0022:Ret kernel32.GetProcessHeap() retval=00110000 ret=60468343
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00001000)
ret=60468358
0022:Ret ntdll.RtlAllocateHeap() retval=0012f540 ret=60468358
0022:Call ntdll.strlen(0033f3d0 "HKEY_USERS\\S-1-5-4\\Software\\Google\
\Picasa\\Picasa2\\Preferences") ret=604684c5
0022:Ret ntdll.strlen() retval=0000003d ret=604684c5
0022:Call ntdll.strcpy(0012ed30,0033f3d0 "HKEY_USERS\\S-1-5-4\\Software
\\Google\\Picasa\\Picasa2\\Preferences") ret=604684f3
0022:Ret ntdll.strcpy() retval=0012ed30 ret=604684f3
0022:Call kernel32.lstrcpynA(0033ef20,0033f3d0 "HKEY_USERS\\S-1-5-4\
\Software\\Google\\Picasa\\Picasa2\\Preferences",00000400)
ret=60466f4e
0022:Ret kernel32.lstrcpynA() retval=0033ef20 ret=60466f4e
0022:Call ntdll.strchr(0033ef20 "HKEY_USERS\\S-1-5-4\\Software\\Google\
\Picasa\\Picasa2\\Preferences",0000005c) ret=60466f62
0022:Ret ntdll.strchr() retval=0033ef2a ret=60466f62
0022:Call ntdll.strcmp(0033ef20 "HKEY_USERS",6046ac50
"HKEY_LOCAL_MACHINE") ret=60466f93
0022:Ret ntdll.strcmp() retval=00000001 ret=60466f93
0022:Call ntdll.strcmp(0033ef20 "HKEY_USERS",6046ac63 "HKEY_USERS")
ret=60466f93
0022:Ret ntdll.strcmp() retval=00000000 ret=60466f93
0022:Call ntdll.strcpy(0033ef20,0033f3d0 "HKEY_USERS\\S-1-5-4\\Software
\\Google\\Picasa\\Picasa2\\Preferences") ret=60466df6
0022:Ret ntdll.strcpy() retval=0033ef20 ret=60466df6
0022:Call ntdll.strchr(0033ef20 "HKEY_USERS\\S-1-5-4\\Software\\Google\
\Picasa\\Picasa2\\Preferences",0000005c) ret=60466e07
0022:Ret ntdll.strchr() retval=0033ef2a ret=60466e07
0022:Call ntdll.strchr(0033ef20 "HKEY_USERS\\S-1-5-4\\Software\\Google\
\Picasa\\Picasa2\\Preferences",0000005d) ret=60466e1f
0022:Ret ntdll.strchr() retval=00000000 ret=60466e1f
0022:Call ntdll.strlen(0033ef2b "S-1-5-4\\Software\\Google\\Picasa\
\Picasa2\\Preferences") ret=60466e38
0022:Ret ntdll.strlen() retval=00000032 ret=60466e38
0022:Call kernel32.GetProcessHeap() ret=60466e40
0022:Ret kernel32.GetProcessHeap() retval=00110000 ret=60466e40
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00000033)
ret=60466e52
0022:Ret ntdll.RtlAllocateHeap() retval=0012cd90 ret=60466e52
0022:Call ntdll.strcpy(0012cd90,0033ef2b "S-1-5-4\\Software\\Google\
\Picasa\\Picasa2\\Preferences") ret=60466e6b
0022:Ret ntdll.strcpy() retval=0012cd90 ret=60466e6b
0022:Call advapi32.RegOpenKeyA(80000003,0012cd90 "S-1-5-4\\Software\
\Google\\Picasa\\Picasa2\\Preferences",0033f370) ret=604685a6
0022:Call kernel32.GetVersion() ret=6051b2fc
0022:Ret kernel32.GetVersion() retval=08930005 ret=6051b2fc
0022:Call ntdll.NtCreateKey(0033f220,000f003f,
0033f1f0,00000000,00000000,00000000,00000000) ret=6051ad67
0022:Ret ntdll.NtCreateKey() retval=00000000 ret=6051ad67
0022:Call ntdll.RtlInitAnsiString(0033f238,0012cd90 "S-1-5-4\\Software\
\Google\\Picasa\\Picasa2\\Preferences") ret=6051b368
0022:Ret ntdll.RtlInitAnsiString() retval=00000033 ret=6051b368
0022:Call
ntdll.RtlAnsiStringToUnicodeString(7ffdcbf8,0033f238,00000000)
ret=6051b37d
0022:Ret ntdll.RtlAnsiStringToUnicodeString() retval=00000000
ret=6051b37d
0022:Call ntdll.NtOpenKey(0033f370,000f003f,0033f240) ret=6051b3b9
0022:Ret ntdll.NtOpenKey() retval=c0000034 ret=6051b3b9
0022:Call ntdll.RtlNtStatusToDosError(c0000034) ret=6051b38c
0022:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=6051b38c
0022:Ret advapi32.RegOpenKeyA() retval=00000002 ret=604685a6
0022:Call msvcrt.__p__iob() ret=6046860f
0022:Ret msvcrt.__p__iob() retval=604f5040 ret=6046860f
0022:Call kernel32.MultiByteToWideChar(00000000,00000000,6046bbe0 "%s:
Can't export. Registry key '%s' does not exist!\n",ffffffff,
00000000,00000000) ret=604d2249
0022:Ret kernel32.MultiByteToWideChar() retval=00000035 ret=604d2249
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,0000006a)
ret=604d226c
0022:Ret ntdll.RtlAllocateHeap() retval=0012cdd0 ret=604d226c
0022:Call kernel32.MultiByteToWideChar(00000000,00000000,6046bbe0 "%s:
Can't export. Registry key '%s' does not exist!\n",ffffffff,
0012cdd0,00000035) ret=604d229b
0022:Ret kernel32.MultiByteToWideChar() retval=00000035 ret=604d229b
0022:Call kernel32.WideCharToMultiByte(00000000,00000000,0012cdd4 L":
Can't export. Registry key '%s' does not exist!\n",0000001e,
00000000,00000000,00000000,00000000) ret=604d2a26
0022:Ret kernel32.WideCharToMultiByte() retval=0000001e ret=604d2a26
0022:Call kernel32.WideCharToMultiByte(00000000,00000000,0012cdd4 L":
Can't export. Registry key '%s' does not exist!\n",0000001e,
0033eb07,0000001e,00000000,00000000) ret=604d2ab7
0022:Ret kernel32.WideCharToMultiByte() retval=0000001e ret=604d2ab7
0022:Call kernel32.WideCharToMultiByte(00000000,00000000,0012ce14 L"'
does not exist!\n",00000012,00000000,00000000,00000000,00000000)
ret=604d2a26
0022:Ret kernel32.WideCharToMultiByte() retval=00000012 ret=604d2a26
0022:Call kernel32.WideCharToMultiByte(00000000,00000000,0012ce14 L"'
does not exist!\n",00000012,0033eb62,00000012,00000000,00000000)
ret=604d2ab7
0022:Ret kernel32.WideCharToMultiByte() retval=00000012 ret=604d2ab7
0022:Call kernel32.WideCharToMultiByte(00000000,00000000,0012ce38 L"",
00000001,00000000,00000000,00000000,00000000) ret=604d2a26
0022:Ret kernel32.WideCharToMultiByte() retval=00000001 ret=604d2a26
0022:Call kernel32.WideCharToMultiByte(00000000,00000000,0012ce38 L"",
00000001,0033eb74,00000001,00000000,00000000) ret=604d2ab7
0022:Ret kernel32.WideCharToMultiByte() retval=00000001 ret=604d2ab7
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ret=604d22d1
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604d22d1
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00000075)
ret=604c1395
0022:Ret ntdll.RtlAllocateHeap() retval=0012cdd0 ret=604c1395
0022:Call
kernel32.WriteFile(00000020,0012cdd0,00000075,0033eaa8,00000000)
ret=604be84c
0022:Call
ntdll.NtWriteFile(00000020,00000000,00000000,00000000,0033e9a0,0012cdd0,00000075,00000000,00000000)
ret=60387ca2
regedit: Can't export. Registry key 'HKEY_USERS\S-1-5-4\Software\Google
\Picasa\Picasa2\Preferences' does not exist!
0022:Ret ntdll.NtWriteFile() retval=00000000 ret=60387ca2
0022:Ret kernel32.WriteFile() retval=00000001 ret=604be84c
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ret=604c1352
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604c1352
0022:Call kernel32.GetLastError() ret=604679f9
0022:Ret kernel32.GetLastError() retval=00000000 ret=604679f9
0022:Call
kernel32.FormatMessageA(00001100,00000000,00000000,00000000,0033f328,00000000,00000000)
ret=60467a2e
0022:Call ntdll.RtlFindMessage(60360000,0000000b,
00000000,00000000,0033f1c8) ret=6038cdf3
0022:Ret ntdll.RtlFindMessage() retval=00000000 ret=6038cdf3
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00000009)
ret=6039096d
0022:Ret ntdll.RtlAllocateHeap() retval=0012cdd0 ret=6039096d
0022:Call ntdll.RtlAllocateHeap(00110000,00000008,00000064)
ret=6039096d
0022:Ret ntdll.RtlAllocateHeap() retval=0012cde8 ret=6039096d
0022:Call ntdll.RtlAllocateHeap(00110000,00000008,0000000a)
ret=6039096d
0022:Ret ntdll.RtlAllocateHeap() retval=0012ce58 ret=6039096d
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cde8) ret=603909ad
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=603909ad
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ret=603909ad
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=603909ad
0022:Ret kernel32.FormatMessageA() retval=00000009 ret=60467a2e
0022:Call msvcrt.puts(0012ce58 "Success\r\n") ret=60467a83
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,0000000a)
ret=604c1395
0022:Ret ntdll.RtlAllocateHeap() retval=0012cdd0 ret=604c1395
0022:Call kernel32.WriteFile(0000001c,0012cdd0,0000000a,
0033f1f8,00000000) ret=604be84c
0022:Call ntdll.NtWriteFile(0000001c,
00000000,00000000,00000000,0033f0f0,0012cdd0,0000000a,
00000000,00000000) ret=60387ca2
Success
0022:Ret ntdll.NtWriteFile() retval=00000000 ret=60387ca2
0022:Ret kernel32.WriteFile() retval=00000001 ret=604be84c
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ret=604c1352
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604c1352
0022:Call ntdll.RtlAllocateHeap(00110000,00000000,00000002)
ret=604c1395
0022:Ret ntdll.RtlAllocateHeap() retval=0012cdd0 ret=604c1395
0022:Call kernel32.WriteFile(0000001c,
0012cdd0,00000002,0033f1f8,00000000) ret=604be84c
0022:Call ntdll.NtWriteFile(0000001c,
00000000,00000000,00000000,0033f0f0,0012cdd0,00000002,00000000,00000000)
ret=60387ca2

0022:Ret ntdll.NtWriteFile() retval=00000000 ret=60387ca2
0022:Ret kernel32.WriteFile() retval=00000001 ret=604be84c
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ret=604c1352
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604c1352
0022:Ret msvcrt.puts() retval=00000000 ret=60467a83
0022:Call kernel32.LocalFree(0012ce58) ret=60467a8e
0022:Call ntdll.RtlLockHeap(00110000) ret=60391394
0022:Ret ntdll.RtlLockHeap() retval=00000001 ret=60391394
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012ce58) ret=603909ad
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=603909ad
0022:Call ntdll.RtlUnlockHeap(00110000) ret=60391415
0022:Ret ntdll.RtlUnlockHeap() retval=00000001 ret=60391415
0022:Ret kernel32.LocalFree() retval=00000000 ret=60467a8e
0022:Call msvcrt.exit(00000001) ret=60467a78
0022:Call ntdll.RtlEnterCriticalSection(604f4a40) ret=604c290d
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604c290d
0022:Call kernel32.InitializeCriticalSection(604f49d0) ret=604c2953
0022:Call ntdll.RtlInitializeCriticalSection(604f49d0) ret=603c72df
0022:Ret ntdll.RtlInitializeCriticalSection() retval=00000000
ret=603c72df
0022:Ret kernel32.InitializeCriticalSection() retval=00000000
ret=604c2953
0022:Call ntdll.RtlLeaveCriticalSection(604f4a40) ret=604c2a2d
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604c2a2d
0022:Call ntdll.RtlEnterCriticalSection(604f49d0) ret=604c290d
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604c290d
0022:Call ntdll.RtlLeaveCriticalSection(604f49d0) ret=604c2a2d
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604c2a2d
0022:Call kernel32.ExitProcess(00000001) ret=604ba130
0022:Call ntdll.LdrShutdownProcess() ret=603b670f
0022:Call PE DLL (proc=0x6052e330,module=0x60500000
L"advapi32.dll",reason=PROCESS_DETACH,res=0x1)
0022:Ret PE DLL (proc=0x6052e330,module=0x60500000
L"advapi32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
0022:Call PE DLL (proc=0x604d2d60,module=0x604a0000
L"msvcrt.dll",reason=PROCESS_DETACH,res=0x1)
0022:Call ntdll.RtlDeleteCriticalSection(604f49d0) ret=604c2856
0022:Ret ntdll.RtlDeleteCriticalSection() retval=00000000
ret=604c2856
0022:Call ntdll.RtlDeleteCriticalSection(604f4a40) ret=604c2856
0022:Ret ntdll.RtlDeleteCriticalSection() retval=00000000
ret=604c2856
0022:Call ntdll.RtlDeleteCriticalSection(604f4a78) ret=604c2856
0022:Ret ntdll.RtlDeleteCriticalSection() retval=00000000
ret=604c2856
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604bb9dc
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604bb9dc
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604bba12
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604bba12
0022:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=604c1352
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604c1352
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604bb3f8
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604bb3f8
0022:Call kernel32.CloseHandle(00000018) ret=604bb426
0022:Call ntdll.NtClose(00000018) ret=603b7149
0022:Ret ntdll.NtClose() retval=00000000 ret=603b7149
0022:Ret kernel32.CloseHandle() retval=00000001 ret=604bb426
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604ba3ab
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604ba3ab
0022:Call kernel32.SetStdHandle(fffffff6,00000000) ret=604ba425
0022:Ret kernel32.SetStdHandle() retval=00000001 ret=604ba425
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604ba3f8
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604ba3f8
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604bb45a
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604bb45a
0022:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=604c1352
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604c1352
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604bb3f8
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604bb3f8
0022:Call kernel32.CloseHandle(0000001c) ret=604bb426
0022:Call ntdll.NtClose(0000001c) ret=603b7149
0022:Ret ntdll.NtClose() retval=00000000 ret=603b7149
0022:Ret kernel32.CloseHandle() retval=00000001 ret=604bb426
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604ba3ab
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604ba3ab
0022:Call kernel32.SetStdHandle(fffffff5,00000000) ret=604ba425
0022:Ret kernel32.SetStdHandle() retval=00000001 ret=604ba425
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604ba3f8
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604ba3f8
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604bb45a
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604bb45a
0022:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=604c1352
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604c1352
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604bb3f8
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604bb3f8
0022:Call kernel32.CloseHandle(00000020) ret=604bb426
0022:Call ntdll.NtClose(00000020) ret=603b7149
0022:Ret ntdll.NtClose() retval=00000000 ret=603b7149
0022:Ret kernel32.CloseHandle() retval=00000001 ret=604bb426
0022:Call ntdll.RtlEnterCriticalSection(604f47e4) ret=604ba3ab
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=604ba3ab
0022:Call kernel32.SetStdHandle(fffffff4,00000000) ret=604ba425
0022:Ret kernel32.SetStdHandle() retval=00000001 ret=604ba425
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604ba3f8
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604ba3f8
0022:Call ntdll.RtlLeaveCriticalSection(604f47e4) ret=604bb45a
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=604bb45a
0022:Call ntdll.RtlDeleteCriticalSection(604f47e4) ret=604bbabe
0022:Ret ntdll.RtlDeleteCriticalSection() retval=00000000
ret=604bbabe
0022:Call kernel32.CloseHandle(00000024) ret=604b1e0b
0022:Call ntdll.NtClose(00000024) ret=603b7149
0022:Ret ntdll.NtClose() retval=00000000 ret=603b7149
0022:Ret kernel32.CloseHandle() retval=00000001 ret=604b1e0b
0022:Call kernel32.CloseHandle(00000028) ret=604b1e1c
0022:Call ntdll.NtClose(00000028) ret=603b7149
0022:Ret ntdll.NtClose() retval=00000000 ret=603b7149
0022:Ret kernel32.CloseHandle() retval=00000001 ret=604b1e1c
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012d7a8) ret=604b60b5
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604b60b5
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012df28) ret=604b60db
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604b60db
0022:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=604b6101
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604b6101
0022:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=604b6127
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604b6127
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012ca48) ret=604b614d
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604b614d
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cb58) ret=604b6173
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=604b6173
0022:Call kernel32.SetConsoleCtrlHandler(604b9510,00000000)
ret=604b96c8
0022:Call ntdll.RtlEnterCriticalSection(604481a0) ret=6037dfa0
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=6037dfa0
0022:Call ntdll.RtlFreeHeap(00110000,00000000,0011c488) ret=603909ad
0022:Ret ntdll.RtlFreeHeap() retval=00000001 ret=603909ad
0022:Call ntdll.RtlLeaveCriticalSection(604481a0) ret=6037df82
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=6037df82
0022:Ret kernel32.SetConsoleCtrlHandler() retval=00000001
ret=604b96c8
0022:Call kernel32.SetUnhandledExceptionFilter(00000000) ret=604b96d7
0022:Ret kernel32.SetUnhandledExceptionFilter() retval=604b9560
ret=604b96d7
0022:Call kernel32.TlsFree(00000000) ret=604c2d64
0022:Call ntdll.RtlAcquirePebLock() ret=603b692f
0022:Ret ntdll.RtlAcquirePebLock() retval=00000000 ret=603b692f
0022:Call ntdll.RtlAreBitsSet(6031ae4c,00000000,00000001) ret=603b6a08
0022:Ret ntdll.RtlAreBitsSet() retval=00000001 ret=603b6a08
0022:Call ntdll.RtlClearBits(6031ae4c,00000000,00000001) ret=603b69b5
0022:Ret ntdll.RtlClearBits() retval=000000fe ret=603b69b5
0022:Call ntdll.NtSetInformationThread(fffffffe,0000000a,
0033eec0,00000004) ret=603b69e1
0022:Ret ntdll.NtSetInformationThread() retval=00000000 ret=603b69e1
0022:Call ntdll.RtlReleasePebLock() ret=603b697d
0022:Ret ntdll.RtlReleasePebLock() retval=00000000 ret=603b697d
0022:Ret kernel32.TlsFree() retval=00000001 ret=604c2d64
0022:Ret PE DLL (proc=0x604d2d60,module=0x604a0000
L"msvcrt.dll",reason=PROCESS_DETACH,res=0x1) retval=1
0022:Call PE DLL (proc=0x603dd5a0,module=0x60360000
L"kernel32.dll",reason=PROCESS_DETACH,res=0x1)
0022:Call ntdll.RtlEnterCriticalSection(60448a00) ret=603bcb25
0022:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=603bcb25
0022:Call ntdll.RtlLeaveCriticalSection(60448a00) ret=603bcb35
0022:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=603bcb35
0022:Ret PE DLL (proc=0x603dd5a0,module=0x60360000
L"kernel32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
0022:Call PE DLL (proc=0x602fcf60,module=0x602b0000
L"ntdll.dll",reason=PROCESS_DETACH,res=0x1)
0022:Ret PE DLL (proc=0x602fcf60,module=0x602b0000
L"ntdll.dll",reason=PROCESS_DETACH,res=0x1) retval=1
0022:Ret ntdll.LdrShutdownProcess() retval=00000000 ret=603b670f
0022:Call ntdll.NtTerminateProcess(ffffffff,00000001) ret=603b671f
bash-3.2$ 001f:Ret ntdll.NtWaitForMultipleObjects() retval=00000000
ret=603e4e55
001f:Ret kernel32.WaitForMultipleObjectsEx() retval=00000000
ret=6072e3fc
001f:Ret winex11.drv.MsgWaitForMultipleObjectsEx() retval=00000000
ret=6051f64f
001f:Call kernel32.94(6058c1a0) ret=60541872
001f:Ret kernel32.94() retval=0000001f ret=60541872
001f:Call
winex11.drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,000004ff,
00000000) ret=6051f23f
001f:Call kernel32.TlsGetValue(00000000) ret=6072e2fa
001f:Ret kernel32.TlsGetValue() retval=00165bf8 ret=6072e2fa
001f:Call ntdll.RtlEnterCriticalSection(607762c0) ret=6074c502
001f:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=6074c502
001f:Call ntdll.RtlLeaveCriticalSection(607762c0) ret=6074c532
001f:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=6074c532
001f:Ret winex11.drv.MsgWaitForMultipleObjectsEx() retval=00000102
ret=6051f23f
001f:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=6051d9a9
001f:Ret ntdll.RtlFreeHeap() retval=00000001 ret=6051d9a9
001f:Call kernel32.94(6058c1a0) ret=60541872
001f:Ret kernel32.94() retval=0000001f ret=60541872
001f:Ret user32.GetMessageW() retval=00000001 ret=604878da
001f:Call user32.DispatchMessageW(0034f930) ret=604878e9
001f:Call kernel32.97(6058c1a0) ret=60541812
001f:Call ntdll.RtlEnterCriticalSection(6058c1a0) ret=603e8567
001f:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=603e8567
001f:Ret kernel32.97() retval=60466b60 ret=60541812
001f:Call kernel32.98(6058c1a0) ret=60541842
001f:Call ntdll.RtlLeaveCriticalSection(6058c1a0) ret=603e86f6
001f:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=603e86f6
001f:Ret kernel32.98() retval=00000000 ret=60541842
001f:Call kernel32.94(6058c1a0) ret=60541872
001f:Ret kernel32.94() retval=0000001f ret=60541872
001f:Call window proc 0x604872e0
(hwnd=0x30020,msg=WM_CLOSE,wp=00000000,lp=00000000)
001f:Call user32.PostQuitMessage(00000000) ret=6048735e
001f:Ret user32.PostQuitMessage() retval=00000000 ret=6048735e
001f:Ret window proc 0x604872e0
(hwnd=0x30020,msg=WM_CLOSE,wp=00000000,lp=00000000) retval=00000000
001f:Ret user32.DispatchMessageW() retval=00000000 ret=604878e9
001f:Call user32.GetMessageW(0034f930,00000000,00000000,00000000)
ret=604878da
001f:Call kernel32.94(6058c1a0) ret=60541872
001f:Ret kernel32.94() retval=0000001f ret=60541872
001f:Call
winex11.drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,000004ff,
00000000) ret=6051f23f
001f:Call kernel32.TlsGetValue(00000000) ret=6072e2fa
001f:Ret kernel32.TlsGetValue() retval=00165bf8 ret=6072e2fa
001f:Call ntdll.RtlEnterCriticalSection(607762c0) ret=6074c502
001f:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=6074c502
001f:Call ntdll.RtlLeaveCriticalSection(607762c0) ret=6074c532
001f:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=6074c532
001f:Ret winex11.drv.MsgWaitForMultipleObjectsEx() retval=00000102
ret=6051f23f
001f:Call ntdll.RtlFreeHeap(00110000,00000000,00000000) ret=6051d9a9
001f:Ret ntdll.RtlFreeHeap() retval=00000001 ret=6051d9a9
001f:Call kernel32.94(6058c1a0) ret=60541872
001f:Ret kernel32.94() retval=0000001f ret=60541872
001f:Ret user32.GetMessageW() retval=00000000 ret=604878da
001f:Call kernel32.ExitProcess(00000000) ret=60487903
001f:Call ntdll.LdrShutdownProcess() ret=603d470f
001f:Call PE DLL (proc=0x60554200,module=0x604b0000
L"user32.dll",reason=PROCESS_DETACH,res=0x1)
001f:Call kernel32.__wine_dll_unregister_16(6058121c) ret=604b8238
001f:Ret kernel32.__wine_dll_unregister_16() retval=0000000a
ret=604b8238
001f:Call kernel32.__wine_dll_unregister_16(605818d0) ret=604b8804
001f:Ret kernel32.__wine_dll_unregister_16() retval=0000000b
ret=604b8804
001f:Call kernel32.__wine_dll_unregister_16(6058238c) ret=604b8a80
001f:Ret kernel32.__wine_dll_unregister_16() retval=0000000c
ret=604b8a80
001f:Call kernel32.__wine_dll_unregister_16(6058281c) ret=604b8b68
001f:Ret kernel32.__wine_dll_unregister_16() retval=0000000d
ret=604b8b68
001f:Call kernel32.__wine_dll_unregister_16(60582bd8) ret=604ba9b8
001f:Ret kernel32.__wine_dll_unregister_16() retval=0000000e
ret=604ba9b8
001f:Ret PE DLL (proc=0x60554200,module=0x604b0000
L"user32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Call PE DLL (proc=0x607615d0,module=0x60700000
L"winex11.drv",reason=PROCESS_DETACH,res=0x1)
001f:Call ntdll.RtlEnterCriticalSection(607762c0) ret=6074c502
001f:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=6074c502
001f:Call ntdll.RtlLeaveCriticalSection(607762c0) ret=6074c532
001f:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=6074c532
001f:Call ntdll.RtlEnterCriticalSection(60776a40) ret=60759872
001f:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=60759872
001f:Call ntdll.RtlLeaveCriticalSection(60776a40) ret=607598a9
001f:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=607598a9
001f:Call ntdll.RtlDeleteCriticalSection(607762c0) ret=6074dc88
001f:Ret ntdll.RtlDeleteCriticalSection() retval=00000000
ret=6074dc88
001f:Call kernel32.TlsFree(00000000) ret=6074dc9b
001f:Call ntdll.RtlAcquirePebLock() ret=603d492f
001f:Ret ntdll.RtlAcquirePebLock() retval=00000000 ret=603d492f
001f:Call ntdll.RtlAreBitsSet(60338e4c,00000000,00000001) ret=603d4a08
001f:Ret ntdll.RtlAreBitsSet() retval=00000001 ret=603d4a08
001f:Call ntdll.RtlClearBits(60338e4c,00000000,00000001) ret=603d49b5
001f:Ret ntdll.RtlClearBits() retval=000000fe ret=603d49b5
001f:Call ntdll.NtSetInformationThread(fffffffe,0000000a,
0034f560,00000004) ret=603d49e1
001f:Ret ntdll.NtSetInformationThread() retval=00000000 ret=603d49e1
001f:Call ntdll.RtlReleasePebLock() ret=603d497d
001f:Ret ntdll.RtlReleasePebLock() retval=00000000 ret=603d497d
001f:Ret kernel32.TlsFree() retval=00000001 ret=6074dc9b
001f:Ret PE DLL (proc=0x607615d0,module=0x60700000
L"winex11.drv",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Call PE DLL (proc=0x609018f0,module=0x608f0000
L"imm32.dll",reason=PROCESS_DETACH,res=0x1)
001f:Call user32.UnregisterClassW(60902584 L"IME",00000000)
ret=608fd488
001f:Call kernel32.GlobalFindAtomW(60902584 L"IME") ret=604cbda9
001f:Call ntdll.NtFindAtom(60902584,00000006,0034f3c2) ret=60393451
001f:Ret ntdll.NtFindAtom() retval=c0000034 ret=60393451
001f:Call ntdll.RtlNtStatusToDosError(c0000034) ret=60393460
001f:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=60393460
001f:Ret kernel32.GlobalFindAtomW() retval=00000000 ret=604cbda9
001f:Ret user32.UnregisterClassW() retval=00000000 ret=608fd488
001f:Call kernel32.__wine_dll_unregister_16(6090549c) ret=608fd2d4
001f:Ret kernel32.__wine_dll_unregister_16() retval=0000000f
ret=608fd2d4
001f:Ret PE DLL (proc=0x609018f0,module=0x608f0000
L"imm32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Call PE DLL (proc=0x60632a20,module=0x605e0000
L"gdi32.dll",reason=PROCESS_DETACH,res=0x1)
001f:Call kernel32.__wine_dll_unregister_16(60642730) ret=605e6e48
001f:Ret kernel32.__wine_dll_unregister_16() retval=00000007
ret=605e6e48
001f:Call kernel32.__wine_dll_unregister_16(60642828) ret=605e89a4
001f:Ret kernel32.__wine_dll_unregister_16() retval=00000008
ret=605e89a4
001f:Call kernel32.__wine_dll_unregister_16(606465c8) ret=605e8b60
001f:Ret kernel32.__wine_dll_unregister_16() retval=00000009
ret=605e8b60
001f:Ret PE DLL (proc=0x60632a20,module=0x605e0000
L"gdi32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Call PE DLL (proc=0x60690330,module=0x60660000
L"advapi32.dll",reason=PROCESS_DETACH,res=0x1)
001f:Ret PE DLL (proc=0x60690330,module=0x60660000
L"advapi32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Call PE DLL (proc=0x603fb5a0,module=0x60380000
L"kernel32.dll",reason=PROCESS_DETACH,res=0x1)
001f:Call ntdll.RtlEnterCriticalSection(60466a00) ret=603dab25
001f:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=603dab25
001f:Call ntdll.RtlLeaveCriticalSection(60466a00) ret=603dab35
001f:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=603dab35
001f:Ret PE DLL (proc=0x603fb5a0,module=0x60380000
L"kernel32.dll",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Call PE DLL (proc=0x6031af60,module=0x602d0000
L"ntdll.dll",reason=PROCESS_DETACH,res=0x1)
001f:Ret PE DLL (proc=0x6031af60,module=0x602d0000
L"ntdll.dll",reason=PROCESS_DETACH,res=0x1) retval=1
001f:Ret ntdll.LdrShutdownProcess() retval=00000000 ret=603d470f
001f:Call ntdll.NtTerminateProcess(ffffffff,00000000) ret=603d471f

Mike

unread,
May 15, 2008, 11:01:18 AM5/15/08
to Google-Labs-Picasa-for-Linux
Same issue here. Though Picasa does run if I execute it as root from
the command line.

Mike
> 0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ...
>
> read more »

leiz

unread,
May 15, 2008, 1:41:31 PM5/15/08
to Google-Labs-Picasa-for-Linux
Thanks for the reports. I just finished downloaded the Fedora 9 ISO.
Will try it out in a bit.
> ...
>
> read more »

leiz

unread,
May 15, 2008, 2:48:15 PM5/15/08
to Google-Labs-Picasa-for-Linux
Ok, I installed from the Fedora 9 dvd. It came with kernel-2.6.25-14.
Picasa worked out of the box. Then the system asked to be updated. Now
it's running kernel-2.6.25.3-18, and that also works.

If you're using kernel-2.6.25-0 or kernel-2.6.25-1, consider
upgrading?
> ...
>
> read more »

ts

unread,
May 19, 2008, 12:51:31 AM5/19/08
to Google-Labs-Picasa-for-Linux
Will not install on my 64 FC9
Kern = 2.6.25.3-18.fc9.x86_64
rpm error is
libXi.so.6 is needed by picasa-2.7.3736-15.i386
libXmu.so.6 is needed by picasa-2.7.3736-15.i386
libXpm.so.4 is needed by picasa-2.7.3736-15.i386
libXt.so.6 is needed by picasa-2.7.3736-15.i386
libcups.so.2 is needed by picasa-2.7.3736-15.i386
libsane.so.1 is needed by picasa-2.7.3736-15.i386
Example the libXi installed is ver 1.1.3-4.fc9 libXi.x86_64

ted
> ...
>
> read more »

zorroh

unread,
May 19, 2008, 12:45:02 PM5/19/08
to Google-Labs-Picasa-for-Linux
i have all latest updates, kernel version is 2.6.25.3-18 and not
working. i have same errors like others:

$ picasa
/usr/bin/picasa: line 139: 4259 Segmentation fault "$PIC_BINDIR"/
wrapper check_dir.exe.so
/usr/bin/picasa: line 175: 4366 Segmentation fault "$PIC_BINDIR/
wrapper" regedit /E $registry_export HKEY_USERS\\S-1-5-4\\Software\
\Google\\Picasa\\Picasa2\\Preferences\\

funny thing is that all working in superuser mode?!?!

leiz

unread,
May 19, 2008, 5:30:15 PM5/19/08
to Google-Labs-Picasa-for-Linux

leiz

unread,
May 19, 2008, 5:30:53 PM5/19/08
to Google-Labs-Picasa-for-Linux

ts

unread,
May 19, 2008, 6:24:51 PM5/19/08
to Google-Labs-Picasa-for-Linux
Just got it working then I come over here and read this ---
I installed all the missing libs using 'yum whatprovides"

Thanks

On May 19, 2:30 pm, leiz <zhang...@gmail.com> wrote:
> You need to install the 32-bit packages. They can coexist side-by-side
> with the 64 bit packages.
>
> i.e.http://mirror.cogentco.com/pub/linux/fedora/linux/releases/9/Fedora/x...
> andhttp://mirror.cogentco.com/pub/linux/fedora/linux/releases/9/Fedora/x...
> ...
>
> read more »

zorroh

unread,
May 20, 2008, 5:21:08 AM5/20/08
to Google-Labs-Picasa-for-Linux
for me was helpful reparing wine. my wine had errors like this:

preloader: Warning: failed to reserve range 00000000-60000000
err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address
space,
please report

and reparing going this way:
$ sudo sysctl -w vm.mmap_min_addr=0
$ sudo gedit /etc/sysctl.conf and adding line: vm.mmap_min_addr = 0
> ...
>
> loe edasi »

leiz

unread,
May 20, 2008, 11:59:49 AM5/20/08
to Google-Labs-Picasa-for-Linux
Does it help with Picasa as well?
> ...
>
> read more »

jaketh...@gmail.com

unread,
May 24, 2008, 5:58:31 PM5/24/08
to Google-Labs-Picasa-for-Linux
Hello,

I also had the initial wrapper segmentation fault problem that the
sysctl alteration fixes. Then the Picasa window never opens, stopping
at the registry_export line in /opt/picasa/bin/picasa:

$ sh -x /opt/picasa/bin/picasa
# ...
++ mktemp /tmp/picasa.mediacheck.reg.XXXXXX
+ registry_export=/tmp/picasa.mediacheck.reg.aCqD6g
+ /opt/picasa/bin/wrapper regedit /E /tmp/picasa.mediacheck.reg.aCqD6g
'HKEY_USERS\S-1-5-4\Software\Google\Picasa\Picasa2\Preferences\'
+ rc=1
+ '[' 1 -gt 0 ']'
+ exit 1

That wrapper call is returning 1 instead of 0, so it is exiting. If
you comment out that if..fi statement for the rc variable, I can get
the window to open.


On May 15, 12:31 am, luke <luke.hu...@gmail.com> wrote:
> 0022:Call ntdll.RtlFreeHeap(00110000,00000000,0012cdd0) ...
>
> read more »

JBenedict

unread,
May 26, 2008, 9:44:40 AM5/26/08
to Google-Labs-Picasa-for-Linux
Hi all,

i got the same issue like most of you had but i overcome it (but no
long term solution):-

1. i uses picasa-2.7.3736-15.i386
2. test run in user cannot
3. test run in root no issue

Thus, what i did is create sudo for user and run picasa as followed:-
sudo /usr/bin/picasa

it work, and hope this help.


On May 25, 5:58 am, "jakethomps...@gmail.com"
> ...
>
> read more »

leiz

unread,
May 26, 2008, 11:44:50 AM5/26/08
to Google-Labs-Picasa-for-Linux
I strongly recommend against running as root to overcome this problem
for the obvious reasons.

I'd like to help you find a solution to this problem, but first I have
to be able to reproduce the problem. Unfortunately as I said before, I
don't see this on a fresh install of Fedora 9. I've been testing in
VMWare though. Should I try on a real machine? Are you all running 32-
bit Fedora 9 or 64-bit? Did you do a fresh install of Fedora or
upgrade from an earlier version?
> ...
>
> read more »

Jason Benedict Low

unread,
May 26, 2008, 11:52:19 AM5/26/08
to zhan...@gmail.com, Google-Labs-Picasa-for-Linux
Hi leiz,

i had 2 installation, Fresh and upgrade:-

Fresh installation:-
1. gnome + CompizFusion <32bit system>
2. kernel 2.6.25.3-18
3. ram 2GB
4. CPU Intel

Upgrade(from FC8 to FC9):-
1. gnome + CompizFusion <32bit system>
2. kernel 2.6.25.3-18
3. ram 2GB
4. CPU AMD

Hope this info help and maybe you should install directly to a machine instead of VM.
Thanks you & Have a Nice Day

Best Regards,
Jason Benedict Low
*Allow us to treat you with the individuality you deserve!


leiz wrote:
...

read more �
    

  

zorroh

unread,
May 26, 2008, 4:14:15 PM5/26/08
to Google-Labs-Picasa-for-Linux
yes.
> ...
>
> read more »

luke

unread,
May 26, 2008, 6:01:08 PM5/26/08
to Google-Labs-Picasa-for-Linux
I'm running on a machine incrementally upgraded (now approximately at
Fedora 9) using rawhide.

I'm happy to help debug the issue further if you can think of another
way to get some useful debug output...
> ...
>
> read more »

AdamD

unread,
May 26, 2008, 7:25:40 PM5/26/08
to Google-Labs-Picasa-for-Linux
Just thought I would add that It also behaves like the following for
me;
- user obtains segfault;
- starts fine with root user
- only tray icon opens with sysctl fix

$ rpm -qa | grep kernel
kernel-devel-2.6.25.3-18.fc9.x86_64
kernel-headers-2.6.25.3-18.fc9.x86_64
kernel-2.6.25.3-18.fc9.x86_64
kerneloops-0.10-11.fc9.x86_64
kernel-2.6.25-14.fc9.x86_64
$ uname -a
Linux hostname 2.6.25.3-18.fc9.x86_64 #1 SMP Tue May 13 04:54:47 EDT
2008 x86_64 x86_64 x86_64 GNU/Linux

picasa-2.7.3736-15.i386 installed from repo.

Fedora 9 from a fresh install.

Adam

luke

unread,
May 26, 2008, 10:26:16 PM5/26/08
to Google-Labs-Picasa-for-Linux
Is there a public bug tracker for Picasa-Linux anywhere, or are these
forums the best place to report problems like this?

Jason Benedict Low

unread,
May 26, 2008, 10:46:44 PM5/26/08
to Google-Labs-Picasa-for-Linux
Does not work for me by doing:-

$ sudo sysctl -w vm.mmap_min_addr=0
$ sudo gedit /etc/sysctl.conf and adding line: vm.mmap_min_addr = 0
  

currently runing Picasa in sudo mode - bad idea.... Hope to see a solution soon.

Thanks you & Have a Nice Day

Best Regards,
Jason Benedict Low
*Allow us to treat you with the individuality you deserve!


zorroh wrote:
...

read more �
    

  

leiz

unread,
May 27, 2008, 9:45:33 PM5/27/08
to Google-Labs-Picasa-for-Linux
Ok, so anyone having this problem should just follow the instructions
here?
http://wiki.winehq.org/PreloaderPageZeroProblem

I tried Fedora 9 on a real machine just now. Fresh install + Picasa -
works fine here on my pentium 4 test machine. Ran the system update,
rebooted, still works. I'll try on a core 2 duo in a bit.
> ...
>
> read more »

luke

unread,
May 27, 2008, 11:06:52 PM5/27/08
to Google-Labs-Picasa-for-Linux
Those instructions seem to give a partial solution, but Picasa still
dies at a later stage so there's still a problem. I don't even get a
tray icon.

luke

unread,
May 27, 2008, 11:19:45 PM5/27/08
to Google-Labs-Picasa-for-Linux
Just figured it out! I now have Picasa working fine on my F9
installation. This is the first time in several months this has
worked.

I had tried deleting .wine to make sure there wasn't a problem with
something in the wine filesystem that was causing the problem, to no
avail. This is, it turns out, because Picasa doesn't use .wine, but
has a .wine-like structure of its own inside .picasa .

The solution is to delete ~/.picasa (making sure that you don't care
about its contents first :) , I think it just stores thumbnails??),
and *before* you launch picasa again, run the fix described in
http://wiki.winehq.org/PreloaderPageZeroProblem .

If you run picasa even once before applying the zero-page fix, it will
die immediately with:

/usr/bin/picasa: line 139: 9483 Segmentation fault
"$PIC_BINDIR"/wrapper check_dir.exe.so
/usr/bin/picasa: line 175: 9586 Segmentation fault
"$PIC_BINDIR/wrapper" regedit /E $registry_export HKEY_USERS\\S-1-5-4\
\Software\\Google\\Picasa\\Picasa2\\Preferences\\

... and then it somehow corrupts .picasa in such a way that even if
you apply the zero-page fix and run picasa again, it will not start
up. The solution is to apply the fix before starting picasa without
a .picasa directory present.

There are two things I hope the Picasa developers look at, to prevent
further users from being unable to use Picasa:
(1) until Wine finds a fix for the zero-page problem, it would be
great if Picasa could be modified to not rely on low-addressed pages.
(2) if a user has a corrupt .picasa directory (as described above), it
would be great if Picasa could recover from this gracefully rather
than dying silently, so that users can fix the problem by simply
upgrading to the fixed version of Picasa, without having to manually
delete .picasa.

Thanks,
Luke


On May 27, 9:45 pm, leiz <zhang...@gmail.com> wrote:
> Ok, so anyone having this problem should just follow the instructions
> here?http://wiki.winehq.org/PreloaderPageZeroProblem

On May 27, 9:45 pm, leiz <zhang...@gmail.com> wrote:
> Ok, so anyone having this problem should just follow the instructions
> here?http://wiki.winehq.org/PreloaderPageZeroProblem

luke

unread,
May 27, 2008, 11:25:27 PM5/27/08
to Google-Labs-Picasa-for-Linux
One more thought: the reason this doesn't appear on new installations
of Fedora or other distros may be that /etc/sysctl.conf already has
the line vm.mmap_min_addr = 0, or (for some distros) that the kernel
default is not the safer value of 65536. It is possible that when
upgrading a system, /etc/sysctl.conf is not overwritten during the
upgrade, etc.
> ...
>
> read more »

leiz

unread,
May 28, 2008, 12:52:24 AM5/28/08
to Google-Labs-Picasa-for-Linux
Actually on a fresh install of Fedora 9, vm.mmap_min_addr defaults to
65536. (It's not in /etc/sysctl.conf though)
So I found a 6 GB (woo!) hard drive, plugged it in to a core 2 duo and
installed F9. it works just fine there as well. I guess I can try 64-
bit Fedora 9 next?

With regards to ~/.picasa, I see two scenarios:
1. You already had a ~/.picasa directory from before. If this is the
case, I doubt running into this problem will corrupt your ~/.picasa
directory. Thus just apply the fix and you should be good to go.
2. You did not have a ~/.picasa directory and you ran into this
problem the first time you ran Picasa. (while creating ~/.picasa?) In
this case, there's nothing valuable in ~/.picasa. Apply the fix, blow
away ~/.picasa, and try again.
> ...
>
> read more »

leiz

unread,
May 28, 2008, 3:25:29 AM5/28/08
to Google-Labs-Picasa-for-Linux
64-bit Fedora 9 and Picasa worked for me as well on my core 2 duo.
Again, both from the install cd and after I got the latest updates.
> ...
>
> read more »

Jason Benedict Low

unread,
May 28, 2008, 5:17:34 AM5/28/08
to zhan...@gmail.com, Google-Labs-Picasa-for-Linux
leiz, did you tried with Compiz-fusion installed? maybe that the cause?

I had FC9 fresh installed on a 32bit PC and also a upgrade from FC8 to FC9 on a 32bit Laptop. Both have Compiz-fusion installed and both can't run Picasa as user execpt root.

Anyway i also check both machine in /etc/sysctl.conf for vm.mmap_min_addr, but it not in it too.

hope this info is useful for your help.

Thanks you & Have a Nice Day

Best Regards,
Jason Benedict Low
*Allow us to treat you with the individuality you deserve!


leiz wrote:
...

read more �
    

  

luke

unread,
May 28, 2008, 1:33:56 PM5/28/08
to Google-Labs-Picasa-for-Linux
I use 32-bit Fedora, so it's not a 64-bit-only problem.

Now that I know how to fix the problem, as described above, I'm happy
-- I was only suggesting that Picasa startup code should probably
somehow detect corrupt .picasa directories and handle that case,
rather than just dying. If it's helpful, I can post a corrupt .picasa
directory archive here (maybe in uuencoded form??), so that you can
see where it's causing the hang. (leiz, do you work for Google?)

I don't know why you can't duplicate this on fresh installations of
Fedora (thanks for trying though!). If on a fresh install of Fedora
9, vm.mmap_min_addr defaults to 65536, there must be another trigger
for the problem too. Is there any dotfile or directory used by picasa
other than .picasa?
> ...
>
> read more »

leiz

unread,
May 28, 2008, 1:39:24 PM5/28/08
to Google-Labs-Picasa-for-Linux
If you want to, you can upload a tarball of the corrupt .picasa
directory somewhere and email me the link.

It's strange that many people have had this problem, but I have not
ran into it. If anyone knows of a recipe for reproducing this starting
with a fresh install, let me know.

- Lei
(yes, I work on Picasa for Linux)
> ...
>
> read more »

Jason Benedict Low

unread,
May 28, 2008, 11:31:21 PM5/28/08
to zhan...@gmail.com, Google-Labs-Picasa-for-Linux
Maybe most do run full install of FC9 + livna repos + Sun Jre (example compiz-fusion, mp3 libs etc....) ...you may like to try that out to see you can reproduce the error.

I followed this link to get my FC9 tuned - http://www.mjmwired.net/resources/mjm-fedora-f9.html

Thanks you & Have a Nice Day

Best Regards,
Jason Benedict Low
*Allow us to treat you with the individuality you deserve!


leiz wrote:
...

read more �
    

  

CanMasagi

unread,
Jun 13, 2008, 3:46:39 AM6/13/08
to Google-Labs-Picasa-for-Linux
Same as mine as fresh installed with kernel-2.6.25-14. picasa works
fine, then upgraded to kernel-2.6.25.3-18 due to nVidia kmod
instalation, picasa also works. but after upgrade kernel again to
2.6.25.4-30.fc9.i686 picasa won't run except I run it with console as
a root.......


On May 26, 10:44 pm, leiz <zhang...@gmail.com> wrote:
> I strongly recommend against running as root to overcome this problem
> for the obvious reasons.
>
> I'd like to help you find a solution to this problem, but first I have
> to be able to reproduce the problem. Unfortunately as I said before, I
> don't see this on a fresh install ofFedora9. I've been testing in
> VMWare though. Should I try on a real machine? Are you all running 32-
> bitFedora9or 64-bit? Did you do a fresh install ofFedoraor
> upgrade from an earlier version?
>
> On May 26, 6:44 am, JBenedict <jbenedict...@gmail.com> wrote:
>
> > Hi all,
>
> > i got the same issue like most of you had but i overcome it (but no
> > long term solution):-
>
> > 1. i usespicasa-2.7.3736-15.i386
> > 2. test run in user cannot
> > 3. test run in root no issue
>
> > Thus, what i did is create sudo for user and runpicasaas followed:-
> > sudo /usr/bin/picasa
>
> > it work, and hope this help.
>
> > On May 25, 5:58 am, "jakethomps...@gmail.com"
>
> > <jakethomps...@gmail.com> wrote:
> > > Hello,
>
> > > I also had the initial wrapper segmentation fault problem that the
> > > sysctl alteration fixes.  Then thePicasawindow never opens, stopping
> > > at the registry_export line in /opt/picasa/bin/picasa:
>
> > > $ sh -x /opt/picasa/bin/picasa
> > > # ...
> > > ++ mktemp /tmp/picasa.mediacheck.reg.XXXXXX
> > > + registry_export=/tmp/picasa.mediacheck.reg.aCqD6g
> > > + /opt/picasa/bin/wrapper regedit /E /tmp/picasa.mediacheck.reg.aCqD6g
> > > 'HKEY_USERS\S-1-5-4\Software\Google\Picasa\Picasa2\Preferences\'
> > > + rc=1
> > > + '[' 1 -gt 0 ']'
> > > + exit 1
>
> > > That wrapper call is returning 1 instead of 0, so it is exiting.  If
> > > you comment out that if..fi statement for the rc variable, I can get
> > > the window to open.
>
> > > On May 15, 12:31 am, luke <luke.hu...@gmail.com> wrote:
>
> > > > Actually I spoke too soon.  While the sysctl command eliminates the
> > > > segfault problem, thePicasawindow never opens.  I'll paste just the
> ...
>
> read more »

dank

unread,
Jun 13, 2008, 7:18:57 AM6/13/08
to Google-Labs-Picasa-for-Linux
On Jun 13, 12:46 am, CanMasagi <ywandia...@gmail.com> wrote:
> Same as mine as fresh installed with kernel-2.6.25-14. picasa works
> fine, then upgraded to  kernel-2.6.25.3-18 due to nVidia kmod
> instalation, picasa also works. but after upgrade kernel again to
> 2.6.25.4-30.fc9.i686 picasa won't run except I run it with console as
> a root.......

You're probably running into
http://wiki.winehq.org/PreloaderPageZeroProblem
Try the workaround suggested there and let us know if it helps.
(You may need to repair the damage done by running it as root
first; if any files in ~/.picasa are owned by root, this will
print out a list of them:
sudo find ~ ~/.picasa -user root -print
If that prints anything, let me know, I'll give the command to
chown them back to yourself.)

- Dan

p.s. People, please trim quotes... no point in quoting huge logs from
ten messages back...

sti

unread,
Jun 19, 2008, 12:02:08 PM6/19/08
to Google-Labs-Picasa-for-Linux

On Jun 13, 7:18 am, dank <daniel.r.ke...@gmail.com> wrote:

> You're probably running intohttp://wiki.winehq.org/PreloaderPageZeroProblem
> Try the workaround suggested there and let us know if it helps.

I had the same problem with RHEL5.2 and kernel 2.6.18-92.el5 and above
referenced patch makes the problem disappear ...

-michael-

John

unread,
Jul 11, 2008, 2:17:01 PM7/11/08
to Google-Labs-Picasa-for-Linux
I'm running Fedora 8 (not 9) X86_64 natively on a MacBook Pro
SantaRosa, and am having the same problem - first the wrapper
segfault, then did the sysctl fix and no errors, but no window opens
either. If I run it as root, there is no problem. Does picasa use it's
own version of wine, or does it use the wine that comes installed with
the distribution?

John

On May 26, 11:44 am, leiz <zhang...@gmail.com> wrote:
> ...
>
> read more »

leiz

unread,
Jul 11, 2008, 2:21:34 PM7/11/08
to Google-Labs-Picasa-for-Linux
John,

Picasa comes with its own copy of Wine. It uses ~/.picasa for
$WINEPREFIX instead of ~/.wine. When you encountered the crash the
first time, it could have created a corrupt ~/.picasa directory. You
no longer get the segfault now right? Just delete ~/.picasa, rerun
Picasa, and it will create a new one properly.
> ...
>
> read more »

daniel....@gmail.com

unread,
Jul 15, 2008, 11:59:03 PM7/15/08
to Google-Labs-Picasa-for-Linux
Same with Fermi SL 5.0 (same as RHEL 5.0) and kernel
2.6.18-92.1.6.el5. sysctl works for me too.

Dan

sHaggY_caT

unread,
Jul 21, 2008, 12:58:45 AM7/21/08
to Google-Labs-Picasa-for-Linux
Hi!

I'm have installed

libXi-devel-1.1.3-1.fc8.i386.rpm and libXi-
devel-1.1.3-1.fc8.x86_64.rpm;

I edited /etc/sysctl.conf and add line

vm.mmap_min_addr = 0

Befor i make this, my picasa make segfault, and now, it not have
anything messages, when i run picasa in konsole.

cat /etc/redhat-release
Fedora release 8 (Werewolf)

uname -a
Linux desktop.loc 2.6.25.10-47.fc8 #1 SMP Mon Jul 7 18:31:41 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux

rpm -qa | grep glibc
glibc-2.7-2
glibc-common-2.7-2
glibc-2.7-2

P.S. sorry for my bad English

leiz

unread,
Jul 21, 2008, 1:17:22 PM7/21/08
to Google-Labs-Picasa-for-Linux
Is the problem that Picasa does not start? You might need to remove
the old ~/.picasa directory, which did not get created properly
because of the earlier segfault.

sHaggY_caT

unread,
Jul 21, 2008, 2:54:48 PM7/21/08
to Google-Labs-Picasa-for-Linux

> Is the problem that Picasa does not start?

Yes, it was problem for start Picasa

> You might need to remove
> the old ~/.picasa directory, which did not get created properly
> because of the earlier segfault.

Thanks, it's work!

I think, this problem for start Picasa need to be add in FAQ....

vasekd

unread,
Sep 7, 2008, 4:00:49 PM9/7/08
to Google-Labs-Picasa-for-Linux
I only deleted

.picasa/drive_c/Program Files and
.picasa/drive_c/windows

And now Picasa is working again with my old settings.

(problem started, when I updated wine from FC8 -> FC9 and had old
drive_c wine settings in home directory)
Reply all
Reply to author
Forward
0 new messages