Kernel update breaks Picasa

Bug #1382251 reported by FairMiles
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After Kernel update (3.2.0-70-pae) Picasa for Linux no longer starts (shows splash screen, then after a while it closes). After restarting the laptop with previous kernel (3.2.0-69-pae), Picasa starts normally.

Back and forth several times -> confirmed

Doesn't change if trying to start Picasa under Nvidia graphics card instead of on-board Intel (Bumblebee)

Ubuntu 12.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-70-generic-pae 3.2.0-70.105
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic-pae 3.2.63
Uname: Linux 3.2.0-70-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.7
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fer 2137 F.... pulseaudio
 /dev/snd/pcmC0D0p: fer 2137 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd9c00000 irq 49'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,10431113,00100100'
   Controls : 24
   Simple ctrls : 13
Date: Thu Oct 16 19:18:28 2014
HibernationDevice: RESUME=UUID=42df4fb0-c9fd-47aa-8274-ce9b3c1255d9
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: ASUSTeK Computer Inc. N53Jf
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-70-generic-pae root=UUID=42e515fa-dd55-4d3f-8668-29854772f749 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-70-generic-pae N/A
 linux-backports-modules-3.2.0-70-generic-pae N/A
 linux-firmware 1.79.18
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2013-02-24 (599 days ago)
dmi.bios.date: 01/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N53Jf.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N53Jf
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53Jf.210:bd01/25/2011:svnASUSTeKComputerInc.:pnN53Jf:pvr1.0:rvnASUSTeKComputerInc.:rnN53Jf:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: N53Jf
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
FairMiles (fermilesi) wrote :
tags: added: picasa
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
FairMiles (fermilesi)
description: updated
Revision history for this message
Chris J Arges (arges) wrote :

Hi, after Picasa doesn't start do you see anything in the kernel log? Can you attach the output of dmesg after launching the program? Also perhaps running picasa from the command line might show some additional errors from userspace.
Thanks!

Revision history for this message
FairMiles (fermilesi) wrote :

Sorry, newbie here just trying to help. You may have to guide me much better than that to get something useful for you.

I did have try already to run picasa from the command line to see some sort of error, though nothing appears there. In fact, it closes after a while (splash screen appears ok) without messages.

As far as I can see, no new lines are added after this event on the kernel log or in dmesg log (comparing logs before and after picasa tries to open and closes)

Revision history for this message
Mike Durham (mdurhamesq) wrote :

I have this problem on two computers running 12.04 using kernel 3.2.0-70, it works fine with previous kernel.
Running in a terminal shows nothing.

Revision history for this message
Mike Durham (mdurhamesq) wrote :

Here is a dmesg output after running picasa and waiting several minutes for the flash screen to disappear.

Revision history for this message
James Schurz (pjschurz) wrote :

I also have this problem. Picasa starts on 3.2.0-69 but not on 3.2.0-70. I also have not seen any error messages.

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
James Schurz (pjschurz) wrote :

Some additional information. When Picasa starts the splash sacreen comes up imediately but there is no disc activity as is normally the case. The splash scree then goes away after about 1-2 minutes with no disc activity.

Revision history for this message
sw (privat-z) wrote :
Download full text (8.6 KiB)

I guess the bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382251
is related to the modify_ldt changes made in the kernel.

5559 5064 0 15:03 pts/1 00:00:00 /opt/google/picasa/3.0/wine/lib/wine/license.exe.so /gate c:\Program Files\Google\Picasa3\Picasa3.exe
Here is some strace output of this process:

