[00:00] <wd50> it's been my experience that i sometimes have to change a systemd script to make the change take effect, in addition to the config change to reflect it.
[00:00] <wd50> for example, docker
[00:01] <sarnold> rafis: if you use sudo you have to type 'sudo systemctl suspend' etc
[00:01] <tomreyn> my default 20.04 primary restricted user can "systemctl poweroff" without entering a password
[00:02] <sarnold> tomreyn: even from a fresh shell or a fresh ssh connection?
[00:02] <sarnold> some of these polkit things have short grace periods
[00:02] <scott_tams> yeah, but this is more the driver/kernel level than the init system. `for keyword in nvidia nouveau; systemctl list-units | grep $keyword` prints nothing
[00:02] <rafis> tomreyn: how did you get it to work! ?
[00:03] <tomreyn> sarnold: that's from a gnome-terminal of the logged in user. i had not entered the user password for a good while.
[00:03] <tomreyn> rafis: out of the box, fresh install
[00:03] <wd50> i know.
[00:03] <wd50> i'll look for a solution
[00:04] <sarnold> tomreyn: huh. interesting :)
[00:04] <scott_tams> I'm just pissed/confused (and also pissed in the other sense) as to why SuperTuxKart looked great with motion blur and bloom yesterday or the day before and now it's a slideshow at the lowest settings
[00:04] <tomreyn> its groups are: user adm cdrom sudo dip plugdev lpadmin lxd sambashare
[00:05] <scott_tams> brb
[00:05] <tomreyn> "user" is the name of the user
[00:05] <tomreyn> as well as its primary grouü
[00:05] <tomreyn> *group
[00:09] <tomreyn> "pkaction" lists "org.freedesktop.login1.reboot" and "org.freedesktop.login1.power-off" amongst other
[00:10] <rafis> sarnold: worked
[00:11] <rafis> sarnold: you were right, still needs to write sudo before systemctl
[00:12] <sarnold> tomreyn: oh wow, I've never seen that before
[00:12] <tomreyn> are you "administrator" on settings -> users?
[00:12] <tomreyn> rafis: ^
[00:12] <tomreyn> sarnold: this command seems to be pretty useless though :)
[00:13] <sarnold> tomreyn: it's the single most useful thing I've learned about polkit so far :)
[00:13] <wd50> scott_tams: did you make any changes to your grub configuration?
[00:14] <tomreyn> sarnold: this can either mean that you find it to be mostly useless or that you haven't learnt much about it, yet. i'd be the latter class.
[00:14] <scott_tams> yes as I said in the first few messages I added `nouveau_blacklist=1` after I noticed the problem in order to force the switch back
[00:14] <scott_tams> brb
[00:14] <wd50> ah, okay, i see where it said that
[00:15] <tomreyn> bedtime for me, ttyl.
[00:15]  * scott_tams is back
[00:15] <wd50> but i do notice that the line in that post said had a period where you placed an underscore.
[00:16]  * scott_tams logged in from another machine, so that I can reboot without /quitting
[00:18] <wd50> what happens if you put `nouveau.blacklist=1`, instead of `nouvear_blacklist=1`?
[00:18] <wd50> i typoed that last part
[00:18] <scott_tams> yup, trying that now. dumbass mistake, bet that'll fix it
[00:19] <wd50> alright.
[00:24] <scott_tams> no changfe
[00:25] <wd50> hmm
[00:25] <wd50> well that was from like a decade ago..
[00:25]  * wd50 keeps looking
[00:27] <Bashing-om> scott_tams: Not paid attention to your issue - restate it for me please .
[00:27] <wd50> okay, so you mentioned editing grub, but did you also do anything with `/etc/modprobe.d/blacklist-nouveau.conf`
[00:27] <scott_tams> system unexpectedly switched from nvidia proprietary to nouveau, trying to get it to go back to nvidia
[00:27] <wd50> Bashing-om: he wants to use nvidia drivers but nouveau is resilient.
[00:29] <Bashing-om> scott_tams: wd50: Nvidia driver (module) fully installed ' dpkg -l | grep -i nvidia ' ?
[00:30] <wd50> he seems to have the respective driver packages installed.
[00:32] <scott_tams> Bashing-om, that returns 28 packages
[00:33] <wd50> scott_tams: did you create `/etc/modprobe.d/blacklist-nouveau.conf`?
[00:33] <scott_tams>  no
[00:34] <scott_tams> what if I try uninstalling xserver-xorg-video-nvidia-470, then running ubuntu-drivers autoinstall? Do you think that would have any effect?
[00:35] <scott_tams> If so, should I reboot between the two commands?
[00:35] <wd50> scott_tams: i found a slightly newer answer. https://askubuntu.com/questions/841876/how-to-disable-nouveau-kernel-driver that first answer.
[00:35] <scott_tams> the reason I ask is because I feel like i remember before this the 4** number being a lower number, like 440 or 430 or something
[00:36] <wd50> scott_tams: i don't really think so. what did you say caused it to act up, again?
[00:37] <scott_tams> I don't know for sure. I suspect that something was installed as a dependency and got auto-uninstalled, but TBH it came completely out of the blue from my perspective
[00:38] <wd50> interesting. sounds like a rocky patch process.
[00:39] <wd50> i mean i guess you could try reinstalling those packages.
[00:39] <wd50> but with apt, i would use `--purge`, or else nothing is truly reset when it reinstalls.
[00:39] <wd50> at least in my experience. unless someone deletes the python lib and places it back in from an iso, then simple apt reinstall works for me.
[00:41] <wd50> but for this driver thing, i'm seeing quite the community-developed assortment of possible solutions, but none of which are necessarily new or out of the scope of what those two links that you  posted suggest that you did.
[00:43] <scott_tams> i remember running a suspicious autoinstall with something about chromium and some stuff that looked like it was graphics related, but I can't remember what packages it was...it may have been this log entry?
[00:43] <scott_tams> libserd-0-0, librubberband2, chromium-codecs-ffmpeg-extra, python3-cached-property, bridge-utils, pigz, python3-texttable, containerd, ubuntu-fan, python3-websocket, libblas3, libbs2b0, libfftw3-double3, libvidstab1.1, python3-importlib-metadata, python3-more-itertools, docker.io, python3-attr, python3-jsonschema, python3-docker, python3-docopt, libgstreamer-plugins-bad1.0-0, pocketsphinx-en-us, runc, libsord-0-0, libflite1, gstreamer1.0-vaapi,
[00:43] <scott_tams> liblilv-0-0, python3-dockerpty, python3-pyrsistent, python3-zipp, libsratom-0-0
[00:43] <scott_tams> ah I don't think so
[00:44] <scott_tams> I'll be back in a few minutes. Thanks so much for trying to help wd50 and Bashing-om
[00:46] <wd50> np. i'm happy to help because i've had my fair share of wanting to pull my hair out over these kinds of issues.
[00:46] <wd50> chromium installs docker?
[00:46] <wd50> or was that some of the other stuff?
[00:49] <wd50> i don't see any package names that look like they should have touched your graphics drivers, intofar as i'm aware.
[00:52] <scott_tams> yeah I think that's a dead end
[00:53] <wd50> unless the deb packages for docker might have done that, i guess.
[00:54] <wd50> or unless it had to do with hardware acceleration settings, if you were messing with that. it still doesn't quite explain what happened to me. but these are just guesses. have you tried anything from the askubuntu link that i posted?
[00:55] <scott_tams> your link made me wonder....so I ran `cat /etc/modprobe.d/* | grep nvidia`...
[00:55] <scott_tams> blacklist nvidiafb
[00:55] <wd50> ah.
[00:55] <wd50> trying stuff now?
[00:56] <scott_tams> that doesn't look like the problem...sec
[00:56] <wd50> alright
[00:58] <scott_tams> https://pastebin.ubuntu.com/p/P3z5jqFRCM/
[01:00] <scott_tams> however `lspci -nnk | grep -i vga -A3` still shows `Kernel modules: nvidiafb, nouveau`
[01:01] <scott_tams> this explains a lot -- nvidiafb is blacklisted, which leaves nouveau.
[01:02] <wd50> nvidiafb isn't from nvidia, though
[01:03] <wd50> but do also add that one file for blacklisting nouveau.
[01:04] <scott_tams> I'm gonna try the idea I had to uninstall the NVidia 470 package and run the driver autoinstaller. If `kernel moudles` doesn't include the driver listing under lspci, I don't see what blacklisting the nonexistent module will do.
[01:04] <scott_tams> I'll try the blacklist thing if this doesn't work though, ofc
[01:05] <wd50> alright.
[01:05] <wd50> this is way more tinkering than i would ever hope to have to do on ubuntu lol.
[01:06] <scott_tams> yeah, same. But I'm more used to manjaro and have only switched back to ubuntu for zfs-on-root
[01:07] <scott_tams> if this were my dad's laptop I'd be pissec
[01:07] <scott_tams> s/c$/d/
[01:15] <scott_tams> did that, still get `Kernel modules: nvidiafb, nouveau`. I give up, I'm going to bed. Thanks anyway, guys.
[01:16] <wd50> rip
[01:16] <wd50> take it easy.
[01:16] <scott_tams> you too, thanks
[05:00] <ash_worksi> did ubuntu drop the postgresql-common package for PG12?
[05:08] <ash_worksi> nvm, had to use `apt purge` on 10 to not reinstall common for 10
[05:39] <neff> Good morning friends
[05:41] <neff> ho to fix device descriptor read error?I fixed it once,but can't find solution now
[05:41] <neff> half of usb not working
[05:47] <alkisg> neff, that might mean an ssd/flash disk failure or a controller failure or a power issue etc. It's usually a hardware problem that can't be fixed. Do mention more details about it
[05:47] <alkisg> E.g. paste the exact message in pastebin, mention when it happens, which devices are affected etc
[05:48] <alkisg> Also in some cases it might mean that the Linux kernel isn't compatible with certain hardware; and in few of these cases, changing the kernel makes the problem go away
[05:52] <neff> I remember it was how so connected to iommu
[06:20] <osse> tomreyn: Thanks. What is an SRU ?
[06:21] <osse> I googled it. Sounds serious :p
[06:29] <bouncy>  the xf86sleep key suspends my workstation under X session and also pure terminal. How was that key mapped? Cannot be a X tools like xmodmap nor xbkoptions. I would like to map the other unmapped multimedia keys the same way :)
[06:33] <osse> tomreyn: I see now that it's been fixed in git. So I might as well wait until an actual package exists upstream
[08:45] <hajonnes> hi, after the latest security update my graphics is gone. nvidia settings is a blank window and my 40" 4k screen is set to 724p without any option to change the settings. what to do?
[09:11] <fdan> hi there
[09:11] <fdan> i have a dump file
[09:12] <fdan> its a ssl dump file and i want to read the dnsnames the server certs are valid for  , the last date before the certificates expires, and last 3 characters of the certs PEM encoded format
[09:12] <fdan> i installed ssldump
[09:13] <iomari891> greetings, im using 21.04 and I can only boot from kernel <IP_ADDRESS>. when I try to boot from 34,31, or 25, the system freezes during the boot process. Why is only <IP_ADDRESS> working? I update my system daily.
[09:23] <wd50> iomari891: what process are you using to move between kernels?
[09:40] <nuovolnx> I would like to install ubuntu touch on nexus 6. Is it possible? Works well? Also I would like to know if the "morph" browser has an ad-suppression plugin?
[09:51] <lotuspsychje> nuovolnx: ubuntu touch is finished and the community took over with ubports
[09:51] <lotuspsychje> !touch | nuovolnx
[09:52] <lotuspsychje> nuovolnx: i dont think the ubports webbrowser allows plugins these days, maybe ogra knows?
[09:55] <zetheroo> is it just me, or is http://ch.archive.ubuntu.com/ down?
[09:55] <ogra> lotuspsychje, nuovolnx nope, i dont ... i already pointed nuovolnx to ubports in #ubuntu-arm ...
[09:55] <lotuspsychje> right
[09:55] <lotuspsychje> zetheroo: for mirror issues, you can ask in #ubuntu-mirrors
[09:56] <ogra> oh, i see they still have an IRC channel !
[09:56] <ogra> i didnt know that
[09:56] <zetheroo> on three Ubuntu 20.04 PCs I am getting 'Failed to fetch' with apt update
[09:56] <zetheroo>  lotuspsychje: ok
[09:56] <lotuspsychje> zetheroo: sure its not your end? firewall/router/proxys?
[09:58] <zetheroo>  lotuspsychje: haven't changed anything, and it's been working till today.
[09:58] <zetheroo> Internet is working no probs
[09:58] <lotuspsychje> allrighty
[10:01] <KBar> hello everyone! strange thing: ftp finished downloading the daily iso image but won't return to prompt. it's stuck with this line: 150 Opening BINARY mode data connection for impish-desktop-amd64.iso<PHONE_NUMBER> bytes).
[10:02] <KBar> i can confirm that it has finished downloading by listing that file:<PHONE_NUMBER> Sep  8 14:24  impish-desktop-amd64.iso
[10:03] <KBar> is this potentially a bug?
[10:04] <lotuspsychje> !next | KBar
[10:09] <lotuspsychje> iomari891: we currently have a lot of 5.11 bugs, i reccomend you browse the recent 'linux' bugs on launchpad, see if your issue is amongst them
[10:10] <lotuspsychje> iomari891: investigating your dmesg could help see whats going aswell
[10:16] <ztane> howdy, after installing some recent ubuntu updates to 20.04, fractional font scaling is b0rken, some software have ginormous fonts (kde apps) and the gtk apps including the ubuntu settings app have almost microscopic even at 200 % scaling ratio, fractional scaling or not, it doesn't seem right... any help? :D
[10:17] <hajonnes> Hi, I lost my graphics after last security update. I have timeshift so I reverted. Now I wonder about my nvidia install. I have a couple of packages installed 'automatic', could anyone take a look if I should set any of them to 'manual' https://termbin.com/szmx
[10:18] <medard> Hey, I keep getting random disconnects from wifi
[10:18] <medard> here are some logs, if you could help me
[10:19] <medard> https://termbin.com/y6bs
[10:19] <medard> https://termbin.com/8dvc
[10:37] <jeremy31> medard: check out https://ubuntuforums.org/showthread.php?t=2354328&p=13614520&#post13614520
[10:52] <Spyd> Hi, I have a question about installing Ubuntu on a RAID volume. Can someone help me?
[10:59] <MartinMSPedersen> how to install rpcbind? I get a 404 error ?
[10:59] <MartinMSPedersen> http://us.archive.ubuntu.com/ubuntu/pool/main/r/rpcbind/
[11:00] <MartinMSPedersen> for all mirrors I have tried
[11:00] <MartinMSPedersen> Err:1 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 rpcbind amd64 1.2.5-9
[11:04] <hajonnes> #hexchat
[11:04] <Spyd> I'm building a server, it has two 120Gb SATA SSDs on an AMD B450 motherboard. I want the two SSDs on RAID 1 (redundancy). I tried software RAID, but Ubuntu doesn't want to boot from a software raid. I tried hardware RAID (with the onboard RAID controler from AMD), but there's no included drivers for this RAID controller, and I don't know how to install them.
[11:04] <Spyd> I tried to use the console to install RCRAID, but failed because this program can't be installed on the read-only volume of the live-OS. Any solution that allows me to install Ubuntu on a RAID is fine with me, I don't care if software or hardware.
[11:56] <TJ-> Spyd: it can boot from software RAID1, you just need to configure the devices correctly
[11:57] <BluesKaj> Hi folks
[11:57] <TJ-> Spyd: the trick is to install grub to both underlying devices (and use the correct mdadm --metadata=1.0 to put metadata at /end/ of the device, not start)
[12:02] <TJ-> Spyd: on both use identical GPT arrangement, for UEFI create the EFI-SP (256-512MB), for BIOS create a BIOS boot partition (2MB), then a partition for the OS. RAID-1 the OS partition. grub-install to each underlying device.
[12:48] <Spyd> TJ-: Thank you for your answer, I'm trying to understand it. Please tell me if I understand it correctly. I'm going to use mdadm to partition both phyisical drives, creating the exact same partitions (EFI, SYSTEM, SWAP), then create a RAID-1 of the SYSTEM partition, is that right?
[12:51] <TJ-> Spyd: no, what I was suggesting was to /not/ RAID the entire physical devices, but only a partition for the OS. You can do as you suggest as long as you use --metadata=1.0 but firmware can only boot from a single device, and that'll prevent grub-install working on the MD device since it can only read, not write, to MD
[12:59] <Spyd> TJ-: If I create the same partitions on both SSDs, and then create a RAID-1 of the partition where the OS is installed, will it work? Also, for this to work, do I have to install on a single disk before or I can make the RAID-1 on the installer shell and then continue with installation?
[13:08] <nunya> CRTL Home no longer does screenshot I've tried CRTL ALT Home. My screen flashes but when I go into GIMP and hit paste it says nothing in clipboard. Please help. I've googled but found no solution.
[13:10] <nunya> There is no image data in the clipboard to paste is the exact message
[13:11] <TJ-> Spyd: Yes it'll work. Create the mdadm array with --metadata=1.0 manually before running the installer so you can select the md device as the location for installation, but set bootloader to one of the devices. Later, you can use dpkg-reconfigure grub-pc (or grub-efi-am64) to reinstall to multiple devices - it gives a list of devices and you can 'tick' more than one in debconf)
[13:17] <leftyfb> nunya: screenshot by default is the print screen button
[13:19] <nunya> leftyfb: Was CRTL for me as long as I can remember until last security update
[13:20] <nunya> leftyfb: Print scr by itself does nothing
[13:21] <leftyfb> nunya: check your keyboard shortcut settings
[13:21] <nunya> leftyfb: I did and I'd send you a sreenshot but...
[13:22] <nunya> leftyfb:The keyboard shortcut for screenshot is CRTL Home My Home key is also the Print Scr button.
[13:23] <leftyfb> nunya: is the "Print Scr" text on your keyboard blue?
[13:25] <nunya> leftyfb:There are no blue printed keys on my logitec wireless keyboard. It is the one I'm using to type now so I know it works.
[13:26] <leftyfb> nunya: so "home" and "print scr" are both printed in the same color on the same key?
[13:27] <nunya> leftyfb:No Home is bigger in white Print Scr is Orange and smaller
[13:28] <leftyfb> nunya: and do you have a "fn" key with "fn" being printed in orange?
[13:29] <nunya> leftyfb: Yes
[13:31] <leftyfb> nunya: did you try hitting fn + print scr?
[13:32] <leftyfb> nunya: what version of Ubuntu are you running and which desktop environment?
[13:34] <nunya> leftyb:I just tried gnome-screenshot in terminal and it didn't work either so I'm starting to think it's not the keyboard shortcuts but the actual gnome-screenshot program. It flashed like it was taking a screenshot but put nothing on clipboard.
[13:37] <leftyfb> nunya: the default is to take a screenshot and save it in pictures
[13:39] <nunya> leftyfb: It was never like that for me before but you are correct now I'm finding all the previous screenshot attempts in pictures. Any way to get it back to clipboard instead of creating images in pictures?
[13:42] <leftyfb> nunya: first, yes, it has always been like that as default. If you changed it, that's another story.  There just doesn't seem to be any option other than changing shortut to create screenshot. Once again, I am trying to get contents of screen shot to clipboard instead of creating a new image.
[13:51] <leftyfb> nunya: what is your "Copy a screenshot to clipboard" set to?
[13:55] <Koopz> so why are the only results on google on how to fix my dns issues involving disabling whatever daemon may be used as an inbetween for /etc/resolv.conf
[13:56] <leftyfb> Koopz: lets troubleshoot your dns issues then, not google results
[13:57] <Koopz> i got a domain ending in .local, how do i make "nslookup username.projectname.local" work without appending the ip of the network's DNS server
[13:57] <leftyfb> Koopz: systemd-resolve --status|grep "DNS Servers" | nc termbin.com 9999
[13:59] <Koopz> https://termbin.com/o0th now that's a nifty service
[13:59] <Koopz> the 1.10 is correct
[13:59] <leftyfb> Koopz: and what about "nameserver" entries in /etc/resolv.conf ?
[14:00] <Koopz> the usual nameserver <IP_ADDRESS>
[14:01] <leftyfb> Koopz: hm, not sure. I do know that using .local can be problematic due to mDNS
[14:03] <Koopz> what would you recommend as an alternative?
[14:03] <Koopz> .network?
[14:03] <nunya> leftyb: I have changed copy an area screenshot to clipboard shortcut and the screen flashes but nothing in clipboard. Like I said before I think clipboard is broken. Going to reinstall. At least I know where the screenshots are and can import them in gimp or some other editor to work with them. Thanks
[14:04] <leftyfb> nunya: "copy an area screenshot"?
[14:07] <nunya> leftyb: None of the copy screenshot to clipboard shortcuts (area, window,...) work. The screen flashes like it's taking a screenshot but nothing in clipboard.
[14:11] <cluelessperson> I'm experiencing something weir
[14:11] <cluelessperson> running:   rename --help   prints out the help
[14:11] <cluelessperson> but then it just hangs
[14:11] <cluelessperson> and not anymore
[14:11] <cluelessperson> wut
[14:12]  * cluelessperson suspects its the network fs
[14:47] <alterjsive> why does ubuntu use wine-6.16 (Staging)?
[14:47] <alterjsive> by default
[14:48] <alterjsive> shouldn't ubuntu use wine-6.15?
[14:48] <alterjsive> a stable release
[14:49] <alterjsive> I'm having trouble with the latest version
[14:59] <jabberwock> Does the gnome file manager have a "go to folder" shortcut? I would expect to click on the space that shows the folder to be able to type
[15:03] <lotuspsychje> jabberwock: you mean ctrl + l to type a dir?
[15:04] <shark> junk
[15:11] <nunya> leftyb: I couldn't get gnome-screenshot -c to work in custom keyboard shortcuts. I installed flameshot and wrote a custom keyboard shortcut flameshot full -c assigned to Alt CRTL Home That puts screenshot of whole screen into clipboard. Meanwhile I have assigned CRTL Home to put screenshot in ~/Pictures Thanks for your help. I guess something about gnome shell or gnome-screenshot got broken with last update.
[15:28] <cluelessperson> Is there a set of wireless adapters with which ubuntu fully supports wireless AC / 1300mbps plug and play?
[15:30] <lotuspsychje> !hardware | cluelessperson
[15:35] <cluelessperson> lotuspsychje, thank you for the link.  I see that my laptop's adapter isn't listed.
[15:35] <Samnzdat> Linux Election Management System Disk Images how-to: https://termbin.com/hj71
[15:36] <cluelessperson> what is even a Linux Election Management System Disk
[15:37] <cluelessperson> Samnzdat, what's the point of that
[15:37] <cluelessperson> cd pyzozord
[15:38] <Samnzdat> Maricopa County election forensic audit evidence
[15:39] <leftyfb> !ot | Samnzdat
[15:39] <Samnzdat> Someone answered a goddamn question, I answered it.
[15:39] <genii> cluelessperson: Atheros/Qualcomm chipsets also are well supported in Linux. You can find 802.11ac capable versions here, and the products they are found in https://deviwiki.com/wiki/Qualcomm_Atheros#tab=Wireless_chipsets
[15:39] <Samnzdat> s/answered/asked
[15:40] <leftyfb> Samnzdat: nobody asked anything related to disk images or the Maricopa County election
[15:47] <leftyfb> !op | Samnzdat  - spamming some political B.S. in multiple channels
[15:49] <Samnzdat> Thanks for the list of potential allies.
[16:02] <linsux> is there calendar program that's compatible with outlook calendar?
[16:27] <leftyfb> linsux: https://threenine.co.uk/setup-office365-calendar-with-thunderbird/
[18:14] <Spyd> TJ-: I tried what you told me. I had been able to, but when I try to install, the installer crashes doing something in the background just after you click on the "Done" button on the custom partition page of the installation. I tried with both the latest and the LTS ISO of Ubuntu, with the same results. I guess I'm doing something wrong, but I don't know what. I have screenshots of the partitioning (https://paste.pics/31ef1c44ef9452c84828975fb8b4b67d) and the
[18:14] <Spyd> crash message (https://paste.pics/3466f10c6c6c7a0e6b41972820459b73)
[18:18] <Yuvraj> Hi all.
[18:18] <Yuvraj> I am Trying to install ubuntu-server on Wedge 100BF-32X Switch - Intel x86 Broadwell-DE, Pentium D -1517
[18:19] <Yuvraj> But stuck with Error, Please help.
[18:24] <LadyCailin> Have you tried not having the error?
[18:26] <sarnold> Spyd: is there anything in the full report that describes what failed?
[18:27] <Spyd> sarnold: The report has like 50 pages... and what should I look for?
[18:29] <Spyd> sarnold: One thing strange is that when I created the raid volume, I called it md0, but after the first reboot when it crashed, now it's called md127.
[18:29] <TJ-> Spyd: not sure why it would crash. I gave up on installers a long time ago - I can do it quicker and better manually + debootstrap :)
[18:30] <Spyd> TJ-: I'm too much of a noob to even try that.
[18:31] <TJ-> Spyd: after some years fighting ubiquity it becomes 2nd nature :)
[18:32] <sarnold> Spyd: it's usually a good bet to go to the very end and then start reading backwards to find the 'first' error
[18:34] <TJ-> Spyd: one issue I see is sda and sdb don't have identical partition layouts
[18:37] <TJ-> Spyd: that may not be why the installer failed, but where you're trying to create a mirror layout, then even where the RAID1 mirror isn't active (the EFI-SP for example) you should manually duplicate that so in the event the device with the primary EFI-SP fails the system can still boot (you should also ensure using "grub-install --force-extra-removable ..." so grub's core is also installed to the
[18:37] <TJ-> removable media path)
[18:37] <Spyd> I found the error, it says the raid volume is bad? https://paste.pics/d3925ef03000ded63965778e6980f96a
[18:37] <lmat> I did apt install docker; docker; and it says Command 'docker' not found.
[18:38] <lmat> apt install docker; says "docker is already at the newest version"
[18:41] <lmat> How do I install docker in ubuntu?
[18:45] <sarnold> lmat: docker is a system tray tool
[18:45] <sarnold> lmat: you probably want docker.io instead
[18:48] <TJ-> Spyd: "comparing device lists: expected [/dev/sda2, /dev/sda2] found [/dev/sda2, /dev/sdb2]
[18:48] <TJ-> Spyd: looks like (another) installer bug!
[18:49] <lmat> sarnold: so docker is some system tray tool and https://github.com/docker/docker is docker.io?
[18:51] <matsaman> lmat: yup
[18:53] <lmat> matsaman: Thank you for the confirmation. This is fairly surprising, but sounds workable. Thank you!
[18:53] <matsaman> one must be careful choosing a name as simple and bland as 'docker' if one doesn't want to intersect with other projects already existing
[18:57] <sarnold> lmat: exactly that :)
[20:06] <ELFrederich> On 20.04 when I install gimp-plugin-registry I get plugin errors when starting gimp.  The liquid rescale and heal selection plugins are not available.  This wasn't an issue on 18.04.
[20:33] <samy1028> Hello all, I'm trying to find the rsyslog-omudpspoof for 18.04 or 20.04.  Is there a package for it in Ubuntu's repository?  If so, I can't seem to find it.
[20:39] <sarnold> samy1028: I can't find any files with that name in any package in ubuntu focal, nor any files with that name in any source code shipped with any supported version of ubuntu
[20:42] <samy1028> Yeah, I did an update a little while back on 18.04 and it updated rsyslog, but I think my omudpspoof is still on the prior version of rsyslog and the new one doesn't like it anymore.  I guess I could find the .so file to match my build of rsyslog from another distro and copy it to my ubuntu box?  I don't remember exactly as it's been a long time since I set it up initially.
[20:44] <samy1028> or, I wonder if I copied it from 16.04?  I just did a strings on omdupspoof.so and found reference to Ubuntu 5.4.0-6ubuntu1~16.04.9
[20:47] <leftyfb> samy1028: there are no files that exist in 16.04 that match omdupspoof either
[20:47] <leftyfb> samy1028: or omudpspoof
[20:48] <leftyfb> I take that back, there is a .txt and .html file
[20:48] <leftyfb> as part of rsyslog-doc
[20:48] <leftyfb> no modules
[20:49] <leftyfb> samy1028: I searched 16.04, 18.04 and 20.04
[20:50] <leftyfb> samy1028: if it's something you've had before, it's because you added it from a 3rd party
[20:51] <samy1028> odd.  I have to figure out how to make it work again. :)  always fun when something breaks.
[20:52] <samy1028> It's an isolated system whose sole job is to collect syslogs, store them, and forward a few to another system for further reporting/analysis.  The omdupspoof.so is from 2018, last time I worked on it.
[20:52] <scott_tams> "Night Light" has stopped changing the temperature of my screen. Ubuntu 21.04 (wayland/gnome) what do?
[20:52] <samy1028> at least this points me in the rigth direction.  Thank you sarnold and leftyfb.
[20:53] <sarnold> good luck samy1028 :)
[20:53] <samy1028> when I find the solution I'll let ya'll know.
[20:59] <scott_tams> I installed redshift and this is the output but nothing changes https://pastebin.ubuntu.com/p/KzHznkNYxW/
[20:59] <scott_tams> if no one knows how to fix this, could someone at least advise me on the steps necessary to run 21.04 using X11?
[21:29] <tomreyn> scott_tams: install xserver-xorg. you can switch your session at login
[21:30] <scott_tams> thanks
[21:31] <scott_tams> "xserver-xorg is already set to the newest version"
[21:31] <scott_tams> where does the selection show up in the login screen? I was looking for it yesterday and couldn't find it
[21:36] <tomreyn> scott_tams: i don't have 21.04 installed, but it should be on the first login screen where you pick the username
[21:37] <scott_tams> ok, I'll try it now.
[21:37] <tomreyn> actually no, the second screen
 actually no, the second screen
