Re: [ubuntu-studio-devel] xfce4-screensaver
Hi Ross, On Sun, Mar 10, 2019 at 8:17 AM, Ross Gammon wrote: Hi Erich, On 3/10/19 12:43 AM, Erich Eickmeyer wrote: Hi all, Sean Davis (bluesabre) did an amazing job and ported mate-screensaver to xfce4-screensaver. The motivation, as I understand it, is because light-locker is largely unmaintained and causes a race condition when resuming from sleep due to the vt change (or something like that, we don't need to get too technical on this). With that, light-locker and xscreensaver are being largely depricated by the Xubuntu team (who can correct me if I'm wrong... well, anybody can correct me) in favor of xfce4-screensaver. I think this change, if it needs to happen in our seeds, needs to happen. If you want to test it first, that's good practice. That said, I can say from personal experience that I have experienced the light-locker race condition myself, and it's definitely not a good bug to have. Anyhow, we don't need to make this change immediately. Our priority right now is the Developer Membership Board meeting happening on Monday at 1500 UTC (I may have posted that this was at 1200 UTC, that was a mistake) for mine and Ross's applications for Per-Package Uploader permissions. My application, I expect, will be rejected due to lack of experience, so I'm in it mostly for the feedback. However, we're hoping for success with Ross's application, which is getting a lot of support at present. With that, I want to say that this change in the seed, if necessary, isn't as high of a priority, but it would bring some good bug fixes to our default Xfce desktop. The last time we discussed screensavers was quite a while ago when Kai was still in charge and we decided to remove our Ubuntu Studio screensaver package becasue it was broken and we didn't have it in the seeds anyway. There was some discussion about the use of screensavers in general and it was decided that in the days of flatscreens the original purpose has disappeared, and the fact that in audio and video we might want to watch some rendering/mastering chuntering along for quite a while, that screensavers did not make much sense. I think the power management settings would need to be fiddled with to get the screensaver to work instead of blanking. But I suppose we could test it as a replacement for light-locker and see how it goes with audio/video work. I have not had a computer with a screen saver for so many years (at work or at home), I have forgotten what it is like :-) Ross I completely agree that with LCD screens the reason for screensavers (burn-in) has largely been removed. That said, this is more about screen locking than for the screensavers themselves. Unfortunately, with light-locker unmaintained and causing resume-from-sleep issues (that I have experienced, and apparently I'm not the only one), this is something that needs to happen. I'm working with the Xubuntu team on this one, since our setup largely needs to reflect theirs in terms of defaults since we're using their DE. Thanks, Erich -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190309
Hi Ross, On Sun, Mar 10, 2019 at 7:36 AM, Ross Gammon wrote: Hi Erich, On 3/10/19 1:55 PM, Ross Gammon wrote: Hi Erich, It seems there is a problem with the plymouth theme post-install maintainer script in ubuntustudio-look. On 3/9/19 7:31 PM, CD Image wrote: Setting up plymouth-theme-ubuntustudio (0.57) ... update-alternatives: using /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth to provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in auto mode update-alternatives: using /usr/share/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth to provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode update-initramfs: diverted by livecd-rootfs (will be called later) /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). dpkg: error processing package plymouth-theme-ubuntustudio (--configure): installed plymouth-theme-ubuntustudio package post-installation script subprocess returned error exit status 1 I haven't tried upgrading my test Disco machine yet, which I will do some time today. Any ideas? Cheers, Ross Well, the update went fine on an already installed Disco: Setting up plymouth-theme-ubuntustudio (0.57) ... update-alternatives: updating alternative /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth because link group default.plymouth has changed slave links update-initramfs: deferring update (trigger activated) Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency Found Ubuntu 18.10 (18.10) on /dev/sda2 Found Ubuntu 18.04.2 LTS (18.04) on /dev/sdb1 Found Ubuntu 18.10 (18.10) on /dev/sdb2 Found Ubuntu Disco Dingo (development branch) (19.04) on /dev/sdb3 Adding boot menu entry for EFI firmware configuration done I am a bit out of my comfort zone here, but it seems that /dev might not mounted at this stage in the LiveCD installation process. Do we need to add back in the guard that was taken out recently?: if [ -e /boot/grub/grub.cfg ] && which update-grub2 >/dev/null 2>&1; then Steve Langasek (whom I have CC'd in this email) said it's nothing we should worry about, but rather a bug in livecd-rootfs revealed by our grub/plymouth themes. I suggested putting the code back which you suggested, but he said something along the lines of that it shouldn't even be a factor to begin with. He has code for a change up for reveiw at https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/364206. So, this is one of those "Wait-and-see" things. Steve can chime-in too if he feels so inclined and can probably give more details than I. Erich -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] xfce4-screensaver
Hi Erich, On 3/10/19 12:43 AM, Erich Eickmeyer wrote: > Hi all, > > Sean Davis (bluesabre) did an amazing job and ported mate-screensaver to > xfce4-screensaver. The motivation, as I understand it, is because > light-locker is largely unmaintained and causes a race condition when > resuming from sleep due to the vt change (or something like that, we > don't need to get too technical on this). > > With that, light-locker and xscreensaver are being largely depricated by > the Xubuntu team (who can correct me if I'm wrong... well, anybody can > correct me) in favor of xfce4-screensaver. I think this change, if it > needs to happen in our seeds, needs to happen. > > If you want to test it first, that's good practice. That said, I can say > from personal experience that I have experienced the light-locker race > condition myself, and it's definitely not a good bug to have. > > Anyhow, we don't need to make this change immediately. Our priority > right now is the Developer Membership Board meeting happening on Monday > at 1500 UTC (I may have posted that this was at 1200 UTC, that was a > mistake) for mine and Ross's applications for Per-Package Uploader > permissions. My application, I expect, will be rejected due to lack of > experience, so I'm in it mostly for the feedback. However, we're hoping > for success with Ross's application, which is getting a lot of support > at present. > > With that, I want to say that this change in the seed, if necessary, > isn't as high of a priority, but it would bring some good bug fixes to > our default Xfce desktop. The last time we discussed screensavers was quite a while ago when Kai was still in charge and we decided to remove our Ubuntu Studio screensaver package becasue it was broken and we didn't have it in the seeds anyway. There was some discussion about the use of screensavers in general and it was decided that in the days of flatscreens the original purpose has disappeared, and the fact that in audio and video we might want to watch some rendering/mastering chuntering along for quite a while, that screensavers did not make much sense. I think the power management settings would need to be fiddled with to get the screensaver to work instead of blanking. But I suppose we could test it as a replacement for light-locker and see how it goes with audio/video work. I have not had a computer with a screen saver for so many years (at work or at home), I have forgotten what it is like :-) Ross -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190309
Hi Erich, On 3/10/19 1:55 PM, Ross Gammon wrote: > Hi Erich, > > It seems there is a problem with the plymouth theme post-install > maintainer script in ubuntustudio-look. > > On 3/9/19 7:31 PM, CD Image wrote: >> Setting up plymouth-theme-ubuntustudio (0.57) ... >> update-alternatives: using >> /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth to >> provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in >> auto mode >> update-alternatives: using >> /usr/share/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth to >> provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode >> update-initramfs: diverted by livecd-rootfs (will be called later) >> /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). >> dpkg: error processing package plymouth-theme-ubuntustudio (--configure): >> installed plymouth-theme-ubuntustudio package post-installation script >> subprocess returned error exit status 1 > > I haven't tried upgrading my test Disco machine yet, which I will do > some time today. Any ideas? > > Cheers, > > Ross > Well, the update went fine on an already installed Disco: Setting up plymouth-theme-ubuntustudio (0.57) ... update-alternatives: updating alternative /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth because link group default.plymouth has changed slave links update-initramfs: deferring update (trigger activated) Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency Found Ubuntu 18.10 (18.10) on /dev/sda2 Found Ubuntu 18.04.2 LTS (18.04) on /dev/sdb1 Found Ubuntu 18.10 (18.10) on /dev/sdb2 Found Ubuntu Disco Dingo (development branch) (19.04) on /dev/sdb3 Adding boot menu entry for EFI firmware configuration done I am a bit out of my comfort zone here, but it seems that /dev might not mounted at this stage in the LiveCD installation process. Do we need to add back in the guard that was taken out recently?: if [ -e /boot/grub/grub.cfg ] && which update-grub2 >/dev/null 2>&1; then Using Debian Code Search, I found a few other packages where this is used and the comments mention being in a build chroot: https://codesearch.debian.net/search?q=path%3Adebian%2F*.postinst+update-grub Cheers, Ross -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190309
Hi Erich, It seems there is a problem with the plymouth theme post-install maintainer script in ubuntustudio-look. On 3/9/19 7:31 PM, CD Image wrote: > Setting up plymouth-theme-ubuntustudio (0.57) ... > update-alternatives: using > /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth to > provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in > auto mode > update-alternatives: using > /usr/share/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth to > provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode > update-initramfs: diverted by livecd-rootfs (will be called later) > /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). > dpkg: error processing package plymouth-theme-ubuntustudio (--configure): > installed plymouth-theme-ubuntustudio package post-installation script > subprocess returned error exit status 1 I haven't tried upgrading my test Disco machine yet, which I will do some time today. Any ideas? Cheers, Ross -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
