inky is now known as inky_afk
stano_ has joined #maemo-leste
stano has quit [Ping timeout: 258 seconds]
Pali has quit [Ping timeout: 258 seconds]
cockroach has quit [Quit: leaving]
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 258 seconds]
joerg is now known as Guest9675
Guest9675 has quit [Killed (silver.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
Danct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
<pere> hm, my n900 test unit has lost its wifi connectivity again. :(
<stano_> for deskwork i stick to usb networking
<pere> it was working before my last upgrade a while back.
<stano_> there are many variables with wifi
<stano_> how is the brightness applet working for you pere?
<stano_> can you control the brightness?
<pere> did not try...
inky_afk has quit [Ping timeout: 245 seconds]
<stano_> one thing i am great at triggering is this sgx driver error
<stano_> PVR:(Warning): PVRSRVOpenDCDevice: Warning - 138 returned [80, /bridged_pvr_dc_glue.c]
<stano_> malloc(): smallbin double linked list corrupted
tmlind has quit [Ping timeout: 252 seconds]
buZz has quit [Ping timeout: 245 seconds]
tmlind has joined #maemo-leste
buZz has joined #maemo-leste
buZz is now known as Guest5137
inky_afk has joined #maemo-leste
uvos has joined #maemo-leste
<stano_> maemo-leste simple brightness applet demonstration video (40 sec, 659kB) http://0x0.st/-4ki.mkv
<uvos> yes all sliders in gk2 are somewhat broken atm
<uvos> you have to touch it multiple times to get it to register the correct value
<uvos> or scrub it from left to right
<stano_> i didn't realize it was really a slider
<stano_> thought there were 5 fields to tap
<uvos> its a slider with 5 possible values
<stano_> but i can tap the same spot and get from full dark to full bright
<stano_> or rather almost full dark, i didn't measure the actual range
<uvos> yes because the slider gets 2 inputs somehow
<uvos> one where you tap
<uvos> and one all the way to the left
<uvos> which one arrives last ist random
<uvos> so sometimes it registers a tap where you press
<uvos> and sometimes it registers full brightness
<uvos> *all the way to the right is what i ment
<stano_> ok thanks for confirming this not just a 'me' problem
<stano_> picodrive now. nothing but picodrive til it's done. no distractions.
<Danct12> parazyd, the fxtec uses a/b partition layout
<Danct12> so you can have android on slot b, and leste on slot a
inky_afk has quit [Remote host closed the connection]
inky_afk has joined #maemo-leste
inky_afk has quit [Ping timeout: 245 seconds]
inky_afk has joined #maemo-leste
<parazyd> Danct12: ok, thanks
Pali has joined #maemo-leste
<Wizzup> morn
<Wizzup> pere: did the upgrade succeed fully?
<Wizzup> pere: and did you reboot after?
<pere> Wizzup: yes, and yes.
alex1216 has joined #maemo-leste
<Wizzup> pere: hm, so apt doesn't complain about anything unfinished?
<Wizzup> pere: I am not aware of any problems now on the n900, I'm pretty sure I fixed them all
<Wizzup> pere: also new kernel?
<pere> the last upgrade was some n900 specific stuff, do not remember the details. can look it up if you want the details?
<Wizzup> pere: well, can you try to use usb net and just upgrade and see if there is anything to upgrade?
<pere> sadly I do not have any usb net device that can fit. lack the required cable.
<Wizzup> no microusb?
<pere> my only usb net device use a larger usb connector.
<Wizzup> pere: you misunderstand me :)
<Wizzup> pere: you know how you can charge your n900 on your pc with a normal microusb cable?
<Wizzup> pere: if you connect it to your pc like that, you will see a 'usb0' interface or similar on your debian pc
<Wizzup> the n900 will export a usb ethernet device
<Wizzup> pere: with the wiki page instructions you can share your pc network with the n900
<Wizzup> pere: does that make sense?
<Wizzup> you don't need any usb-to-ethernet adapter
<uvos> maybe some package is missing in non-devel?
<Wizzup> uvos: I tested it on non-devel, pretty sure
<uvos> my n900 works fine
<uvos> but its on devel
<uvos> Wizzup: ok
<Wizzup> we can compare packages I guess
<Wizzup> parazyd: could you take a quick glance at the diff?
<parazyd> What diff?
<uvos> devel non devel
<uvos> package version diff
<uvos> libicd-network-wpasupplicant
<uvos> yeah so that might be it
<parazyd> >foo: package is higher in beowulf
<parazyd> <foo: package is higher in beowulf-devel
<uvos> oh
<uvos> ok
<uvos> connui-common connui-conndlgs then?
<parazyd> Yeah those are lower version
<Wizzup> I guess we should look at merging these again in a bit
<Wizzup> parazyd: also what could be good to add (later) is to see which packages are in -devel but not at all in non-devel
<uvos> salutem
<Wizzup> uvos: yes, that for example
<uvos> not that it is important
<Wizzup> uvos: but I mean to the tool
<pere> Wizzup: sorry, got busy in a phone. I see from dpkg.log the two upgraded packages were leste-config-common and dbus.
<parazyd> Wizzup: I think this is it: http://sprunge.us/4FVrTz
<uvos> none of those sound ripe for moving to non-devel
<uvos> except salutem and hildon-theme-devel
<uvos> which are both sufficantly unimportant to not matter if they break anyhow
<uvos> how dose the image builder work with sunxi not in non-devel?
<uvos> it dosent
<parazyd> There are no sunxi images on CI yet
<parazyd> except pine{phone,tab}, but they have their own kernel
<pere> Wizzup: <URL: https://leste.maemo.org/Status/USB_Peripheral#Share_PC_network_with_Leste_device > do not state if I should choose pc suite or mass storage on the n900 popup?
<Wizzup> pere: just ignore the popup
<Wizzup> pere: sorry, it should say that, good point
<Wizzup> freemangordon: are you around this weekend?
<pere> Wizzup: also, no usb0 device show up on my linux machine, no matter what I choose.
<uvos> you have to choose nothing
<Wizzup> pere: it could have a different name if it is systemd
<Wizzup> 'dmesg' will probably show you
<uvos> the modern deterministic names is dbus related not systemd but yeah
<pere> dmesg is my friend: enp0s26u1u2: renamed from usb0
<Wizzup> right
<uvos> er i mean udev ofc
<Wizzup> uvos: yeah it just came after it 'merged' with systemd so I confuse that
<pere> Wizzup: ran into a problem with the n900 drawing too much power from my laptops usb connector, causing the laptop to disable the usb port and thus loosing network. changed to a 'ss' port solved it.
<pere> 109 packages to upgrade... will take a while.
<pere> Wizzup: you talked earlier about sending me a device. nothing arrived so far, hope nothing got lost in the mail.
<pere> btw, what is with the l10n-nono name? one of the 'no's should most likely be 'nb' or 'nn', not 'no'.
Guest5137 is now known as buZz
<pere> Wizzup: wifi is back after the upgrade.
<Wizzup> pere: check
<Wizzup> pere: I don't remember if I sent anything yet
<Wizzup> pere: what device would that be?
<Wizzup> pere: also, regarding the translations, all our translations are now on weblate and we generate them from weblate, so we take corrections and/or renames
<pere> something 4 or 5, something more modern than n900.
<uvos> Wizzup: you where going to give him a d4 i remember dimly
<Wizzup> droid 4 then, I can send it later this year :)
<uvos> Wizzup: im sure you forgot
<Wizzup> uvos: that's usually a safe bet with me :)
<Wizzup> :D
<Wizzup> pere: so if you can take a look at some of the translations and tell us what it needs to be, we can fix it
<pere> Wizzup: url? written 'norwegian' do not really exist, ie language code 'no'. It is either 'norwegian bokmål' (nb) or 'norwegian nynorsk' (nn), which we have been trying to implement for 30 years or so...
<pere> the majority is nb, so if you got 'no', you most likely should change it to 'nb'. All texts I have seen has been 'nb' so far.
<uvos> how about making the norwegian languague package called fi and the finnish pacakge nn
<uvos> just to annoy everyone
<uvos> :P
<pere> better to use gr, as 'greek to me' is the norwegian phrase for 'I do not understand the language'. :)
<uvos> :D
<pere> I would be able to honestly state that finnish is greek to me. :)
<Wizzup> it is bokmal on weblate it looks lke
<Wizzup> at least per title
<Wizzup> so maybe we just need to change some packages names
<pere> good. I talked to the weblate author several years ago about it, hope he disabled the 'no' code.
<Wizzup> yeah, but I think we still generate it with the wrong package name probably (cc parazyd )
<parazyd> Hey
<parazyd> If you rename it on weblate, we can easily regenerate debian/control
<pere> nb on weblate seem to be complete already.
<parazyd> So it's nb_NO ?
<pere> parazyd: it is already nb_NO on weblate. the package was named nono, though.
<parazyd> I see
<lel> parazyd opened an issue: https://github.com/maemo-leste/bugtracker/issues/566 (translations: Rename no_NO to nb_NO)
<lel> parazyd labeled an issue: https://github.com/maemo-leste/bugtracker/issues/566 (translations: Rename no_NO to nb_NO)
<lel> parazyd assigned an issue: https://github.com/maemo-leste/bugtracker/issues/566 (translations: Rename no_NO to nb_NO)
<Wizzup> (and locale.gen)
<parazyd> You wanted to do that through apt or something IIRC
inky_afk has quit [Ping timeout: 256 seconds]
<Wizzup> mhm
* pere checked the failing controls on weblate for nb_NO, and corrected a few entries.
<Wizzup> cool
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/355 (Droid 4: USB OTG Works only with a Powered Y-cable, and crashes when unplugged)
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/441 (Status applet doesn't render well in 16bit X)
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/435 (Hildon desktop not starting after battery depletion on Droid 4)
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/410 (mce: switch from dpms to drm blanking)
lel has quit [Remote host closed the connection]
lel has joined #maemo-leste
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/35 (N900: Look at libinput at some point for TS)
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/505 (Feature Request: Way to get to console when gui fails to start.)
<Wizzup> :)
<uvos> Wizzup: could you comment on https://github.com/maemo-leste/bugtracker/issues/539
<uvos> i dont think this problem exists anymore but im unsure what bug its describing exactly
<uvos> so cant repo
<Wizzup> basically an application can request the network/scan dialog to pop up
<Wizzup> if you then select a network from it, it would always fail
<Wizzup> but indeed I think this is fixed with the newer conndlgs
<uvos> could you repo?
<Wizzup> repro you mean?
<uvos> yeah
<Wizzup> I'm pretty sure I used it to test if fmg's fix worked, so I think we can close it
<uvos> ok
<lel> IMbackK closed an issue: https://github.com/maemo-leste/bugtracker/issues/539 (Certain ways of invoking the connection dialog result in connection failure)
<Wizzup> ty
<Wizzup> (i'm adding all of these to the news post too)
inky_afk has joined #maemo-leste
<Wizzup> uvos: should we close #35 if we don't have a fix?
<Wizzup> or?
<uvos> well it sais "look at" libinput on n900 would gain us no benefit, whilest requireing reimplementation of a calibration ui
<uvos> while on other devices there is benefit (eg for the console vkb on bionic) so we switched those devices over
<uvos> as far as i am concerned there is nothing to fix here
<uvos> n900 also dosent support mutitouch
<uvos> so the libinput gestures dont gain us anything either
<uvos> in contrast to the other devices
<Wizzup> ok
<Wizzup> fine
inky_afk has quit [Ping timeout: 272 seconds]
elastic_dog has quit [Ping timeout: 272 seconds]
elastic_dog has joined #maemo-leste
inky_afk has joined #maemo-leste
inky_ has joined #maemo-leste
inky_afk has quit [Ping timeout: 256 seconds]
Evil_Bob has joined #maemo-leste
uvos has quit [Ping timeout: 258 seconds]
avoidr has quit [Quit: Lost terminal]
avoidr has joined #maemo-leste
<freemangordon> Wizzup: around... yes, around :)
uvos has joined #maemo-leste
<Wizzup> freemangordon: ok, when you have a moment, maybe we can look at the hildon-desktop xrandr PR and mce cmake PR
<uvos> the pr concerns xinput not randr
<Wizzup> uvos: yeah ok but it adds better randr handling no?
<uvos> no
<uvos> it adds xinput handling
<Wizzup> ok, let me re-look
<uvos> full stop
<Wizzup> this was from memory
<Wizzup> ok
<uvos> sorry-not-sorry im lazy about that
<uvos> *note
<Wizzup> :p
<Wizzup> freemangordon: the other is https://github.com/maemo-leste/mce/pull/50
<Wizzup> freemangordon: both are significant so I'd like your ack
<stano_> 'maemo-leste doesn't have much software!' // dpkg-query -l |wc -l // 3529 :P
belcher_ is now known as belcher
<freemangordon> Wizzup: ok, maybe tomorrow
inky_ has quit [Ping timeout: 272 seconds]
<Wizzup> freemangordon: ok
inky_ has joined #maemo-leste
stano_ has quit [Ping timeout: 240 seconds]
inky_ has quit [Ping timeout: 245 seconds]
inky_ has joined #maemo-leste
alex1216 has quit [Quit: WeeChat 2.3]
inky_ has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
plab has joined #maemo-leste
<Wizzup> https://jonnylamb.com/2010/01/14/telepathy-exras/ looks like the irc, hazy and some others are foss
<Wizzup> the UIs that is
<sicelo> you mean the plugins? those aren't tied to the UI per se, iiuc
<uvos> what tool can i use to introspect a dbus interface?
<uvos> other than just reading the xml files
<sicelo> dbus-send
<uvos> is there something i can pass --introspect whatever.interface
<uvos> and see all the methods
<Wizzup> Package: liblongcat1
<Wizzup> Description: Base plugin for the Accounts user interface A base plugin for writing accounts plugins, which makes it easier and needs less code.
<Wizzup> lol
<Wizzup> sicelo: rtcom plugins, so uis for configuring tp
<Wizzup> uvos: there is a gui
<sicelo> or utools like qtdbus
<sicelo> there used to be d-feet for gtk/gnome ... no idea if that still works
<sicelo> anyway, not all dbus interfaces (esp. the nokia ones) are introspectable
<uvos> yeah i know
<uvos> im interested in ofono mostly
<Wizzup> I use mdbus2 as cli tool
<Wizzup> it allows you to browse it from cli
<uvos> qt currently dosent work over remote x
<uvos> for bug reasons
<uvos> (pvr related)
<Wizzup> uvos: just use mdbus2 I think
<uvos> otherwise the qt tool would have been nice
<sicelo> okay. although ofono's interfaces are well documented ... that's not sufficient to discover all methods?
<uvos> sicelo: sure but who wants to read documentation :P
<uvos> (im just looking for options ;)
<uvos> _
<uvos> )
<Wizzup> uvos: yeah so mdbus2 can do all of this for you
<Wizzup> I do it all the time with ofono
<uvos> MDBUS2> org.ofono
<uvos> Segmentation fault
<uvos> nice
<sicelo> heh,
<sicelo> it worked for me too (last time i used it)
<lel> MerlijnWajer opened an issue: https://github.com/maemo-leste/bugtracker/issues/567 (rtcom/tp configure ui)
<Wizzup> uvos: mdbus2 -s org.ofono
<Wizzup> I never had a problem with that
<uvos> yeah that works
<Wizzup> and then after that comes the iface path
<Wizzup> or w/e it is called
<uvos> \me after 30min of dicking around with dbus - f*** it im replaceing the sphone dbus ofono code with libgofono
* uvos after 30min of dicking around with dbus - f*** it im replaceing the sphone dbus ofono code with libgofono
<uvos> or maybe not it dosent support half the interfaces we need
<uvos> sigh
inky_ has quit [Ping timeout: 250 seconds]
inky_ has joined #maemo-leste
plab has quit [Ping timeout: 240 seconds]
plab has joined #maemo-leste
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 256 seconds]
inky has quit [Ping timeout: 252 seconds]
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 258 seconds]
inky has joined #maemo-leste
uvos has quit [Ping timeout: 258 seconds]
<Wizzup> uvos: what do you need that libgofono does not support?