[21:39] <tomreyn> there's a cog icon on the bottom right corner of the gdm password screen of my 21.10 preview
[21:39] <scott_tams> tomreyn, your message came through just before i /quit. But I didn't see a drop-down in either screen
[21:40] <scott_tams> I'll check once more
[21:40] <tomreyn> https://i.imgur.com/zBAGujz.png
 https://i.imgur.com/zBAGujz.png
[21:41] <scott_tams> it didn't work. TBH don't stress about it. This install is having a bunch of problems. Just gonna start from scratch again. Thanks anyway.
[21:42] <scott_tams> I was in here for hours yesterday trying to figure out why it insists on using the nouveau drivers rather than the nvidia ones
[21:44] <tomreyn> long sessions trying to get "nvidia" working aren't unheard of. i can only recommend intel and amd at this time.
[21:45] <tomreyn> (or those better supported graphics on arm64)
[21:46] <scott_tams> absolutely, and if I were in the market for a video card now, i wouldn't even consider Nvidia. But I bought this card 5+ years ago for cheap and it's served me well, so I'm not just gonna throw it out. TBH this troubleshooting session has revealed to me how little value ZFS-on-root snapshots have next to an efficiently rebuildable architecture. I'll try some old snapshots and see if I can recover just for the sake of learning, but I think I'm going
[21:46] <scott_tams> to (yet again) go back to ext4-on-root from a snapshottable root FS
[21:47] <scott_tams> this time, with a rebuildable arch for the whole system as opposed to just the containers
[21:58] <orion> Hello. How can I build only the kernel and not its associated modules with the deb framework? "LANG=C fakeroot debian/rules binary-aws" seems to want to build both.
[21:58] <orion> Alternatively, what's the best way to establish a cadence for kernel development on a remote server?


