The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)


Nemo/Status

From Mer Wiki
< Nemo
Revision as of 13:27, 5 December 2011 by Vesku (Talk | contribs)

Jump to: navigation, search

Contents

Nemo Status

NOTE: Many of the fixes can be fetched with zypper.

 su
 zypper ref
 zypper update

NOTE: Problems not crossed out or marked fixed are still valid. If you find problems with the Nemo image please file a bugs to Nemo bugzilla or add your findings to the list below. Please add prefix to the error based on your finding (ALL/N900/N950/ia32).

Nemo 12-01.2

Nemo 11-24.1

On N950 the image does not boot. Please, use this workaround to get device booting.

Nemo 11-17.1

Missing/Broken (not in bugzilla yet)

  • N900: Network indicator broken Fixed.
  • ALL: Missing apps: Fennec, Peregrine, Calendar
  • ALL: System menu animation slow

Nemo 11-10.1

Missing/Broken

  • ia32:Lenovo(other?): mcompositor makes things extremely slow in some situations fixed, TFP support was being incorrectly turned off

Nemo 11-03.1

Missing/Broken

  • N950: Small graphical issues. Sometimes not seeing indicator icons in System UI, just seeing turquoise rectangles instead. Also sometimes in widgetsgallery the menubar is turquoise after orientation change.
  • N950: holding a finger down appears to make mce go wild, and take ~17% CPU
  • N950: I've seen meegotouch-home go crazy and use ~50% CPU. OTOH, I use lipstick, so not a major problem for me now.
  • N950: sometimes VKB and HW keyboard broken
  • ia32:ExoPC/WeTab boot messages obscure splash screen
  • iaa2:ExoPC Toggle Icon view a few times and screen blanks, can get VT2 access. Seen on previous ia32 builds of CE log files below :- I'm wondering if we need to use Pinetrail kernel on Exopc - Tried it same issue - I'll try and get some debug info
    • http://dl.dropbox.com/u/5715485/x86-nemo/messages
      • [ 83.708078] Call Trace:
      • [ 83.764521] meegotouchhome[484]: segfault at 29 ip b6a00957 sp bfdf7dcc error 4 in libQtGui.so.4.8.0[b6896000+a62000]
      • [ 83.764583] meegotouchhome/484: potentially unexpected fatal signal 11.
      • [ 83.764591] code at b6a00957: 8b 00 8b 40 08 83 e0 0f c3 55 89 e5 8b 45 08 5d
      • [ 83.764626] Modules linked in: joydev uvcvideo ath9k ath9k_common ath9k_hw battery asus_laptop
      • [ 83.764650]
      • [ 83.764659] Pid: 484, comm: meegotouchhome Not tainted 3.0.0-1.1-adaptation-pc #1 EXOPC EXOPG06411/EXOPG06411
      • [ 83.764674] EIP: 0073:[<b6a00957>] EFLAGS: 00010246 CPU: 1
      • [ 83.764684] EIP is at 0xb6a00957
      • [ 83.764691] EAX: 00000029 EBX: b7318aac ECX: 0000000a EDX: 08601a58
      • [ 83.764700] ESI: 00000007 EDI: 00000029 EBP: bfdf80a8 ESP: bfdf7dcc
      • [ 83.764708] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b
      • [ 83.764718] Process meegotouchhome (pid: 484, ti=f5fba000 task=f517c0b0 task.ti=f5fba000)
    • http://dl.dropbox.com/u/5715485/x86-nemo/Xorg.log
    • http://dl.dropbox.com/u/5715485/x86-nemo/xsession-errors
      • X Error: BadMatch (invalid parameter attributes) 8
      • Extension: 147 (Uknown extension)
      • Minor opcode: 30 (Unknown request)
      • Resource id: 0xab
      • X Error: BadPixmap (invalid Pixmap parameter) 4
      • Major opcode: 54 (X_FreePixmap)
      • Resource id: 0x8000c6
  • missing all QtMobility libraries. (re-apply same fix as in https://bugs.meego.com/show_bug.cgi?id=23299)
  • ia32:WeTab playing Qt Flying Bus have black screen
Personal tools