[00:12] * agaida will like black global menues on a black background much [00:18] aaaand that's why I'm doing dark panels ;) [00:20] RIGHT [00:20] XD [00:36] great, my bouncer is down [00:38] @VikingRedwolf, Aren't they supposed to be like 6'4"... 6'6" tall and girthy tho [00:38] Hard to take them down [00:38] Did he drink too much? [00:38] º__________º [00:43] redwolf: become modern and get a quassel-core [00:43] a wut? [00:43] no more bouncers needed :P [00:44] and quassel client works fine on windows - and there is even quasseldroid [00:44] isn't quassel an irc client? [00:44] there [00:44] and server [00:44] ah [00:45] https://quassel-irc.org [00:45] is it hosted there? [00:45] no [00:45] one can host it everywhere [00:45] hm, it seems complicated. remember that I'm internally blonde [00:46] I did enough by setting up a normal server, nextcloud and even a pastebin service, but tthat's all [00:47] nah - its easy - setup an super performant postgresql server, setup a quasselcore and be done with :P [00:47] can you see my irc user here, btw? ("here") [00:48] redwolf, redwolf[m] ? [00:48] aye [00:50] https://pb.5id.eu/OgIC - my own little quassel server [00:51] oohh [00:51] ok, little is a bit understatement [00:51] :P [00:51] indeed [00:52] ok, my server just for fun [00:52] I like when a man doesn't bluff about the size of his server .__. [00:53] https://pb.5id.eu/cnIN - as i said, only for pet projects [00:54] "persistent" [00:54] cheaper than a root server - so what :P [00:55] oh, there's a package for ubuntu (quassel-core) [00:56] right - i guess two cores and a littel postgre database should be enough - isn't so expensive [00:56] and works with nearly everything [00:56] two cores? [00:56] as in cpu? [00:56] a VM with 2 processor cores [00:57] 10 is a little bit much :D [00:57] I should check mine [00:58] https://contabo.com/?show=configurator&vserver_id=193 - had this as starter, was fully enough for my web things and quassel [00:59] my own gitlab instance changed this a little bit [01:00] I have 1 CPU core :( [01:01] I'M BACK!! [01:01] YISSSS [01:02] :) [01:02] but it's definitely something to think about [01:03] I'm happy with my server though. I only use it mainly for syncing things to nextcloud [01:04] I know it's cheap and tiny, but it's enough for someone like me [01:04] but I can add cores ;) [01:04] i like to have a strong machine as a backup or for testing things without the need of digital ocean or aws [01:04] that's expensive here [01:05] for me, I mean, for now [01:05] 4 cores/12G for 9 € isn't to bad [01:11] !offtopic [01:11] #lubuntu is the Lubuntu support channel, #lubuntu-devel for discussion regarding development of Lubuntu, and #lubuntu-offtopic is for random chatter. Welcome! [01:11] :) [01:32] 😐 [11:17] @tsimonq2 for the docs should I remove anything that has to do with using the terminal [12:09] @anyytime, tbh, I think that it shouldn’t be just content from leafpad site, screenshot and output from `leafpad -h` [12:10] what do you suggest otherwise? [12:11] @anyytime, Wouldn't that discourage the use of the terminal for future lubuntu users? [12:14] @num13, Saying that you should open temrinal to start leafpad instead of using applications menu or alt+f2 isn't good idea [12:16] Either way @tsimonq2 What do you suggest? [12:19] imo it should say in what category you can find the app, its features (but not copy-pasted), explanation of UI and maybe what to do if the file was opened with incorrect encoding [12:20] and explain some options available in settings window, if any [12:20] yea I decided to replace the usage from terminal part to which category to find the app [12:20] (y) [12:21] about explanation of ui, it's just a standard text editor I believe? [12:21] yup [12:23] and 2051x1379 is probably too big resolution for a screenshot… [12:24] of something as simple as leafpad [12:24] that’s just what I think [12:25] I’m trying to guess what typical user would think, but it’s hard for me [12:27] somebody says that people with Asperger’s syndrome (like me) can’t understand others XD [12:28] But it’s definitely off-topic, so I won’t say about it here… :> [12:31] @num13, I don't have much of a preference tbh :) [12:33] I’ll make a PR basing on how I think it should look and I’ll ask @anyytime for review [12:33] Ok [13:51] @tsimonq2, @julienlavergne, wxl, one small detail. I have to completely replace Openbox and LXQT (widgets and panel) themes. I need a day for that. Maybe two. [14:17] -GitHub113:#lubuntu-devel- [lubuntu-artwork] vikingredwolf pushed 1 new commit to master: https://git.io/vNKTV [14:17] -GitHub113:#lubuntu-devel- lubuntu-artwork/master 953e881 Redwolf: Add Lubuntu Arc theme [14:19] @VikingRedwolf, OK. We're waiting on @julienlavergne to look into XDG brokenness anyways ;) [14:20] O.O why? [14:23] -GitHub189:#lubuntu-devel- [lubuntu-artwork] vikingredwolf pushed 1 new commit to master: https://git.io/vNKIJ [14:23] -GitHub189:#lubuntu-devel- lubuntu-artwork/master 3ed6170 Redwolf: Add (custom) Lubuntu Arc for Openbox [14:24] @GitHub189, sneaky! [14:24] @tsimonq2, ? Bug number ? [14:25] @VikingRedwolf, ...screen is black on login? [14:25] @tsimonq2, that's minimalism! XD [14:26] @julienlavergne, I don't have one but I assumed Rafael mentioned something to you... Try grabbing a Lubuntu Next ISO, the themes and everything is black on login, and the panel is empty. I suspect XDG. [14:27] Themes are already uploaded. we only need three packages to make this look possible: [14:27] - arc-themes (in the repos) [14:27] - papirus-icon-theme (in the repos) [14:27] - kvantum (somewhere) [14:28] I might need to re-send you, @julienlavergne, the settings for gtk2 and gtk3 [14:31] I wonder if all this LXQt confifurarion will collide with LXDE's [14:39] it's siesta time. brb! [14:51] ramon_gabriel was added by: ramon_gabriel [15:16] @ramon_gabriel, o/ [15:17] @VikingRedwolf, OK, but I'm lost when touching XDG settings so I'll pass that to @julienlavergne to figure out and get working :) [15:17] agaida says things are merged upstream, so there shouldn't be any blockers left? [15:17] @ramon_gabriel, Welcome! [15:22] for the XDG things - we have moved nearly all XDG things to /usr/share/lxqt iirc - except the configurations for lxqt-globalkeys [15:24] in case where no upstream pre-configurations are available the normal XDG behaviour works, implemented in libqtxdg - so the application will have a look at the '"normal" pathes in /usr/share, etc/xdg/$foo, /etc/$bar and $HOME/.config/$baz [15:25] @tsimonq2, Thank you! [15:26] i would suggest to use /etc/xdg to provide settings and not to touch the XDG standard dirs - that will leave /etc/$bar open and not touched for derivatives [15:27] to sum it up - lubuntu can just throw the lubuntu configs to /etc/xdg - there will be no file conflicts with debian or upstream [17:38] @tsimonq2, I hope so [17:57] -GitHub58:#lubuntu-devel- [lubuntu-artwork] vikingredwolf pushed 1 new commit to master: https://git.io/vNKiA [17:57] -GitHub58:#lubuntu-devel- lubuntu-artwork/master 8461385 Redwolf: Fix some colours [17:58] @GitHub58, 🇬🇧 [17:58] @GitHub58, *colors :P [17:58] 🖕🏻🇺🇸 [18:03] have you added papirus-icon-theme and arc-theme to the seed? [18:03] and KCALC? º___º [18:05] @VikingRedwolf, It's open for pull requests... [18:05] Although yeah I guess I should [18:05] @VikingRedwolf Have we switched to Arc on LXDE and LXQt? [18:06] nope [18:06] we could though [18:06] Just LXQt needs those seed additions then? [18:06] @VikingRedwolf, No [18:06] yes [18:06] Ok [18:06] I prefer to keep the diferent settings [18:07] I do too [18:08] Which is why we need different default settings packages boi [18:08] *ahem* ;) [18:08] BTW agaida, lubuntu-meta in Bionic should be fixed now. [18:08] aah, don't tell me that. tell @julienlavergne ;) [18:09] you want to switch the theme + icons for the LTS ? Really ? [18:10] yes, he does :) [18:11] @gilir, Not for Lubuntu, Lubuntu Next [18:11] Lubuntu needs to stay static [18:11] Lubuntu Next however is the playing ground :) [18:12] ok [18:15] btw, the settings should work, because there are in a XDG directory [18:16] I'm downloading the ISO, I'll look at it [18:29] tsimonq2: is a fixed iso ready to download? [18:30] hi gilir [18:53] @gilir, OK [18:53] @agaida, Idk offhand if today's daily has the fix. [18:56] hmm - just downloaded the daily image - unfortunately the metapackage changes are not in [19:07] Then apt update in tty1, wipe away your settings, kill lightdm and start sddm :D [19:08] that doesn't help much - in that special case reading the sources is more fruitful and faster - look good first hand [19:09] and btw - apt purge libgtk* libqt* would help more [19:09] after that starting with a nearly cleaned up system even :D [19:11] gilir: Mind if I just do a quick Lubuntu Next amd64 rebuild to pick up the metapackage changes? [19:12] question. can we include pcmanfm-qt settings there as well? [19:13] @VikingRedwolf, agaida: Was the xdg change made there as well? [19:16] I already have the settings. do you want them? [19:22] tsimonq2: i had a nice and clear black screen [19:22] @julienlavergne ? [19:22] agaida, it's a "minimalistic screen" [19:22] and after choosing the wm a installer icon on the screen [19:23] redwolf: the cool thing about is - one can start with an empty task bar - a future proof solution :D [19:23] hi agaida [19:23] s/task bar/lxqt-panel [19:23] :) xfce does that: "do you want an empty panel or a default one?" gentle [19:24] @agaida, I really think this is XDG settings at fault [19:24] tsimonq2: no, I'll restart the download after :-) [19:24] so what i can say about the meta packages is - looks good for me right now [19:25] apt install lubuntu-qt-desktop looks reasonable with no debris in it (given that one use --no-install-recommends) [19:26] @gilir, OK :) [19:26] redwolf: yes, you can send them to me, but currently lxqt-config doesn't apply gtk settings, so it will be tweaky to apply them [19:27] how does lxappearance work? we need it for gtk [19:27] the qt settings manager should call the other one. otherwise we'll have some apps "naked" [19:28] that's not so simple, lxappearance is GTK & C, lxqt-config is Qt + C++, and no way to run lxappearance without the GUI [19:29] redwolf: just provide reasonable gtk2 and 3 default to start with [19:29] @gilir, :( [19:29] ok [19:30] gilir, there: https://pastebin.ubuntu.com/26453603/ [19:35] https://github.com/lxde/lxqt/issues/403 - so i guess LXQt 1.0 will have GTK support for themes and so on [19:35] Issue 403 in lxde/lxqt "Lxqt Appearance, set GTK settings" [Open] [19:36] and if one have a look on the date - it really has very high priority [19:36] I always said it's absurd to make end users to have TWO different engines. it's confusing [19:36] until then lxappearance is the best bet for openbox [19:36] there's people who don't know what's gtk or qt, and they shouldn't at all [19:36] agaida, but lxappearance can control qt either [19:37] nope [19:37] in no way [19:37] bidirectional problem [19:37] only if qt use the gtk2 themes [19:38] or if you use the gtk-qt-bridge. same things reversed. ugly [19:38] and thats a f***ing problem since i started with linux [19:38] yes. as it was the package format. this always was OUR problem in Linux [19:38] the fragmentation [19:38] and that was 2009 - also here the best bet is using the qt-gtk theme [19:39] gilir, you got the settings? [19:39] I included the pcmanfm-qt one too [19:40] redwolf: yes, thank you [19:40] you're welcome [19:42] redwolf: but in the real world™ the gtk thing isn't really a deal breaker - with some reasonable gtk defaults most people don't tinker around with the settings (that was the feedback from siduction users) [19:56] you had no problems at all? [19:57] you're telling me you made possible to load gtk settings in a qt environment, right? [20:17] agaida: So I've been thinking about lxqt-panel more and more... One thing that I think would be good is to have it like other panels where you can add favorites and have your profile pic + name there. If I write the code, is this something that would be accepted? [20:18] tsimonq2, wouldn't you need some setup "manager" for that? [20:19] @redwolf, No, the defaults would be sane. [20:19] Then you can customize on the panel itself from there. [20:19] and how would you change layouts? [20:19] ...what do you mean? [20:19] I'm just thinking about expanding the start menu a bit :) [20:20] ah, I was thinking about a different thing, like MATE, having different layouts (mutiny, gnome2...) [20:21] That's something I'm still thinking about; let's see what happens after gilir gets the default settings working :) [20:21] ok [20:21] It honestly wouldn't be hard to do. [20:22] I have some cool ideas for that should it all work out. [20:22] But one thing I want to finish, get packaged, and upload to Ubuntu is the Lubuntu About program. [20:24] YESSS! [20:24] tsimonq2: have fun and make the "new" enhanced Version of the main menu optional - like in kde - so one could choose the classic one via the enhanced one [20:25] we will see it in 0.13 or 14 then [20:25] @agaida, Should enhanced be default or should classic? [20:25] @agaida, Alright, cool. [20:26] classic - and not to forget - file a bug about so people have a place for opinions about [20:27] Ok [20:27] If it's not accepted upstream, I fully expect Lubuntu to carry it downstream. [20:28] where's my audacious-qt?! [20:28] dinner is ready. brb [20:28] @redwolf, I'll work on it. [20:57] *burp* [20:57] *cough* [21:00] -GitHub175:#lubuntu-devel- [lubuntu-default-settings] tsimonq2 pushed 2 new commits to master: https://git.io/vN6fX [21:00] -GitHub175:#lubuntu-devel- lubuntu-default-settings/master d47b797 Julien Lavergne: Add a symlink from xdg-Lubuntu to xdg-QLubuntu to apply also the settings on QLubuntu session [21:00] -GitHub175:#lubuntu-devel- lubuntu-default-settings/master 6d03722 Julien Lavergne: Fix debian/changelog [21:00] not sure the fix for default-settings is enough, but that should be better [21:01] redwolf: re audacious-qt - it isn't primetime ready yet - i was playing with the debian packaging a bit to separate the gtk and qt-part a bit more and cleaner -- after some days i switched back to audacious gtk. I would guess another year until GTK and Qt are feature par and a-Qt is mature enough [21:02] aw, okies :( [21:02] debian had another solution to handle the Qt situations - they don't even build the Qt part first hand :P [21:03] still not? feels like they have been working on the Qt UI for like ever [21:03] qmp then! [21:03] .____. [21:04] i don't know how qmmp behave now - but there was a reason why i switched with siduction LXQt to audacious :D [21:04] :) [21:05] and i had the latest upstream in siduction for three years - to be honest - there are better opportunities if one want to waste time [21:06] I know gilir had ideas for other media players :) [21:06] I don't :| [21:07] well ... actually I don't :-( The only ones I know on Qt are Clementine and Amarok ... [21:07] Amarok is dead upstream and will be removed when Qt 4 is removed from Debian [21:08] Clementine might work [21:08] I'm still inclined to go with VLC, actually. [21:08] clementine is a fine choice - ok, not exactly lightweight and qt4 too [21:08] Kubuntu uses it. [21:08] @agaida, I'm -1 because it's Qt 4 [21:08] apt show clementine [21:08] right [21:08] Amorok is being ported, but seems to have stalled again in that [21:08] gilir: What objections did you have to VLC? [21:09] babe and elisa have promise [21:09] I know it's a really popular media player, I use it too. [21:10] Honestly I know VLC is the de-facto choice for a lot of people, much like LibreOffice [21:10] smplayer has better performance, less cpu to play the same movie [21:10] gilir: but a F ugly default UI [21:10] and the VLC UI sucks :-p [21:10] erm - while we talk about Qt4 - one should have a look at the libreoffice choice - libreoffice-kde will go away soon - it is dead [21:10] acheronuk: agree, but it can be changed [21:11] @agaida, Yep, I've been keeping my eye on that [21:11] LibreOffice looks awful, btw, in Lubuntu Next [21:11] agaida: LO 6 should have Qt5 VCL [21:11] @gilir, Honestly, I prefer the VLC UI. [21:11] And like I said, the upside is that it's very popular :) [21:11] @acheronuk, I hope so! [21:12] erm - not soon [21:12] When will LO 6 come out? [21:13] tsimonq2: the UI can be changed, my only real point is about performance [21:13] when it is released https://wiki.documentfoundation.org/ReleasePlan/6.0 [21:14] if performances were equal, I'll be agree to go with VLC (and hope we can find a good UI / theme ...) [21:14] https://tracker.debian.org/media/packages/libr/libreoffice/control-16.0.0rc2-1 - just search for Qt [21:14] LO 6 is scheduled end of January [21:15] and i will talk with the maintainer about libre office beginning of march at the CLT 2018 [21:16] @gilir, Out of curiosity, what stats do you have regarding VLC performance? [21:16] I asked libroffice uploaders before Xmas, and they seemed to think V6 would definitely go in 18.04 [21:16] but right now the Qt Frontend isn't release ready - and LO6 will hit sid on release date - and we all hope to have it in sid as soon as possible [21:16] s/sid/experimental [21:17] If the performance is just slightly less gilir, it shouldn't make much of a difference. But if it's a lot, then yeah. [21:17] that is annoying. I lost tack with that. last I heard LO devs had asked KDE devs for help getting the UI up to speed. guess not much help happened [21:17] sed: -e expression #1, char 13: unterminated `s' command [21:18] tsimonq2: try to play the same video with both player, you will see [21:18] to be blunt, the gtk LO VCL is now better than than the KDE4 one. [21:18] @gilir, I have, with little difference :) [21:18] which is a painful truth [21:19] @acheronuk, We might go with that temporarily then until the Qt 5 frontend gets better. [21:20] tsimonq2: I am seriously wondering for Kubuntu, as the KDE4 one is getting quite bad [21:20] and especially does not take dark themes well [21:21] tsimonq2: last time I checked it was 30 - 40 % better, of course on small % because I have good CPU [21:21] @gilir, OK, I'll check it out. [21:22] yes, smplayer can be made to look ok https://i.imgur.com/mNSAnkK.png [21:22] and i might not be the most clever developer in the world - but for now i prefer nice working GTK solutions combined with LXQt over Qt only and crappy - and that count even more because some big applications rely on GTK already [21:23] esp there is no secure and well maintained browser available in Qt (and please don't mention the upcoming falcon as secure) [21:24] About that... [21:24] I've been talking with the security team [21:24] We can make it work [21:24] So I'll stand behind Falkon being secure on this one :P [21:24] falcon will be secure if it is possible that qt.io is following the chromium development with less than one week delay [21:25] And they are, iirc. [21:25] hihihi - and when QtWebengine will hit the distributions - having patched sources is one thing [21:25] ... [21:27] I can make it work [21:27] I'm telling you :P [21:29] assuming you can, can you guarentee that can be mantained for lifetime of a LTS release? [21:30] tsimonq2: let me know the result of your testing, perf may have changed since I tested them [21:31] Ok [21:31] @acheronuk, Yes. [21:31] * acheronuk raises eyebrow [21:35] ok - back to reality - last chromium update in QtWebengine 5.9.2 was 17. Sept. 17 or so [21:36] I'm not focusing on Artful for QtWebEngine security updates [21:36] Only Bionic [21:36] lifetime half a year - cool [21:36] that is still a very ambitous commitment [21:37] @acheronuk, Not really. [21:38] It is, unless it is being back officially by ubuntu security teams [21:38] *backed [22:02] are redwolf and i the only ones that totally hate the desktop pager? [22:02] they just look so..... plain [22:02] (lxqt btw) [22:03] booooooooring [22:03] I prefer the "squared" ones, not just plane numbers. and having a visual representation of the windows is also handy [22:03] i think even if they were visually more like desktops (as with lxpanel) it might be at least a wee bit more appealing [22:05] like diz: https://lescahiersdudebutant.fr/jessie/index-en-img/index-en-img93.png [22:05] that'd be enough [22:05] yeah [22:05] wxl says it's possible using the current code [22:05] right? [22:05] well with a few tweaks [22:05] aha [22:06] visually all that is, relative to what we already have is a fixed (non expanding) area, with a specific color [22:06] although it ALSO has the windows [22:06] that will take more i believe [22:06] it should take the accent colour of the theme [22:06] aka "selection colour" [22:07] i'm not sure i grok this enough to know where the color is even coming from. obviously, it seems to match the panel color [22:08] I'm sure that colour variable is being used in the code [22:08] yeah it's just not entirely obvuious [22:09] yes, tsimonq2, I said COLOUR .___. [22:10] i can say this is where the expanding size comes from https://github.com/lxde/lxqt-panel/blob/master/plugin-desktopswitch/desktopswitchbutton.cpp#L43 [22:10] and it does look like you can choose not to use a label https://github.com/lxde/lxqt-panel/blob/master/plugin-desktopswitch/desktopswitchbutton.cpp#L56 [22:11] so it's a switch [22:11] it seems like (not a c++ expert) the button is inheriting things from a parent https://github.com/lxde/lxqt-panel/blob/master/plugin-desktopswitch/desktopswitchbutton.cpp#L37 [22:13] and there is some style function (assumedly from QStyle) that allows it to change color with alerts https://github.com/lxde/lxqt-panel/blob/master/plugin-desktopswitch/desktopswitchbutton.cpp#L81 [22:32] is there a problem with the current lubuntu-next iso? [22:32] it just dies on boot in vbox 5.2.6-120293~Ubuntu~trusty [22:33] Yes [22:34] what's the deal? [22:35] get a working vbox - thats the primary problem - secondary problem is the, erm, strange design right now [22:35] oh vbox works fine, actually [22:36] * tsimonq2 nods [22:36] ok - more verbose about - if you get finally a black screen, the iso is started correctly, only the settings are messed up [22:37] no, i mean it crashes [22:37] could you provide a log? [22:37] i get to the GRUB menu and then if i select try or install it dies [22:37] a vbox log, sure [22:38] actually even the old check disc for defects fails [22:38] right now i have a problem with vbox (upstream) - and it might be a kernel problem to, in my case it is - dkms don't like some migitation patches in my kernel or the provided headers [22:39] beside of that - the current iso just work fine with kvm [22:39] * agaida will just fix his vbox [22:39] harumph [22:41] xp works.. a super old precise lubuntu works... [22:42] That's because those are OLD :) [22:45] weird that there's nothing on the tracker suggesting problems [22:55] @gilir, Yes [23:25] yeah it is something with the current kernel. harumph [23:26] the guest kernel [23:26] that's weird. haven't had that one yet [23:28] https://www.youtube.com/watch?v=yWssLQSlRdQ [23:28] todays image [23:29] current vbox, kernel 4.14.15 [23:30] so what ended up fixing it? [23:30] i had to delete a line in the kernel headers - a unmotivated retpolline mention - and rebuild the kernel objects [23:31] and after that just start the vm from the ispo [23:31] this is upstream vbox yah? [23:31] this is upstream - sid and debians vbox aren't good ideas - esp if one run his own kernel [23:33] you might notice some lxde packages in the iso and lightdm as dm - fixed yesterday, unfortunately the newest meta packages wasn't used in that build [23:33] so the remaining problems are "only" some settings [23:34] ok, not exactly release ready, but very usable - if one can start it and know the beast [23:35] heh we don't even have 4.14 in bionic [23:37] :) - thats one point in siduction - we don't use the debian kernel - ok, we borrow some settings now and then - but we manage a set of patches from the upstream queue and so on [23:37] and if we like something - we just throw it in :P [23:38] so it seems the fix was the kernel [23:39] thats esp. helpful when it comes to patches or minor glitches - get a patch, apply it, upload it - and just update the system 25 mins later [23:39] but we have an older kernel and it still seems to be a problem [23:39] i'm on 4.4.0 [23:39] two possible choices - try upstream vbox or kvm - at least kvm should work fine without glitches [23:39] i am using upstream vbox [23:40] i always do [23:40] strangse [23:40] e [23:40] grr [23:40] and yes i can use kvm but that doesn't necessarily fix whatever problem there is with vbox [23:40] it seems to be something specific about the image that's failing [23:40] but your current problem is vbox and not the iso [23:41] the most current artful (17.10.1) works fine [23:41] the iso work fine even in Microsofts hyper-v [23:41] and the problem is not restricted to lubuntu [23:43] so i guess that you are not running the latest bionic on your workhorse? [23:43] nope [23:44] :) - sorry, no experiences with stable systems [23:46] and its not restricted to ubiquity either [23:46] alternate fails just the same [23:53] hmm - strange