Thursday, 2021-03-11

T42<edp_17> No, I couldn't try to connect as my whole family is sleeping. 😊 The jolla demo video is played fine in the Gallery app. Does it say the video playback with gst-droid work?00:04
T42<elros34> I guess. You can always confirm with logcat or GST_DEBUG. There should be messages from omx if hardware decoder is used. Is that same device for which you had wrong framerate in dconf? Maybe you have tried different values or removed it previously and that is why it worked?00:05
T42<edp_17> I have not found any mini* service in either 'systemctl list-units -t service --all' nor 'systemctl --user list-units -t service --all'00:06
T42<elros34> pgrep -af mini00:06
T42<edp_17> No, it is a different device. It is the hammerhead.00:06
T42<elros34> ah cm12?00:07
T42<edp_17> @elros34 [pgrep -af mini],
T42<edp_17> @elros34 [ah cm12?], Yes. 12.100:07
T42<edp_17> I gave up the n7000 for a while because I don't know what I changed in my local repo that caused the camera stopped working on fresh builds. So, I moved on to hammerhead to try fixing the video recording. (If it is possible.)00:08
T42<elros34> just idea I wonder whether this warning is important:
T42<edp_17> Could be. mal mentioned last time to check the media_codecs* for the n7000.00:16
T42<edp_17> This is what I got on the hammerhead:
T42<edp_17> The /etc/media_codecs_performance.xml is missing on the n7000 and that symlink is broken on the hammerhead. Should I remove that broken symlink?00:19
T42<edp_17> This is the jolla-camera-hw.txt:
T42<edp_17> and the output of GST_DEBUG=6 mk-cam-conf 0 & 1 /dev/null 2>&1 | grep params_parse | sed -e 's/.*param\s//':
T42<elros34> sure you can remove broken symlinks but unlikely this will change anything just make sure all xml files in system and vendor are symlinked in /etc00:24
T42<edp_17> Some of them are missing:
T42<edp_17> I'll remove this one too.00:27
T42<elros34> there are few default symlinks in droid-config sparse I wouldn't worry about them but you can remove them like that:
T42<edp_17> So, these are not needed? Okay, thanks.00:32
T42<edp_17> @elros34 [there are few default symlinks in droid-config …], Oh, you meant droid-config-device sparse. I've found them in there.00:34
T42<edp_17> @elros34 [ …], Thanks! I'll double check them and will add to all my ports.00:35
T42<edp_17> These two urls do have contrary info. E.g. one of them says to keep '/system/etc/media_codecs_google_video.xml' while the other says to remove it.00:38
T42<elros34> Unknown HAL color format 0x7f000789: video-frame-format = android-opaque = > OMX_COLOR_FormatAndroidOpaque = 0x7F000789 that is from you logs. Maybe you could ask some smart guy whether this is important00:39
T42<edp_17> I am asking him. 😃00:39
T42<elros34> sure I am just a porter like you:) but seriously maybe mal or abranson would know something more about this00:40
T42<edp_17> Is abranson on this channel?00:40
T42<edp_17> I know he is on the fan club one.00:41
T42<edp_17> Yep, he is not in here.00:41
T42<edp_17> Not with tg at least.00:42
T42<elros34> not sure if he is still available here but for sure he was00:42
T42<elros34> btw that delete_file.list correct for my device, do not use same for yours00:42
T42<edp_17> Okay, I see.00:43
T42<edp_17> Right before the camera service dies, the logcat says: "E/DroidMediaCodec( 2109): Received a buffer without a timestamp!"00:47
T42<elros34> you have a lot "Replacing invalid timestamp: 99:99:9" so that could be related00:52
T42<edp_17> Whether is this time stamp used when generating the file name?00:52
T42<edp_17> Interestingly, there are .mp4 files in $HOME/Videos/Camera. All are empty but their file name is correct.00:54
T42<edp_17> Okay, I leave this for now. I'll ask Andrew tomorrow. Now I install the fresh image on the n7000 to see whether camera works there. Annoying, as I only have the camera and bluetooth to fix and the device works fine. (and the camera is fixed on the first build on the device but doesn't work on fresh builds.)00:57
techgeeksterHi to everyone! When building the mw i get this error: Problem: libhybris-libGLESv2- conflicts with mesa-llvmpipe-libGLESv2 provided by mesa-llvmpipe-libGLESv2-19.3.3+git2-1.5.2.jolla.aarch6409:36
techgeekster Solution 1: deinstallation of mesa-llvmpipe-libGLESv2-19.3.3+git2-1.5.2.jolla.aarch6409:36
techgeekster Solution 2: do not install libhybris-libGLESv2-
techgeeksterI tryied removing the mesa-llv... package but the problem remains09:36
*** techgeekster_ is now known as techgeekster09:46
srxlHello all! Looking to start work on a port for a device I have. The HADK talks about using libhybris to make a HAL for my device, but I'd rather avoid that if possible - I already have a (very close to) mainline kernel that works very well for my device. Are there any resources for building a port without libhybris?10:07
techgeeksterProblem solved. I was dumb and did the FAQ Solution in PlatformSDK.11:06
rinigusI have a rare issue of mce starting panic leds after flashing and installing jolla default apps. doesn't seem to occur after reboot. summarized . couldn't see anything special in the logs either11:23
rinigusin the meeting, sledges mentioned something regarding xperia 10 reboots. any idea if it could be related? a fix that I can look into?11:24
*** mal__ is now known as mal13:07
T42<lackingcheesepuffs> I am building droid-hal but it saying this while the build goes on... Will this cause an issue later?13:29
T42<elros34> yes and even it points you to solution in next line13:32
malrun "export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true" before make hybris-hal13:33
T42<swanux> Just wondering if anyone has any ideas for it (still that lipstick situation) -
T42<lackingcheesepuffs> Alright13:39
T42<lackingcheesepuffs> I will try again13:39
mal@swanux which android base? which device?13:40
T42<swanux> mal: dipper (Mi 8) los 16.013:41
maldoes test_hwcomposer work?13:41
T42<swanux> No. It's in the paste (with link to full logcat). Both test_hwcomposer and lipstick logs13:42
maland you run it using EGL_PLATFORM=hwcomposer test_hwcomposer13:43
swanuxYes of course.13:43
malswanux: can you find your generated android-config.h from droid-hal devel rpm?13:46
swanuxmal: Yes, here it is (from droid-hal-dipper-devel.rpm)
malok, so that rules out one possible reason13:50
malis that aarch64 build?13:51
swanuxYes it is.13:51
maldo any other tests work?13:51
swanuxtest_gps, test_dload, test_opencl seem to work13:52
malhopefully you have strace installed, could you run this: EGL_PLATFORM=hwcomposer strace test_hwcomposer &> log.txt13:52
maland then show that log.txt13:53
swanuxmal: Well, I had to stop it manually (as you can see) because the last part loops infinitely otherwise.
malswanux: can you make a quick test, run this on device: ln -s /usr/libexec/droid-hybris/system/lib64/ /usr/libexec/droid-hybris/system/lib64/libGLESv3.so14:08
swanuxI ran it.14:09
malany difference with test_hwcomposer?14:10
swanuxYeah. Now it isn't running infinitely but throwing segfault instead (like lipstick before)14:11
malnew strace please14:12
swanuxHere's the output : (doing strace now...)14:12
malhmm, wait14:12
malswanux: another attempt, remove that /usr/libexec/droid-hybris/system/lib64/ and then make a copy of the /usr/libexec/droid-hybris/system/lib64/ with name /usr/libexec/droid-hybris/system/lib64/libGLESv3.so14:14
swanuxDone. Should I reboot or can I run the test now?14:15
maljust run it again14:15
malmaybe you could reboot also at some point just to be sure14:16
swanuxSame output14:16
swanuxAgain after reboot14:17
swanuxHere's the strace (from the first time after creating the symlink, but as I can see nothing changed) -
malswanux: do you have your config repo in github?14:20
swanuxYes (it's private though). I'll share it in a minute14:20
malok, you are missing something14:23
techgeeksterSmall Question. In the --gg, it produces this error ( ERROR: Git program not found.) Were does it want to install git?14:24
maldoes this help: sudo zypper in git14:24
swanuxmal: What am I missing?14:25
malswanux: I can't see the ld.config.28.txt things in your repo mentioned here
malthe last 3 parts in there14:27
techgeekster'git' is already installed. Maybe it wants git in the Target build? What else could it be?14:27
malthen try: sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in git14:27
swanuxmal: Thanks. I'll push them now manually just to check what they change (will put them in my repo later)14:28
techgeeksterInstalling git in the target solved the previous fault. Now a new one. 'gstreamer-photography-1.0' not found in package names. Trying capabilities. No provider of 'gstreamer-photography-1.0' found.14:42
techgeeksterThe exact error is: Looking for a fallback subproject for the dependency gstreamer-photography-1.014:44 ERROR: Subproject directory not found and gstreamer-plugins-bad.wrap file not found14:44
swanuxmal: I placed those files according to the guide and rebooted, but test_hwcomposer outputs the same as before.14:44
maltechgeekster: ah, sorry, porting is a bit complicated now because latest gst-droid shouldn't be used14:46
techgeeksterOh ok. How can I fix this? Or there is nothing I can do?14:47
maltechgeekster: go to hybris/mw/gst-droid and run "git clean -x -f -d" and then "git reset --hard 0.20201104.0" and then check that the common/ folder in there has content, then back to $ANDROID_ROOT and run rpm/dhd/helpers/ -b hybris/mw/gst-droid14:52
techgeekstermai: got it. trying it now14:53
malswanux: is the ld.config.28.txt mounted, check output of mount14:53
malswanux: also make sure you copied the file correctly (in raw mode)14:53
swanuxmal: Here's the cat from the file - and here's the output of mount - - I don't see it as mounted14:56
malswanux: I don't see it in mount14:57
maldid you reboot?14:57
maldid you symlink the service file correctly?14:58
T42<lackingcheesepuffs> @elros34 [yes and even it points you to solution in next …], When building droid-hal in platform sdk I face this14:58
T42<lackingcheesepuffs> Is this something to do with my defconfig?14:58
T42<elros34> probably, mer-kernel-check finished without errors?14:59
swanuxmal: I think so. I checked and it doesn't seem to be broken, and rebooted again (just in case) but no change in mount15:00
malswanux: meaning /usr/lib/systemd/system/system-etc-ld.config.28.txt.mount is a file and /usr/lib/systemd/system/ is a symlink pointing to that earlier file (ln -s ../system-etc-ld.config.28.txt.mount /usr/lib/systemd/system/
malswanux: note the paths in faq used the old /lib location15:00
malI should fix that15:00
techgeekstermal: The git reset solution worked. Thanks!15:10
swanuxmal: I changed the paths, here's the mount output now ( still can't see it) and the commands after that (which show that the files - I think - are at proper locations)
malswanux: show content of /usr/lib/systemd/system/system-etc-ld.config.28.txt.mount15:16
malswanux: btw, do you even have file /system/etc/ld.config.28.txt15:17
swanuxI have that file under usr/libexec/droid-hybris/system/etc/ld.config.28.txt ... I guess new location here too (?)15:18
malswanux: I asked if there is a file /system/etc/ld.config.28.txt15:20
swanuxmal: here's the contetn:
swanuxNo, there isn't15:20
malso then the service won't work, can you show the content of any ld.config file in /system/etc/15:21
malif there are any15:21
swanux There is one15:22
swanuxmal: Soo, how to proceed?15:31
malnot sure yet15:36
T42<edp_17> @elros34 : Is it possible to install your mouse tracker without patchmanager? (On sfos I cannot install it with patchmanager.) Thanks.15:46
techgeeksterWhen building with --mic, this error appeared (Error <creator>[03/11 15:41:13] : Unable to find pattern: Jolla Configuration raphael). I tried upgrading tooling and target. Everything is on Still the error stands15:46
malswanux: just to verify, you have fully aarch64 based build?15:48
T42<elros34> @edp_17 should be possible if you ignore dependencies and then apply patch manually. You can also use pm2:
malswanux: noticed that one patch is missing from hybris-16.0 base for aarch6415:48
T42<edp_17> Thanks @elros34 !15:49
swanuxmal: Yeah, I think so.15:50
T42<elros34> @techgeeksterlooks looks you have outdated target/tooling15:51
malswanux: so PORT_ARCH is aarch64?15:51
techgeeksterThis is the result of sdk-foreach-su -ly ssu re (
malI will push the needed fixes to github soon15:52
maltechgeekster: is that port using PORT_ARCH aarch64?15:53
T42<elros34> @techgeekster do you really updated it or just set release with ssu? I ask because " Jolla Configuration" is not used anymore on 4.0.1.x15:53
mal@elros34 probably the issue that aarch64 mic builds have issues because of broken sed15:53
malin build_packages.sh15:54
techgeeksterI've started with outdated tooling but did this ( run "sdk-foreach-su -ly ssu re" then "sdk-foreach-su -ly zypper ref" and finally "sdk-foreach-su -ly zypper dup")15:54
T42<elros34> mal: no, that is different error. It's because latest target/tooling points to 3.4.0.x15:54
malswanux: looks like I forgot to push the changes before, I have had the needed changes locally since november15:55
swanuxWhich repo?15:55
malswanux: hybris-patches, I will check that my commit is ok before pushing15:55
T42<elros34> @techgeekster check with sb2 /etc/os-release in target15:56
mal@elros34 are you sure? the ssu re looked ok15:58
T42<elros34> mal: I thinks so.  "Unable to find pattern: Jolla Configuration raphael" shouldn't happen on 4.0.1. FOr sed issue he should have 'Unable to find patterns-sailfish-device-configuration-raphae'15:59
T42<elros34> @techgeekster do you use meta packages for patterns? Do you in droid-config patterns/*.inc files?16:01
techgeekster@T42 Not sure, let me check16:03
maltechgeekster: check .ks file in $ANDROID_ROOT does it have any adaptation* repos in the repo list16:05
T42<elros34> and whether you have pattern or package in %packages section of ks file16:07
techgeekster@Jolla Configuration raphael16:07
T42<elros34> rebuild droid-config and then check that file in droid-local-repo/$DEVICE/droid-config/droid-config-$DEVICE-ssu*.rpm16:09
techgeeksterOk. Should I delete the .ks file?16:09
techgeeksterIn order to start "clean"?16:10
T42<elros34> you can but it should be generated every time --mic is used16:10
malswanux: download (as raw file) and apply this to frameworks/native16:38
swanuxmal: I downloaded it. How do I apply it? (sorry for the stupid question)16:43
malswanux: copy it to that frameworks/native folder and run git am 0007-hybris-Fix-loading-64-bit-EGL-libraries.patch16:47
malof course in that folder16:47
T42<lackingcheesepuffs> @mal [swanux: download (as raw file) and apply this …], is this required for android 10?16:48
malandroid 10 has that already, this is for android 916:48
malhmm, actually no16:49
mal@lackingcheesepuffs I need to check that16:50
mal@lackingcheesepuffs looks like that was also missing from hybris-17.116:53
T42<lackingcheesepuffs> oof, so do I need to apply patch before building android hal?16:54
malyes, there are two patches I added to hybris-17.116:55
malnot yet merged16:56
swanuxHow to resolve that error?16:58
malswanux: I have no idea how that is possible17:00
malswanux: is there file opengl/libs/EGL/Loader.cpp in frameworks/native?17:01
swanuxmal: Yes17:02
maltry running "git fetch github" first17:05
swanuxDone. Same output on apply attempt17:07
malwhat does git log say17:10
swanuxHere's the first 3 commit from log:
malswanux: wait that is from your frameworks/native? does git diff show something?17:18
malswanux: run git am --abort17:18
swanuxSure it does
malswanux: so did you accidentially run hybris-patches/ instead of hybris-patches/ --mb?17:20
malanyway after the git am --abort run patch -p1 < 0007-hybris-Fix-loading-64-bit-EGL-libraries.patch17:21
deathmist_mal: any idea about I can't seem to boot SFOS 4.0 on hybris-16.0/arm32 after updating submodules and such17:24
maldeathmist_: did you move systemd service to /usr/lib from /lib also which kernel version does the device?17:25
malso many typos in my comment17:26
deathmist_mal: 4.4 kernel and yes I did that back when SFOS 3.4 was current as per your previous suggestion:
swanuxmal: To be honest I built it so many times in the previous weeks and tried so many variations that I have no idea at all17:27
swanuxOk, I patched it.17:27
malswanux: then make hybris-hal as usual and package droid-hal17:27
maldeathmist_: can you show output of mer kernel checker for you kernel, make sure you have latest kernel checker first17:28
swanuxSo I need only the rootfs to be repackaged, not the boot.img? (after rebuilding of course17:28
malswanux: or you can manually install the needed droid-hal rpms for testing directly to device17:30
swanuxGood to know. So every rpm from droid-hal?17:30
malno, only those that have been installed before17:31
deathmist_mal: I suppose droid-hal-$DEVICE.log works too since it contains that output:
swanuxmal: So not everything is installed from droid-local-repo/droid-hal-DEVICE?17:32
maldeathmist_: yes, assuming you had updated to latest kernel checker before that17:32
maldeathmist_: should be easy to rerun it if you have the out/ still in your build env17:32
maldeathmist_: did you do the changes in the init.rc patch mention in the chat log?17:33
deathmist_mal: seems to be the same output and if you mean yes I manually commented out the remaining lines mentioning cg2_bpf (mount was already commented during droid-hal build)17:38
deathmist_ah, because of droid-hal that mount was ofc turned into a systemd unit, let me try masking it17:40
maldeathmist_: what do you mean?17:41
malah, yes, it might be running on device in theory17:41
deathmist_hmm that didn't seem to help still17:44
deathmist_still same "systemd[1]: System is tainted: var-run-bad" with "API bus" and "system bus" errors after D-Bus is started17:46
maldeathmist_: show output of mount17:49
maldeathmist_: is /var/run a symlink17:51
deathmist_nope, directory17:51
deathmist_seems it should point to /run?17:51
malwondering why it's like that17:52
maldeathmist_: on my xa2 with 4.4 kernel also I have /var/run -> ../run17:52
deathmist_I'll remove the dir from recovery and create the symlink17:53
deathmist_or is there some info you'd like from me before I do that?17:53
maldeathmist_: the hint for that was "System is tainted: var-run-bad"17:53
T42<elros34> check whether systemd-tmpfiles-setup.service create that directory17:53
deathmist_mal: @elros34 on my rootfs inside the flashable zip /var/run exists as a directory containing connman, console, faillock & vpnc subdirs17:55
deathmist_(those subdirs are all empty)17:57
deathmist_I assume this isn't normal?17:58
maldeathmist_: I check some image I made, those have just the symlink17:58
maldeathmist_: how did you build the image, using manual mic command or using --mic?17:59 --mic17:59
maldeathmist_: one thing to run if you still can, rpm -qf /var/run17:59
deathmist_file /var/run is not owned by any package18:00
malare the folders under it owned by something?18:01
deathmist_/var/run/{console,faillock} are both owned by pam-1.3.1+git1-1.2.1.jolla.armv7hl, vpnc /var/run/{connman,vpnc} aren't owned by anything however18:03
malthose are normal18:05
malwondering what goes wrong during mic build18:06
deathmist_I can send a build log if you'd like18:06
maldeathmist_: why do you have this custom version
deathmist_mal: the default hybris-boot installer ( + didn't work for me due to broken TWRP tar, so I went an extra mile and created a custom one @ (I also do a few other smaller things on top of just working around broken tar)18:13
T42<elros34> maybe running something like: 'rpm -qp --scripts *-* | grep /var/run' in /srv/mer/sdks/sfossdk/var/tmp/mic/cache/packages could reveal if there is some package which create that directory18:13
deathmist_I did check if that file needed updating before updating to 4.0 however and it didn't seem like it was touched in years18:13
maldeathmist_: how long have you had that custom installer?18:13
deathmist_since the beginning pretty much :p18:14
deathmist_Jul 2019, when was current18:14
maldeathmist_: just wondering that the difference there is the --numeric-owner option, maybe it's not critical then18:14
maldeathmist_: so the zip already has the folder instead of symlink?18:15
malso then installation is then not the problem18:15
deathmist_the rootfs .tar.bz2 yes, it has /var/run directory as I described earlier18:15
maldeathmist_: can you check output of "sdk-foreach-su -ly ssu re"18:17
maldeathmist_: in your 3.4.0 build in ci the symlink is correct18:19
deathmist_really odd issue, removing the dir and adding the proper symlink in manually does fix the issue for now though18:34
maldeathmist_: does a new image build result in the same folder?18:36
deathmist_let me try18:36
techgeeksterWhere in the rpm/dhd/helpers/ script is the kernel_check called?18:39
malit's not in the script, it's in the inc file used in droid-hal spec18:40
techgeeksterOh okk. Thank you!18:42
deathmist_mal: another mic image build still resulted in /var/run directory with the 4 empty subdirs getting created inside rootfs.tar.bz218:43
maldeathmist_: anything obvious in build log?18:45
deathmist_mal: searching for "/run" at least didn't yield anything in here's also "rpm -qp --scripts *-* | grep /var/run" as per @elros34's suggestion
T42<Chrisme69> @Miklos have you got any idea about nexus 5 not starting after a Sfos 3.2 reflash cover Cm12.1?18:52
T42<Chrisme69> I tried the Cm 12.1 unofficial and even this version by itself doesn't start18:53
T42<Chrisme69> Then I tried with a Cm12.1 yoga: it starts but then the overwritten sfos doesn't boot18:54
T42<elros34> @deathmist: error: filesystem-3.1+git4-1.2.1.jolla.noarch: install failed. filesystem provides that symlink18:59
deathmist_@elros34 aha, makes more sense now as that was indeed not installed on my device, BUT a "zypper in filesystem" just worked strangely enough on device after the fact19:03
deathmist_installing the package also fixed practically all apps crashing, seems it's pretty critical ;) (hint: mic should fail if that package fails to install for whatever reason)19:16
deathmist_I suppose now that my hybris-16.0/arm32 port is working again I can attempt going over to arm64, and then finally attempt migrating to hybris-17.1 once again19:21
T42<elros34> Did you figure out why it fail? Maybe findmnt will show some unusual permissions on /sys. At least error suggest sysfs issue19:22
T42<elros34> on my host /sys have dr-xr-xr-x  root:root19:27
malwhat could cause that filesystem package failure19:30
deathmist_@elros34 I've got the same, for now I'm assuming it's due to the fact that I was running platform SDK (chroot) inside a systemd-nspawn container so I'll do a re-test soon with platform SDK setup on my host instead19:37
deathmist_I was building all of SFOS + HAL stuff inside the container so I had a clean env and so I could write personal instructions on what deps were needed as the Ubuntu 14.04 HA BUILD chroot is practically useless now that repo needs Python 3.5+19:38
T42<elros34> repo for python2 is still available at android.com19:40
deathmist_oh well, I notiecd HAL build times were noticeably faster on my host as well and I'd rather not deal with building Android 10 under Ubuntu 14.04 soon anyway ;)19:44
maldeathmist_: I do my hybris-hal builds directly on ubuntu 20.04, just need some small things usually19:57
malexcept fp2 for which I do those still in ubu-chroot19:58
rinigusafter OTA (3.4 -> 4.0.1) is finished (version --dup) and screen is off, pressing power button shows GUI for a sec, then blank screen, and then leads to reboot. after automatic OTA induced boot image update, reboots into GUI. is such reboot after OTA expected now?20:01
rinigusissue with log
T42<Chrisme69> An info. I don't know if this is the right group. I'm trying to install Sfos 3.2 on a nexus 5 (hammerhead)  without results20:28
malwhere did you get the image for that?20:28
malwhat problem do you have?20:29
T42<Chrisme69> I'm flashing it over a CM12.1 unofficial but It doesn't work20:29
malyou mean installation fails?20:29
malor booting it fails?20:29
T42<Chrisme69> Cm12.1 doesn't boot even.20:30
T42<Chrisme69> I tried the yoga one and that's starts20:30
T42<Chrisme69> Then I tried to flash sfos over it 3.220:30
T42<Chrisme69> And doesn't start20:31
T42<Chrisme69> Boot20:31
T42<Chrisme69> The only sfos that worked over a Cm 13 was a sfos 3.0.3 that hasn't got any sfos opportunity20:31
T42<Chrisme69> That's the post where I took some instructions20:33
malwhy did you install sfos 3.2?20:34
T42<Chrisme69> Cause it had android support20:35
T42<Chrisme69> I tried the 3.2.020:37
T42<Chrisme69> And the 3.420:37
T42<Chrisme69> Now I'm downloading 4.0.120:38
T42<Chrisme69> But has some issues with android support20:38
malso installation works fine?20:45
T42<Chrisme69> Not at all20:46
T42<Chrisme69> The only one that works is the 3.0.3 from cm 1320:46
T42<Chrisme69> Then I do not manage to.upgrade to other versions20:47
T42<Chrisme69> Tried 3.3 sfos and installation came to the language choice but touch screen wasn't working. It booted in half an hour. It's a lot20:59
mal@edp_17 are you still doing hammerhead, maybe you could help ^21:06
T42<Chrisme69> Yess21:08
T42<Chrisme69> Now trying with 4.0.121:14
T42<Chrisme69> Thank's a lot. Hope @edp_17 can help me. He already helped me finding the files hosted on talk.maemo21:23
deathmist_any ideas where this "bash: Pictures: unknown operand" line could be coming from twice when opening a shell session for "defaultuser"? I'll go digging for this if no one else knows22:12
deathmist_oh it comes from one of my extra additions to /etc/profile.d/ xD I'll need to fix that22:23
deathmist_/bin/bash: symbolic link to ../usr/bin/busybox well that explains things22:26
malyeah, sounded like something you had done to environment22:26

Generated by 2.17.1 by Marius Gedminas - find it at!