=== arraybolt3_ is now known as arraybolt3
=== meetingology` is now known as meetingology
[16:39] <arraybolt3> Is there any way for me to get an email every time a new upload has been done in the Lubuntu packageset? I see other Ubuntu devs keep syncing LXQt stuff from Debian into Ubuntu and would like to be notified when that happens.
[17:10] <RikMills> arraybolt3: not aware of any way to get just those. you can subscribe to the lunar-changes list which gets an email for every upload and filer with rule perhaps
[17:10] <RikMills> *filter
[17:11] <arraybolt3> Hmm, that sounds doable.
[17:11] <RikMills> https://lists.ubuntu.com/mailman/listinfo/lunar-changes
[17:13] <RikMills> I do a similar thing for debian changes list, so I know when one of the qt-kde uploaders has uploaded something
[20:57] <lubot> [telegram] <lynorian> sigh I have had openbox crash on me but need to figure out a way to have it be reproducible to actually make a good bug report
[22:50] <guiverc> @lynorian, what release are you running?   I experienced a crash yesterday too but was first & tend to overlook first until occurs again; which it just did (openbox crash in /var/crash)
[23:06] <guiverc> to recreate crash here, open snap package (chromium/firefox/telegram..) make it full screen (F11) then open something in new window (right-click open new page for browser, ~equiv in telegram) & openbox crashes...
[23:06] <lubot> [telegram] <lynorian> lunar
[23:07] <guiverc> yeah lunar here, have caused it to crash with firefox, chromium, telegram (ie. snap packages)
[23:10]  * guiverc is logging out & will explore same in xubuntu/xfce..  (alas not using openbox, but will still look)
[23:11] <lubot> [telegram] <lynorian> sadly not quite as simple for me
[23:12] <lubot> [telegram] <lynorian> or is it opening two snaps at once?
[23:26] <guiverc> I did not re-create it in either Xubuntu/Xfce or Ubuntu-Desktop/GNOME.using.Xorg but neither use openbox  (openbox started/running in background didn't crash, but expected as its not being used)
[23:28] <lubot> [telegram] <lynorian> also it crashes pretty immediately if you run openbox again
[23:32] <guiverc> my default usage has 3 snaps running; firefox, chromium & telegram; so on lubuntu i likely had more than one running at a time  (likely only had a single running in xfce/gnome during my brief test)
[23:32] <guiverc> I am not having it re-crash if I CTRL+ALT+T & run `openbox &` though
[23:33] <guiverc> to get it to re-crash I have to re-open a tab/window using full-screen window
[23:37] <guiverc> turned on another box (lunar) & opened firefox as crashes on my main system (qterminal only other open app) & NO CRASH here... you maybe right with needing multiple snap...
[23:38] <guiverc> nope... chromium & firefox both running (2nd box) & no crash on other box..
[23:40] <guiverc> me added telegram (3rd snap) & no crash too  (on second box; my primary has crashed ~8 times today in testing; on queue each time)
[23:43] <lubot> [telegram] <lynorian> what gpu driver are you using
[23:43] <lubot> [telegram] <lynorian> amdgpu here
[23:45] <guiverc> my primary box where I've had openbox crashes reports hd530/i915  (two displays connected to old amd/radeon card in it)
[23:45] <lubot> [telegram] <lynorian> is it requireing multiple monitors plugged in
[23:45] <lubot> [telegram] <lynorian> I remember using one monitor yesterday and thinking that it didn't crash as much then
[23:46] <guiverc> i have 3 monitors connected to my primary; 1 to intel; 2 into radeon - all used.. the other box i'm using is similar though; radeon with 2 monitors plugged (from memory) & intel reported using `lshw`
[23:47]  * guiverc is updating software on other box & will re-test.. 
[23:58] <lubot> [telegram] <lynorian> reported https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011753
[23:58] -ubottu:#lubuntu-devel- Launchpad bug 2011753 in openbox (Ubuntu) "openbox crashes with at least three snaps open." [Undecided, New]