[00:12] <ken> hi
=== ken is now known as Guest9421
[00:12] <whiskey76> \o
=== Guest9421 is now known as hadoken
[00:13] <hadoken> hi, I have steam (deb package version) installed on ubuntu and some games freeze running full screen, but run perfectly fine windowed, why is that?
[00:13] <hadoken> I had uninstalled the snap version of steam thinking it was the problem but same thing happens with the official deb version of steam
[00:17] <hadoken> my pc specs are amd fx 8350, geforce gtx 1080, 16gb ddr3 ram
[00:18] <rbox> sounds like something you should talk to valve about
[00:20] <hadoken> but does nobody else have this issue? Seems like this issue is as common is it can get, I have proton enabled but when I run the game full screen it runs at like 1 frame per 10 minutes but if I window it, runs perfectly.
[00:21] <hadoken> I just really want to run games full screen like on windows instead of having them windowed
[00:21] <rbox> that "some" games have issues?
[00:21] <rbox> lol
[00:21] <hadoken> so is the issue at a per-game basis?
[00:21] <hadoken> well, I figured
[00:22] <hadoken> but even while checing protodb, while the game says it has full compatibility, results still vary (at least on ubuntu, I'm sure they run perfectly on steam deck)
[00:25] <hadoken> this is such a weird quirk to have
[00:25] <hadoken> running on ubuntu 22,04,04
[00:25] <hadoken> 22.04.4
[00:28] <rbox> that not every game works perectly?
[00:28] <rbox> thats weird?
[00:32] <hadoken> like I said, it's 100% fully compatible with proton, but it seems to be an ubuntu thing where you run something full screen and it freezes. It shouldn't be happening
[01:48] <hadoken> https://steamcommunity.com/app/388210/discussions/0/365172547957969635// seems like this issue has been happening since 2016, jesus christ
[02:28] <JanC> that bug was fixed in 2016, so I'm sure it's not the same
=== chris14_ is now known as chris14
[03:06] <Ascavasaion> I ran a do-release-upgrade, and left it running. While I was away the screensaver kicked in, and when I try to log in now it will not request a password and informs me that I am locked out. The upgrade is not complete, so I do not know what to do now.
=== antonispgs7 is now known as antonispgs
[03:10] <Bashing-om> Ascavasaion: How about seeing what can be done from the recovery console from grub's boot menu ? dpkg   -> repair broken packages.
[03:11] <Ascavasaion> Bashing-om: Um, I don't know... the upgrade is still active, the screensaver has locked me out.
[03:19] <JanC> you should always run commands like that in screen/tmux
[03:19] <Bashing-om> Ascavasaion: Sorry - here I am at a loss - got to get to a terminal somewhere and I do not know that from the login screen one can activate a terminal :(
[03:19] <JanC> Ctrl+Alt+F3 or so
[03:22] <tomreyn> do-release-upgrade (at least in server mode) starts a backup SSH session on port 1022 and a backup GNU screen session (if you have GNU screen installed).
[03:23] <tomreyn> sudo screen -list
[03:23] <tomreyn> sudo screen -d -r (name of the session printed by above command)
[03:23] <Ascavasaion> Bashing-om: Exactly my problem. I do not know how to jump to a terminal, and then figure out a way to 'capture' or log into the session that is running the upgrade.
[03:24] <tomreyn> !tty
[03:24] <ubottu> To get to the TTY terminals 3-6, use the keystroke Ctrl + Alt + F3-F6 respectively. Ctrl-Alt-F2 or Ctrl-Alt-F1 will get you back to your graphical login (Ctrl-Alt-F7 on 16.04). To change TTY resolution, see https://help.ubuntu.com/community/ChangeTTYResolution
[03:25] <Josephur> I wonder if TTY was meant to be pronounced titty :P
[03:26] <Ascavasaion> tomreyn: I did what you suggested, logged in, and I see that screen is not installed.
[03:30] <tomreyn> Ascavasaion: then i assume your only option to continue from where you  left off would be to either replace the gnome shell (will only work if running Xorg, not wayland), or to use https://packages.ubuntu.com/reptyr with the -T option
[03:33] <Ascavasaion> tomreyn: reptyr is not installed, and if I try sudo apt install reptyr I get told that I am locked out of it by a session (the one running the do-release-upgrade I presume).
[03:34] <tomreyn> you could install it manually, as described int he first answer here (make sure to pick the correct download link for your ubuntu release, this one is for 18.04 LTS) https://askubuntu.com/questions/1201705/resume-do-release-upgrade-after-screen-terminated
[03:36] <tomreyn> note that this approach does not verify that the reptyr package you download is authentic.
[03:36] <Ascavasaion> tomreyn: Would I have to hard reboot it to do this? I am worried that doing that will lock me out of the computer completely, as in the terminal I got to with Ctrl+Alt+F3 was riddled with errors.
[03:37] <tomreyn> no, you would have to not reboot to do this
[03:38] <tomreyn> if you see a lot of error messages on tty3 this suggests that there can be worse issues than just loosing control to do-release-upgrade
[03:39] <tomreyn> depends on the error messages, though, some could be benign
=== swebb_ is now known as swebb
[03:40] <Ascavasaion> tomreyn: I think the errors are exactly because the release upgrade is not finished. Well, that is what I summise.
[03:40] <tomreyn> a hard reboot is indeed the worst choice you could make at this point, even a soft reboot would be better, but not advisable for now.
[03:41] <Josephur> What happened you started an upgrade from a gui gnome session?
[03:41] <Josephur> reptyr should get the job done
[03:43] <Ascavasaion> Josephur: Yes, I op-ened a terminal in GUI and typed sudo do-release-upgrade. I then left it to run, and when I came back to check on its progress the screensaver had kicked in. Where it usually prompts for screensaver password it only showed login name, and does not give me the usual field where I enter my password.
[03:43] <Josephur> oh bother
[03:44] <Josephur> Yeah install reptyr manually as suggested, should get you somewhere
[03:47] <tomreyn> if you're on gnome-shell on Xorg, running, as your restricted user (unless when using nvidia proprietary driver, i assume),    gnome-shell -r    would be the easier approach - assuming that the desktop is currently in a workable state.
[03:47] <Ascavasaion> tomreyn: I have downloaded the reptyr package and typed in ar x reptyr_0.6.2-1.2_amd64.deb it returns to the command line (success I presume). I do not understand what the poster on the link you sent me means by "Inside, data.tar.gz is extracted, then inside the new usr/bin folder was a file called reptyer.".
[03:48] <tomreyn> check what's in the directoy now, what was extracted by ar
[03:48] <Ascavasaion> tomreyn: No gnome-shell installed that I can see.
[03:49] <tomreyn> which ubuntu version adn variant is this?
[03:49] <tomreyn> *and
[03:50] <Ascavasaion> tomreyn: Am I supposed to decompress the data.tar.gz file?
[03:50] <tomreyn> you should have extracted a control.tar.gz and data.tar.gz file. running    tar xzf data.tar.gz   would provide the reptyr binary
[03:51] <Ascavasaion> tomreyn: lsb_release gives 20.04.6 LTS
[03:52] <tomreyn> i see, that's probably where you upgraded *from*
[03:53] <Ascavasaion> tomreyn: Yes, definitely the release I was upgrading from. I saw the 20 on the desktop wallpaper ealrier.
[03:53] <Ascavasaion> tomreyn: xzf not installed it says.
[03:53] <Ascavasaion> oops
[03:53] <Ascavasaion> I missed the trat part
[03:54] <Ascavasaion> tar
[03:55] <Ascavasaion> tar xzf data.tar.gz  returns message saying that it is not in gzip format.
[03:58] <arraybolt3> gzip -d data.tar.gz && tar -xf data.tar   ?
[04:00] <tomreyn> oh it's .xz
[04:00] <arraybolt3> ah
[04:01] <arraybolt3> unxz data.tar.xz && tar -xf data.tar
[04:01] <tomreyn> or   tar xJvf data.tar.xz
[04:01] <arraybolt3> how on earth do you remember all these esoteric tar commands :P
[04:02]  * arraybolt3 is really bad at remembering the syntax for two things in Linux - tar, and rsync
[04:02] <tomreyn> i'm bad at rsync, but use tar occasionally
[04:02] <Ascavasaion> This worked - unxz data.tar.xz && tar -xf data.tar - thank you.
[04:04]  * Ascavasaion chuckles... Now I need to figure out the PID hehe Have run htop... Am I looking for the terminal I ran in the GUI, or am I looing for the do-release-upgrade I ran within that terminal?
[04:06] <tomreyn> the bash shell which is a child process of the terminal emulator, or the do-release-upgrade process
[04:09] <tomreyn> pstree may help identifying it, or pgrep -a .
[04:09] <Ascavasaion> There are two... 2041 and 23289 (I think). but neither reptyr -T 2041 or reptyr -T 232289 did anything.
[04:10] <tomreyn> you'll need sudo. make sure you know the exact pid, not one of two possibly matching.
[04:12] <Ascavasaion> The two PIDs above are identical and are listed in htop as (let me type this across from the other computer) "/usr/bin/python3 -s /tmp/ubuntu-release-upgrader-517bvyin/jammy --mode=server --frontend=DistUpgradeViewText"
[04:14] <tomreyn> pstree -hps 2041     and    pstree -hps 23289      would show their process trees
[04:15] <tomreyn> it's puzzling me why there would be two of those running, though
[04:16] <tomreyn> worst case you can rebind one to tty3 and the other to tty4, though
[04:17] <tomreyn> (switching back and forth between them using ctrl-alt-f3 and -f4, logging in on each, and running reptyr on each (with different pids)
[04:18] <tomreyn> often, the one with the lower pid is the one started earlier.
[04:22] <Ascavasaion> Not sure how to interpret the two outputs from pstree, but they both have the same top line, but the smaller PID has 5 'branches' below it, whilst the bigger PID has 0 'branches'.
[04:24] <Ascavasaion> Silly thought perhaps, but could the second one be when the GUI pops up automatic notifications for upgrades and updates, and the smaller one be the one I ran?
[04:24] <tomreyn> you're looking at a process hierachy, the first process listed in a line spawned the child process lested next to it, and so on.
[04:25] <tomreyn> the automatic one should not say --mode=server (and actually i don't think that would use do-release-upgrade at all)
[04:25] <tomreyn> i assume the first one is the one you want
[04:25] <tomreyn> lower pid
[04:26] <Ascavasaion> Let me try the first one then... here goes.. the 2041 one.
[04:29] <Ascavasaion> command not found.
[04:29] <Ascavasaion> But I did the sudo chmod +x reptyr
[04:30] <tomreyn> you need to specify the full path to reptyr
[04:30] <tomreyn> relative or absolute
[04:31] <tomreyn> if you're in the same directory the binary reptyr is in, you still need to use    sudo ./reptyr ...
[04:33] <Ascavasaion> when done as my standard user with sudo as I normally do with 'restricted' actions it gives permission denied. I then did a sudo -s and then tried again and it still said permission denied.
[04:34] <tomreyn> what's the command you ran, what's your current working directory (run "pwd" to tell) and which directory is reptyr in?
[04:34] <Ascavasaion> Exact message is "Unable to attach to pid 2041 : Permission Denied"
[04:35] <tomreyn> run sudo without -s
[04:38] <tomreyn> what to learn from this experience? don't run the server updater utility on a desktop, in a terminal emulator. and run it through a teminal multiplexer, which it will do by itself if you have gnu screen installed, so consider installing this.
[04:38] <Ascavasaion> sudo ./usr/bin/reptyr -T 2041 scrolls up one line and then waits.
[04:39] <Ascavasaion> Consider installing gnome-screen you mean? In future I presume?
[04:39] <tomreyn> GNU screen
[04:40] <tomreyn> the terminal multiplexer
[04:40] <tomreyn> try pressing question mark and hitting enter now
[04:40] <Ascavasaion> ? and return does nothing but scroll up one line.
[04:41] <tomreyn> if this does nothing then leave this tty alone and login to tty4 and retry there with the other PID
[04:42] <tomreyn> ctrl-alt-f4, login, sudo ./usr/bin/reptyr -T 232289
[04:42] <Ascavasaion> "Operation not permitted"
[04:46] <tomreyn> might be a namespace issue, hard to tell without all the details.
[04:46] <tomreyn> if you can't get this to work then your best option may be to sudo kill (-1, -3 or -6) the running dpkg process and then to follow some guide to recover a failed release upgrade
[04:47] <tomreyn> or reinstall, after backing up what you haven't backed up yet
[04:47] <tomreyn> Ascavasaion: i'll have to move on, but try egtting help from someone else with this if you like.
[04:47] <Ascavasaion> Sheesh.
[04:48] <Ascavasaion> tomreyn: I understand... Thank you for trying.
[04:48] <tomreyn> you're welcome
[04:48] <Ascavasaion> Is this a bug with the upgrade? I mean, I have done this before without issues.
[04:49] <Ascavasaion> Have a good one tomreyn
[04:49] <tomreyn> it's a bug with the user
[04:49] <tomreyn> <tomreyn> what to learn from this experience? don't run the server updater utility on a desktop, in a terminal emulator. and run it through a teminal multiplexer, which it will do by itself if you have gnu screen installed, so consider installing this.
[04:49] <Ascavasaion> tomreyn: HAHA! Ouch.
[04:50] <tomreyn> on a server, you would already have 'screen' installed. and on a desktop, you would not run --mode=server, i think
[04:50] <Ascavasaion> Now to get back to GUI, seeing that Ctrl_Alt+F1 and Ctrl+Alt+F2 do nothing but give me new terminal login screens
[04:51] <tomreyn> anyways, good luck
[04:51] <Ascavasaion> Thank you very much.
=== diogeness_ is now known as diogeness
[06:17] <Ascavasaion> tomreyn: Thought you might like to know. https://askubuntu.com/questions/391620/how-to-resume-release-upgrade helped me to fix and complete the crashed do-release-upgrade issue I had. I had to insert one line of sudo apt --fix-broken install in there and I also did a sudo apt-get autoremove. Just thought you would like to know. Thank you again.
=== sia_ is now known as isak
=== isak is now known as siak
[08:15] <zzarr> Hello! I have a problem, on a server I have that runs Ubuntu 20.04 I wish to upgrade to 22.04, however /boot is only have 118M available and I only have one kernel installed, the upgrade require more than 118M on the /boot partition
[08:16] <zzarr> Making things worse is that the / partition begins directly after /boot
[08:17] <zzarr> Is there a way to move / in order to free up space to grow /boot?
[08:18] <akik> zzarr: /boot can also be located under your / fs
[08:20] <zzarr> akik, can I move it? (I don't have physical access to the machine)
[08:20] <akik> zzarr: move the partition?
[08:21] <akik> zzarr: you can first try what it says if you try to "sudo umount /boot" and maybe "sudo umount /boot/efi" before that
[08:21] <zzarr> akik, sorry, I meant move the files from the partition /boot to the folder /boot
[08:22] <akik> zzarr: this is of course risky if you haven't tested it before
[08:22] <zzarr> I have not tested it before
[08:23] <akik> zzarr: are you able to umount /boot/efi and /boot ?
[08:23] <zzarr> I wonder, could I mount /boot in another location and / in yet another location and then move the files before doing anything more?
[08:24] <akik> this is so risky i wouldn't do it now
[08:24] <zzarr> akik, there's no /boot/efi, yes /boot is unmounted
[08:24] <akik> zzarr: so it's booting in bios mode?
[08:25] <zzarr> akik, it's a "cloud vm" I don't know what system it's on
[08:25] <rolandh1992> Hi all, looking into music production software for ubuntu could anyone recommend software or a group thanks?
[08:25] <akik> zzarr: sudo ls /sys/firmware/efi
[08:25] <zzarr> akik, but that would be my guess too
[08:26] <akik> rolandh1992: ubuntu studio
[08:26] <zzarr> akik, no such file...
[08:26] <akik> rolandh1992: ardour works fine
[08:26] <akik> zzarr: ok seems to be booting in bios mode then
[08:26] <zzarr> akik, yepp
[08:27] <rolandh1992> Thanks alot akik
[08:30] <zzarr> akik, something came up, but I checked /boot is mounted as ext3 and / is mounted as ext4
[08:30] <akik> zzarr: it doesn't matter
[08:31] <mcphail> rolandh1992: you can also use Reaper, which you may be familiar with from other operating systems
[08:31] <akik> zareem: i can't be 100% certain if this works but i'd do it like this: sudo -i; mount /boot; mkdir /boot_new; copy everything from /boot to /boot_new; umount /boot; rmdir /boot; mv /boot_new /boot; then grub-install and update-grub
[08:31] <akik> oops
[08:31] <akik> zzarr: that was of course for you :)
[08:31] <zzarr> thanks akik now I have a way forward
[08:31] <akik> zzarr: you need to provide grub-install with the correct options
[08:33] <akik> zzarr: probably: grub-install --boot-directory=/boot /dev/sdX (your storage device)
[08:33] <akik> might be vdX
[08:33] <akik> you can see it with lsblk or fdisk -l
[08:33] <zzarr> akik, yes, I have done something like this before, but it was on a hobby machine not a server for a company, thanks a lot for the help, I will have to read up on grub-install and other things
[08:34] <zzarr> akik, the disk is called /dev/xvda
[08:34] <akik> zzarr: i wouldn't do it if a company is using it for their business
[08:35] <zzarr> akik, I will talk to my foreman
[08:35] <akik> zzarr: i mean, arrange a service break for it and ensure you have backups
[08:36] <zzarr> I have to go to a meeting, akik yes I will, thanks again
[09:12] <ice9> disabling ipv6 in sysctl.conf didn't work, but applying 'ipv6.disable=1' to kernel boot parameters did it, why is that? that's 23.10
=== five618480337 is now known as five61848033
=== zer0bitz_ is now known as zer0bitz
[12:15] <BluesKaj> Hi all
=== esv_ is now known as esv
=== five618480337 is now known as five61848033
=== Ganok is now known as Ganonk
=== JanC is now known as Guest5517
=== JanC_ is now known as JanC
[14:58] <utsweetyfish> grub 2.12 with secure boot seems starts to verify fonts' sig
[14:59] <utsweetyfish> `loadfont' errors with `prohibited by secure boot policy'
[14:59] <utsweetyfish> grub-core/kern/efi/sb.c
[15:00] <leftyfb> utsweetyfish: disable secure boot
[15:00] <utsweetyfish> leftyfb: no
[15:01] <leftyfb> oh, sorry, I assumed you wanted everything to work with no error messages
[15:03] <utsweetyfish> leftyfb: no problem! i've viewed related patches and now thinking what should a distro do in this case..
[15:05] <utsweetyfish> for ex, should distros sign all fonts? Or, should user generate a PGP key locally and sign fonts with local key?
=== Poster` is now known as Poster
=== JanC_ is now known as JanC
=== p3lim3 is now known as p3lim
=== onjen_ is now known as onjen
=== decobus_ is now known as decobus
=== runbgp0 is now known as runbgp
=== chaser4206 is now known as chaser420
=== pacbard8 is now known as pacbard
=== kinghat81 is now known as kinghat8
=== eax__ is now known as eax_
=== himcesjf_ is now known as himcesjf
=== Szadek364 is now known as Szadek36
=== kinghat8 is now known as kinghat
=== NotEickmeyer is now known as Eickmeyer
=== mandem0110_ is now known as mandem0110
=== EriC^ is now known as EriC^^
=== sia is now known as siak
[19:15] <ice9> gnucash isn't starting on 23.10, only showing it's app icon in the dock but no app window and I have to kill it in order to close it
[19:19] <bprompt> ice9: how about if you run it from the terminal?  does it show any errors?
[19:20] <bprompt> ice9: an option, might just be to try using the "snap" version of it
[19:23] <ice9> why clicking on app icon in the dock, doesn't reset the notification number displayed on the icon?
[19:23] <pragmaticenigma> ice9, are you running in a wayland desktop, or X11 desktop. I'm not sure the devs for GnuCash are Wayland ready yet.
[19:23] <ice9> pragmaticenigma, wayland
[19:25] <pragmaticenigma> try it with an X11 session... I'm running across bug reports as recent as December 2023 that there are issues running under wayland
=== tom_ is now known as paul424
=== JanC_ is now known as JanC
=== gnuser is now known as GNUsuari
=== Vercas97 is now known as Vercas9
=== veegee_ is now known as veegee