[00:01] <tomreyn> Praxis: well, the problem you're seeing is probably related to the afpd (netatalk) failing. if you can stop this service for now and see whether that fixes it, it should get easier to debug this.
[00:01] <tomreyn> that's based on the limited systemd journal you posted at https://pastebin.com/raw/UYVxQ46L
[00:02] <Praxis> tomreyn interesting
[00:02] <Praxis> will do
[00:02] <tomreyn> it's possible that this is somehow related to the plex media server instance you're also running on this system.
[00:03] <Praxis> I've been using netatalk because samba was being annoying, but it started failing a while ago
[00:05] <Praxis> I'm going to reboot and see if disabling netatalk helps
[00:06] <tomreyn> i'm going to bed and see whether that helps
[00:07] <Praxis> tomreyn thanks
[01:18] <Praxis> tomreyn that wasn't it
[01:33] <jhutchins> Praxis: Still trying?
[02:28] <Praxis> jhutchins yeah
[02:28] <Praxis> I mean at this point i'm kinda lost
[03:09] <tupoy> im running Jammy.  gnome.  I have a Desktop shortcut to Home ( obviously to my files in ~/ )  .  How can I create a shortcut like that for another dir , like ~/Documents/ ?
[03:10] <arraybolt3[m]> tupoy: Open the file manager (Nautilus).
[03:10] <arraybolt3[m]> tupoy: Then click the triple lines right next to the Minimize button.
[03:11] <arraybolt3[m]> tupoy: Next click "Preferences", and switch on the "Create Link" option.
[03:11] <arraybolt3[m]> tupoy: Now right-click on the Documents folder and click "Create Link".
[03:11] <arraybolt3[m]> tupoy: Now drag the new "Link to Documents" link onto the "Desktop" folder.
[03:12] <arraybolt3[m]> And... now where's that refresh button when you need it (this worked for me before...)
[03:12] <arraybolt3[m]> Oh wait, there it is. OK, the new link should now be in the lower-right corner of the screen.
[03:13] <tupoy> thats not the kind of link im looking for on the Desktop.  it looks like the Home icon is special somehow
[03:13] <tupoy> is what you suggested any different than " cd ~/Desktop ; ln -s ~/Documents " ?
[03:13] <arraybolt3[m]> tupoy: True. The Home icon has a special switch in GNOME just for it.
[03:18] <arraybolt3[m]> tupoy: And no, the steps I listed are functionally identical to the command you mentioned.
[03:19] <arraybolt3[m]> (Except it does enable a fancy setting in Nautilus.)
[03:20] <arraybolt3[m]> If you can find the icon used for the Documents folder, you can probably set that icon on a manually made link of this kind and get a similar effect (however my attempts at finding said icon have been futile so far...).
[03:21] <arraybolt3[m]> (Granted, I've only been looking through the folders and didn't do a Web search - you could probably find the icons instantly that way. /me wonders why I didn't do that before)
=== gacuxz1 is now known as gacuxz
[05:03] <sdubois> Hello. I'm running 22.4 ubuntu mate. I have a an external usb drive formatted as exFAT. Ubuntu seems to mount this fine, but the permissions on it are very locked down. I've tried changing the mount point to be /media/drive-name, and changed the chmod on that directory. The most I am able to get is temporary write access, but when I reboot it is
[05:03] <sdubois> again locked down and owned by root:root
[05:03] <sdubois> Kind of running out of ideas here...
[05:06] <lotuspsychje> !chmod | sdubois
[05:06] <ubottu> sdubois: An explanation of what file permissions are and how they can be manipulated can be found at https://help.ubuntu.com/community/FilePermissions
[05:07] <lotuspsychje> sdubois: another idea could be dragging your data off (backup) and reformat it fresh, see what the usb does
[05:12] <lotuspsychje> sdubois: usualy gparted does a great job formatting media
[05:12] <sdubois> was hoping to avoid that, its a very large drive...
[05:14] <lotuspsychje> i see, maybe you can pastebin your permissions of your usb, so the volunteers can check on it and help you sdubois
[05:35] <sdubois> i think i fixed it... i added umask=0000 as an option in fstab
=== realivanjx7 is now known as realivanjx
=== realivanjx6 is now known as realivanjx
[06:28] <Guest92> how do I get window previews on ubuntu
[06:28] <Guest92> from dock
[06:28] <lotuspsychje> Guest92: set in dconf-editor
[06:30] <lotuspsychje> Guest92: the search the value: dash-to-dock/shift-click-action
[06:36] <Guest92> minimise or show all windows
[06:36] <Guest92> I don't see preview selected ones or minimise
[06:37] <lotuspsychje> Guest92: there are a few values with previews, test them out
[06:52] <Hash> new info
[06:52] <Hash> I think I use kleopatra in kde, export/backup my gpg wallet key what's used by kde wallet and I'm going to try nuking home and starting fresh ag ain
[06:58] <cbus> hey I am getting that python3-distupgrade ubuntu-release-upgrader-core and ubuntu-release-upgrader-gtk are held back when updating how should I handle them?
[07:01] <murmel> cbus: those are phased updates, wait till they become "upgradable" or just use "apt upgrade python3-distupgrade <more packages>"
[07:02] <cbus> ah oki, thanks
[07:02] <Unit193> It's very awkward because the version that was on the system has been removed, and last I looked those phased updates were at 0%.
=== polve2 is now known as polve
[08:54] <ShrekD> jal
[09:04] <toffe> Hi, question. Evolution mail client seems to be removed from ubuntu so I no longer find a way to install it. Anyone know how to do this? https://www.ubuntuupdates.org/package/core/jammy/universe/proposed/evolution
[09:06] <lotuspsychje> !info evolution
[09:06] <ubottu> evolution (3.44.1-0ubuntu1, jammy): groupware suite with mail client and organizer. In component universe, is optional. Built by evolution. Size 290 kB / 461 kB
[09:06] <lotuspsychje> wich ubuntu release are you on toffe
[09:07] <toffe> just did dist-upgrade i think it is 22.04
[09:07] <toffe> DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
[09:07] <toffe> Can confirm :)
[09:07] <toffe> I had evolution installed before the dist upgrade (was 21.04, EOL)
[09:08] <lotuspsychje> reinstall toffe
[09:09] <toffe> its not to be found in apt or snap
[09:09] <toffe> evolution/now 3.40.0-1 amd64 [residual-config]
[09:09] <toffe> this is all i ahve when apt search for evolution
[09:10] <toffe> as the jammy repo say it is "DELETED" from the repo for some weird reason.
[09:10] <toffe> WARNING: the "evolution" package was deleted from this repository
[09:10] <lotuspsychje> toffe: you have the 'universe' repo enabled?
[09:11] <toffe> No all lines in sources.list end on either main resttricted of multiverse.
[09:11] <toffe> Should i uncomment all with "universe" at the end?
[09:15] <toffe> https://pastebin.com/riGy1AGp - this is the current sources.list
[09:17] <ogra> yes, evolution is in universe ... (since 2017 i think)
[09:19] <ogra> toffe, you should not look at the "proposed" repo ... that is the test repo that packages go to before enteing the archive ... (and as you can see at the top of the page you linked above, it moved to "jammy:universe:updates" after its tests passed)
[09:19] <toffe> aha, ok I'm a noob here. Sorry :) So I added "universe" after "main restricted" on the first line and i got 370 package udates :P
[09:20] <toffe> but now it seems that it is available. Just need to update libgtk e.t.c.
[09:20] <ogra> yeah
[09:20] <toffe> I'm working too much, should be doing regular upgrades instead :P
[09:20] <ogra> the release upgrade should have made sure that universe is enabled ... how did you update ?
[09:20] <toffe> sudo apt dist-upgrade
[09:20] <toffe> I think it was.
[09:20] <ogra> from 20.04 to 22.04 ?
[09:20] <toffe> 21.04 to 22.04
[09:21] <ogra> uh
[09:21] <ogra> that means your system is messed up
[09:21] <ogra> you would have needed to go: 21.04 -> 21.10 -> 22.04
[09:21] <toffe> I am not sure what it did do to be honets. I just did the dist-upgrade and sleected yes to everything
[09:22] <ogra> skipping a release means you are missing migration of configs and stuff ... these are only happening reöease to release
[09:22] <toffe> Should dist-upgrade do the 21.04 -> 21.10 automatically?
[09:22] <ogra> no, dist-upgrade *never* switches releases
[09:22] <ogra> it upgrades your current distro
[09:23] <toffe> hmm.. what did i do then XD i was so stressed as apt did not work due to EOL on my 22.04 so i hurried everything
[09:23] <toffe>  2000  sudo do-release-upgrade
[09:23] <toffe> I did that :P
[09:23] <ogra> to switch releases you do "sudo do-release-upgrade" which will switch your sources.list properly, make sure everything needed is enabled
[09:23] <ogra> aha
[09:23] <ogra> that is fine then
[09:23] <ogra> tough it is still curious how you ended up withut universe enabled
[09:24] <lotuspsychje> maybe he had universe disabled before?
[09:24] <toffe> I got another sources.list file sources.list.distUpgrade
[09:24] <ogra> doesnt matter ... do-release-upgrade usually enables it again
[09:24] <lotuspsychje> oh
[09:24] <toffe> but it has no universal enabled either.
[09:24] <toffe> it seems like the same file
[09:25] <ogra> it should always make sure you end up with the same setup you'D get when ding a fresh install of the new release (which has universe enabled by default)
[09:25] <ogra> *doing
[09:25] <toffe> Well, I'm a QA software tester.. So I am prone to find bugs ;9
[09:25] <ogra> lol ...
[09:25] <toffe> Stuff like this always happens to me ;P
[09:25] <ogra> canonical is hiring FWIW 🙂
[09:26] <lotuspsychje> lol
[09:26] <toffe> Do they apy a yearly salery of 62k USD? :P
[09:26] <toffe> pay*
[09:26] <lotuspsychje> https://canonical.com/careers/all
[09:26] <ogra> probably ... not sure what a fresh QA person gets
[09:26] <lotuspsychje> pick one
[09:28] <toffe> Hehe! :D
[09:28] <toffe> Well. It seems like Evolution finally came to me aswell. :D Thanks a bunch. IRC is always the best resort
[09:29] <ogra> 😄
[09:59] <admin0> hi all .. if i see the total cpu usage of 60% where 30% is user ( instanecs ) and 30% is system, how to further drill down what in the system/kernel that 30% comes from
[10:10] <Guest43> When I boot into livecd on my machine it's upside down. I can use xrandr on X11 to fix that, but is what is the wayland to rotate the screen 180 degrees?
[11:04] <blomberg> hi
[11:05] <blomberg> it says you can use livepatch for security between restarts?? how livepatch gives security
[11:08] <ogra> blomberg, it patches the running kernel with a binary patch
[11:08] <ogra> blomberg, imagine an "extra module with the fix" that gets loaded to overlay the existing binary code
[11:10] <ogra> blomberg, you should indeed still do your regular kernel package updates, so *if* you reboot you get the actual fixed kernel running next time
[11:10] <ogra> but livepatch will help until this next reboot to keep your kernel safe ...
[11:20] <ph88> hey guys how can i upgrade to the latest lts ? i tried the following  https://pastebin.com/khzTcMkp
[11:23] <ogra> ph88, just wait til friday and you will get the regular update prompt ... https://discourse.ubuntu.com/t/ubuntu-22-04-1-delayed-until-august-11/29859
[11:40] <transhumanist> hi! I have long avoided the question. How do I setup graceful shutdowns of kvm guests (bsd, windows 10/11, and linux) I thought the kvm-guest-agent or tools or whatever they are called (I forget) took care of this problem. But I think not, because they shut down too quickly, any thoughts? thanks in advance aparently its a standard feature in centos from about 2010 so I assume its made its way into Ubuntu by now?
[11:55] <transhumanist> ON_SHUTDOWN=shutdown  or = shutdown suspend and its in /etc/default/libvirt-guests
[12:01] <ph88> thanks ogra
=== jadenlian1 is now known as jadenlian
=== Andrew is now known as HaxCPU
=== HaxCPU is now known as Andrew
[12:30] <ry3> Learn C for Linux Users: Taking Inputs from the User: https://www.youtube.com/watch?v=Lj4aI6C41tg
=== Andrew is now known as HaxCUP
=== HaxCUP is now known as HaxCPU
=== HaxCPU is now known as ANdrew
=== ANdrew is now known as Andrew
[12:37] <nmourey> Anyone know where I can buy a shrink wrapped version of ubuntu?
[12:38] <Andrew> how do you shrink wrap an OS
[12:39] <geirha> I'm sure they mean a shrink wrapped dvd, collector's edition
[12:40] <Andrew> that makes sense
[12:41] <geirha> Back in the early days of ubuntu you could order a cd and have it shipped to you for free, but now ... no idea
[12:42] <geirha> According to  https://help.ubuntu.com/community/GettingUbuntu  it's still possible, but all the links are dead, so I guess not
[12:44] <guiverc> nmourey, as I understand it, LoCo's (Local Communities) have the capacity to have Ubuntu for sale (or gratis) but it won't be shrink-wrapped/boxed usually
[12:56] <BluesKaj> Hi all
[13:04] <dobbicorp> hi
=== babble is now known as babble_
[14:31] <qqz> I get 502: bad gateway for https://wiki.ubuntuusers.de/Internetradio/Stationen/
[14:31] <qqz> status report says everything up and running
[14:33] <Maik> qqz: wrong channel to ask in, you need to contact ubuntuusers.de about that
[14:34] <qqz> it says you can ask on #ubuntu-de at libera ...
[14:35] <Maik> well, you're in #ubuntu not #ubuntu-de
[14:58] <deadrom> hi all
[14:59] <deadrom> 3 monitors, one won't display anything. can move the mouse into its area, it is displayed in settings, xrandr lists the active mode but monitor says nothing. different computer goes in on another port, is fine.
[15:00] <deadrom> U18.04LTS on Radeon HD7750, old monitors, hdmi, dvi, vga. ideas how to narrow it down? current signal path is computer:DP-adapter2hdmi-HDMIswitch-monitor
[15:01] <arraybolt3[m]> deadrom: Maybe check the monitor's refresh frequency and try to set it to a lower value in Settings?
[15:01] <leftyfb> deadrom: do you have said monitor on the correct input setting? Have you tested said monitor by itself using the same cable and port?
[15:04] <deadrom> nvm, fixed, somewhat: bypassed the hdmi switch. cheap chinese shit, should have known.
[15:53] <jhutchins> Finally confirmed that the boot errors on "ata2" were the CD drive.  I caught the access light on the drive flashing in a regular cycle.  Ejected and re-seated the drive and it stopped.  Checked dmesg and sure enough, error after error, then nothing.
[15:54] <gordonjcp> people still use CD drives?
[15:55] <arraybolt3[m]> LOL yes, it's rare but it happens.
[16:33] <jhutchins> gordonjcp: No, I don't use it.
[16:33] <jhutchins> I would guess that this model probably came with a dummy drive blank so you could swap the drive out and leave it at home when you wanted a little less weight (a futile exercise, this thing's a brick).  That would actually be more useful to me than the drive is.
[16:33] <jhutchins> I might want to retrieve some archaic data or content.
[17:10] <Guest5659> I just hit a bug literally after system reset probably after some system update or something. I forgot what I did in the last 1.5 weeks while the computer was hibernated instead of shut down.
[17:11] <Guest5659> so first problem was that the monitor resultion is 1024x786 instead of some full HD
[17:11] <Guest5659> then I tried to update, the updater suggested to do this
[17:11] <Guest5659> https://pastebin.com/cB8QBt6d
[17:11] <Guest5659> so I hit that bug https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983565
[17:11] <ubottu> Launchpad bug 1983565 in initramfs-tools (Ubuntu) "package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1" [Undecided, New]
[17:12] <Guest5659> the updater complained that there isn't enough space in /boot
[17:16] <Guest5659> any hints or suggestions?
[17:17] <kushal_kumaran> @Guest5659: do you actually have room in `/boot`? Check using `du -hs /boot`. If not, then try removing old kernels.
[17:17] <Guest5659> 630M    /boot
[17:17] <Guest5659> thx
[17:18] <kushal_kumaran> Guest5659: my mistake. Try `df -h /boot` to check used *and* free space.
[17:19] <kushal_kumaran> then you can use `uname -r` to see which kernel you're running and `ls -l /boot` to see what you have installed. Then remove the kernel packages that are older than the one you're running.
[17:25] <Guest5659> removing a kernel doesn't seem to work either
[17:25] <Guest5659> https://pastebin.com/WkgnKzPX
[17:28] <kushal_kumaran> What's the current situation with `df -h /boot`? Seems like you might need to uninstall more of those. (I recall there is some way to automatically have older kernels removed, but I don't know if that had to be manually configured). BTW, what are you currently running (check with `uname -r`) and which are installed (check with `ls -l /boot/vmlinu*`)
[17:30] <kushal_kumaran> From the output, it looks like `-52` is the newest package you have. If you have no use for older kernels, remove the `-27`, `-41` packages.
[17:31] <kushal_kumaran> Your attempt to uninstall the `-52` package did not work (got replaced by the `unsigned` package) because that is probably the latest package on focal, so is required. You'll probably need to install that one back.
[17:34] <Guest5659> this seems to fix it, many thanks!
[17:42] <jhutchins> This is why you should not partition your drive, especially if you're a novice.
[17:46] <InPhase> More partitions rarely helps.
[17:47] <InPhase> I've even finally joined the masses and stopped partitioning a separate swap partition.
[17:48] <kushal_kumaran> Well, I've been using Debian since 2006, and I chuck as much as I can onto a single partition. /boot was an exception for a long time, because I didn't know how to make it work with disk encryption. I understand that no longer applies, but I got used to it.
[17:48] <kushal_kumaran> I assume the considerations around luks are the same in ubuntu
[18:36] <gneeriiloeepdeer> what command do I need to see when I executed a specific command?
[18:37] <leftyfb> gneeriiloeepdeer: ~/.bashrc isn't setup to do the by default
[18:38] <leftyfb> gneeriiloeepdeer: but you can set this and your "history" command will show you timestamps:   export HISTTIMEFORMAT='%F %T '
[18:40] <EriC^^> gneeriiloeepdeer: did you use sudo with the command?
[18:41] <gneeriiloeepdeer> with the original command EriC^^ ? no
[18:43] <EriC^^> what's the command supposed to do?
[18:44] <gneeriiloeepdeer> noob here has added export >HISTTIMEFORMAT='%F %T '< to /etc/bash.bashrc. Is this the way to go leftyfb ?
[18:44] <gneeriiloeepdeer> nope
[18:44] <leftyfb> that is not the preferred way. You should add it to ~/.bashrc
[18:45] <gneeriiloeepdeer> but there is no .bashrc in my home dir
[18:45] <gneeriiloeepdeer> leftyfb, Im an idiot
[18:47] <gneeriiloeepdeer> leftyfb, I dont see timestamps, or do you mean 2367, 2368, 2369...?
[18:48] <leftyfb> gneeriiloeepdeer: close your terminal and open a new one
[18:49] <gneeriiloeepdeer> leftyfb, it shows timestamps, but it's the current time, the time when I executed 'history'
[18:49] <gneeriiloeepdeer> for every entry
[18:50] <leftyfb> gneeriiloeepdeer: because it didn't record until now. The timestamps will only be valid from this point forward
[18:50] <leftyfb> gneeriiloeepdeer: as I said, this isn't enabled by default so it wasn't recording timestamps. It is now though
[18:51] <gneeriiloeepdeer> just to confirm: I added >export HISTTIMEFORMAT='%F %T '< to ~./bashrc
[18:51] <gneeriiloeepdeer> including that last '
[18:51] <gneeriiloeepdeer> is this correct?
[18:52] <leftyfb> yes, it's all setup correctly and will record timestamps for all future commands typed into your bash sessions
[18:52] <leftyfb> it will not, however, record timestamps that happened in the past
[18:52] <leftyfb> before this point
[18:52] <gneeriiloeepdeer> thanks a bunch leftyfb ! it works like a charm!
=== jesopo is now known as jess
=== _koolazer is now known as koolazer
=== blackest_mamba_ is now known as blackest_mamba
[20:15] <solsTiCe>  /msg saslserv help
[20:15] <solsTiCe>  /msg chanserv help
[20:16] <sarnold> try without the leading spaces
[20:16] <solsTiCe> ooops sorry
[20:24] <The_LoudSpeaker> Hey! I have a hp victus with Ryzen 5 5600H and radeon RX5500M. Is there an utility to help disable the amd dGPU and enable it when required? I know there is one for an intel+Nvidia setup. But don't know any for amd+amd setup.
=== Polo is now known as gambino
=== PeGaSuS- is now known as PeGaSuS
=== silentfury6 is now known as silentfury
=== Phase_ is now known as Phase
=== Casper26_ is now known as Casper26
=== NightMonkey_ is now known as NightMonkey
=== Juan- is now known as Juan
=== dstein64- is now known as dstein64
=== mnepton is now known as mneptok
=== trekkie1701c_ is now known as trekkie1701c
=== N3X15_ is now known as N3X15
=== greknod165 is now known as greknod16
=== codingkoopa9 is now known as codingkoopa
=== GrantN05- is now known as GrantN05
=== zakalwe` is now known as zakalwe
=== scoobydoob is now known as scoobydoo
=== wbrawner_ is now known as wbrawner
=== AJC_Z0 is now known as AJ_Z0
=== Amaranth5 is now known as Amaranth
=== toozej85179 is now known as toozej8517
=== nizzan7 is now known as nizzan
=== B1773rm4n6 is now known as B1773rm4n
=== chrfle_ is now known as chrfle
=== s8n2 is now known as s8n
=== lord4163_ is now known as lord4163
=== mikesmoniker_ is now known as mikesmoniker
=== Morfeus is now known as _--_
=== Mibixy is now known as Mibix
=== dabbill_ is now known as dabbill
=== steam_ is now known as steam
=== Kobaz_ is now known as Kobaz
=== mickey79 is now known as mickey7
=== hack_ is now known as hack
=== waxfire150 is now known as waxfire15
=== leftyfb_ is now known as leftyfb
=== DArqueBish0p is now known as DArqueBishop
=== Erisa0 is now known as Erisa
=== isnessness is now known as ugjka
=== m_ueberall is now known as ueberall
=== Kamilion|ZNC is now known as Kamilion
=== acosta6 is now known as acosta
=== hans__ is now known as hans_
=== mrelcee_ is now known as mrelcee
=== anderson_ is now known as anderson
=== dionysus70 is now known as dionysus69
=== rosseaux_ is now known as rosseaux
=== NiKaN_ is now known as NiKaN
=== JeremyD is now known as SleePy
[21:08] <xwallpaper> is the server getting bombed
=== TheMaste1 is now known as Unit193
[21:28] <elias_a_> No.
=== Kuraokam1 is now known as Kuraokami
=== petris_ is now known as petris
=== yarddogg_ is now known as yarddogg
=== Metamorphosis_ is now known as Metamorphosis
=== Exagone313 is now known as Exa
=== markthomas1 is now known as markthomas
=== Jeremy31_ is now known as Jeremy31
=== Agent_Isai is now known as Agent
=== toabctl_ is now known as toabctl
=== Iamthehuman1_ is now known as Iamthehuman1
=== boxrick_ is now known as boxrick
=== sa_ is now known as sa
=== PotatoGim_ is now known as PotatoGim
=== kenzie3 is now known as kenzie
=== jcm_ is now known as jcm
=== madhens_ is now known as madhens
=== graingert_ is now known as graingert
=== AKTheKnight1 is now known as AKTheKnight
=== c355E3B_ is now known as c355E3B
=== bsdbandit01_ is now known as bsdbandit01
=== LjL^ is now known as LjL
=== SuperL4g is now known as SuperLag
[22:18] <solsTiCe> netsplit ?
[22:18] <tomreyn> !irc | solsTiCe
[22:18] <ubottu> solsTiCe: A list of official Ubuntu IRC channels, as well as IRC clients for Ubuntu, can be found at https://help.ubuntu.com/community/InternetRelayChat - For a general list of !Libera channels, see !Alis - See also !Guidelines
[22:19] <tomreyn> i mean
[22:19] <Unit193> tomreyn: !netsplit might help more. :P
[22:19] <tomreyn> !netsplit
[22:19] <ubottu> A netsplit is when two IRC servers of the same network (like Libera) disconnect from each other, so users on one server stop seeing users on the other. If this is happening now, just relax and enjoy the show. See https://en.wikipedia.org/wiki/Netsplit
[22:19] <tomreyn> but the better place to discuss it is #libera, if you need to.
=== V3n3RiX_ is now known as V3n3RiX
[22:32] <pony> https://usercontent.irccloud-cdn.com/file/7yiwk3ym/Screenshot%20from%202022-08-09%2010-30-18.png
[22:32] <pony> why are these greyed out? I can't select another one.
[22:32] <pony> my video is all slow, screen tearing and stuff
=== waltman_ is now known as waltman
=== stw__ is now known as stw
[22:36] <tomreyn> pony: it says you're using a manually installed driver (twice). is this not so?
[22:39] <pony> I didn't install something myself, unless that includes clicking [intsall 3rd party stuff] during the os installer
[22:39] <pony> install *
[22:40] <tomreyn> no, it does not. maybe the hardware is no longer supported. is this old?
[22:41] <pony> not that old, gt 1030
[22:43] <tomreyn> pony: are you running wayland by chance?
[22:44] <tomreyn> and which ubuntu version is this?
[22:46] <xwallpaper> install the drivers from terminal maybe
[22:46] <pony> I'm running x11 on 22.04
[22:47] <tomreyn> driver series 515 should support GT 1030
[22:48] <pony> it says xserver-xorg-video-nvidia-515 is installed. how do I switch to it?
[22:48] <tomreyn> i do not know why this UI is not allowing you to install. i would assume this to happen when leftovers of an earlier manual (download and installation from nvidia.com or elsewhere) installation were detected.
[22:49] <pony> yeah, me neither :/
[22:49] <tomreyn> you can try what xwallpaper suggested, using the "ubuntu-drivers" CLI, which is the equivalent to the screen you posted.
[22:50] <tomreyn> or you can make sure that nvidia-driver-515 is the only "nvidia*" driver package installed: apt list --installed nvidia*
[22:51] <tomreyn> https://packages.ubuntu.com/jammy/nvidia-driver-515
[22:52] <tomreyn> if this issue persists, have a look at your X initialization logs. use the "journalctl" command to access system logs and look for (type / to search) "gdm"
[22:52] <pony> thx
[22:53] <tomreyn> thats assuming you're using the default ubuntu graphical desktop
[22:53] <tomreyn> +login manager
[22:53] <pony> yes
[22:53] <pony> apt list --installed nvidia* prints out over 200 lines though
[22:54] <tomreyn> there can be other packages installed. 200 seems like a lot.
[22:54] <tomreyn> to share, if you run bash:  apt list --installed nvidia* |& nc termbin.com 9999
[22:56] <jhutchins> pony: Good eye, line count here is 21/
[22:57] <pony> found a forum that says secure boot can be the culprit (re greyed out selections?) maybe I'll try that
[22:57] <jhutchins> (I'm assuming your keyboard stuttered.)
[23:00] <tomreyn> if you had secureboot enabled when you installed 22.04 (freshly), a signing key should have been installed on your 'bios' and this should also be used automatically (i think?) to sign the nvidia drivers setup via dkms. that's if i recall this correctly.
[23:00] <tomreyn> actually this may not have happened if you didn't choose to enable third party drivers during installation
[23:06] <pony> hmm ok
[23:06] <pony> I'll try turning it off and see what that does
[23:06] <mijk> I installed Ubuntu Server from USB and I guess I wasn't watching what I was doing and I installed grub onto the USB stick. If I do sudo grub-install /dev/sda it works until I install updates and then I need to use my USB stick just to boot into the OS
[23:06] <mijk> how do I make it permanent?
[23:08] <murmel> how can I get sbuild to uncompress zst debs? it's complaining about not knowing about zstd, but I did install it in the chroot
[23:10] <tomreyn> mijk: are you saying you installed ubuntu-server on the internal permanent storage, as intended, but accidentially had it write the grub legacy bios boot stage onto the usb stick rather than the internal storage?
[23:10] <mijk> correct
[23:11] <arraybolt3[m]> murmel: I'd make sure zstd support was installed on the host too, just in case that helps. If not, unpack the zstd file, repack it as a tar.gz or tar.xz, then sign it with your own GPG key and sbuild that.
[23:11] <arraybolt3[m]> (There may be some other way to make sbuild work with zstd, but that's a quick solution from right off the top of my head.)
[23:12] <arraybolt3[m]> (You may also want to check your debian/watch file and make sure that it's set to download the zstd. That might be the problem.)
[23:12] <tomreyn> mijk: you can either repair from recovery (if the installation on the internal storage is bootable, possibly via the grub loader on the usb), chroot repair, or reinstall.
[23:12] <sarnold> murmel: dpkg also needs to be adapted to deal with it -- what's in your chroot? debian? an ubuntu before focal?
[23:12] <mijk> it boots if I use the USB stick
[23:13] <mijk> it boots to the USB stick which then loads the OS on the internal drive
[23:13] <murmel> arraybolt3[m]: zstd is definitely installed also on the host
[23:13] <murmel> sarnold: jammy
[23:13] <tomreyn> mijk: then you should just need to update-grub and grub-install to the right target
[23:13] <murmel> running on a debian host
[23:13] <murmel> (testing specifically)
[23:13] <mijk> oh? maybe it's just a matter of running update-grub first?
[23:14] <murmel> i include the deb with --extra-package=./package.deb
[23:15] <tomreyn> mijk: update-grub just updates /boot/grub.cfg , grub-install installs the legacy bios boot loader in the MBR you point it to.
[23:15] <sarnold> murmel: aha! that explains a lot :) I didn't expect anything in the schroot to be doing the unpacking, I thought that ought to have happened already.. I'm not sure what to suggest as a fix though :(
[23:16] <tomreyn> mijk: or to the targets' bios grub partition if it's a GPT partition table
[23:16] <arraybolt3[m]> murmel: Ah, zstd debs, I thought you meant a .tar.zstd file of source code.
[23:16] <mijk> didn't work
[23:16] <tomreyn> mijk: it's more common to boot in uefi mode nowadays, though
[23:17] <arraybolt3[m]> murmel: Uh... ok so what's the exact error message sbuild is spitting out? Pastebin it and we'll take a look.
[23:17] <murmel> arraybolt3[m]: sbuild is complaining about control.tar.zst
[23:18] <arraybolt3[m]> murmel: Right, but I've not seen anything like that in my use of sbuild, so I'm hoping I can see the error verbatim in case it gives me any extra knowledge.
[23:20] <murmel> arraybolt3[m]: https://paste.debian.net/1249732/ if you need more output, just scream :P
[23:20] <arraybolt3[m]> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[23:20] <arraybolt3[m]> (ok that's a joke)
[23:21] <sarnold> arraybolt3[m]: that's because you've got an ubuntu box
[23:21] <sarnold> arraybolt3[m]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 for the extra context
[23:21] <ubottu> Debian bug 892664 in dpkg "dpkg: Please add decompression support for zstd" [Wishlist, Open]
[23:22] <arraybolt3[m]> Ugh. Right, because Debian and Ubuntu are different. And while this is on-topic since Ubuntu is involved... it also means some Debian-fu is necessary. Hmm...
[23:22] <Unit193> I don't know context at all, but debootstrap from backports has a fix so you can bootstrap Ubuntu from Debian, but I suspect that's not the problem.
[23:22] <arraybolt3[m]> Well how about this hack. Debian host -> LXD container -> Ubuntu guest, run sbuild in that?
[23:23] <murmel> sarnold: huh? I thought the stuff would be done in the chroot? as it dl the packages (through apt) etc also in it
[23:23] <arraybolt3[m]> murmel: What version of Ubuntu are you running in the chroot?
[23:23] <mijk> sudo grub-install --boot-directory=/boot/ /dev/sda
[23:23] <murmel> Unit193: that's definitely not the issue ;)
[23:24] <mijk> seems to have dne the trick
[23:24] <murmel> arraybolt3[m]: chroots in chroots don't work for me (especially with sbuild :/)
[23:24] <murmel> tested it already
[23:24] <Unit193> I just use pbuilder normally, don't need hacks to get Ubuntu builds on Debian.
[23:24] <murmel> arraybolt3[m]: jammy
[23:24] <sarnold> murmel: maybe supply the deb in a repo inside the chroot rather than via --extra-package ?
[23:24] <murmel> Unit193: well I also have it, but I do want to get sbuild running
[23:24] <murmel> which should definitely work imho :/
[23:25] <mijk> worked once, reboot caused it to not work
[23:25] <Unit193> I'd imagine it's somewhat the same, sbuild just uses schroot instead so you don't need root.
[23:25] <arraybolt3[m]> murmel: If all else fails you could also use a VM (I used that for quite a while).
[23:25] <mijk> alright well it's obviously a hardware issue then
[23:26] <murmel> sarnold: I am trying to get this into a ppa, but I can't get the sources.changes file out of the dsc, as I don't have the dep. on the host
[23:27] <murmel> arraybolt3[m]: sure :) but I want to avoid it. but honestly I think I will maybe test out sbuild-qemu. but i still feel weirded out if the host dpkg would be used to extract extra packages, not the chroot one
[23:27] <murmel> which wouldn't work on a vm
[23:39] <linext> what's the way to allow php to run proc_open through apache?
=== Gamah_ is now known as Gamah
[23:44] <tomreyn> linext: do you have an error message?
[23:44] <tomreyn> and which ubuntu + apache + phph version are you using?
[23:45] <tmus> I usually suspend my thinkpad at home (while connected to an usb-c monitor), then plug it in at work when it's connected to another similar usb-c monitor. Sometimes (often but not always), the computer becomes useless after resume, because the mouse somehow moves behind the windows on the desktop. Is this a know issue?
[23:48] <tomreyn> tmus: i'm not familiar with this issue. what's your ubuntu version, graphical login manager and desktop (defaults would be gdm3, gnome-shell/mutter), graphics driver?
[23:49] <tmus> tomreyn, 22.04, gdm3, gnome-shell/mutter (but vanilla gnome session) and open source amd graphics stack (amdgpu)
[23:50] <tmus> It seems hard to reproduce reliably and hard to describe when/why it happens exactly - But it it annoying and takes a reboot to clear up (perhaps open/close laptop lid works, not entirely sure)
[23:51] <tomreyn> tmus: so switching to a tty and back is insufficient?
[23:52] <tmus> tomreyn, it was at one point, but the last few days it's not been sufficient. Perhaps since switching to mainline 5.19 kernel
[23:54] <tomreyn> tmus: those aren't supported, but if it still occurs on jammy's default kernel you could file a bug report
[23:54] <tomreyn> tmus: i'd also compare wayland vs xorg
[23:54] <tomreyn> (if it's well reproducible)
[23:55] <tmus> tomreyn, It does (or at least it did). I will go back to normal kernel and try it out. Thanks
[23:55] <tmus> Will test xorg vs wayland too, although i think this is probably a mutter thing
[23:58] <tmus> thanks, tomreyn
[23:59] <tomreyn> good luck
[23:59] <tomreyn> !bug | tmus
[23:59] <ubottu> tmus: If you find a bug in Ubuntu or any of its official !flavors, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.