[00:25] <knoppix> hi, how do  i connect from kde to a smb server (gnome user here) , the smb server is on my subnet
[00:26] <knome> knoppix, ask #kubuntu
[00:27] <knoppix> home, oops sorr
[00:27] <knoppix> sorry
[00:53] <ron_o> might have found a bug in 8.04
[00:54] <ron_o> keyboard shortcuts. I add the keyboard shortcut, say 'xkill' .. then it asks me for the shortcut and won't let me place it anywhere.
[00:55] <ron_o> nevermind. you have to type the keys on the keyboard. just weird.
[01:18] <McCallister> Hey guys.
[01:19] <McCallister> I lost my panel.
[01:22] <McCallister> hello dsmith
[01:29] <phix> hi McCallister
[01:29] <phix> how are you?
[01:30] <McCallister> I'm alright.
[01:31] <McCallister> I lost my panel.
[01:31] <McCallister> Not sure how to restart it.
[01:32] <McCallister> xfce4
[01:32] <knome> McCallister, alt+f2 > xfce4-panel
[01:34] <Recursiv3> How do I enable SHMConfig in Xubuntu 8.10? The xorg.conf file is not working.
[01:50] <McCallister> I'm not sure.
[01:52] <phix> McCallister: :(
[01:56] <Kudi> how do i get conky to show my ip address?  What did i do wrong?: IP - ${color white}${addr interface}
[01:58] <McCallister> That's it!!
[01:58] <McCallister> Got it. Thanks a bunch
[02:01] <Recursiv3> How do I edit my touchpad settings in Intrepid Ibex?
[02:02] <Recursiv3> I can't use GSynaptics because I can't enable SHMConfig
[02:04] <McCallister> I'm not sure.
[02:04] <McCallister> What type of laptop?
[02:08] <Recursiv3> eeePC
[02:09] <McCallister> Are there any posts about it on the forums?
[02:09] <Recursiv3> Yes. They don't seem to work.
[02:10] <Recursiv3> I just need some way to turn tapping off.
[02:11] <McCallister> That would get annoying.
[02:12] <McCallister> What operating system came installed?
[02:13] <Recursiv3> A version of Xandros.
[02:13] <Recursiv3> It was really dumbed down; I needed a real OS.
[02:14] <ball> CP/M-80 ftw
[02:15] <ball> Speaking of "dumbed down", I think Mrs. ball's next PC will have MS Windows Vista Home Basic
[02:16] <Recursiv3> God damn it.
[02:16] <ball> What's wrong?
[02:16] <Recursiv3> I've been trying for at least a week to get tapping disabled.
[02:17] <Recursiv3> This damn computer.
[02:17] <ball> On a trackpad?
[02:17] <Recursiv3> YEs.
[02:17] <ball> Yeah, that would be annoying.
[02:17] <ball> s/would/could/
[02:17] <ball> Is it a CMOS setting?
[02:17] <Recursiv3> No, you are supposed to be able to use gsynaptics, but it doesn't work on Intrepid.
[02:18] <ball> So there's no CMOS setting to disable it?
[02:18] <Recursiv3> I will check, I am almost certain not.
[02:19] <ball> Definitely worth checking.  If the firmware's passing "clicks" to the OS, there's nothing gsynaptics (or whatever) will be able to do about it.
[02:19] <Recursiv3> No, no option.
[02:19] <ball> hello effie_jayx
[02:19] <ball> Recursiv3: that's odd.
[02:19] <effie_jayx> hello ball
[02:20] <Recursiv3> I have not been able to get any touchpad configuration stuff running.
[02:21] <ball> Are you running some sort of touchpad driver, or just generic mouse?
[02:21] <Recursiv3> IDK.
[02:21] <Recursiv3> I think there is some sort of driver installed.
[02:21] <ball> I'm inclined to blame the firmware, but then I'm always inclined to blame the firmware.
[02:22] <ball> ...because /so/ much firmware is broken, or at best poorly-written
[02:34] <Kudi> how do i make the volume applet control pcm instead of master?
[02:36] <ball> hello Kudi
[02:38] <Kudi> ball: hi
[02:39] <Kudi> ball: what are u bored or something?
[02:40] <Recursiv3> Some sites say that I can use xinput to configure the touchpad.
[02:41] <Kudi> Recursiv3: if your talking to me i have no idea what your talking about but if you are i can google
[02:42] <Recursiv3> I'm just saying it to anyone who will listen.
[02:42] <Recursiv3> Can anyone tell me what command I would use to disable the tapping using xinput?
[02:43] <Kudi> ohh...i dont think any1 is answering questions here, there probably all out for tea
[02:43] <ball> Recursiv3: I reckon you're barking up the wrong tree.
[02:43] <ball> Kudi: depends on the question
[02:44] <Recursiv3> ball, what do you mean?
[02:45] <ball> Recursiv3: Well, I've an idea, but I don't know enough about Xubuntu to know how to test it.
[02:45] <Recursiv3> Tell me your idea and I can test it.
[02:45] <Kudi> ball: ha, what are u trying to say..
[02:46] <ball> Recursiv3: There may be a way in Xubuntu (or in X, specifically) to see what events the firmware is sending to your X server.
[02:46] <ball> That could tell you whether your firmware is at fault.
[02:47] <Recursiv3> I don't think the firmware is at fault.
[02:48] <ball> Why do you think that?
[02:48] <Recursiv3> The OS that was previously installed was able to have tap-to-click disabled.
[02:48] <ball> Hmm... ok
[02:48] <ball> Well that supports your thought.
[03:38] <D-MAN> DOES ANYONE KNOW WERE TO GET AN EASY TO USE INVOICE TEMPLATE?
[03:38] <D-MAN> sry caps
[03:38] <izinucs> OO should have one either built in or downloadable.
[03:39] <D-MAN> izinucs,  tried downloading on for oo but cant edit it it says read only?
[03:40] <izinucs> D-MAN, once open in oo save it again with a new name
[03:40] <D-MAN> kk let me try that
[03:43] <D-MAN> IZ IT WORKED BOY DO I FEEL DUMB!!!!!
[03:44] <D-MAN> izinucs,  thnx
[03:44] <izinucs> np.. :)
[05:04] <D-MAN> my printer keeps cutting off the right side of page in oo spreadsheeet how can i fix this?
[05:51] <R1cochet> is there any way to view printer ink levels?
[06:01] <crawlthewarriork> does anyone perhaps know why when I update packages or use apt-get to dl software, it goes really slow (download speed) but on the internet (firefox) I can download really fast?
[06:05] <crawlthewarriork> anyone?
[06:06] <cody-somerville> crawlthewarriork, try a different mirror
[06:07] <crawlthewarriork> how do you do that using apt-get or update manager?
[06:09] <crimsun> cody-somerville: do you know if Xubuntu 9.04 will use PulseAudio?
[06:19] <crimsun> cody-somerville: ok, well, if you happen to know, find me during lunch tomorrow
[08:59] <bebop_> anyone available to help with a issue?
[09:04] <generalsnus> We have a problem with our thin clients,  It seems like each user has 2 instances of the process "ps" running.. using 2% cpu each.. as you imagine..this is a problem when there is 30 users logged on.. cpu load is at 90-100%  what can i do?
[09:26] <generalsnus> We have a problem with our LTSP clients.. each user have x2 instances of the process "ps" its eating all cpu. What could be wrong? pstree: http://paste2.org/p/113585
[09:33] <TheSheep> generalsnus: it's being called by some python script...
[09:34] <TheSheep> generalsnus: maybe try 'ps auxwww' to see the full command that started it
[09:44] <generalsnus> http://paste2.org/p/113591  is the output of "ps auxwww|grep python "
[09:45] <TheSheep> generalsnus: what's /usr/bin/scp-client ?
[09:46] <TheSheep> hmm... it's part of thin-client-manager-backend
[09:47] <TheSheep> whatever it is
[09:47] <TheSheep> I see it's placed in autostarted applications
[09:48] <generalsnus> isnt it somthing i would need to have autostarted?
[09:50] <TheSheep> no idea
[09:50] <TheSheep> you can file a bug for it
[09:52] <TheSheep> generalsnus: that script is strange
[09:52] <TheSheep> looks like it's written by a java programmer who never saw python before
[09:52] <generalsnus> here is the script tho: http://paste2.org/p/113596
[09:53] <TheSheep> generalsnus: yes, I downloaded it from packages.ubuntu.com
[09:53] <generalsnus> ah
[09:54] <TheSheep> generalsnus: it should run the 'perent poller' function every 10 seconds
[09:54] <TheSheep> parent_poller
[09:56] <TheSheep> it then forks a shell running ps and grep just to see if its parent process is still running
[09:56] <TheSheep> madness
[09:58] <generalsnus> hm.. we tried to killall python, just to get the system responsive again... cpu load went back to 20%
[09:58] <generalsnus> is there somthing i can do to the script, to prevent this?
[09:59] <TheSheep> generalsnus: let me see
[10:03] <TheSheep> generalsnus: try this: http://paste.pocoo.org/show/94659/
[10:06] <TheSheep> generalsnus: but please report the bug too
[10:06] <generalsnus> ok, ill wait until i can reboot the thing..
[10:07] <generalsnus> ill report bug aswell as reporting feedback here
[10:09] <generalsnus> brb lunch
[11:43] <R1cochet> is there a way to check my printer ink cartridge levels? 8.10
[11:46] <gabkdlly> R1cochet: you might check if the site of your printer manufacturer has a page dedicated to linux support
[11:46] <gabkdlly> if there is not a way to do this, then it is a bug, since I have heard that running your printer when there is no ink can damage the heads
[11:47] <gabkdlly> although I guess on some printers it does not matter, you just find out that the cartridges are empty by your printouts fading to white
[11:47] <gabkdlly> you should definitely consult your user manual and/or the printers manufacturers site
[15:05] <likemindead> Can anyone explain why are some updates "kept back" when I try to "sudo apt-get update" and then "sudo apt-get upgrade" ?
[15:06] <likemindead> Is it most likely that there are dependencies for those packages that haven't made it into updates yet?
[16:00] <Shaba1> anyone here?
[16:02] <tingle> jep
[16:04] <Shaba1> Hello tingle
[16:04] <tingle> hello Shaba1
[16:04] <Shaba1> I think I found the answer to my question already
[16:04] <Shaba1> but I will stand by just in case
[16:05] <Shaba1> here is one though
[16:05] <tingle> good, google is your friend
[16:05] <Shaba1> how do I find the version of xubuntu I am running
[16:05] <tingle> hm let me think
[16:05] <tingle> uname -a maybe
[16:05] <tingle> sec ill check
[16:06] <tingle> well you cant really see what XUBUNTU you running whit uname -a
[16:07] <tingle> Shaba1: applications > help on the top page you can see what version your running
[16:08] <tingle> Shaba1: Welcome to Xubuntu 8.10! for example
[16:09] <Shaba1> that opened a web page in firefox
[16:09] <Shaba1> it said welcome to xubuntu 8.04 or something similar
[16:11] <tingle> well than you prolly have 8.04
[16:12] <Shaba1> Ok next
[16:12] <Shaba1> How do I "install" a .deb file
[16:12] <Shaba1> sorry for all the stupid newbie questions
[16:12] <tingle> dpkg -i packagename.deb
[16:12] <tingle> as root ofc..
[16:12] <Shaba1> I a quite versed in windows but totally new to linux
[16:13] <tingle> its no problem but you can google most of the question too
[16:13] <tingle> im sure there has been someone whit the same question before you
[16:15] <Shaba1> thanks tingle
[16:16] <tingle> no problem Shaba1
[16:17] <Shaba1> I will still hang out here though
[16:17] <Shaba1> Now that I knew there is someone here
[16:17] <Shaba1> :D
[16:18] <tingle> xD
[16:44] <Shaba1> is the not and edit command in linux
[16:46] <Erant> How come my system boots up in the wrong resolution? I've only got about 1/4 of the screen. I can go to the Settings Panel and change the resolution, and then it's fine.
[16:46] <Erant> But it does that everytime I boot
[16:52] <Shaba1> ok what question
[16:52] <Shaba1> what does '/etc/profile/" do>?
[16:53] <TheSheep> Shaba1: it's explained in teh first line of that file
[17:14] <Erant> Hmm, other question then. The GRUB that comes with Ubuntu, would that be GRUB2 or GRUB legacy?
[17:17] <crimsun> Erant: grub legacy
[17:18] <crimsun> Erant: we're actually in a session currently at UDS discussing replacing grub legacy with grub 2
[17:19] <crimsun> Erant: and by "GRUB that comes with Ubuntu", I presume you mean not "GRUB available in Ubuntu" (because both are) but "GRUB that is the default bootloader"
[17:19] <MiVo> Hello, I try to use icecast2 in Xubuntu, but I get this error: "Starting icecast2: start-stop-daemon: Unable to set gid to 123 (Operation not permitted)"
[17:20] <Shaba1> what is "UDS"
[17:22] <Kudi> KAD is firewalled still but i cant control udp in my router settings and i have no idea how to update the node list...all im looking for is a green arrow.  What are my options?
[17:27] <Shaba1> linux is so frustrating
[17:28] <Shaba1> no wonder it had not made it as a general user OS
[17:29] <Kudi> Shaba1: ha if you think ubuntu is frustrating you need to read a lil more, ubuntu already does so much for you
[17:33] <Shaba1> I have been using computer since I brought my first altair 5000 in the 70s
[17:34] <Shaba1> I seperate things into how easy is it for someone like me to do operations
[17:34] <Shaba1> and how easy it is for a general user to do the an operations
[17:34] <Shaba1> and trust me linux is NOT for the average user
[17:37] <TheSheep> Shaba1: it also hurts that you can't use all your experience from Other Operating Systems (tm)
[17:37] <TheSheep> Shaba1: on the bright side, you learn a bit of POSIX, which is a standard that is going to stay
[17:40] <Shaba1> true
[17:40] <Shaba1> and that is why I am learning linus
[17:41] <Shaba1> linux
[17:41] <Shaba1> right now I am tring to get the roadsendphp compiler to complie itself
[17:41] <Shaba1> and its frustrating
[17:44] <TheSheep> bootstrapping is always tricky
[17:46] <Shaba1> bootstrapping?
[17:46] <Shaba1> I used this page
[17:46] <Shaba1> http://www.compdigitec.com/labs/2008/07/24/install-roadsend-php-compiler-on-ubuntu-without-compiling-anything/
[17:47] <Shaba1> but when I get to step four I get and error. something about pcc.conf not availible or something
[17:47] <TheSheep> Shaba1: remember how baron Munhausen pulled himself from swamp by his boot straps?
[17:48] <Shaba1> nope
[17:49] <TheSheep> Shaba1: anyways, the process of a program compiling itself or a loading itself into memory, or doing similar things with itself is called 'bootstrapping'
[17:49] <TheSheep> Shaba1: that's why you 'boot' the operating system
[17:52] <Shaba1> I know what that is TheSheep. I just did not see how it applied in this context
[17:53] <TheSheep> well, compiler compiling itself...
[17:56] <Shaba1> lol
[17:56] <Shaba1> I now it sounds silly
[17:56] <Shaba1> did you look at that page?
[18:00] <TheSheep> Shaba1: took a cursory glance
[18:01] <TheSheep> Shaba1: not much to do, they provide ready debs, you just have to set up a bunch of environment variables because the debs have the files in wrong places
[18:05] <TheSheep> Shaba1: btw, instead of setting LD_LIBRARY_PATH, you can jsut add it to /etc/ld.so.conf.d/libc.conf and run ldconf
[18:05] <TheSheep> ldconfig
[18:21] <Shaba1> what does that do?
[18:22] <Shaba1> TheSheep check out this pastbin.
[18:22] <Shaba1> http://pastebin.com/d3a5f49ff
[18:22] <Shaba1> that is the error I get when I use the -d 2 debug levle
[18:28] <Veinor> So I just switched from GNOME to xfce, what should I know?
[18:29] <knome> Veinor, be happy.
[18:30] <Veinor> lol
[18:30] <Veinor> but seriously, what should I get used to doing differently?
[18:31] <MOras> hi anyone to help me with xubuntu 6.06. I click on Applications but the list won't show
[18:34] <Shaba1> TheSheep are you still here?
[18:37] <knome> Veinor, not really anything in particular.
[18:37] <Veinor> awesome
[18:40] <knome> but little things, xfce should be a bit more logical and have some different configurability
[18:40] <knome> you can just ask if you need help or don't know how something is supposed to be workinhg
[18:40] <knome> -h
[18:40] <Veinor> so far this is great
[18:42] <knome> good to hear..
[18:45] <Veinor> hmm
[18:45] <Veinor> although my mute button doesn't seem to be able to unmute things
[18:45] <knome> did it work in gnome?
[18:45] <Veinor> yep
[18:45] <Veinor> and banshee doesn't seem to be liking this at all
[18:46] <knome> Veinor, mine works so i don't have any experience in fixing it
[18:58] <Erant> Veinor: Banshee works fine here too
[18:58] <Veinor> i get stuff like "Trying to dispose element playbin, but it is not in the NULL state.
[18:59] <Erant> I'm currently having some issues with XUbuntu as well though. In order to get a proper desktop, I have to re-set the resolution each time I boot. When I boot, I only get 1/4 of the screen :/
[19:00] <Erant> It's like 640x480, with a 1024x768 framebuffer
[19:05] <Veinor> yeah, it's doing it even after a reboot. :/
[19:08] <Veinor> hmm
[19:08] <Veinor> totem's doing it, but VLC isn't, nor is exaile
[19:08] <Veinor> er
[19:08] <Veinor> totem's glitching, VLC and exaile aren't
[19:14] <Veinor> fixed it
[19:14] <Veinor> pulseaudio wasn't starting for some reason
[19:17] <Veinor> now how do i get the multimedia keys to work again?
[19:26] <ohgodnotanother1> hi there
[19:26] <ohgodnotanother1> my brother is having trouble with his sound card on a fresh Xubuntu 8.10
[19:26] <ohgodnotanother1> where can I set the sound "manager"? OSS or ALSA?
[19:27] <ohgodnotanother1> it's a built in intel sound card btw.
[19:27] <ohgodnotanother1> the problem: no audio playback under the os
[19:36] <Voluhar> hello, my instalation of alternate xubuntu freeze up after first reboot in xfce
[20:40] <Aquina> hoi
[20:41] <Aquina> Is there a way to rename the "/home/<username>/Desktop" direcory to something like ".dektop"?
[20:41] <Aquina> It's often getting into my way...
[20:52] <David-A> Aquina: there are setting i this file that might be what you want, not tested: ~/.config/user-dirs.dirs
[21:48] <Aquina> thx, David-A ;-)
[21:49] <David-A> did it work changing XDG_DESKTOP_DIR?
[22:01] <Aquina> well I need to restart the gdm session. I'm gonna tell you later. ;-)
[22:01] <Aquina> 5 mins.
[22:02] <David-A> no worries, take your time, no need to hurry for me
[22:06] <ig0r1> Hi everybody
[22:06] <ig0r1> can anyone please tell me where is the Font dir in xubuntu???
[22:06] <knome> ig0r1, you can put fonts in ~/.fonts
[22:07] <knome> ig0r1, then fc-cache -f -v
[22:07] <ig0r1> knome: but that would be for one user only?
[22:07] <knome> ig0r1, yes.
[22:07] <knome> !fonts
[22:08] <knome> there you are.
[22:08] <David-A> ig0r1: remember, every user config for him self
[22:08] <ig0r1> Thank you very much I will read it! ))
[22:21] <Aquina> brb
[22:21] <Aquina> It didn't work. :-(
[22:22] <Aquina> I followed there instructions: http://ubuntuforums.org/archive/index.php/t-631711.html
[22:26] <David-A> Aquina: just a hunch, what if, what happens if you add a line "export XDG_DESKTOP_DIR=~/.desktop" in the file ~/.profile or ~/bash_profile (but no "quotes") (and logout/in)
[22:29] <Aquina> sec I'm loggin in and out...
[22:31] <Aquina> no, It doesn't work
[22:31] <Aquina> :-(
[22:33] <David-A> Aquina: well, i dont know then. remember to restore your ~/.profile or ~/.bash_profile and ~/.config/whatsitsnameagain
[22:35] <R1cochet> everytime i try to add an .mp3 to audio project in Brasero it freezes the program
[22:35] <R1cochet> is there anyway to fix this?
[22:43] <Aquina> thx, David-A
[22:43] <Aquina> :-/
[22:44] <David-A> :-( with u and the environment, otherwise :-)
[22:45] <Aquina> :-)
[22:45] <David-A> sorry, no comparision with u and the environment intended
[23:27] <Aquina> "with me and the environemnt" - a strange expression...
[23:27] <ubendu> Is xubuntu just a shortened-down version of ubuntu? Or is it completely different.
[23:28] <ubendu> Looking for something light to run on office computers.
[23:28] <knome> R1cochet, i don't actually know if brasero supports mp3
[23:28] <knome> ubendu, it's basically the same, but it uses xfce as window manager rather than gnome, so for the enduser it might look quite a lot different
[23:29] <ubendu> knome: So it's not 'lighter' at all really? Just different.
[23:29] <knome> ubendu, it is also lighter, yes,
[23:29] <ubendu> knome, right okay :)
[23:29] <knome> ubendu, it really depends on the machine you have whether it's usable
[23:30] <ubendu> Well, they have Windows (am I allowed to say that here?) on the server and all computers at the moment
[23:30] <ubendu> So it would be a big conversion.
[23:31] <knome> ubendu, how much ram?
[23:32] <ubendu> knome: It differs from machine to machine, but I thought the requirements for Windows XP Professional > ubuntu
[23:32] <ubendu> > x 100.
[23:33] <knome> ubendu, yes...
[23:33] <knome> ubendu, which is the lowest? are we talking about 128 or 256 or 512
[23:33] <ubendu> 256
[23:33] <ubendu> I will have to check though first.
[23:34] <knome> it should be ok, but maybe a bit slow user experience.
[23:34] <ubendu> What would be the easiest way of install ubuntu on all of those computers?
[23:34] <ubendu> We're talking 30/40.
[23:34] <ubendu> ubuntu-server will be on the server, so is there a net install feature?
[23:34] <knome> i'm not actually an expert on this.
[23:34] <knome> cody-somerville, ?
[23:35] <TheSheep> we are actually dd-ing the whole hard disk, it's about 100-150 computers
[23:35] <knome> hello TheSheep. how are you?
[23:35] <TheSheep> we have a simple linux boot disk that brings up the network, downloads and unzips the disk images and runs grub
[23:36] <TheSheep> knome: hi, all good
[23:36] <zoredache> you probably should consider setting up a apt-cache, you might want to look at pxe booting the mini.iso, you might want to look at building an answer script so you can completely automate the install
[23:36] <TheSheep> I admit we do that mainly because we also install windows that way
[23:37] <zoredache> TheSheep: how do you deal with hardware varation?
[23:38] <TheSheep> zoredache: our installs are proofed to it
[23:38] <TheSheep> zoredache: at least in the range of the computers we have to support
[23:38] <TheSheep> zoredache: I thin they use something called sysprep on windows
[23:39] <zoredache> yeah, but on linux boxes, do you do something to resize the partitions to take up all the available space?
[23:40] <TheSheep> zoredache: no, we use sfdisk to create the partitions and just leave the empty space as it on the larger disks
[23:41] <TheSheep> zoredache: the installs are prepared for the smallest disks we support
[23:41] <zoredache> ah
[23:42] <TheSheep> it's easier this way, we also have some hooks in /etc/rc.local to run scripts from nfs-mounted partition, so we can add fixes after the install
[23:42] <TheSheep> and they will be applied on next boot
[23:43] <TheSheep> for the next year we are working on instalation scripts based on torrent :)
[23:45] <Constrabus> What is the default root password to enter su for the xubuntu live CD
[23:46] <Constrabus> Im using the xubuntu live cd to install gentoo on a hard drive.
[23:46] <knome> Constrabus, you should use sudo
[23:50] <j_xinudsb> yes --sudo passwod root
[23:50] <j_xinudsb> sorry
[23:50] <j_xinudsb> sudo passwd root
[23:50] <j_xinudsb> to set it
[23:52] <j_xinudsb> or $sudo bash
[23:53] <knome> actually i referred to using sudo and not root at all.....


