<freemangordon>
this is without changing the platform plugin
<freemangordon>
just adding second group
<freemangordon>
Wizzup: please have a loop at qpa patch I posted ^^^
<Wizzup>
freemangordon: patch looks like, feel free to commit
<Wizzup>
also you can as far as I am concerned just push these to another branch instead of pastebinning ti, but whatever works
<Wizzup>
uvos__: let me try this featherpad
<freemangordon>
ok, but later on, have to run now
<Wizzup>
ttyl
<freemangordon>
well, new branch for such a patch looks like an overkill to me
<freemangordon>
ttyl
<Wizzup>
branches are cheap, they point to a commit :)
<Wizzup>
but sure
<freemangordon>
yeah, but I have to waste time to delet them later
<freemangordon>
anyway
Livio has joined #maemo-leste
<Wizzup>
freemangordon: uvos__: with the qmenu sub menus being supported, should we attempt to hide the qmenubar by default?
<freemangordon>
Ithink yes
<uvos__>
Wizzup: yes deffinatly
<uvos__>
i am hideing it with ctrl-m everywhere this is supported
<uvos__>
pcmanfm-qt is also very nice with this menu
<Wizzup>
cool, I'll see if I can figure out if we can hide the menus somehow
<amunizp>
OK I now see the welcome to Leste page on the n900 I did not see that before. got excited and unplugged the phone.
<Wizzup>
amunizp: are you struggling with the lock code still? I saw your email, I am a bit surprised, I don't know what else would prefer the lock code, you're sure it's not the pinm dialog I guess?
<Wizzup>
uvos__: btw, so you agree that headset works for HiFi, just not for calls, right?
<Wizzup>
on mapphones
<Wizzup>
at least in pulseaudio I think I saw a headset mic show up and I think it responded to me tapping the headset mic, but I am not 100% sure
<Wizzup>
I understand there's kernel work to do, just trying to understand the scope
<Wizzup>
I try to regulary have calls when I'm riding my bicycle for an hour or two and it's really hard to do this on speaker or handset, so I have some motivation to fix it :D
<amunizp>
hi @Wizzup I am now logged into the n900 and I even ran the expandcard.sh
<amunizp>
the problem I guess is that I was able to boot leste by connecting to my ubuntu machine but the lock code will probably go on again if I reboot the n900 and try to log into it.
<amunizp>
can I get to the original partition from within leste?
<amunizp>
maybe /etc/X11/Xsession.d/04devlock-blocker might be there and not in the new leste installation?
<uvos__>
Wizzup: i dont know if i ever tried that, but in theroy it should work for hifi, yes
<uvos__>
we cant determine between headset and handset on plug
<uvos__>
so you may have to change the mixers by hand
xmn has joined #maemo-leste
<uvos__>
the hp type information is acessed by android through a cpcap-mcu macro that writes some values into a mailbox somewhere
<uvos__>
the manline kernel dosent support any of that
<Wizzup>
uvos__: I understand, thank you, the cpcap-mcu info part was missing for me
<amunizp>
Ok tried finding the original maemo instalation in /mnt but nothing is there.
<Wizzup>
I should do a bit more checking but I think pavucontrol was able to (somehow?) differentiate
<Wizzup>
amunizp: so if you're in leste then you're mostly there
<Wizzup>
amunizp: just run the tools to crack the lock code that I linked earlier
<uvos__>
Wizzup: it should work fine besides not autodetecting
System_Error has joined #maemo-leste
<Wizzup>
ok
<Wizzup>
and for calls, do we just lack the alsamixer control to have the right regs set?
<amunizp>
ah OK if I did the expansion it is safe to connect to wifi?
<Wizzup>
(and the corresponding kernel/driver parts for the cotnrol)
<uvos__>
Wizzup: probubly unless you also need to tell the modem about it (probubly not)
<Wizzup>
amunizp: sure, should be, why would it not be?
<Wizzup>
uvos__: ok, ty
<amunizp>
something about makin sure there is swap?
<Wizzup>
amunizp: I think there should be swap set up now, is there not?
<Wizzup>
amunizp: for this 'cal' where the lock code is stored is accessible directly from leste, you don't need to find the fremantle partitions AFAIK
<amunizp>
The welcome text is inviting me to install zram-tools but I guess I need wifi for that.
<Wizzup>
I think you can ignore this, this text is generic
<Wizzup>
swap should be set up already
<amunizp>
cool
<Wizzup>
just type 'free' in terminal
<amunizp>
yep 746428 total swap
<amunizp>
thanks!
<Wizzup>
cool
<amunizp>
not sure I understand this: for this 'cal' where the lock code is stored is accessible directly from leste, you don't need to find the fremantle partitions AFAIK
<dsc_>
freemangordon: ah cool @ checkable
<amunizp>
/etc/X11/Xsession.d/04devlock-blocker this file is not there.
<dsc_>
freemangordon: i like it
nela has joined #maemo-leste
<dsc_>
qscrollarea exists for scrolling stuff, maybe a good idea there
<Wizzup>
amunizp: so the lock code is stored on special part of flash or something
<Wizzup>
amunizp: and you can access it from userspace using some tools
<Wizzup>
and then you jus need to read the lock code hash with the tools and then use john (the ripper) to crack it to get your lock code back
<Wizzup>
I am not intimitaly familiar with the details but others might have more concrete info
<amunizp>
got it at moment the recoverlock package is not there. I will try the other one.
<amunizp>
I washoping to just get into the special part of the flash and just delete it. not really interested in recovering.
<Wizzup>
yeah the package I linked is part of the original maemo
<Wizzup>
I would just download the _all.deb, extract it, and look at the script
<Wizzup>
it might just work
<amunizp>
Ok i will try wget. had forgotten how patient I was 10 years ago typing this stuff out.
<Wizzup>
I think what do you for .deb kpkgs is
<Wizzup>
mkdir mypkg;
<Wizzup>
ar x /path/to/pkg
<Wizzup>
tar xf data.tar.gz
<Wizzup>
and then you should have the _all.deb pkg contents
<amunizp>
oh. I think I see what you mean I did sudo dpkg on the deb package and it asked for john. John now is asking for john-data... I will pull this thread and if it does not get anywhere I will try to extract
<Wizzup>
if sudo dpkg -i works that is fine too
<Wizzup>
then just run apt-get install -f
<sicelo>
or -R (instead of -x) if you need the control files, etc.
<Wizzup>
and it might just pull john and john-data
<Wizzup>
looks like it should
<Wizzup>
The following additional packages will be installed: john-data
<Wizzup>
The following NEW packages will be installed: john john-data
<amunizp>
apt-get install -f seems to be working fetching john and john-data thanks!
<amunizp>
recoverlock returned error exit status 127
<amunizp>
hum ran it anyway.
<amunizp>
hahaha
<amunizp>
begining to crack (...) Done! Your lock code should be : awk: cannot open /tmp/lockcode.pot (no such file or directory) rm: cannot remove (...)
Livio has quit [Ping timeout: 268 seconds]
<Wizzup>
what was the error when trying to finish the install
<amunizp>
the post removal script subprocess trunred error exit status 127 @Wizzup
<amunizp>
update-sudoers:not found
<Wizzup>
dpkg -L recovercode and maby see if you need to run it as root
<amunizp>
it then trys to script from new package instead and hits the same problem: post removal script sub process returned error exist status 127
<Wizzup>
yes, this is expected, this is just debian stuff
<Wizzup>
debian/postinst fails since we don't use update-sudoers anymore for a long time
<Wizzup>
but it might not be fatal, you just need to sniff around a bit
<amunizp>
using sudo dpkg -L says package recoverlock(...).deb is not installed and ofers me to look at conents
<Wizzup>
sorry, I would just extract the script and run it as sudo.
<Wizzup>
It'll take a lot more time to somehow try to fix this the 'proper' way
<amunizp>
haha OK let me do that then.
<Wizzup>
if someone is inclined they can take the _all.deb pkg and repackage it for leste
<Wizzup>
then we can fix the postinst while we're at it
<sicelo>
amunizp: you're running this under leste? or fremantle?
<Wizzup>
leste
<amunizp>
leste. I can't get into fremantle. @sicelo
<Wizzup>
amunizp: did you try to just run the recoverlock script as root
<amunizp>
yes sudo recoverlock give the same result.
<amunizp>
funny that it runs at all given that dpkg says it is not installed.
<sicelo>
no idea if leste is able to find/read the correct place in mtd. did you try rescueOS?
<Wizzup>
leste can read cal.
<amunizp>
I was going to but I lost the name of it after I had to restart computer and lost IRC convo.
<Wizzup>
we have irc logs, see the topic
<Wizzup>
sicelo: leste can ask for pin and verify it, so it can access cal
<sicelo>
ah, yes
<amunizp>
ohh. irc logs and topics I had really forgotten all about this. thanks.
<amunizp>
OK since I am here let me follow the depack path for a bit
<amunizp>
OK extracted and found recoverlock under user/bin
<Wizzup>
maybe just analyse the script and see what it does
<Wizzup>
then you cna maybe see what goes wrong
<Wizzup>
brb
<sicelo>
where's the deb? i'd like to have a look as well
<amunizp>
ran it in the folder $sudo ./recoverlock and I get the same error as before.
<sicelo>
what do you have in /tmp/lockcode (i.e. not .pot)?
<amunizp>
Ok thanks! bootloader, confit, log, kernel, initfs, roootfs
<amunizp>
but the apt install mtd-utils fails because recoverlock needs to be rreinstalled.
<sicelo>
you don't need mtd-utils
* sicelo
suspects john's arguments work differently now ...
<sicelo>
what do you have in /tmp/lockcode (i.e. not .pot)?
<amunizp>
there is'nt a file called lockcode in /tmp
<sicelo>
there should be, after you've run the script
<amunizp>
right? I am also puzzled.
<sicelo>
did you `set -x` ?
<amunizp>
I think I need to make sure those mtd are there.
<sicelo>
the mtd are there of course :-)
<sicelo>
13:39 < amunizp> Ok thanks! bootloader, confit, log, kernel, initfs, roootfs <<< here they are
<sicelo>
cal (where pin is) is the "config" partition
<sicelo>
that's what you're after
<amunizp>
OK that should be mtd1.
<Wizzup>
I think he's saying that /dev/mtd1 being empty is the problem, no?
<Wizzup>
I don't know if ti's actually empty of course
<amunizp>
OK
<amunizp>
I was doing nano on mtd1 and it was looking empty.
<sicelo>
no, it's not a file in that sense :-)
<amunizp>
so I did $ sudo cat mtd1 and I got loads of ???
<sicelo>
you can `cat /dev/mtd1` though
<amunizp>
so the script seems to take out the tail of that file.
<sicelo>
anyway, it just can't be empty ... for the same reason - your pin is there, so if device knows you have a pin, it means your mtd1 is in good shape (somewhat)
<amunizp>
OK lemme try runnig this directly: sudo (grep -A 13 lock_code /dev/mtd1|tail -n 1): > /tmp/lockcode
<amunizp>
ohh. how to I get | on the n900 keyboard?
<Wizzup>
I think blue arrow and then sym/ctrl button
<amunizp>
haha that did something wierd to the cursor.
<Wizzup>
are you sure? it should bring up the special keys keyboard
<Wizzup>
press the blue array on the left, and then button baove it
<Wizzup>
above it*
Livio has joined #maemo-leste
<amunizp>
where should I be seeing the special keys? I ssee ctrl, tab, ex , pgup pgdn
<Wizzup>
it will pop up when you press the key combination that I mentioned
* Wizzup
boots his leste n900 to verify
<amunizp>
really apreciate this hand holding.
<amunizp>
great. should have not installed recoverlock now because it is in a limbo I cannot sudo apt update. because it is asking for me to reinstall recoverlock. I even tried
<amunizp>
sudo dpkg –-remove –-force-remove-reinstreq recoverlock with the same result.
<amunizp>
"I can't find an archive for it"
<amunizp>
I can't seem to be able to remove it gonna try to just open /var/lib/dpkg/status file as root and remove the corresponding entry from it. https://askubuntu.com/a/1349608/36396
<Wizzup>
wait..
<amunizp>
ok
<Wizzup>
did you try 'apt-get remove recoverlock'
<amunizp>
yes.
<Wizzup>
sudo dpkg -r recoverlock ?
<amunizp>
and the -force option
<Wizzup>
sudo dpkg --force-all -r recoverlock ?
<amunizp>
and the force-all
<Wizzup>
with dpkg?
<amunizp>
yep.
<Wizzup>
and what does it say
<amunizp>
and sudo
<Wizzup>
well it always has to do be sudo.
<amunizp>
can't find an archive to it. that I need to reinstall it.
<Wizzup>
amunizp: I just tried the blue arrow + sym/ctrm and it works for me in terminal
<amunizp>
ok lemme transcrive.
<Wizzup>
you don't have ssh access yet?
<amunizp>
no not yet.
<Wizzup>
if you are connected to wifi it should be simple
<amunizp>
OK if it involves installing new packages I will not be able until I do the part of removing the package.
<Wizzup>
it does not
<Wizzup>
you just connect to wifi and then ssh to the device from your laptop/computer
<amunizp>
OK lemme look up how this is done. in a minute. I would like to know why blue arrow plus sym does not show me the keyboard.
<Wizzup>
you are pressing that in the x terminal yes?
<amunizp>
yep
<Wizzup>
maybe you're not pressing the right buttons?
<Wizzup>
sorry that's all I can think of :D
<amunizp>
haha only so many buttons to press.
<amunizp>
the one on the top left second and the one under that first.
<amunizp>
blue arrow so that I can use the blue caracters. I am able to type numbers 1, 2, 3, ...
<amunizp>
anc ctrl works when I quit out of nano ctrl + x
<amunizp>
but blue arrow plus Sym/ctrl does not bring anything new on the screen.
<amunizp>
OK so ssh might be what I need to do.
<Wizzup>
really strange
pere has joined #maemo-leste
<amunizp>
hum what is the toor password. ? or did I understand it wrong?
<amunizp>
ant toor is the password for root.
<amunizp>
OK I am in as user.
<amunizp>
this will speed things up! haha
<dsc_>
lol :)
<amunizp>
$ sudo grep -A 13 lock_code /dev/mtd1|tail -n 1
<amunizp>
grep: /dev/mtd1: binary file matches
<amunizp>
pere has quit [Ping timeout: 255 seconds]
<sicelo>
maybe try something like `sudo cat /dev/mtd1 | grep -A 13 lock_code | tail -n 1`
<Wizzup>
ooh
<Wizzup>
no, wait
<Wizzup>
add -a to grep
<Wizzup>
grep -a -A 13 lock_code
<Wizzup>
-a is --text
<Wizzup>
this way it won't just say 'binary file matches' but it will just print the text
arno11 has joined #maemo-leste
<Wizzup>
this cleverness probably just wasn't present in the busybox at the time
<dsc_>
i can take a look if you want (and if you promise you are not north korea)
<dsc_>
cat /tmp/lockcode.pot | base64 -w0
<amunizp>
I am not north korea.
<amunizp>
the problem I think I am getting is that lockcode.pot is not being created.
<amunizp>
Oh wait you mean lockcode where the hash is saved?
<dsc_>
eh sorry I meant /tmp/lockcode probably
<amunizp>
I get a load of /////////////////////////
<amunizp>
are you north korea?
<dsc_>
아니요
<dsc_>
oops, I mean no
<amunizp>
it starts with AAAA////// it ends in /////////////8k
<amunizp>
haha
<dsc_>
cat /tmp/lockcode | base64 -w
<dsc_>
cat /tmp/lockcode | base64 -w0
<amunizp>
yeah the latter.
<Wizzup>
dsc_: this is a well treaded path, it just looks like these is some diff in grep and john
<Wizzup>
you can also test this on your own n900 I think
<Wizzup>
bbiab
<dsc_>
i know, trying to lend a hand
<freemangordon>
dsc_: what is 'checkable' that you like? QActionGroup ?
<amunizp>
OK I think I am not typoing it correctly. --format=NAME force hash type NAME: descrypt/bsdicrypt/md5crypt/
<amunizp>
bcrypt/LM/AFS/tripcode/dummy
<amunizp>
none work says No Password haches loaded (see FAQ) I will now look for that FAQ.
<dsc_>
freemangordon: i like this top bar from your screenshot, didnt look too much into the code
<freemangordon>
ok
<freemangordon>
we only have to find a way to maki it working properly for lots of accounts
<freemangordon>
*make
<amunizp>
I find it so strange that I can't just factory reset the n900 phone somehow.
pere has quit [Ping timeout: 268 seconds]
arno11 has quit [Quit: leaving]
nmdv has joined #maemo-leste
<amunizp>
Ok what if I do sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f ?
<amunizp>
there is nothing in the original instalation I want to keep. will it still have the pin block?
<Wizzup>
yes.
<amunizp>
Ok have to leave now. I don't know how to turn off the phone.
<amunizp>
ok hold down the button. douh!
<amunizp>
wait it is not off loads of text
<amunizp>
woops forgot to log out from ssh.
ceene has quit [Remote host closed the connection]
amunizp has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
<freemangordon>
Wizzup: shall we keep qpa plugin changes in qsubmenu branch or merge it to -devel?
fab_ has quit [Quit: fab_]
nmdv has quit [Ping timeout: 256 seconds]
arno11 has joined #maemo-leste
pere has quit [Ping timeout: 264 seconds]
<arno11>
Wizzup: hi, i'll have time today to look @emulators, so i need your help to have a look in jenkins for pcsx if possible :P
<Wizzup>
freemangordon: qsubmenu is already in devel
<Wizzup>
freemangordon: did you see my code to hide the menus?
<freemangordon>
didn't look as you said it works :)
Livio has quit [Ping timeout: 268 seconds]
<freemangordon>
hmm, can't merge
amunizp has joined #maemo-leste
<freemangordon>
Wizzup: hiding code looks ok to me
<freemangordon>
shall I pull to -devel and make a new release?
uvos__ has joined #maemo-leste
<Wizzup>
freemangordon: what do you mean can't merge?
<Wizzup>
freemangordon: let me merge the menu hiding and then you can work on master
<Wizzup>
freemangordon: pushed to master
<freemangordon>
oh, ok, lemme see if I can fix it. as I pushed to -devel
fab_ has joined #maemo-leste
<freemangordon>
Wizzup: will force-push -devel
<Wizzup>
freemangordon: no
<Wizzup>
why?
<Wizzup>
your -devel is just outdated
<freemangordon>
because you pushed to master
<Wizzup>
??
<freemangordon>
and I pushed to -devel
<freemangordon>
and now they have different commits
<Wizzup>
ok, then just rebase devel on master
<Wizzup>
and if you force push it won't affect me
<freemangordon>
right
<freemangordon>
please try to pull to see if it is ok
<freemangordon>
I will try to implement multi-row QActionGroup
Livio has joined #maemo-leste
<Wizzup>
freemangordon: no issues pulling
<freemangordon>
great
<sicelo>
amunizp: even flashing uboot to the rootfs won't get around the pin issue
<sicelo>
... I find it so strange that I can't just factory reset the n900 phone somehow <<< this was the 2009's equivalent of icloud lock (and similar in android world) :-P
<freemangordon>
Wizzup: hmm, there is some issue with font size in the menu
<freemangordon>
font is bigger than those of gtk applications
<dsc_>
is it 18?
<dsc_>
pointSize
<uvos__>
no android device i am aware of ever became unresetable or bricked because of service discontinuation
<uvos__>
sure specific preinstalled apps/ featrues have
System_Error has quit [Remote host closed the connection]
<freemangordon>
dsc_: it is not specific to conversations
<dsc_>
yes in conversations I was getting 18 as the default pointSize and was wondering why
pere has joined #maemo-leste
<dsc_>
i suspect other Qt apps also get this 18
<freemangordon>
mhm
<freemangordon>
no idea abut the exact value
<Wizzup>
freemangordon: not on d4
<freemangordon>
hmm, ok
<freemangordon>
maybe something on the VM
<sicelo>
uvos__: replying to me? what service discontinuation? i was talking about device lock. Android has FRP (or at least used to)
pere has quit [Ping timeout: 268 seconds]
nmdv has joined #maemo-leste
<amunizp>
OK it just thought this. If I ssh into the phone when I boot it from my PC I then bring the mnt1 file back via the ssh tunnel and have a go with john on my pc?
amunizp has quit [Read error: Connection reset by peer]
amunizp has joined #maemo-leste
<amunizp>
this is interesting ./0xFFFF -b does not run again after I do it the first time?
<amunizp>
pere has joined #maemo-leste
ac_laptop has joined #maemo-leste
LIERO has quit [Changing host]
LIERO has joined #maemo-leste
<amunizp>
$ ./0xFFFF -b
<amunizp>
(...)
<amunizp>
Found block device /dev/sdb with id 8:16
<amunizp>
Error: Cannot open block device /dev/sdb: Permission denied
<amunizp>
Detected USB device: RX-51
<amunizp>
Error: No device detected
<gnarface>
well, do you have permission?
<amunizp>
clearly not.
<gnarface>
just chmod it?
uvos__ has quit [Ping timeout: 264 seconds]
<amunizp>
... not sure I understand. I was able to use the same command this morning @gnarface
<gnarface>
amunizp: well, any number of things may have changed the permissions, did you actually check to see if your user still had access was all i was asking...
<gnarface>
ls -l /dev/sdb
<gnarface>
for that matter usb devices can change order, they're notorious for it in fact, are you sure it's even still /dev/sdb?
<gnarface>
sorry if these are dumb questions, i didn't read the whole scrollback
<amunizp>
humm no such file of directory.
<amunizp>
with me they are not dumb don't you worry.
<gnarface>
interesting, the plot thickens
<amunizp>
technically I should be able to boot again from my pc if I did it once right?
<gnarface>
i assume so yea
<gnarface>
but i also assume stuff in /dev/ might change order on the fly with response to hotplug commands
<gnarface>
there's usually some notice at the tail of the output of dmesg that tells you when it happens thoguh
<amunizp>
do you think I need to do the whole reflashing as in step 3? https://leste.maemo.org/Nokia_N900#Quick because maybe the issue is that I did it when it was already done? and I broke it?
<gnarface>
uh, that i can't be sure
<gnarface>
i see that it says to use sudo
<gnarface>
so maybe you have to be the root user or use sudo
<gnarface>
maybe you need that for ./0xFFFF -b too? just a guess
<gnarface>
oh, hmm, in step 4 it doesn't say so but still...
<Wizzup>
run 0xffff as root
<gnarface>
i dunno, only other thing i can think of is maybe whatever was plugged in as /dev/sdb before got unplugged accidentally? if not physically removed then maybe by a weak contact?
<amunizp>
Found USB device: RX-51 (0x421:0x1c7) in RAW disk mode
<amunizp>
Detected USB device: RX-51
<amunizp>
USB device serial number string: 372041756775
<amunizp>
USB device product string: N900 (Storage Mode)
<amunizp>
Found block device /dev/sdb with id 8:16
<amunizp>
Error: Cannot open block device /dev/sdb: Permission denied
<amunizp>
Error: No device detected
<amunizp>
it is clearly finding it. I moved it to another USB port.
System_Error has joined #maemo-leste
<gnarface>
that was as root or...?
<amunizp>
not root. omg hope that's not it. it will be a big facepalm.
<gnarface>
yea, it's weird that ls -l didn't find it though if this says it did... maybe that's just some mistake in the output?
<amunizp>
Switching to NOLO mode...
<amunizp>
Unplug USB cable, turn device off, press ENTER and plug USB cable again
<amunizp>
interesting. seems to think it is on?
<gnarface>
maybe it's on?
<gnarface>
or maybe it's just another mistake in the output...
pere has quit [Ping timeout: 260 seconds]
arno11 has left #maemo-leste [#maemo-leste]
uvos__ has joined #maemo-leste
<sicelo>
the device should be turned off to use with 0xFFFF... not in Storage Mode
pere has joined #maemo-leste
Livio has quit [Ping timeout: 256 seconds]
akossh has joined #maemo-leste
nmdv has quit [Ping timeout: 264 seconds]
<dsc_>
regarding scrollback messages, was anyone working on preventing duplicate insertions in the rtcom db?
<amunizp>
@sicelo how do I make sure it is not on storage mode. I turned it off and the screen seems off. n900 light is blink but just because it is charging.
<freemangordon>
dsc_: any objections if I push conversations changes that use the above?
fab_ has quit [Quit: fab_]
<dsc_>
freemangordon: go for it
<dsc_>
are nested QMenu->QActions still supported in qt-maemo after this?"