[08:34] <coconut> When i multiboot two or more distro's, would they be able to share the same swap partition?
[08:36] <coconut> I have 32GB ram.
[08:40] <well_laid_lawn> coconut: sure
[08:41] <coconut> well_laid_lawn, ok so they do not interfere when i would reboot and start another distro from another partition?
[09:19] <guiverc> coconut, one can only run at a time, and you cannot hibernate a system to use the other (the other will overwrite the hibernated system's memory which will be in swap)  (I've not shared an encrypted swap though so can't speak to that)
[09:24] <coconut> guiverc, so the swap gets deleted every reboot?
[09:24] <guiverc> i don't think it's deleted... more considered unused at boot time (thus booted os will use swap found)
[09:32] <coconut> i see
[09:32] <coconut> thank you guiverc
[09:35] <guiverc> coconut, actually this system uses encrypted swap; shared between 18.04 & gorilla/20.10
[09:40] <coconut> guiverc, sounds like i want to know how much space i would need for just swap in a file under /.
[09:42] <guiverc> how much swap varies on your actual end-use case.. if you hibernate, you need enough for any hibernate.used + memory.used (most users wouldn't use all of 32gb I suspect very often). if you don't hibernate, you likely won't need much with all your ram (i'd lower swappiness anyway to reduce use unless your needs need ram)
[09:44] <guiverc> (lower swappiness comment gives wrong impression, I'd leave it standard & monitor, then consider if it needed to be lowered.. changing when/if necessary)
[09:48] <coconut> guiverc, laptop is just new, so i don't know whether i would hybernate... need some use case for this new thinkpad first. :)
[09:53] <coconut> (it is not a super fast laptop, so hybernation might be slow)
[09:59] <guiverc> coconut, hibernate is a system that allows you to save system state (memory) to disk/ssd to turn off, using less power than suspend (suspend is quick), speed of box isn't important with hibernate - but not everyone uses it https://help.ubuntu.com/community/PowerManagement/Hibernate
[10:58] <coconut> i will probably most likely want to suspend
[10:59]  * coconut is waiting on a new ssd to arrive
[15:58] <miu5> Hi, does anyone know where passwords and keys are stored in Xubuntu?  Is it gnome-keyring?
[15:59] <diogenes_> miu5, yes.
[16:15] <miu5> diogenes_, thanks.  Why does Xubuntu use a gnome application as a keyring ?  why doesnt it have its own?  just curious
[16:18] <diogenes_> miu5, it's not Xubuntu but it's Xfce doesn't have it's own.
[17:18] <Celso> Good afternoon!
[17:19] <diogenes_> hello.
[18:18] <kitster> hi my xubuntu os is not able to boot and it's on grub mode. have tried some online advice but can't work. can someone help?
[18:22] <diogenes_> kitster, tell us the full story.
[18:23] <kitster> i installed xubuntu 20.04 on my MacBook air and it was working fine. then my batt went flat and when i restarted it's in the grub command mode
[18:24] <kitster> went online to look for some solution and i tried a few of them like identifying ls partition to look for the boot file
[18:24] <kitster> cldnt find a command that could boot up the os
[18:25] <GLAT-agent1> Hello. I am selling GNU/Linux licenses. Contact me if you want one ($99 for single computer, $49 for each computer if purchasing for 25 or more machines).
[18:25] <diogenes_> what text do you see on the screen kitster ?
[18:25] <GLAT-agent1> "Your GNU/Linux copy is not activated"
[18:26] <diogenes_> GLAT-agent1, nice joke but not now.
[18:27] <kitster> grub>
[18:27] <diogenes_> and when you do ls?
[18:28] <kitster> it shows my partitions like (hd0,gpt2) (hd0,gpt1)
[18:29] <diogenes_> ls (hd0,gpt2)/
[18:30] <kitster> ls (hd0,gpt1)/ efi/
[18:30] <kitster> nothing on gpt2
[18:31] <kitster> shld i insert the usb that as the os file i first installed
[18:32] <diogenes_> yes boot live.
[18:33] <kitster> i kinda tried that but not sure how
[18:34] <kitster> ls shows the partitions in the usb
[18:36] <kitster> now i have (hd1,msdos3) (hd1,msdos2) (hd,apple1) (hd,apple2)
[18:37] <diogenes_> kitster, boot the system from the usb.
[18:38] <kitster> it can't boot from the usb. when i restart the machine it goes to the grub command again
[18:38] <kitster> i tried pressing F12 didn't work
[18:39] <GLAT-agent3> Hello. I am selling GNU/Linux licenses ($99 for single computer, $49 for each computer if purchasing for 25 or more machines).
[18:40] <diogenes_> kitster, so how did you manage to install?
[18:40] <kitster> i installed when it was running on mac os
[18:43] <kitster> let me try using those same steps
[18:44] <diogenes_> we need to find  (hd0,gptx) which contains your system so do: ls (hd0,gptx) untill you find /boot /etc /home ...
[18:50] <kitster> yeah i tried that method to look for the /boot/ etc file but to no success. am trying to reinstall from the usb now
[18:51] <diogenes_> ok
[18:51] <kitster> am seeing the logo now, hope it'll go well.
[18:52] <kitster> tks Diogenes for the guidance, reminded me on how i first installed on the machine
[18:53] <diogenes_> no problem.
[18:54] <kitster> it's starting again now, cheers!
[18:54] <diogenes_> good luck!
[20:11] <zenlinux> Hi all. I have a Dell XPS 13 (9343) that I've done a fresh install of Xubuntu 20.04 onto. If I suspend the laptop by using the Logout/Power dialog, suspend and resume work correctly. However, if I close and open the lid, when it resumes from suspend I can see my screen, move my mouse, but everything on the desktop is frozen (e.g, if I had a
[20:11] <zenlinux> terminal window open, I can't type into it). My question is how can I make the lid open/close behavior do whatever the Logout/Power dialog action is doing?
[20:12] <zenlinux> I'm seeing some references to systemd's logind handing lid events, but my /etc/systemd/logind.conf is fully commented out.
[20:12] <zenlinux> so I *think* lid events are being handled by xfce power manager?
[20:14] <diogenes_> zenlinux, uncomment HandleLidSwitch=suspend.
[20:15] <zenlinux> alright, giving that a try - rebooting just to be completely sure the service has restarted...
[20:16] <diogenes_> wait
[20:16] <diogenes_> that's not all
[20:16] <diogenes_> cp /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml
[20:17] <diogenes_> mousepad ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml
[20:17] <diogenes_> somewhere between the lines add:
[20:17] <diogenes_> <property name="logind-handle-lid-switch" type="bool" value="true"/>
[20:17] <diogenes_> xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s true
[20:18] <diogenes_> reboot
[20:22] <zenlinux> ok, tried that - getting the same behavior unfortunately. should I be setting the lid events to something other than "suspend" in the xfce power settings?
[20:25] <zenlinux> yeah, looks like changing those settings re-writes the ~/.config file, so repeating the process
[20:25] <diogenes_> zenlinux, yes put blank in xfce4 power manager.
[20:26] <diogenes_> Switch off Display
[20:29] <zenlinux> kk, going afk for few, will report back
[20:31] <diogenes_> ok
[20:32] <n-iCe> hi
[20:36] <diogenes_> hi
[20:50] <zenlinux> diogenes_: still no luck. I've tried putting the relevant config and xfconf-query info in this gist: https://gist.github.com/ScottGarman/90db55c78155379998cdfab03934c61e
[20:52] <diogenes_> zenlinux, let's see if it at least works, try instead of suspend to put poweroff, HandleLidSwitch=poweroff
[20:52] <zenlinux> good idea, I'll give that a spin
[20:54] <diogenes_> it will work only after reboot.
[20:54] <zenlinux> nod
[20:55] <xubuntu23i> Yeah, i'm installing Xubuntu
[20:55] <zenlinux> ok, I can confirm that HandleLidSwitch=poweroff in logind.conf works to power off the laptop
[20:55] <zenlinux> upon closing the lid
[20:56] <diogenes_> then it executes the command.
[20:57] <zenlinux> right, and typically before I close the lid I bring up a terminal that does a tail -f of /var/log/syslog, so when I open it up again I can confirm that it was suspending
[20:57] <zenlinux> I think the issue is in resume from suspend
[20:57] <zenlinux> resuming from suspend seems to work fine when I do it from the Logoff/Power dialog
[20:59] <zenlinux> I'm not seeing any odd messages in the syslog when I resume either - no kernel panics or video errors
[21:01] <diogenes_> maybe look in bug reports, one thing i can tell for sure is that linux inherently has had problems when it comes about suspend/resume, try after resume to switch TTYs back and forth.
[21:02] <zenlinux> ok, I'll keep hunting. totally appreciate the time you took to troubleshoot this with me! and it's good for me to know about the bits in ~/.config that power manager uses
[21:03] <diogenes_> you're welcome
[23:01] <Yogui> ¿Se puede hablar en español aquí?
[23:04] <Unit193> Hello!  This is an English speaking channel, if you'd like help in Spanish please see:
[23:04] <Unit193> !es