<freemangordon>
parazyd: please look at my comment
<parazyd>
freemangordon: Yeah I suppose at least devices with keyboard should have it.
<freemangordon>
parazyd: why we shall keep separate configs for them? I think it is more simple like - enable it for all devices, no matter HW kbd or not.
<freemangordon>
if currently h-d cannot support more than one shortcut per function, well, lets implement that
<freemangordon>
but I think you should not merge that commit but instead have a discussion how to best handle that
* freemangordon
is going afk for a while
<parazyd>
ok, let's see what uvos says about that
<parazyd>
Multiple shortcuts per function sounds good.
* parazyd
afk too
uvos has joined #maemo-leste
<uvos>
freemangordon: we had this discussion before, yes ctrl-backspace should work everywhere, no hildon cant assign more than one shortcut per action atm, yes this is a planed improvement
<uvos>
also other shortcuts should work everywhere like alt-f4 same as mapphone "back"
cr4y1 has joined #maemo-leste
uvos has quit [Ping timeout: 260 seconds]
vectis_ has quit [Ping timeout: 240 seconds]
diejuse1 has joined #maemo-leste
<diejuse1>
good morning
<diejuse1>
I had to start from scratch, reinstalling the chroot Maemo image
<diejuse1>
I had a problem. I can do ping to IP but "apt update" get the error "could not resolve host". I resolved this problem last time trying many thing but now I don't know what solution I used.
inky has joined #maemo-leste
<diejuse1>
solved
diejuse1 has quit [Quit: Leaving.]
<freemangordon>
uvos: do we have an issue about that(multiple shortcuts)?
inky has quit [Quit: Leaving.]
inky has joined #maemo-leste
Pali has joined #maemo-leste
<parazyd>
freemangordon: No, I don't think we even considered it until now
<freemangordon>
hmm, uvos said it has been discussed...
<freemangordon>
( 9,21,18) uvos: freemangordon: we had this discussion before, yes ctrl-backspace should work everywhere, no hildon cant assign more than one shortcut per action atm, yes this is a planed improvement
<freemangordon>
I wonder who is 'we' here, as I don;t remember such discussion as well, but that could be my aging memory and lack of Fe
uvos has joined #maemo-leste
<freemangordon>
parazyd: anyways, we shall have an issue for that, to not forget to fix/implement it
<freemangordon>
I am going to open one
diejuse1 has joined #maemo-leste
<parazyd>
I think he meant discussion for what should the shortcuts be
<tmlind>
for boot.cfg, i'm using multiple partitions too
<uvos>
"is there a way to test the charging mode yet, btw?" sure add softlevel=charge-mode to the kernel cmdline
<uvos>
Wizzup:
<uvos>
tmlind: we will have to break it once (the maemo boot.cfg) after that you should be able to restore your changes and have it be fine from there on out
diejuse1 has joined #maemo-leste
<tmlind>
uvos: ok no problem with the file on my maemo partition, it only has maemo stuff
<Wizzup>
uvos: fwiw I'm looking at the location-status crashes, will update later today
<Wizzup>
freemangordon: what is a good way to debug hildon-status-menu applets again?
<Wizzup>
gdb and maemo-invoker or something?
diejuse1 has quit [Ping timeout: 265 seconds]
inky has quit [Ping timeout: 246 seconds]
inky has joined #maemo-leste
jonsger has joined #maemo-leste
sicelo has quit [Quit: Bye!]
sicelo has joined #maemo-leste
halftux has joined #maemo-leste
random_yanek has quit [Ping timeout: 250 seconds]
random_yanek has joined #maemo-leste
<halftux>
yeah finally I got the droid4 running with leste don't know if the files where corrupt or if the usb port is laggish. So booting the latest image and connecting it to usb makes the droid4 crazy with repeating messages from usb connection. Could you recommend an image which is most stable?
<halftux>
hmm is there an droid4 image where usb network should work? I get a Multifunction Composite Gadget which vanishs when going pc suite mode..
<Wizzup>
what kind of messages from usb?
<Wizzup>
halftux: the default mode should be network
<Wizzup>
don't select mass storage or pc suite
<uvos>
you cant boot the device with usb plugged in atm or ever
<halftux>
with messages I mean charging and disconnect charger and drain more power that it get ... now took other image and it looks like it is a bit less. I will try without mode and see.
<uvos>
your usb cable has to high imedance
<uvos>
*impedance
<uvos>
charging fails and reconnects when the voltage sags to mutch
<halftux>
okay so I used original Nokia N900 cable will see if I have another one.
<uvos>
its finiky no doubt
<uvos>
[20:44] <gemiller1> If 80mW is your budget, then gpsd is not for you.
<uvos>
frendly
<Wizzup>
they're not friendly it seems
<Wizzup>
freemangordon: so I think I should use maemo-summoner to use gdb on programs
<Wizzup>
yet gdb just shows the raise() from maemo-summoner
<uvos>
im telling you guys this mameo launcher thing is more trouble than its woth it saves around 150ms application startup time over readahead-replay
<uvos>
for being a pretty big pain in the but
<uvos>
and thats absolute best case too
<uvos>
most of the time it saves 0ms
<halftux>
now using different laptop same cable and the droid4 is not crazy any more. So Sony sucks HP rocks. But still not able to get a usb network.
xmn has quit [Quit: ZZZzzz…]
<uvos>
its just the d4 being picky atm
<uvos>
we hope to solve this
<uvos>
the sony is very likely in spec
<Wizzup>
uvos: I think we benchmarked it to save quite a bit more, in any case, that's not the painful part per se tbh
xmn has joined #maemo-leste
<freemangordon>
Wizzup: sorry, don;t get the issue. What is the backtrace?
<Wizzup>
freemangordon: I am trying to debug a problem with parazyd's location-status applet
<Wizzup>
It crashes every time when invoking something with osso, and I am pretty sure the code somehow doesn't set up the private struct, or it overrides the osso data somehow
<freemangordon>
Wizzup: is that hildon-status-menu applet?
<Wizzup>
so I'd really like to run valgrind on it, or gdb, but the only way I've been able to do it so far is to run it via dsme tool and attach with gdb
<Wizzup>
yes
<freemangordon>
so, just attach gdb to the second hildon-status-menu process
<freemangordon>
or, start HSM with maemo-invoker
<Wizzup>
so maemo invoker is the thing?
<freemangordon>
sorry, maemo-summoner
<Wizzup>
so if I do that, I still don't get the useful bits
<freemangordon>
bencoh: invoker starts it under launcher
<freemangordon>
but we don;t want that
<freemangordon>
Wizzup: also, maybe it needs to be started as user, by using run-standalone.sh to start gdb
<Wizzup>
I did try various combinations of that, hang on, let me try
<Wizzup>
of course now it doesn't segfault, sec
<Wizzup>
most annoying thing about hildon-status-menu which annoyingly also makes sense: if it exits with non-sigint or non-normal, it disabled loading most plugins on next start
<halftux>
but in principle the problem is solved for me it was something with the lock screen and screen saver together that no input was recognized
<halftux>
so now when I push the virtual acpi power switch the black screen goes away and when I press it again the power button menu shows up like before