[00:04] sudodus asked for a Lubuntu logo (scalable, svg?) on https://discourse.lubuntu.me/t/focal-fossa-20-04-lts-wallpaper-competition/566/38 ; I've looked and failed at finding one; anyone know a location easily? [00:07] guiverc: i *THINK* @kc2bez is on that one [00:07] btw guiverc does this describe you? [00:07] 0943 < lubot:#lubuntu-devel> Someone using nvida and dual monitors wit lubuntu lxqt? I'm having a hard time to configure it properly. [00:09] i have "hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)" with 2x 1920x1080 [00:09] ^ @HMollerCl [00:09] also hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) though currently 'live' only (no disk space) [00:15] @guiverc [ i have "hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)" with 2x 19 …], working ok? [00:15] are you using propietary or nouveau? [00:17] i only use them for qa-testing; dc7700 for installs; 8200 for 'live' so it'll be whatever is default (nouveau I'd suspect) .. booting 7700 now [00:17] yep nouveau [00:18] aaaa, ok, nouveau works fine for me too, problem is with propietary. Default config doesn't work well and in the formus I read that I need to create xorg.conf but when I create that sddm fails to start [00:25] I don't havea nvidia I kind of hate mounting gpus thouse and just got a new amd one [00:26] bug 1861465 [00:26] Bug 1861465 in calamares (Ubuntu) "Calamares 3.2.17.1 fails to erase existing partition" [Critical, Triaged] https://launchpad.net/bugs/1861465 [00:26] ^ we could always have a shellprocess job that renames os-prober XD [00:27] ^^^ @tsimonq2 want to make you aware of this because it's pretty freaking critical. [00:28] I may install lubuntu on 8200 next week ... loading nvidia-340 now on 7700 (ubuntu-drivers; 20.04), rebooting.. now driver=nvidia; the screen positioning appears default (doesn't match my screen setup) but otherwise looks normal.. [00:33] dc7700 was a ~clean install (i change wallpaper as sign of modifying config on qa-installs; this wallpaper was still default); logout; general play looks normal with minimal test since driver=nvidia on this box [00:33] @HMollerCl ^ [00:34] @wxl [ guiverc: i *THINK* @kc2bez is on that one], Yeah, sorry I haven't replied yet. I will do that tonight. [00:34] guiverc: trying to make it match your config is the problem [00:34] in my case nvidia-settings only detected one big screen [00:35] i changed screen positions to what I use, no issues, firefox stream local news etc. but it's minimal testing & not use.. [00:36] Thanks Dan (kc2bez) [00:37] guiverc: in my case dpi wasn't detected correctly and the default was unified view [00:39] it could be card specific.. i won't leave that box on though today (it's fan screams when ambient temperature is 30oC as it is today..) [00:44] @wxl [ ^^^ @tsimonq2 want to make you aware of this because it's pretty freaking …], Understood. Glad you can reliably repro [00:44] wxl: I updated copyright on the theme [00:45] saw that thx [00:45] @guiverc [ it could be card specific.. i won't leave that box on though today (it …], It has been really hot this summer in southern hemisphere... [00:46] @HMollerCl don't forget you need to update D71 [00:48] @wxl [ @HMollerCl don't forget you need to update D71], with qt5 vcl_plugin pdf problem, I think we should wait for that. [00:49] @HMollerCl i'm kind of of the opposite inclination since we're in a devel release.. let's get it in there and see what happens and revert it if we need to [00:50] wxl sorry I've not got to testcases & to chase you up (yet) [00:50] guiverc: np. you get your machine all back to normal? [00:53] wxl: I'm on another computer now, how can I get the same "branch"? [00:53] @HMollerCl you mean get your branch? [00:54] yes [00:54] arc patch D71 --nobranch [00:55] but I git clone the repo as normal [00:55] wxl my data is all there (outside anything .*), bzr issue remains (https://answers.launchpad.net/bzr/+question/688323) or "brz: ERROR: A control directory already exists" which I've had before, but haven't resolved yet. [00:56] @HMollerCl yep [00:56] @HMollerCl think of arc as a git frontend [00:56] guiverc: try checking our your branch instead of lp:ubuntu-manual-tests, i.e. lp:~guiverc/ubuntu-manual-tests/lubuntu-calamares [00:57] guiverc: and don't forget about #launchpad [01:00] wxl: how was that I use anorther user when cloning? seed is from launchpad.... [01:00] Thanks Walter, the lp:~guiverc gives a different issue, so I'll try there awhile.. (shortly) [01:01] @HMollerCl i'm not sure i understand? [01:01] guiverc: aw jeez. you really should check in at #launchpad [01:01] git clone 'ssh://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu' … ... … Launchpad user 'hmoller' doesn't have a registered SSH key … hmoller@git.launchpad.net: Permission denied (publickey). [01:02] because my launchpad user is "hmollercl" not hmoller [01:02] oh boy [01:02] that i'm not sure of [01:02] ask at #launchpad XD [01:03] jaja, I've done that before, I don't remember [01:03] oh [01:03] change the uri to ssh://hmollercl@git.launchpad… ? [01:04] facepalm [01:10] wxl:done [01:30] wxl: since there is only one branch for cala settings I just `arc land` right? [01:31] right [01:31] not sure why there's only one branch tho.... [01:31] thanks [01:31] I dunno [01:32] -lugito:#lubuntu-devel- [rCALASETTINGS2cc0bed73bcf: Add shellprocess for i386 multiarch] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rCALASETTINGS2cc0bed73bcf [02:01] guiverc: aw hell. good catch. [04:13] @HMollerCl [git clone 'ssh://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu' … ... … L …], Modify your .ssh/config file. … I remember someone offering me a dollar to get that right. [04:13] XD [06:19] -lugito:#lubuntu-devel- [rMANUAL9cd46a2aa1a4: Split tab into own paragraph] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL9cd46a2aa1a4 [06:51] -lugito:#lubuntu-devel- [rMANUAL3b31af5fe444: Update kde partition manager summary] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL3b31af5fe444 [11:09] https://phab.lubuntu.me/D79 [11:09] -lugito:#lubuntu-devel- [Needs Review] Merge from Ubuntu Merge-o-Matic: https://phab.lubuntu.me/D79 [11:11] @The_LoudSpeaker [ commit for l10n https://phab.lubuntu.me/rLXQTLTENNPACKAGING350 …], @tsimonq2 can you upload this? also, we should add it in packageset since debian added it back? [11:17] @The_Loudspeaker did that patch in lxqt-config apply cleanly and build? [11:17] yes it did. [11:17] the problem was that manpages weren't installed anywhere. [11:17] so I added a few lines in .install file. [11:18] That makes sense based on your paste yesterday. [11:18] https://phab.lubuntu.me/P62 … ^ This one is from from MoM. it doesn't have those install file changes which I made just now. So gives the error I pasted yesterday. [11:19] wxl: take a look at the patch in that ^^ I think it may address an issue we found a while ago. [11:19] which issue? [11:21] in the keyboard layout configuration and switching between different configurations [11:25] link ploxx? [11:26] The link in the patch takes you to the github issue :) [11:29] ow. yes. [11:49] -lugito:#lubuntu-devel- [rLXQTOPENSSHASKPASSPACKAGING5b12c424f345: Merge from Ubuntu M-o-M] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTOPENSSHASKPASSPACKAGING5b12c424f345 [11:54] @The_LoudSpeaker ^ [11:54] haa? [11:54] @The_LoudSpeaker [haa?], you put me as reviewer on the merge :P [11:55] yeah that one is for config. I was facing some issues. [11:56] https://paste.ubuntu.com/p/s7s4hdVHf7/ [11:56] ^ This one @RikMills [11:57] But it is fixed in the revision I added you as a reviewer. Kindly review when free. [11:59] side quest: once the package is out of proposed pocet, only then it disappears from Merge-o-Matic na? [11:59] @The_LoudSpeaker [But it is fixed in the revision I added you as a reviewer. Kindly review when fr …], I just commented on the merge [12:00] @The_LoudSpeaker [side quest: once the package is out of proposed pocet, only then it disappears f …], Correct [12:06] @RikMills [I just commented on the merge], I did a debdiff between previous ubuntu version and the one created from the merge. Shouldn't it have the changes from debian and changelogs as provided by debian when making those changes? [12:07] When you are doing the remaining changes section in the changelog, these are the differences between debian version and the result of your ubuntu merge. [12:08] okay. So I need to be more verbose about those changes. [12:09] @The_LoudSpeaker [okay. So I need to be more verbose about those changes.], Yes, as they are they to either remind you or inform someone else, what changes you kept and why. For example, 'update rules' doesn't tell anyone what was updated and why [12:10] also, I don't see the debian/upstream/metadata in the merge so not there in the revision. [12:10] @RikMills [Yes, as they are they to either remind you or inform someone else, what changes …], k. [12:11] @The_LoudSpeaker [also, I don't see the debian/upstream/metadata in the merge so not there in the …], it is in debian [12:11] But not in merge. [12:11] how so? [12:12] The merge was created by MoM I just fixed small errors and manpages thing. [12:12] I don't know, but not merge tool is perfect. Which is why I usually try to do a manual check with meld/kompare to check things over. [12:13] I found meld in software center but how do I install and use it via terminal? I have the work env in a container. [12:14] I will make the other updates to the revision about changelog entries in a while. Time for snacks. [12:16] You can do a ssh session where you can run a GUI app from the host. It lags, but it can work. I forget the option. … Or you could work locally. If you are not doing HUGE packages that is usually ok. [12:17] Other workaround could be a gui container. I will try setting that up. [12:34] You can also use sshfs-fuse to mount a remote file system [14:51] hi i'am testing pipewire 0.3 https://launchpad.net/~jan-koester/+archive/ubuntu/pipewiremaster but lxqt-panel chrashed with it https://pastebin.com/5Qg2UNQb [14:57] @Tuxist [ hi i'am testing pipewire 0.3 https://launchpad.net/~jan-koester/+archiv …], I think better go directly upstream to lxqt and ask them. [17:43] @RikMills can you explain `> - in debian control the Depends: sections have not been sorted and made a line per depend as in debian. This is a trivial difference, but IMO is a pointless delta to keep.` [17:43] as you wrote in your comment [17:46] (Photo, 1111x710) https://i.imgur.com/JFDOsAE.jpg [17:47] @RikMills [], K. Understood [17:49] same further down for depemds of Package: lxqt-config-l10n [17:50] also, about the vcs part, I see you have the change highlighted there in the photo. But isn't the comaprison wrong? I am comparing between two ubuntu versions, one before merge(0.14.1-0ubuntu1) and other after merge(0.14.1-3ubuntu1). while you are comparing between 0.14.1(debian one) and 0.14.1-3ubuntu1(after merge) [17:52] No, my comparison is correct as I am looking at the delta to debian you have after the merge [17:52] To see if there is delta that is not needed, or unexplained [17:57] In some parts like the debian/compat one, According to changelog, those changes are for 0.14.0 but shouldn't they be already there as we have 0.14.1 in our side? [17:57] @The_LoudSpeaker [In some parts like the debian/compat one, According to changelog, those changes …], referring to the first 3 points of your comment [17:59] @The_LoudSpeaker [also, about the vcs part, I see you have the change highlighted there in the pho …], in your comaprison, there will be some things highlighted which we already have in 0.14.1-0ubuntu1 [18:01] @The_LoudSpeaker [In some parts like the debian/compat one, According to changelog, those changes …], No, as no-one has merged with debian for a long time (well before that change) [18:02] @The_LoudSpeaker [in your comaprison, there will be some things highlighted which we already have …], Just because it is highlighted does not mean it is wrong. It is highlighting the delta to debian. … In the case of the Vcs that delta is wanted in Ubuntu. The point is that no-where in your remaining changes did you mention it. [18:06] @kc2bez: re https://github.com/lxqt/lxqt-config/issues/445 do *WE* have a bug for this? [18:06] Issue 445 in lxqt/lxqt-config "Shortcut for switching keyboard layout cannot be changed" [Closed] [18:07] @wxl [ @kc2bez: re https://github.com/lxqt/lxqt-config/issues/445 do *WE* have a …], good point. if there is, might want to add the LP bug to the changelog so it closes it. [18:07] @The_LoudSpeaker this time around are you trying to do the merge yourself or is this all trying to sync up phab? [18:08] @wxl [ @The_LoudSpeaker this time around are you trying to do the merge yourself …], I am trying to merge myself [18:42] @wxl [ @kc2bez: re https://github.com/lxqt/lxqt-config/issues/445 do *WE* have a …], I don't know but I vaguely remember that you and I were discussing it at some point. [18:42] Maybe it was from discourse? [18:58] @RikMills https://phab.lubuntu.me/D79#1705 [18:58] -lugito:#lubuntu-devel- [Needs Review] Merge from Ubuntu Merge-o-Matic: https://phab.lubuntu.me/D79#1705 [18:59] @kc2bez: https://discourse.lubuntu.me/t/lubuntu-19-10-lxqt-cannot-change-keyboard-layout-shortcuts-not-working/507 ? [19:02] @lugito [ 3[ Needs Review 3] Merge from Ubuntu Merge-o-Matic: 2https://phab.l …], So you are not going to correct the debian/upstream/meta or investigate/explain why the lubuntu depends/suggests differ so much? [19:03] @wxl [ @kc2bez: https://discourse.lubuntu.me/t/lubuntu-19-10-lxqt-cannot-change-k …], uff, I didn't follow up very well there. I think think that was what I was remembering. [19:04] Since those were in previous version, I'd like to see what @tsimonq2 has to say about them. I will make the changes if needed. [19:04] @RikMills [So you are not going to correct the debian/upstream/meta or investigate/explain …], ^ [19:05] @The_LoudSpeaker [^], rejecting then [19:07] I will try merging again. After some reading. [19:12] Thanks. I am being picky to try to help in the long run. :) [19:18] As much as I understand, MoM merges upstream, debian and last ubuntu version into a post-merge-ubuntu version. When the merge is complete, it gets applied over last ubuntu version. correct? So why are we bothered about the differences between debain version and the post-merge-ubuntu version? The changes on our side should just reflect changes between last ubuntu version and the post-merge-ubuntu version. [19:18] correct me if I am wrong anywhere. [19:24] ^ @RikMills [19:28] You are wrong because: … 'Remaining changes' means the difference between the debian version and your merged ubuntu version. IT DOES NOT mean the difference between the last ubuntu version and the new Ubuntu version as a normal changelog entry would. … It is important that it be this so that anyone doing another merge in the future, [19:28] or who is looking to drop changes altogether, can easily see from the changelog how your ubuntu version differs from the Debian version and, and why you decided that those changes were important enough to keep. … MoM output is automated, so it does not always do the right thing. Especially in cases were it have been a long log time since a merge wa [19:28] s done. [19:30] @kc2bez can you follow up, make sure the patch works, and respond accordingly to the thread? [19:35] @RikMills okay. Understood. [19:36] hey anyone want to help me sort through old bugs? e.g. https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta [19:39] so this popped up today which i've never seen before. anyways there might be some kernel changes we need to check out https://lists.ubuntu.com/archives/ubuntu-quality/2020-January/007184.html [19:40] That caught my eye too, we should see who set that up [19:41] @tsimonq2 hey you so how's it going? you going to be joining us for 20.04? XD [19:41] I'm uh, managing [19:42] I keep a pulse on things, I just don't step in a lot of the time [19:42] well glad to hear you're still alive :) [19:42] Barely XD [19:42] qyestion is is that legit wxl [19:42] question* [19:43] *injects caffeine into Simon's veins* [19:43] @teward001 [*injects caffeine into Simon's veins*], Hey if you're gonna do that, cure this cold I have [19:44] OH NO HE"S GOT CORONAVIRUS [19:44] ABI BREAK [19:44] ABI BREAK [19:44] ABI BREAK [19:44] XD [19:45] XD [19:49] ack [19:50] @wxl [ @kc2bez can you follow up, make sure the patch works, and respond accordin …], I will try to test that this weekend and reply. [19:51] danke [19:51] sorry for dropping the ball. [19:51] oh no problem [19:52] i've caught a couple of those support things where they were autoclosed but still needed a response [19:52] if you want to generally take a look over those, that might be cool. ping me if anything needs help [20:10] @tsimonq2 [Hey if you're gonna do that, cure this cold I have], i can't you has pootisvirus [20:10] its incurable [20:28] can someone remind me what the deal is with https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1827501 ? [20:28] Launchpad bug 1827501 in lubuntu-meta (Ubuntu) "keyboard layout different changes during installation set-up and boot for de-encrypting unencrypting hard drive" [Undecided, Confirmed] [20:28] i think the difference with mate/us is because we're doing an encrypted /boot with cala, no? [20:32] mate is different. grub is doing the unlocking for us. they are using lvm+luks. I think lvm does the unlocking for them. [20:36] There is an upstream bug that should probably be tied in if it isn't already. https://github.com/calamares/calamares/issues/1203 [23:48] -lugito:#lubuntu-devel- [T104: Get translations going again] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T104#3078