Is it possible to install CSSU in the SDK?
 

Just tried it but ended up in a deeply broken apt state.
Anyone tried?

Re: Is it possible to install CSSU in the SDK?
 

FREMANTLE_ARMEL yes, FREMANTLE_X86 not so much.

Due to technical difficulties, being my internet sucks, I only upload armel binaries.

You can pull sources from git and build on X86 target though.

Re: Is it possible to install CSSU in the SDK?
 

UPDATE: See below

Looks like I'm doing something wrong:

Quote:

[sbox-FREMANTLE_ARMEL: /etc/apt/sources.list.d] > fakeroot apt-get install mp-fremantle-community-pr Reading package lists... Done Building dependency tree... Done 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. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: mp-fremantle-community-pr: Depends: modest (>= 3.90.7-9) but it is not going to be installed Depends: hildon-home (>= 0.3.71-7) but it is not going to be installed Depends: hildon-desktop (>= 1:2.2.142-16) but it is not going to be installed Depends: hildon-application-manager (>= 1:2.2.72-4) but it is not going to be installed Depends: hildon-status-menu (>= 0.3.40-5) but it is not going to be installed Depends: osso-applet-display (>= 1.5.4+0cssu1) but it is not going to be installed Depends: osso-applet-notificationlight (>= 0.0.8+0cssu1) but it is not going to be installed Depends: osso-calculator (>= 2.0-1+0cssu1) but it is not going to be installed Depends: osso-calculator-ui (>= 2.0-1+0cssu1) but it is not going to be installed Depends: hildon-control-panel (>= 1:2.2.27-5) but it is not going to be installed Depends: libcpaboutcssu (>= 1.0+0cssu3) but it is not going to be installed Depends: status-area-orientationlock-applet (>= 1.0+0cssu3) but it is not going to be installed Depends: camera-ui (>= 1.1.29.2+0cssu6) but it is not going to be installed Depends: maemo-statusmenu-fmtx (>= 0.12+0cssu2) but it is not going to be installed Depends: osso-pdf-viewer (>= 1.8.24-2+0cssu3) but it is not going to be installed Depends: qtm-maemo-metapackage but it is not going to be installed Depends: dsme-thermalobject-surface but it is not going to be installed Depends: libqt4-declarative (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-svg (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-webkit (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-maemo5 (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-gui (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-multimedia (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-phonon (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqt4-opengl (>= 1:4.7.4~git20110505+cssu5) but it is not going to be installed Depends: libqtm-messaging (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-sensors (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-systeminfo (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-bearer (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-multimedia (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-contacts (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-location (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-versit (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: libqtm-serviceframework (>= 1:1.0.2-maemo4+0m5+0cssu1) but it is not going to be installed Depends: modest-home-applet but it is not installable PreDepends: maemo-optify-runonce but it is not installable E: Broken packages

Quote:

[sbox-FREMANTLE_ARMEL: /etc/apt/sources.list.d] > cat /etc/apt/sources.list deb http://repository.maemo.org/ fremantle/sdk free non-free deb-src http://repository.maemo.org/ fremantle/sdk free deb http://repository.maemo.org/ fremantle/tools free non-free deb-src http://repository.maemo.org/ fremantle/tools free # Repository for Nokia Binaries, added by Maemo 5.0 SDK Installer deb http://repository.maemo.org/community-testing/ fremantle free non-free [sbox-FREMANTLE_ARMEL: /etc/apt/sources.list.d] >

Re: Is it possible to install CSSU in the SDK?
 

UPDATE: See below

Added Nokia binary repo and switched to community-ssu-enabler

Quote:

Setting up community-ssu-enabler (0.6-6) ... Please accept the license agreement displayed on your N900's screen. dpkg: error processing community-ssu-enabler (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: community-ssu-enabler E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an error code (1) [sbox-FREMANTLE_ARMEL: /etc/apt/sources.list.d] >

I didn't run Xephyr this time because last time it changed my target from armel back to x86. Trying again with Xephyr.

Re: Is it possible to install CSSU in the SDK?
 

UPDATE: See below

Quote:

$ cat /usr/local/bin/start_xephyr.sh | grep X86 /scratchbox/login sb-conf select FREMANTLE_X86

Ok, got it.

Re: Is it possible to install CSSU in the SDK?
 

UPDATE: See below

Xephyr is not starting with ARMEL target:

Quote:

$ /usr/local/bin/start_xephyr.sh [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list! [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Keyboard is not running hildon-desktop is not running Sapwood image server is not running D-BUS session bus daemon is not running DBUS system bus is not running Stopping Maemo Launcher: maemo-launcher not running. Note: For remote X connections DISPLAY should contain hostname! Sample files present. Starting DBUS system bus Starting D-BUS session bus daemon Starting Maemo Launcher: maemo-launcher. defender: died my parent is not who he claims to be maemo-launcher: warning raising the oom shield for pid=2282 status=2816 getsockopt level=1 optname=17 not yet supported Starting Sapwood image server getsockopt level=1 optname=17 not yet supported Error setting value: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported Error setting value: No D-BUS daemon running Starting hildon-desktop maemo-launcher: invoking '/usr/bin/hildon-desktop.launch' maemo-launcher: invoking '/usr/bin/hildon-status-menu.launch' maemo-launcher: invoking '/usr/bin/hildon-home.launch' Starting Keyboard Initializing trackerd... getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported process 2377: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235. This is normally a bug in some application using the D-Bus library. process 2377: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235. This is normally a bug in some application using the D-Bus library. process 2377: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235. This is normally a bug in some application using the D-Bus library. process 2377: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235. This is normally a bug in some application using the D-Bus library. process 2377: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3099. This is normally a bug in some application using the D-Bus library. qemu: Unsupported syscall: 314 qemu: Unsupported syscall: 314 maemo-launcher: opening of /usr/bin/hildon-status-menu.launch took 7129 usec maemo-launcher: opening of /usr/bin/hildon-home.launch took 17756 usec maemo-launcher: opening of /usr/bin/hildon-desktop.launch took 20917 usec Starting log: File:'/home/i/.local/share/tracker/trackerd.log' getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported process 2356: arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5257. This is normally a bug in some application using the D-Bus library. getsockopt level=1 optname=17 not yet supported unable to dump 00096800 getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported unable to dump 000e2800 getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported process 2335: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. process 2335: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298. This is normally a bug in some application using the D-Bus library. process 2335: arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1395. This is normally a bug in some application using the D-Bus library. getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported GConf Error: No D-BUS daemon running getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported getsockopt level=1 optname=17 not yet supported X connection to :0 broken (explicit kill or server shutdown). The application 'sapwood-server' lost its connection to the display :2.0; most likely the X server was shut down or you killed/destroyed the application. The application '/usr/bin/hildon-desktop' lost its connection to the display :2.0; most likely the X server was shut down or you killed/destroyed the application. maemo-launcher: child (pid=2335) terminated due to exit()=1 Stopping Keyboard Keyboard is not running maemo-launcher: child (pid=2336) terminated due to exit()=1 Stopping hildon-desktop hildon-desktop is not running Stopping Sapwood image server Sapwood image server is not running Stopping D-BUS session bus daemon Stopping DBUS system bus Stopping Maemo Launcher: maemo-launcher. $ ps aux | grep mae i 2282 0.0 0.0 101124 6892 ? S 01:24 0:00 /scratchbox/devkits/qemu/bin/qemu-arm-sb --sbox-call /usr/bin/maemo-launcher /usr/bin/maemo-launcher --daemon --booster gtk i 2337 1.6 0.1 137692 16424 ? Ss 01:24 0:00 /scratchbox/devkits/qemu/bin/qemu-arm-sb --sbox-call /usr/bin/maemo-launcher /usr/bin/maemo-launcher --daemon --booster gtk i 2386 0.0 0.1 137692 16424 ? S 01:24 0:00 /scratchbox/devkits/qemu/bin/qemu-arm-sb --sbox-call /usr/bin/maemo-launcher /usr/bin/maemo-launcher --daemon --booster gtk i 2387 0.0 0.1 137692 16424 ? S 01:24 0:00 /scratchbox/devkits/qemu/bin/qemu-arm-sb --sbox-call /usr/bin/maemo-launcher /usr/bin/maemo-launcher --daemon --booster gtk i 2391 1.2 0.1 137692 16424 ? S 01:24 0:00 /scratchbox/devkits/qemu/bin/qemu-arm-sb --sbox-call /usr/bin/maemo-launcher /usr/bin/maemo-launcher --daemon --booster gtk i 2609 0.0 0.0 5548 852 pts/0 R+ 01:25 0:00 grep --color=auto mae

Re: Is it possible to install CSSU in the SDK?
 

UPDATE: See below

Trying to investigate it:

Quote:

[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install mp-fremantle-community-pr Reading package lists... Done Building dependency tree... Done 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. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: mp-fremantle-community-pr: Depends: osso-applet-display (>= 1.5.4+0cssu1) but it is not going to be installed Depends: osso-applet-notificationlight (>= 0.0.8+0cssu1) but it is not going to be installed Depends: osso-calculator (>= 2.0-1+0cssu1) but it is not going to be installed Depends: osso-calculator-ui (>= 2.0-1+0cssu1) but it is not going to be installed Depends: camera-ui (>= 1.1.29.2+0cssu6) but it is not going to be installed Depends: maemo-statusmenu-fmtx (>= 0.12+0cssu2) but it is not going to be installed Depends: osso-pdf-viewer (>= 1.8.24-2+0cssu3) but it is not going to be installed Depends: modest-home-applet but it is not installable PreDepends: maemo-optify-runonce but it is not installable E: Broken packages [sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install camera-ui Reading package lists... Done Building dependency tree... Done 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. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: camera-ui: Depends: osso-camera-ui-l10n-mr0 but it is not installable or osso-camera-ui-l10n-mr but it is not installable E: Broken packages [sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install osso-camera-ui-l10n-mr Reading package lists... Done Building dependency tree... Done Package osso-camera-ui-l10n-mr is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package osso-camera-ui-l10n-mr has no installation candidate

Re: Is it possible to install CSSU in the SDK?
 

Tried to install in the virtual image of the SDK. And it didn't work either.
But at last I've found the answer:
Unable to get N900 display in Xephyr when in ARMEL mode -> http://wiki.maemo.org/Documentation/...ues_in_the_SDK:
MohammadAG, do you test everything directly on the device?

Re: Is it possible to install CSSU in the SDK?
 

Yes, I've never bothered with scratchbox emulation after I had my device.

Re: Is it possible to install CSSU in the SDK?
 

You can use armel madde qemu emulation.