[00:11] <tomreyn> LilUFO: i don't know this one, but generally speaking, gnome-shell-extensions are dragon lands ("here be dragons").
[00:11] <LilUFO> ah
[00:12] <LilUFO> I'm running arch, but I use the tray extension that is part of the ubuntu desktop
[00:12] <LilUFO> just curious if there were similar problems
[00:12] <leftyfb_> :/
[00:12] <LilUFO> I've read about hp-systray working improperly with the ubuntu tray extension
[00:13] <LilUFO> If I were to guess it might be the explicit lack of support for tooltips :P
[00:13] <LilUFO> which in that case it really isn't doing anything wrong
[00:13] <leftyfb> #arch | LilUFO
[00:14] <leftyfb> #archlinux | LilUFO
[00:14] <leftyfb> bah
[00:14] <leftyfb> !arch | LilUFO
[00:14] <leftyfb> !archlinux | LilUFO
[00:15] <LilUFO> hah sorry didn't mean to be rude
[00:15] <LilUFO> I just thought this might be the place to ask about that ubuntu-specific tray extension
[00:16] <leftyfb> how is it ubuntu-specific?
[00:16] <LilUFO> ah true, it really is just the tray used in Ubuntu
[00:17] <LilUFO> it was a silly question, sorry to ask :/
[00:36] <tripp4h> sarnold: what would you help with amixer?
[00:39] <sarnold> tripp4h: it might show you muted devices or something similar
[03:58] <shark> Hi All!!
[03:58] <shark> Lot of crashes happening.
[03:58] <webchat0> Hey.
[03:58] <webchat0> Bot?
[03:58] <webchat0> Nope.
[03:58] <webchat0> Sorry.
[03:59] <webchat0> I've just killed systemd from system monitor, and now all icons (including terminal), wallpaper, menu, (almost everything) disappeared. All I've access to now is file system.
[03:59] <shark> -rw-r--r--  1 kernoops whoopsie      750 Jul 30 01:14 linux-image-4.15.0-151-generic.31772.crash
[03:59] <shark> -rw-r--r--  1 kernoops whoopsie      755 Jul 30 01:14 linux-image-4.15.0-151-generic.31702.crash
[03:59] <shark> -rw-r--r--  1 kernoops whoopsie     3085 Jul 30 01:47 linux-image-4.15.0-151-generic.205774.crash
[03:59] <shark> -rw-r--r--  1 kernoops whoopsie      735 Jul 30 08:37 linux-image-4.15.0-151-generic.33389.crash
[03:59] <shark> -rw-r--r--  1 kernoops whoopsie     3200 Jul 30 08:38 linux-image-4.15.0-151-generic.216214.crash
[03:59] <shark> -rw-r--r--  1 kernoops whoopsie     3228 Jul 30 09:43 linux-image-4.15.0-151-generic.220453.crash
[04:00] <webchat0> What to do restore everythin back to normal?
[04:00] <matsaman> webchat0: restart the systemd service, or just reboot
[04:01] <shark> My system is getting freezed.
[04:01] <shark> While working.
[04:01] <webchat0> how? I restarted it couple of times.
[04:01] <webchat0> But it didn't helped.
[04:01] <webchat0> Can you please tell how to restart systemd?
[04:03] <matsaman> just restart the OS then
[04:04] <webchat0> Sorry. Is restarting OS equivalent to restarting computer?
[04:07] <shark> My system is getting freezed.
[04:07] <shark> While working.
[04:08] <shark> Ubuntu 18 LTS
[04:08] <webchat21> I restarted it, but it didn't helped.
[04:09] <webchat21> It seems I'm not the "owner" of the system, because I cannot change the permission of executions of files.
[04:09] <webchat21> (Don't get me wrong, I own the machine, it is the machine who is not aware of this fact)
[04:09] <webchat21> XD
[04:10] <webchat21> (Now, how to really convince it that I'm the owner?)
[04:23] <shark> Here is the link having details->
[04:23] <shark> https://drive.google.com/file/d/16svmsj0XoP6zWDxtYfsD425s113Wk5x8/view?usp=sharing
[04:23] <shark> Pls help.
[04:38] <shark> ok putting here
[04:38] <shark>  BUG: Bad rss-counter state mm:00000000969bc6a1 idx:2 val:-1
[04:38] <shark>  BUG: Bad rss-counter state mm:00000000969bc6a1 idx:3 val:1
[04:38] <shark>  wlp2s0: authenticate with f8:da:0c:37:de:d5
[04:38] <shark>  wlp2s0: send auth to f8:da:0c:37:de:d5 (try 1/3)
[04:38] <shark>  wlp2s0: send auth to f8:da:0c:37:de:d5 (try 2/3)
[04:59] <Aro> I think there might be a bug where when I have Ubuntu running for over somewhere between 12 and 24 hours, it freezes up. I'm running Ubuntu 21.04 64-bit on the Raspberry Pi 4B.
[05:01] <Aro> Another thing I noticed is a portion of my RAM allocated for video memory, but Ubuntu still things that's available as normal memory.
[05:09] <kwilczynski> shark: That is a detailed issue report!
[05:10] <kwilczynski> shark: 4.15.0-151 - what version of Ubuntu do you run?
[05:43] <Guest83> hi all
[05:43] <Aro> Hi
[05:44] <Guest83> Aro hi
[05:45] <Aro> :(
[08:21] <unstablewifi4448> Can anybody help me with my wifi or direct me where I can get help, please?
[14:49] <movah4c> Hello, i have a little problem with the lazarus-ide and compiled programs. The IDE start takes 20-30 seconds to show up. I fixed that with addding "--no-splash-screen --primary-config-path=/home/mov/.lazarus/ %f" to the "startlazarus" program. But the compiled programs have the same problem. They are all starting with a delay of 20-30 seconds. How can i fix that?
[14:51] <leftyfb> movah4c: sudo apt install appmenu-gtk2-module
[14:53] <movah4c> leftyfb, tank you i try it out now
[14:53] <leftyfb> movah4c: I found that solution by typing "ubuntu lazarus slow" into google and clicking on the first result
[14:55] <movah4c> leftyfb,  then my search phrase was to long :)
[14:55] <movah4c> leftyfb,  not working
[14:58] <leftyfb> movah4c: maybe try recompiling the application you're using to test with?
[14:58] <movah4c> did that just now
[14:59] <movah4c> same result compiling takes a few seconds and starting takes  20-30 sec.
[14:59] <leftyfb> some other possible solutions: https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start
[14:59] <leftyfb> other than that, I have no idea
[15:00] <movah4c> ok i look at that page now
[15:02] <arh> Hello. Does anyone here know how can I encrypt/password-protect a folder?
[15:02] <movah4c> hmm, if i launch it with "dbus-launch <progname>" it's there in 1-2 seconds
[15:03] <arh> I tried ecryptfs but I was unsuccessful making it work
[15:04] <TJ-> arh: depends on which file-system ; ext4 supports encryption per directory
[15:04] <arh> TJ-, really? Is there a GUI for that?
[15:04] <Aro> I think there might be a bug where it freezes up when I have Ubuntu running for over somewhere between 16 and 24 hours. I'm running Ubuntu 21.04 64-bit on the Raspberry Pi 4B. Does anyone have any tips of how I could definitively test this and rule out other causes?
[15:05] <TJ-> Aro: enable kernel 'debug' log-level and then review what was recorded just before it next locks up, in case there are clues
[15:05] <Aro> Also, I noticed is a portion of my RAM allocated for video memory, but Ubuntu still things that's available as normal memory. This causes a crash for sure when I use up everything.
[15:06] <Elliria> Hey there, I can use history | tail -5 to see the last five commands that I've issued in a terminal window. Is there a similar command to see the last five desktop or menu shortcuts that I've clicked?
[15:07] <TJ-> Elliria: no
[15:07] <Elliria> It doesn't have to be five, by the way. That was just an example.
[15:07] <Elliria> Blast.
[15:09] <Aro> TJ-, the problem is, I don't know when exactly it would freeze. It might be too late to check when I know it freezes.
[15:10] <TJ-> Aro: you'd check afterwards when it's rebooted, in the hope the log caught some clue
[15:10] <Aro> Oh they get retained?
[15:10] <leftyfb> Aro: journalctl -k -b1
[15:10] <Aro> Where?
[15:10] <leftyfb> Aro: that'll show you kernel messages from before the last boot
[15:11] <Aro> Ahh
[15:12] <alkisg> If it's a kernel panic, it might not show up in the logs. Try to make it freeze while at vt2 (ctrl+alt+f2), so that you see the kernel panic messages on screen (or get a serial cable...)
[15:13] <leftyfb> Aro: right, to add to alkisg's suggestion, open up a virtual terminal (VT2) and run dmesg -Tw. Then wait till it freezes and see if there's anything that shows up on the screen. Make sure to disable suspend or the screen blanking/sleeping
[15:17] <BluesKaj> Hi all
[15:17] <Aro> Oh let me try that.
[15:32] <movah4c> leftyfb, here they the same problem "https://forum.lazarus.freepascal.org/index.php?topic=51016.0". I try it now with a reboot. Thank you.
[15:58] <movah4c> leaftype, this did it: "sudo dpkg-reconfigure appmenu-gtk-module-common"
[15:59] <leaftype> movah4c: think you auto-corrected to the wrong person. I'm assuming you meant leftyfb
[15:59] <movah4c> leaftype, oh yes :) sorry
[16:00] <movah4c> leftyfb, this did it: "sudo dpkg-reconfigure appmenu-gtk-module-common"
[16:09] <shimbles> how do I find out who is filling up my root volume and what file(s)
[16:10] <Mekaneck> older kernels maybe?
[16:11] <oerheks> nowadays ubuntu removes old kernels after reboot and update again
[16:11] <shimbles> my root volume is going from 0 to 100% during a workload; how do I find out exactly what's up
[16:11] <leftyfb> shimbles: sudo apt install ncdu ; sudo ncdu -x /
[16:12] <Mekaneck> oerheks: thanks, good to know
[16:12] <oerheks> those are 0kb updates :-D
[16:13] <shimbles> more specifically, disk utilization reported by df -ha for /dev/xvda1 mapped to / goes from about 100G free to about 0G free during a workload, after which it is cleaned up; i'd like to find out who is doing that, and tell them to do it somewhere else
[16:14] <shimbles> who being, some code that i wrote
[16:14] <shimbles> which calls some code that someone else wrote
[16:14] <leftyfb> shimbles: uhm it's your code. Write it to write data elsewhere.
[16:15] <shimbles> so, disk utilization is going up, but no file tools seem to be able to pinpoint where its happening
[16:16] <leftyfb> shimbles: you're looking for iotop
[16:17] <shimbles> i am looking for the specific location on disk that's being written to
[16:17] <shimbles> no tool that i've tried shows me; but eventually the disk fills up, program dies, which frees up the disk again
[16:17] <leftyfb> shimbles: use ncdu like I showed above while the disk space is mostly filled up
[16:18] <shimbles> it's not revealed by ncdu
[16:18] <shimbles> the only place i can see the utilization changing, is df -ha
[16:19] <leftyfb> shimbles: wait till your disk is almost full, then pause the program with CTRL+Z, then use ncdu to see where most of your disk utilization is taken up
[16:20] <shimbles> the utilization is several multiples above the known files on disk; ncdu can't see what is taking up that space
[16:20] <leftyfb> huh?
[16:20] <leftyfb> nc will tell you which directories/files take up the most space starting with your top level directory if you tell it to start at /
[16:20] <leftyfb> ncdu*
[16:21] <shimbles> according to ncdu, /var 13G /usr 6G /home 1G, and how there are 45G used on /, constantly increasing
[16:22] <leftyfb> shimbles: ncdu isn't realtime. It reads it once. Fill up the space with your $program and pause it, then use ncdu to see a snapshot of disk utilization and determine where most of it is
[16:23] <shimbles> that tool doesn't work for this problem; moreover, it's not particularly useful
[16:23] <leftyfb> shimbles: ok, good luck
[16:23] <shimbles> compared to more standard tools
[16:23] <movah4c> shimbles, maybe try lsof
[16:24] <shimbles> lsof strongly suggests the culprite is pyspark
[16:25] <shimbles> which i have instructed to keep its data elsewhere; also, where exactly it would be writing, such that it can't be seen as an actual file, i am not sure about
[16:28] <alkisg> shimbles: if an app creates a temp file, then deletes it while still open, the app still has a handle to it and can write to it and it won't show up in `ls`. Sometimes this is used for temp files.
[16:29] <alkisg> https://unix.stackexchange.com/questions/68523/find-and-remove-large-files-that-are-open-but-have-been-deleted
[16:34] <shimbles> thanks alkisg
[19:30] <akulbe> I have an Nvidia GPU and I can't get resolution past 1024x768, even though I have the recommended nvidia-drivers-470 package installed. Help?
[19:31] <akulbe> this is on 20.04, btw
[20:37] <locsmif> I have a few packages about to be upgraded. Of at least one of them, I'd like to its changelog before I upgrade. Can I do that from the cli, right now, before installing, or do I have to download the package, unpack it and try to find it in there?
[20:38] <leftyfb> locsmif: apt changelog <package name>
[21:06] <Walex> locsmif: also "C" in Aptitude
[21:07] <ludiusvox> hello
[22:00] <the_restless> quit
[22:23] <Guest25> I have been trying ubuntu out on a 2015 iMac. It seems to work fine except for shutdown. It won't shutdown. It ends up hanging up and then rebooting. Choosing to restart instead of shutdown works fine. I've looked through a bunch of threads various places I've found searching the internet but none of the typical grub kernel command line tricks seem
[22:23] <Guest25> to work. Does anyone have any experience with this issue on a 2015 21.5" iMac?
[22:33] <src> Guest25: just out of interest, same issue when initiating shutdown from cli?
[22:33] <src> poweroff or shutdown -H now
[22:34] <src> Guest25: also we need the exact version of ubuntu you're using
[22:38] <Guest25> Yes, same issue.
[22:40] <Guest25> I reinstalled a couple of times after reloading mac os and making sure it shutdowns properly which it does. Latest test was the current LTS version which I just downloaded. 20.04.2.0. I booted from USB and did the try instead of install and it happens there too.
[22:43] <Guest25> I was considering trying debian testing or something next just to see if it's a kernel issue that might be fixed in a newer kernel. I was just hoping someone had run into this before. I've only had to deal with issues like this once or twice in linux before and I don't know very much about troubleshooting issues like this. This feels like it might
[22:43] <Guest25> be a tricky one to sort out.
[22:44] <src> how about downloading 21.04 before going so far as to install debian testing
[22:45] <src> Guest25: but let me have a look online
[22:46] <src> I assume you tried acpi=force in grub, did you have a look in your bios settings btw? If something could be related to it somehow?
[22:48] <src> Guest25: you should also check your logs via $ journalctl -b -1 -r
[22:50] <Guest25> Yes, I tried acpi=force. No real bios to speak of on an iMac. At least not in the traditional PC sense. There are some settings that can be made in Mac OS that stick between reboots, and I did try turning off wake on lan as I saw some reports of that curing the problem on some PCs, but it didn't help.
[22:51] <Guest25> I'll load 21.04 and see what happens.
[22:52] <src> Guest25: I would definitely save the systemd logs though
[22:52] <src> see journalctl command
[22:52] <src> on what the exact error is
[22:52] <src> so you can compare with 21.04 if the issue still persists and see if it's the same which might be valuable
[22:53] <leftyfb> Guest25: you can run the 5.10 and 5.11 kernel in ubuntu 20.04. No need to upgrade to 21.04
[22:53] <src> Guest25: hopefully needless to say, but your 20.04 installation is fully up to date?
[22:54] <leftyfb> Guest25: linux-image-generic-hwe-20.04-edge will give you the 5.11 kernel
[22:55] <Guest25> It's got Mac OS on it right now. I just ran 20.04 again from the USB drive to see if changing the wake on lan or power settings would make a difference. Didn't seem to change anything so I'll go ahead and try 21.04 since I've got in downloading to USB now. Shouldn't take too long to install.
[22:55] <leftyfb> Guest25: the only real difference that's probably going to affect you is the kernel, which you can run in 20.04 as mentioned above. Save you a lot of time by just installing that and rebooting
[23:13] <tomreyn> !acpi_osi | Guest25
[23:14] <tomreyn> this approach (trying to make it look like windows) may seem weird here, but it could still work.
[23:15] <tomreyn> acpi is the "advanced configuration and power interface", it's a way for firmware and OS to talk to each other, and handle power management (such as power off) events and firmware configurations queries.
[23:16] <Guest25> Interesting. I haven't tried that yet. Right now I'm waiting to see what happens with 21.04. I loaded it up and it booted fine. On shutdown it's hung at the little spinner. I'm just waiting to see if it's going to reboot or just freeze forever. Usually in the past it would reboot. If it just hangs that's at least different behavior.
[23:17] <tomreyn> if this firmware (the mac's) doesn't properly understand the way linux is teling it to "power off now", then trying to make it look like a more well known (to this firmware) OS is telling it to do so (windows) might actually make it do so properly. but it's really guessing. it helps on some systems but not others.
[23:19] <leftyfb> Guest25:  yeah, I guess you could have just completely ignored my suggestion to try the same kernel in 21.04 on the 20.04 install you already had and save you some time. That works as well
[23:19] <optimant> Guest25: do you know the model name of your specific iMac? you said 2015 and 21.5" so I think it's iMac16,1 or iMac16,2 but that can help search for bug reports and the like. (https://support.apple.com/en-us/HT201634)
[23:22] <tomreyn> the only things that should really matter there linux-wise are the kernel version and * really just maybe * the systemd version. as leftyfb pointed out (twice now ;-) ) you can switch between different kernel versions while you have an LTS release (20.04 being the latest) installed - it's probably good enough for testing.
[23:23] <Guest25> Yes, it's a 16,2
[23:24] <Guest25> Looks like it's just frozen at this point. It would have usually restarted on it's own by now on previous versions.
[23:32] <optimant> https://bugzilla.kernel.org/show_bug.cgi?id=103211 seems related - different hardware but similar presentation. that was patched with a model specific quirk, if you're up for building a kernel from source you could try editing the quirk to match your model instead. but the offending address range might be different, or it may be something completely unrelated
[23:32] <optimant> if messing with acpi config etc. doesn't yield anything that's where i would spend time trying to pick up the trail myself.
[23:35] <noarb-> I'm trying to study the layout of an apt repo in ubuntu. I was referencing the debian https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_debian_package_management_internals details about top-level and Archive-level Release files. Does ubuntu maintain a separate reference?
[23:40] <tomreyn> noarb-: i don't think there's separate documentation for ubuntu, things should be identical for .deb and apt repositories for the very most part. note there is also #ubuntu-devel
[23:53] <Guest25> I ran the updates to 21.04 and rebooted.  After the reboot I shutdown and it seemed to shutdown quickly. However after a minute or two it rebooted. I then tried suspend on a whim, and that behaved almost identically. Seemed like it turned off quickly, but rebooted after about 2 minutes. After it came back up I tried shutdown again, and it's been
[23:53] <Guest25> quiet for many minutes now with no reboot. I tried hitting keys on the keyboard and clicking the mouse and nothing, so I think it actually shutdown this time. Odd.
[23:55] <Guest25> Spoke too soon. It was hung up. The power button wouldn't reboot it. Had to hold down the button for a while and then press it again. :-(
[23:56] <britho> FWIW, I was getting a 500 error trying to access a specific page in the wiki a few times.  Once I visited the wiki's homepage, there 500 error went away.