1414069442.802669 open("/opt/google/picasa/3.0/wine/lib/wine/krnl386.exe16", O_RDONLY|O_LARGEFILE) = 9 <0.000017>
1414069442.802718 read(9, "kernel32.dll\n", 19) = 13 <0.000005>
1414069442.802741 close(9) = 0 <0.000008>
1414069442.802799 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 <0.000004>
1414069442.802829 mmap2(0x330000, 1114112, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x330000 <0.000018>
1414069442.802867 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000004>
1414069442.802891 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 <0.000004>
1414069442.802918 mprotect(0x330000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC) = 0 <0.000008>
1414069442.802942 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000004>
1414069442.802976 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 <0.000004>
1414069442.803007 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000004>
1414069442.803029 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 <0.000004>
1414069442.803055 modify_ldt(17, {entry_number:512, base_addr:0x330118, limit:12159, seg_32bit:0, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:0}, 16) = -1 EINVAL (Invalid argument) <0.000018>
1414069442.803104 dup(2) = 9 <0.000005>
1414069442.803126 fcntl64(9, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE) <0.000004>
1414069442.803147 close(9) = 0 <0.000004>
1414069442.803180 open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 9 <0.000014>
1414069442.803219 fstat64(9, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0 <0.000005>
1414069442.803258 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7664000 <0.000006>
1414069442.803283 read(9, "# Locale name alias data base.\n#"..., 4096) = 2570 <0.000008>
1414069442.803336 read(9, "", 4096) = 0 <0.000005>
1414069442.803366 close(9) = 0 <0.000005>
1414069442.803386 munmap(0xb7664000, 4096) = 0 <0.000009>
1414069442.803428 open("/usr/share/locale/de_AT/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) <0.000008>
1414069442.803462 open("/usr/share/locale/de/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) <0.000008>
1414069442.803493 open("/usr/share/locale-langpack/de_AT/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory) <0.000007>
1414069442.803525 open("/usr/share/locale-langpack/de/LC_MESSAGES/libc.mo", O_RDONLY) = 9 <0.000009>
1414069442.803557 fstat64(9, {st_mode=S_IFREG|0644, st_size=149140, ...}) = 0 <0.000004>
1414069442.803594 mmap2(NULL, 149140, PROT_READ, MAP_PRIVATE, 9, 0) = 0x7e566000 <0.000010>
1414069442.803620 close(9) = 0 <0.000005>
1414069442.803682 open("/usr/lib/i386-linux-gnu/gconv/gconv-modules.cache", O_RDONLY) = 9 <0.000010>
14...

Read more...

Revision history for this message
sw (privat-z) wrote :

seems to me not only Picasa is affected by this bug. E.g.: http://www.postfrontal.com/FORUM/topic.asp?whichpage=1&TOPIC_ID=7803

Revision history for this message
sw (privat-z) wrote :

Not sure if my last post really does relate to this bug.
But the following text I found on http://newton.freehostia.com/comp/ubstuff.html seems to describe our Problem with Picasa:

As of kernel update 3.2.0-70 a few days ago, dpmi programs under dosemu no longer work.. again. The new 3.2.63 upstream kernel removed the ltd16 workaround and was supposed to include a proper fix (espfix64) but looks like it doesn't work for whatever reason. I feel like a dinosaur... but I'm not alone. http://ubuntuforums.org/showthread.php?t=2247766

Revision history for this message
sw (privat-z) wrote :
Revision history for this message
Terry Newton (wtn90125) wrote :

The espfix64 patch appears to have config options to enable/disable 16 bit support...
https://lkml.org/lkml/2014/5/4/346
https://lkml.org/lkml/2014/5/4/372
Perhaps the 3.2.0-70 kernel was configured to disallow 16 bit segments? Reaching.
Odd that this is now affecting 32 bit kernels too, when the original issue was 64-bit only.

Revision history for this message
Terry Newton (wtn90125) wrote :

The file /boot/config-3.2.0-70-generic contains the following comment...
# CONFIG_X86_16BIT is not set
This is a new compile-time setting for this kernel, guessing it needs to be set?

Revision history for this message
Ralf Stegmaier (post-ig-schwaben) wrote :

After update 12.04 to kernel 3.2.0-70 only command line login is possible (graphic is shown for 2 seconds, than clear and change to command line login).
And the last kernels doesn't work now too!
- 69 => only command line login
- 65 (and -68, -67) => only command line
- 59 (and -64, -63, -61)

tried with old kernel -55 => graphic login works

So update to kernel 3.2.0-70 killed many older kernels before (graphic login)

Revision history for this message
Terry Newton (wtn90125) wrote :

Today's kernel 3.2.0-72 update fixed the issue I was having with dosemu, perhaps try Picasa after updating and see if it's fixed.

Revision history for this message
FairMiles (fermilesi) wrote :

Solved with new kernel 3.2.0-72 update!

Now it's working again (or so it seems…)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.