[09:02] <Na3iL> o/
[10:37] <theShirbiny> Na3iL, o/
[10:37] <Na3iL> HEllo theShirbiny how are you
[10:38] <theShirbiny> I'm good, you?
[10:41] <Na3iL> good as well ty
[18:11] <Na3iL> theShirbiny, there will be a meeting in #ubuntu-africa feel free to join :)


[00:02] <xnox> vorlon:  https://paste.ubuntu.com/p/6jHRmjjwZ8/
[00:03] <xnox> vorlon:  i like 541, but i don't know how far back it exists.
[00:04] <xnox> and i guess xen doesn't matter as it should just work
[00:04] <xnox> if we do that, we will need not to do the cloud-init stuff either.
[00:05] <vorlon> xnox: I want to do https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=5bb3139fbef5b43b07146d3bfc951e4a0c2ff24e
[00:05] <vorlon> the cloud-init stuff will still matter for dist-upgrades
[00:05] <vorlon> which are unlikely in the cloud, but supported
[00:08] <xnox> vorlon:  i am confused.
[00:10] <xnox> vorlon:  i thought you meant https://paste.ubuntu.com/p/jd5c8p64Pd/
[00:10] <xnox> vorlon:  why would you want to ever run grub-install of grub-pc on upgrades?
[00:11] <vorlon> xnox: I want to fix the problem that a security update is borking you.  But as I said, in the general case, we do still /want/ to have the newer grub written to disk on upgrades, but because of the abi break it's prudent to limit it to release upgrades
[00:12] <xnox> we /want/ but cannot do so.
[00:12] <xnox> you will brick everyone on dist-upgrade then.
[00:12] <vorlon> this solves the present problem and kicks the can on the question of handling the failures on release upgrade due to abi changes
[00:12] <vorlon> xnox: we've already done that in the past
[00:12] <xnox> because this SRU has changed abi for everyone.
[00:12] <chrisccoulson> if grub-install is never executed when upgrading grub-pc, is there a risk of other parts that are upgraded going out of sync (eg, grub.cfg depending on new commands)
[00:13] <vorlon> yes there is
[00:13] <vorlon> or incompatible filesystem support
[00:13] <xnox> chrisccoulson:  update-grub is still called, using the new tooling.
[00:14] <vorlon> if you have old grub, and you do something to upgrade your filesystem, and you don't get new grub, you could also be sunk
[00:14] <xnox> vorlon:  i'd still want you to make your new case to be elif where i show mine.
[00:14] <vorlon> xnox: fair
[00:14] <chrisccoulson> xnox, yeah, that's an issue isn't it - calling update-grub with the new tooling without calling grub-install (not this time around, but maybe in a future update)
[00:16] <xnox> vorlon:  https://paste.ubuntu.com/p/k2Jqt5yWyg/ or some such. Makes it a lot easier to review / update / backport.
[00:17] <xnox> vorlon:  a vendor kept on asking if we will continue to support bios.
[00:17]  * xnox ponders
[00:17] <xnox> it's unsupportable already
[00:18] <vorlon> xnox: :P
[00:19] <vorlon> xnox: https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388437
[00:19] <mwhudson> vorlon: test "$wubi_device" oh boy
[00:20] <vorlon> mwhudson: ignore ignore ignore
[00:20] <vorlon> lalalal
[00:20] <vorlon> a
[00:20] <sbeattie> haha, saw that too, and cried.
[00:21] <vorlon> mwhudson: I mean, aside from the fact that I need to fix the syntax ;)
[00:21] <vorlon> (done)
[00:21] <mwhudson> vorlon: oh i hadn't got as far as syntax yet :)
[00:21] <vorlon> mwhudson: yeah that was a mis-edit of the previous attemp
[00:21] <vorlon> t
[00:24] <mwhudson> vorlon: approvedz
[00:24] <mwhudson> vorlon: i presume you have similar changes for bionic, xenial?
[00:25] <mwhudson> and uh trusty?
[00:25] <vorlon> mwhudson: will do, with adjusted version numbers; but those are not in git I guess :/
[00:26] <mwhudson> yes i was assuming you'd remember the version numbers :)
[00:26] <mwhudson> and hm the branches start with disco it seems?
[00:26] <xnox> i am confused about "ge" still.
[00:26] <mwhudson> also bios is bad
[00:27] <vorlon> xnox: greater than or equal to the version in the release pocket
[00:27] <mwhudson> also also is there a bug for "pls to be not installing modules until after writing the mbr"
[00:28] <xnox> which means "any focal version" or "downgrade from groovy"
[00:28] <xnox> and screw downgrade people
[00:29] <vorlon> xnox: if you're downgrading, you're presumably on the other side of the ABI change
[00:29] <vorlon> at least for focal
[00:29] <xnox> this is safe in-series, ship it.
[00:29] <vorlon> ok
[00:35] <vorlon> bdmurray: around?
[00:36] <Bashing-om> vorlon: xnox: Confirmation: old AMD bios system - apt policy grub-pc >> Installed: 2.02-2ubuntu8.16
[00:36] <Bashing-om> No issues seen here.
[00:40] -queuebot:#ubuntu-release- Unapproved: grub2 (focal-proposed/main) [2.04-1ubuntu26.1 => 2.04-1ubuntu26.2] (core)
[00:49] -queuebot:#ubuntu-release- Unapproved: grub2-signed (focal-proposed/main) [1.142.3 => 1.142.4] (core)
[00:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.1] has been updated (20200730.1)
[00:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.1] has been updated (20200730.1)
[00:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.1] has been updated (20200730.1)
[00:50] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.1] has been updated (20200730.1)
[00:51] <bdmurray> vorlon: yeah
[00:53] <vorlon> bdmurray: grub2, grub2-signed in focal, I could use an SRU reviewer
[00:53] <vorlon> to keep me honest
[00:53] <bdmurray> okay
[00:53] <bdmurray> honesty is good
[00:55] <bdmurray> why does the debdiff look so weird?
[00:55] <vorlon> does it?
[00:55] <bdmurray> or the changelog specifically
[00:55] <vorlon> is it diffing against the wrong target?
[00:56] <vorlon> hmm
[00:56] <vorlon> I based this on the git branch which I assumed was up-to-date
[00:56] <vorlon> chrisccoulson: ^^
[00:56] <vorlon> bdmurray: please reject and I'll reupload
[00:56] <bdmurray> will do
[00:58] -queuebot:#ubuntu-release- Unapproved: rejected grub2-signed [source] (focal-proposed) [1.142.4]
[00:58] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (focal-proposed) [2.04-1ubuntu26.2]
[00:59] <vorlon> xnox: ^^ you synced the focal branch over?  somehow it doesn't contain the debian/2.04-1ubuntu26.1 tag and doesn't match the archive contents
[00:59] <chrisccoulson> oh, huh, I updated the changelog right before uploading the last version to add all of the CVE references, but didn't commit those to git
[00:59] <vorlon> ah
[00:59] <chrisccoulson> vorlon, the tag is missing because the 2.04-1ubuntu26.1 version was already used and tagged for a SRU that wasn't uploaded
[00:59] <vorlon> well
[01:00] <vorlon> nuke those tags from orbit
[01:00] <vorlon> :P
[01:00] <chrisccoulson> I thought I'd pushed the proper changelog (but just without the tag though)
[01:00] <mwhudson> NoMoreSourcePackages pls
[01:04] -queuebot:#ubuntu-release- Unapproved: grub2 (focal-proposed/main) [2.04-1ubuntu26.1 => 2.04-1ubuntu26.2] (core)
[01:04] <vorlon> bdmurray: ^^
[01:05] <chrisccoulson> yeah, that looks better :)
[01:11] <bdmurray> vorlon: looking
[01:18] <bdmurray> vorlon: so there will be a better upload coming and this is a stop gap?
[01:20] <vorlon> bdmurray: there will be further improvements to make grub-pc behave better on upgrades between releases
[01:24] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (focal-proposed) [2.04-1ubuntu26.2]
[01:24] <bdmurray> vorlon: where is the signed version? or should I rescue the old one
[01:25] <bdmurray> yeah that would make sense
[01:39] -queuebot:#ubuntu-release- Unapproved: grub2 (focal-proposed/main) [2.04-1ubuntu26.2 => 2.04-1ubuntu26.2] (core)
[01:48] <vorlon> bdmurray: the old grub2-signed is fine, yeah
[01:51] -queuebot:#ubuntu-release- Unapproved: grub2 (focal-proposed/main) [2.04-1ubuntu26.2 => 2.04-1ubuntu26.2] (core)
[01:51] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.16 => 2.02-2ubuntu8.17] (core)
[04:15] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.18 => 1.93.19] (core)
[04:21] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (bionic-proposed) [2.02-2ubuntu8.17]
[04:23] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.16 => 2.02-2ubuntu8.17] (core)
[04:28] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.26 => 2.02~beta2-36ubuntu3.27] (core)
[04:42] -queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.26 => 1.66.27] (core)
[04:43] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (bionic-proposed) [2.02-2ubuntu8.17]
[04:48] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.16 => 2.02-2ubuntu8.17] (core)
[04:49] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (bionic-proposed) [2.02-2ubuntu8.17]
[04:49] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (focal-proposed) [2.04-1ubuntu26.2]
[04:49] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (focal-proposed) [2.04-1ubuntu26.2]
[04:50] -queuebot:#ubuntu-release- Unapproved: rejected grub2-signed [source] (bionic-proposed) [1.93.19]
[04:51] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.18 => 1.93.19] (core)
[04:52] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (xenial-proposed) [2.02~beta2-36ubuntu3.27]
[04:53] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.26 => 2.02~beta2-36ubuntu3.27] (core)
[05:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (bionic-proposed) [1.93.19]
[05:02] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.17 => 2.02-2ubuntu8.17] (core)
[05:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (xenial-proposed) [2.02~beta2-36ubuntu3.27]
[05:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (xenial-proposed) [1.66.27]
[05:05] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.17]
[05:08] <vorlon> mwhudson: still around at all?
[05:21] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.27 => 2.02~beta2-36ubuntu3.27] (core)
[05:29] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.27 => 2.02~beta2-36ubuntu3.27] (core)
[05:45] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.17 => 2.02-2ubuntu8.17] (core)
[05:45] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-5.6 [amd64] (focal-proposed) [5.6.0-1021.21]
[06:18] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.17]
[06:21] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (xenial-proposed) [2.02~beta2-36ubuntu3.27]
[06:21] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (xenial-proposed) [2.02~beta2-36ubuntu3.27]
[07:31] -queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (focal-proposed) [3.36.4-0ubuntu<IP_ADDRESS>]
[08:56] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu543.16]
[09:24] <LocutusOfBorg> can anybody please accept s390-tools from unapproved? needed for json-c transition
[09:27] <LocutusOfBorg> also, please kick ntopng out from release pocket? its bd uninstallable due to ndpi
[09:27] <LocutusOfBorg> out from debian testing
[09:43] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-440-server [i386] (bionic-proposed) [440.95.01-0ubuntu<IP_ADDRESS>]
[11:01] -queuebot:#ubuntu-release- New: accepted haskell-hgettext [amd64] (groovy-proposed) [<IP_ADDRESS>-7]
[11:02] -queuebot:#ubuntu-release- New: accepted haskell-hgettext [armhf] (groovy-proposed) [<IP_ADDRESS>-7]
[11:02] -queuebot:#ubuntu-release- New: accepted haskell-hgettext [riscv64] (groovy-proposed) [<IP_ADDRESS>-7]
[11:02] -queuebot:#ubuntu-release- New: accepted haskell-hgettext [arm64] (groovy-proposed) [<IP_ADDRESS>-7]
[11:02] -queuebot:#ubuntu-release- New: accepted haskell-hgettext [s390x] (groovy-proposed) [<IP_ADDRESS>-7]
[11:02] -queuebot:#ubuntu-release- New: accepted haskell-hgettext [ppc64el] (groovy-proposed) [<IP_ADDRESS>-7]
[11:20] <LocutusOfBorg> vorlon, with ntopng kicked out from release (we should keep it in proposed, so it builds once ndpi is fixed in debian and syncs), and the s390-tools accept from unapproved, json-c should be fine to go
[11:37] <xnox> mwhudson:  sil2100: new subiquity image regressed on s390x https://bugs.launchpad.net/subiquity/+bug/1889749
[11:43] <xnox> Laney:  https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html is out of date, last generate yesterday?
[11:43] <xnox> sil2100:  grub2-signed & grub2 are ready for release to updates in xenial, bionic, focal
[11:48] -queuebot:#ubuntu-release- New source: agda-stdlib (groovy-proposed/primary) [1.3-1~build1]
[11:56] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.16 => 20101020ubuntu543.17] (core)
[11:58] <xnox> sil2100: bdmurray: vorlon: fix for FTBFS of s390x d-i in bionic uploaded ^
[12:46] <Odd_Bloke> xnox: vorlon: I saw mention of potentially not needing the cloud-init fix; should I continue working on it, or do we categorically no longer need it?
[12:51] <xnox> Odd_Bloke: we absolutely need it now.
[12:51] <xnox> Odd_Bloke: grub is only a cludge, and will delay breaking machines until after release upgrade.
[12:52] <xnox> Odd_Bloke: cloud init fix can unbreak some clouds to correctly upgrade to new grub.
[12:52] <xnox> and not fail release upgrade.
[12:52] -queuebot:#ubuntu-release- Unapproved: accepted bcache-tools [source] (focal-proposed) [1.0.8-3ubuntu0.1]
[12:53] <xnox> Odd_Bloke: however the grub cludge makes cloud-init fix not time sensitive, as much.
[12:54] <xnox> We are choosing to skip grub-install for security update, but will call it on release upgrade.
[12:56] <Odd_Bloke> xnox: Thanks!
[12:57] -queuebot:#ubuntu-release- Unapproved: accepted smokeping [source] (focal-proposed) [2.7.3-2ubuntu20.04.1]
[12:57] <Odd_Bloke> xnox: My next Q: does that affect whether or not we need to release a cloud-init fix to -security?
[12:58] <xnox> Odd_Bloke: we are choosing to not call grub-install in -security, thus cloud-init can simply go to -updates.
[12:59] <xnox> (note this is all about grub-pc, the efi signed stuff is upgraded, as that's the point of this security update)
[12:59] -queuebot:#ubuntu-release- Unapproved: accepted network-manager-applet [source] (focal-proposed) [1.8.24-1ubuntu3]
[12:59] <sbeattie> xnox: FYI, there will at least need to be a respin of grub2 before it can go into security, as the ones in proposed were built with -updates enabled, and so at least a no-change rebuild will be needed for -security.
[13:00] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (focal-proposed) [2.20.11-0ubuntu27.5]
[13:02] <Odd_Bloke> xnox: "we are choosing to not call grub-install in -security" <-- as a rule going forward, or just for this grub upload?  If the latter, then folks running -security will run into this next time around (or on release upgrade?), no?
[13:02] <xnox> vor
[13:02] <xnox> vorlon: why did you direct upload instead of copy?! :-)
[13:03] <xnox> sbeattie: let me prepare that then.
[13:03] <xnox> Odd_Bloke: until we fix grub-install to at least rollback and not fail to install core; yet update to incompatible modules in /boot.
[13:03] <xnox> Od
[13:03] <xnox> Odd_Bloke: as we break machines, intentionally, and know it, and carry on.
[13:08] <Odd_Bloke> xnox: -security-only users who would be fixed by the cloud-init upload still wouldn't get new grubs because their install_devices will still be incorrect.  Or will upgrades of grub fail in a way that's very obvious (and should therefore prompt users to fix install_devices themselves)?
[13:12] <xnox> Odd_Bloke:  once cloud-init fix is out, we can order to have new cloud-init configured first on release-upgrades.
[13:12] <xnox> Odd_Bloke: or, when we fix up grub-install => things will fail, but ensure that system remains bootable & rebootable.
[13:13] <xnox> Odd_Bloke:  when we have better/proper grub-install we will push it to security too, i think.
[13:25] <Odd_Bloke> xnox: Right, it sounds like we will ensure the system remains bootable & rebootable, but with the cloud-init fix we could do better for some systems (in that they would both remain (re)bootable, but also get new grub updates).
[13:26] <Odd_Bloke> (I'm not asserting that the cloud-init fix must go to -security, just making sure I understand what, if any, gap we'll be leaving if it doesn't.)
[13:29] <xnox> yeap yeap yeap
[13:29] <ahasenack> hello ubuntu-archive, are you fine with also promoting adcli and realmd to main in focal? Their MIRs were approved (and done) for groovy. The versions in focal are identical. https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/ubuntu-seeds/+merge/388428
[13:30] <ahasenack> maybe now just before the 20.04.1 is not the best time (or is it?)
[14:07] <paride> xnox, so new trip to candidate for subiquity?
[14:09] <xnox> paride: yeah, pushing buttons to make a new edge build.
[14:09] <xnox> once jfh tests it from edge, will promote it to release.
[14:09] <xnox> paride:  i guess we can trigger edge jenkins jobs too, once i publish it to edge?
[14:10] <paride> xnox, yes you can trigger the -smoke-edge jobs
[14:14] <paride> but  it just tests the default install case
[14:15] <xnox> it's ok.
[14:15] <xnox> they are currently building.
[14:17] <ahasenack> ubuntu-archive, hi, can you please remove sssd from groovy-proposed that I just synced? I wanted to sync ldb and samba first, and sssd later
[14:17] <ahasenack> or is it too late
[14:20] <ahasenack> it's still building for all but s390x: https://launchpad.net/ubuntu/+source/sssd/2.3.1-1
[14:21]  * ahasenack tries cancelling the other builds
[14:33] <paride> sil2100, do you think we can add a 18.04.5 milestone to the ISO tracker?
[14:33] <paride> or is it still too early?
[14:34] <paride> the 20200731.1 bionic images look good
[14:43] <paride> well we probably want the new subiquity there too, even if there's no s390x
[14:43] <paride> but the d-i images should be fine
[14:44] <sil2100> paride: I think it's too early, wanted to add it once we start building candidates
[14:45] <paride> ack
[14:48] <bdmurray> sil2100: I have a "dumb" fix for bug 1889449 but I'm also working on a better one. Do you have a timeline in mind that I should be done by?
[15:10] <xnox> paride: new subiquity in edge, please kick edge jobs off.
[15:16] <paride> xnox, done already, all passed on bionic amd64 and focal amd64 ppc64el s390x
[15:18] <paride> I checked the snap build id to make sure the jobs ran using the edge snap
[15:22] <sil2100> paride: thanks for the testing!
[15:22] <sil2100> bdmurray: I guess the deadline would be next week when we release .1 and enable upgrades, but I guess the earlier the better
[15:22] <sil2100> Let me take a look at what you proposed
[15:25] <sil2100> bdmurray: I don't know the mechanics of the blacklist_removal.cfg - that only affects release upgrades?
[15:27] <bdmurray> sil2100: here's my dumb fix https://pastebin.ubuntu.com/p/sskcZsQ2Kp/
[15:28] <bdmurray> sil2100: yes, removal_blacklist.cfg is a part of the dist-upgrader tarball and is only used during the dist upgrade process
[15:28] <bdmurray> and here's the better fix https://pastebin.ubuntu.com/p/GxF2QHhrJT/
[15:28] <bdmurray> It didn't do what I wanted yesterday but I was missing the third change there
[15:29] <bdmurray> I'm gonna test the better fix shortly
[15:33] <xnox> paride: thinking to release to stable. But did not hear from Frank yet
[15:34] <xnox> ok jfh says it's good
[15:36] <xnox> sil2100:  new subiquity published with regression fix, so live-server could be respun.
[15:36] <xnox> (or well, ready to respin, whenever you want)
[15:38] <paride> sil2100, if you do, I
[15:38] <paride> sil2100, if you do, let me know and I'll submit results before EOD
[15:42] <paride> xnox, can we tell which subiquity went into an image from the image build logs?
[15:45] <sil2100> Yay, I'll have to respin everything now!
[15:45] <sil2100> People will be really happy
[15:49] <sil2100> bdmurray: hm, the 'better' fix looks okay from the look of it, though I still wonder why is the new metapackage marked for autoremoval anyway
[15:55] <xnox> paride:  yes, if you click on the livefs build, and then click on build log of that, one can see subiquity revision in the log.
[15:56] <xnox> paride:  we really should fix the manifests to include subiquity revision id in the manifest.
[16:06] <Odd_Bloke> rcj: xnox: vorlon: One thing I don't think I've fully understood: is the intent to never grub-install on upgrade of grub-pc systems again, or is that a stopgap while we implement reliable grub-install on such systems?
[16:09] <xnox> Odd_Bloke:  it's a stop gap.
[16:10] <xnox> Odd_Bloke:  intent is to call grub-install, and rollback when it is unsuccessful.
[16:13] <Odd_Bloke> xnox: OK, cool, thanks!
[16:18] <vorlon> xnox, Odd_Bloke: I disagree, actually.  The fact that we can never reliably know on BIOS systems that the disk we've installed the bootloader to is the actual boot disk means the ABI break is always a foot-gun, and I think we should avoid applying this to users' systems from grub-pc for the lifetime of these releases and only deal with it during release upgrades
[16:19] <vorlon> the other changes to make grub-install more resilient are still relevant, but I don't think it's an either-or
[16:24] <Odd_Bloke> vorlon: "always a foot-gun" because we could "successfully" install to /boot and /dev/sda and then the system boots from /dev/sdb and hits the incompatibility anyway, you mean?
[16:24] <vorlon> Odd_Bloke: exactly
[16:36] <xnox> Odd_Bloke:  there is no protocol to tell us off what we booted, and where things should be.
[16:36] <xnox> Odd_Bloke:  another example is degraded raid, yes installing on sda sdb sdc is correct, and yes sdc is missing, and sdb has incompatible core, and yes all of them should be updated. etc.
[16:38] <sbeattie> vorlon: that means never being able to SRU a bugfix for bios users again in these releases.
[16:39] <sbeattie> (which may be an okay tradeoff)
[16:39] <xnox> sbeattie:  most of our bugfixes are around generating grub.cfg though.
[16:42] <sbeattie> okay. just want to make sure the implications are understood.
[16:46] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:52] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:53] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:53] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:53] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Focal 20.04.1] has been updated (20200731)
[16:53] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Focal 20.04.1] has been updated (20200731)
[16:57] <Odd_Bloke> If we did hit a circumstance where we did need to SRU a bugfix for bios users that did require a `grub-install` then we could presumably handle "undisabling" it at that time too?
[16:58] <Odd_Bloke> (Feasibly such a bugfix might only apply to a subset of bios systems, so we could conditionally `grub-install` or whatever; we will know better once confronted with such an issue.)
[16:58] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:59] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.1] has been updated (20200731)
[16:59] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.1] has been updated (20200731)
[17:07] <Odd_Bloke> vorlon: So should I drop https://github.com/canonical/cloud-init/pull/514/files#diff-0a6a3bac6b74050d52c36391345e3838R316 from the cloud-init postinst I'm working on?
[17:07] <gitbot> canonical issue (Pull request) 514 in cloud-init "debian/cloud-init.postinst: fix NVMe grub install device on upgrade" [Open]
[17:09] <Odd_Bloke> Or should I still call `grub-install` because it will be a noop when appropriate?
[17:11] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Focal 20.04.1] has been updated (20200731)
[17:11] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Focal 20.04.1] has been updated (20200731)
[17:11] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Focal 20.04.1] has been updated (20200731)
[17:11] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Focal 20.04.1] has been updated (20200731)
[17:11] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Focal 20.04.1] has been updated (20200731)
[17:19] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Focal 20.04.1] has been updated (20200731)
[17:19] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Focal 20.04.1] has been updated (20200731)
[17:21] -queuebot:#ubuntu-release- New binary: pygame-sdl2 [amd64] (groovy-proposed/universe) [7.3.5-1] (no packageset)
[17:23] <sil2100> vorlon: hey! So there's that very old shim-signed in bionic-proposed, which is being pulled in by ubiquity when I try to update the sources
[17:24] -queuebot:#ubuntu-release- New binary: pygame-sdl2 [s390x] (groovy-proposed/universe) [7.3.5-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: pygame-sdl2 [ppc64el] (groovy-proposed/universe) [7.3.5-1] (no packageset)
[17:30] <vorlon> sil2100: that one is effectively verification-failed; there is a fix in the unapproved queue. are you ok with me accepting the new one, or should I just delete the old one?
[17:33] <vorlon> Odd_Bloke: how sure can you be that grub-install is called for the right target?
[17:39] <vorlon> sbeattie: yeah, I understood that implication; we could revisit the question if it came up that we did need an SRU to fix the grub-pc binary bits, but aside from a couple of long-past xenial SRUs, we don't have a history of doing this
[17:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.1] has been updated (20200731)
[17:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.1] has been updated (20200731)
[17:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.1] has been updated (20200731)
[17:39] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.1] has been updated (20200731)
[17:48] <xnox> vorlon:  even if sure of target, it may not be successful as we see in the other cloud.
[17:50] <Odd_Bloke> vorlon: This is basically running the "determine the correct install_device" logic that cloud-init runs at first boot, only on systems with an NVMe disk (to target AWS Nitro instances), and only if the current value is /dev/sda (cloud-init's previous default).
[17:50] -queuebot:#ubuntu-release- New binary: pygame-sdl2 [armhf] (groovy-proposed/universe) [7.3.5-1] (no packageset)
[17:50] -queuebot:#ubuntu-release- New binary: pygame-sdl2 [arm64] (groovy-proposed/universe) [7.3.5-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: pygame-sdl2 [riscv64] (groovy-proposed/universe) [7.3.5-1] (no packageset)
[18:01] <sforshee> vorlon: could you approve the linux signing tarballs for groovy? Not sure if there's anyone else still around today who is willing to touch those
[18:04] <Odd_Bloke> vorlon: Honestly, I am wondering if we need to do anything in cloud-init for existing instances, if we never plan to rely on what they have set in grub-pc/install_devices.
[18:09] <xnox> Odd_Bloke:  wait "never plan to rely on what they have set in grub-pc/install_devices" is not true. we absolutely rely on that to be correct during do-release-upgrade and will attempt installing grub-pc into the devices listed there.
[18:09] <xnox> Odd_Bloke:  so we do want those corrected for nitro instances.
[18:10] <xnox> Odd_Bloke:  but you may choose to skip calling grub-install on them, when correcting that.
[18:12] <Odd_Bloke> xnox: And we shouldn't/won't just be prompting people to select the correct install device at do-release-upgrade time?
[18:15] <Odd_Bloke> I guess where I'm at is: either we trust this determination (and therefore can grub-install immediately) or we don't (and therefore shouldn't use it for do-release-upgrade either).
[18:15] <Odd_Bloke> And the correct value could have changed by the time a `do-release-upgrade` occurs.
[18:17] <Odd_Bloke> So if we won't need it until then, it seems to me that it would make most sense to wait until then to determine it.
[18:24] <xnox> Odd_Bloke:  we know that sda on nitro nvme instances is wrong, that must be corrected.
[18:24] <xnox> Odd_Bloke:  such that user is not asked about it.
[18:33] <paride> sil2100, submitted all the results for focal server 20200731
[18:46] <Odd_Bloke> xnox: vorlon: I'm a couple of hours away from EOW, and I'm out on Monday: can the cloud-init change wait until mid-next-week, or should I be looking to hand it off to someone to keep pushing it on Monday?  (My feeling currently is that it can wait, given the grub change making its way out.)
[18:55] <vorlon> Odd_Bloke: I believe the grub change that's been uploaded is a complete mitigation for the problems we've seen
[18:56] <vorlon> sforshee: I don't see any linux signing tarballs pending for groovy?
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (groovy-proposed) [1.4.5-1]
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (groovy-proposed) [1.4.5-1]
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (groovy-proposed) [1.4.5-1]
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (groovy-proposed) [2.12.0-0ubuntu6]
[19:07] <sforshee> vorlon: someone else must have approved them
[19:10] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (groovy-proposed/main) [5.8.0-12.13] (core, kernel)
[19:56] <vorlon> sforshee: well I don't see any mentioned by the bot in the past day either
[20:02] <sforshee> huh, that's odd
[20:38]  * cjwatson wonders if Foundations are ever planning to send any of this grub maintainer script hackery to Debian so that it can at least be discussed more widely
[20:39] <cjwatson> or just carry on diverging ever further in Ubuntu
[20:40] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (groovy-proposed/main) [5.8.0-12.13] (core, kernel)
[20:50] <bryyce> there are 4 php-horde packages needing blacklisted, could an ubuntu-archive admin merge https://bazaar.launchpad.net/~bryce/+junk/sync-blacklist-php-horde/revision/772 for me?
[20:51] <bryyce> (LP: #1880776)
[21:17] -queuebot:#ubuntu-release- Unapproved: qemu (bionic-proposed/main) [1:2.11+dfsg-1ubuntu7.29 => 1:2.11+dfsg-1ubuntu7.30] (ubuntu-server, virt)
[21:48] <vorlon> cjwatson: that would be... ideal, yes
[21:51] <vorlon> bryyce: I was unclear on the rationale for why we blacklisted php-horde again given that the packages that were coming from Debian are maintained again.  Is this really intended to be a permanent blacklist? cpaelzer's comment suggests it might not be
[21:52] <vorlon> bryyce: anyway, merged in keeping with the existing ones
[22:08] <vorlon> why is retry-autopkgtest-regressions trying (and failing) to parse yaml related to a snap-triggered test?
[22:08] <vorlon> (when run with -s bionic)
[22:08] <bryyce> vorlon, thanks for merging it, sorry about the lack of clarity, yes it was intended to be a permanent block
[22:08] <vorlon> bryyce: what's the rationale of making it permanent, if it's maintained again in Debian?
[22:12] <bryyce> vorlon, rationale is that it has a small userbase (per Josh's review), and it is comprised of a very large number of packages with widely varying upstream maintenance support, which has resulted in lots of effort required on our end to resolve migration conflicts
[22:13] <vorlon> bryyce: ok
[22:13] <vorlon> thanks :)
[22:14] <bryyce> the rationale's also documented on the bug report for posterity
[22:23] <vorlon> rbalint_: the recent changes from lp:~rbalint/ubuntu-archive-tools/retry-intermittent appear to cause retry-autopkgtest-regressions to fail when there are snap-triggered autopkgtests running
[23:19] -queuebot:#ubuntu-release- New binary: gvm-libs [s390x] (groovy-proposed/universe) [11.0.1-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: gvm-libs [arm64] (groovy-proposed/universe) [11.0.1-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: gvm-libs [ppc64el] (groovy-proposed/universe) [11.0.1-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: gvm-libs [armhf] (groovy-proposed/universe) [11.0.1-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: gvm-libs [riscv64] (groovy-proposed/universe) [11.0.1-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: gvm-libs [amd64] (groovy-proposed/universe) [11.0.1-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: ospd [amd64] (groovy-proposed/universe) [2.0.1-1] (no packageset)


[05:52] <kubotu> ::runtime-bugs:: [1320427] package kde-runtime-data 4:4.13.0-0ubuntu1 failed to install/upgrade: cannot copy extracte... @ https://bugs.launchpad.net/bugs/1320427 (by Christian Miller)
[09:24] <Riddell> "Felix Geyer (debfx) renewed their own membership in the Kubuntu Members" yay debfx still loves us
[09:30] <Riddell> vHanda: do we want the nepomuk bits of kget?  since we're not really using nepomuk any more
[09:41] <yofel> well, we removed them for trusty
[09:42] <yofel> scarlett just added it back because it's in debian
[09:48] <lordievader> Good morning.
[10:10] <kdeuser56> why are the neon isos 32 bit? can I grab a x86_64 too?
[10:50] <BluesKaj> 'Morning folks
[11:10] <soee_> good mornign BluesKaj
[11:10] <BluesKaj> Hi soee_