[00:13] when I plug an usb stick, it mounts itself. When I click on unmount in gui, it umounts. If then I try to remount it again via shell, it says cannot open /dev/sdb: No medium found [00:14] is the umount via gui such a powerful umount that not even root can detect it anymore? [00:14] if I were the kernel I'd scared by that button [00:19] you using 19.10? [00:20] opgog: no, 18.04 [00:21] if I umount it with sudo umount, I can remount it again. Using the gui, I have to unplug and replug the usb stick [00:23] hmmmmm not sure what's happening there. [00:23] =\ [00:24] it's ubuntuing, that's it [00:27] giaco: that button is "eject", not umount [00:28] I know the tooltip for it says "Unmount", but that's wrong [00:28] jesus. that's right. [00:28] I hope this bug is not present on jet fighters [00:33] giaco: it's even worse than you think :) https://www.itwire.com/business-technology/new-f-35-fighter-jet-will-fly-by-firewire.html [00:34] sarnold: wow! Why not using dbus? [00:52] Hello, I changed owner and group of /etc/passwd, /etc/shadow, and the passwd program [00:53] logging in is no problem, but when I try to change my password I get a "Authentication token manipulation error" [00:53] can someone tell me, what I forgot the change? [01:05] DarkTrick, chown'ing password lost the setuid bit; you can turn it back on with "sudo chmod u+s /usr/bin/passwd", but I can't guarantee something else won't break with such a crazy scheme [01:08] rfm, sorry, forgot to mention [01:08] the setuid bit is set [01:09] is there any other file, that is getting touched during the password-changing process? [01:13] DarkTrick: why are you doing any of this? [01:15] leftyfb, I thought it's a good idea to give a process only as many rights, as it needs. A password change does not require the god-power for the whole system in my opinion [01:17] DarkTrick: you may prefer this instead https://www.openwall.com/tcb/ [01:17] I haven't got a clue if it needs updating or anything [01:18] but it's surely a better idea than just flipping bits :) [01:21] sarnold, I check it out [01:28] i formatted an external hd as ext4 no journal to use for music/movies, and the filesystem reserved 100GB [01:28] DarkTrick, I suspect passwd does the trick of writing out under a temporary name and then renaming, to make the change safe and atomic. Which means you'd have to give passwd write access to /etc, which is pretty much complete control of the system [01:28] is it ok to lower the amount of reserved space? or do i need that much for defrag? [01:29] p0wder: that's not what the reserved space is used for. [01:29] p0wder: it's reserved for the root user. set it to 0 if you don't feel you need to do that. [01:31] really? yeah- i dont need it for root user [01:31] i just want to be able to backup stuff, and maybe use it for timeshift backups [01:34] man tune2fs: [01:34] Reserving some number of filesystem blocks for use by privileged processes is done to avoid filesystem fragmentation [01:34] ryuo: reserved disk space while partitioning has nothing to do with the root user [01:35] It's so you can still recover your filesystem if it runs out of disk space [01:35] leftyfb: ... the -m argument of mkfs.ext4 disagrees. [01:35] from the manpage [01:35] Specify the percentage of the filesystem blocks reserved for the super-user. This avoids fragmentation, and allows root-owned daemons, such [01:35] as syslogd(8), to continue to function correctly after non-privileged processes are prevented from writing to the filesystem. The default [01:36] percentage is 5%. [01:36] super-user, AKA root [01:36] i made it like this- mkfs.ext4 -O ^has_journal /dev/sdb1 [01:36] how does this have nothing to do with the root user? [01:37] hi, any advice on what the command is to enable sddm from systemctl? I needed to revert back from "systemctl disable sddm" however the reverse (enable) won't apply (gives errors). [01:37] so basically i do need some for fragmentation purposes? [01:37] ryuo: It means, only the root user and it's processes have access to that reserved space so they can be used to recover from running out of disk space. [01:38] joules: pastebin those errors [01:38] leftyfb: yes. i know. you're saying it has nothing to do with the root user. i was telling p0wder that it's safe to disable it for their use case. [01:39] since it's not a system drive. [01:39] or partition even [01:39] yeah i thought 100gb was too much for non os drive [01:40] I'm trying to re-enable sddm but not sure what the command process is for it. https://paste.ubuntu.com/p/tQ7pJCTgrJ/ [01:40] but then i also thought if i do timeshift backups, creating and deleting over time will fragment a little [01:41] storing my music/movies should be fine w/o it tho [01:44] oh well, not sure why systemctl will allow a "disable" but not "enable", seems like someone forgot setting up proper units for that. I'll just --reinstall [01:45] Hi. I have a video file that I captured from a VHS tape. However, the audio and the video are out of sync by a second or so. What tool could I use to correct that? [01:45] I tried kdenlive, but it's nighmarish to use [01:46] rfm, hm... sounds reasonable to me... setting rights for /etc does not [01:46] rfm, thank you [01:47] woenx: kdenlive is great? Guess recommending ffmpeg commands is out of the question then. Also might just be a case of incorrect fps, depends on how it was converted. [01:47] no idea, realy [01:47] I tried kdenlive, since it is what I have installed [01:47] you might have to demux the streams. [01:47] but moving the video track separately from the audio track, seemed to move the other one at a random place [01:47] it is very confusing [01:47] i will try openshot now [01:47] woenx: try #ubuntu-offtopic for non-support questions [01:47] ok [01:52] ohhh, openshot is so much better! [01:59] damn still -q in #systemd from 5 years ago, [02:00] anyhow looking in the deb, lot of setup fudgery could be just a case of missing hook scripts for "systemd enable sddm" [02:06] joules: http://paste.ubuntu.com/p/NyR6z8k6Ff/ [02:07] how does that help? [02:08] joules: I think this means you need to put the path to sddm in /etc/X11/default-display-manager [02:08] I wonder if there's a better way of doing this. hm. [02:08] it feels like there has to be.. [02:09] yeh i figured that, but don't support "systemctl enable sddm" if the opposite doesn't apply. [02:09] I shouldn't have to open up the .deb like I have time to care about the internals of everything. [02:09] joules: try sudo dpkg --reconfigure sddm [02:09] sugh [02:09] yep did all that. [02:09] joules: try sudo dpkg-reconfigure sddm [02:10] you either go full systemd or not XD [02:11] this is 18.04 so it's entirely possible ubuntu has.. [02:11] definitely 18.04 is all systemd all the time [02:11] systemd 4 LyFe [02:12] * kaleido chuckles [02:12] yeah well installed a new GPU, was loading wrong xorg.conf booted into recovery to disable sddm..that worked. nothings changed on linux, still time wasting for the end user. [02:13] joules: how about this? ls -ld /etc/systemd/system/display-manager.service [02:14] I'm not doing that [02:14] mine points to my display manager's service file: [02:14] lrwxrwxrwx 1 root root 31 Jan 24 04:25 display-manager.service -> /lib/systemd/system/xdm.service [02:14] which is why the service file doesn't have an [Install] section [02:14] rather than fudge around I'll just type "apt install sddm --reinstall" and forget it. [02:15] hah, if that works that'll be way faster than figuring out which order ln -s takes its arguments :) [02:15] I have to read the --help output every. single. time. [02:15] been using linux since 98, I'm busy, when noobs ask what distro to recommend I just tell them what I use and what distros to avoid if they don't want their time and life drained. [02:16] I already opened up the .deb to see how it configures it. [02:16] Because I'm curious [02:19] Can't believe we are still using X === zbenjamin is now known as Guest16309 === zbenjamin_ is now known as zbenjamin === kostkon_ is now known as kostkon [02:31] ok "rm" the display-manager.service with "systemcl disable sddm"? SMH [02:38] ok so, "systemctl mask sddm" is a better alternative however.."This is a stronger version of disable, since it prohibits all kinds of activation of the unit," - however "disable" is behaving far stronger than even mask. Just bad package management here for at least sddm. [02:40] all the display managers should work identically -- the /etc/systemd/system/display-manager.service symlink should control which display manager is started [02:42] "systemctl disable" shouldn't behave this way IMO if the reverse requires a dpkg-reconfigure, I mean you can ask in #systemd as see what they say. [02:44] there are examples of services in /etc/systemd/system that symlink to /dev/null, not sure why removing "display-manager.service" is the best approach. [02:46] I haven't got a clue what you're trying to do any more but you can certainly symlink your services to /dev/null if you want to prevent systemctl from ever doing anything with them.. [02:47] i'm not the package manager for sddm or any X display manager services. [02:48] blkmgr.service -> /opt/psyrium/blockmanager/bin/blkmgr.service <- that's my own custom service. Runs fine, what are the chances me working on this broken aspect of x display manager configuration with ubuntu/debian getting anywhere upstream? [02:50] nah just going to use "mask/unmask" instead if this issue arises, looks like when I search this issue, everyone else is clueless. [02:53] all the way to #debian perhaps. [02:53] joules: but the thing is, none of us even know what the issue *is* :) [02:54] joules: your service is easier, because there's presumably only one of them [02:54] I explained it. Well, I'm done then LOL [02:54] joules: but there's dozens of display managers, and you *really* only want one of them enabled at once [02:54] I'm sure I could do better. Just pro-claiming that ;) [02:55] joules: that's why the systemd unit files for display managers have this added complexity of not having an [Install] section and instead symlink them as desired [02:55] but the inner sanctum of debian is a cult I'm not a member of. [02:56] this isn't specific to debian -- note that fedora's unit files are the same way, eg https://www.systutorials.com/241506/how-to-change-the-display-manager-on-fedora-linux/ [02:57] yeah and that's why linux market on the desktop is tiny. [02:59] Like I said I don't recommend linux to any unless they want to tinker on the command line and learn unix/linux commands and master the OS, learn to code etc. [03:00] also not going to run a copy of fedora to see or not if they use the same service unitse etc. [03:02] here's what I did, moved the GPU to another pci slot. booted, couldn't even get a console so had to disable the display script and redo xorg.conf manually. Expect a low percentage of new users to bother with that. [03:04] how do i get to grub when booting up in 18.04lts? It seems to just boot and I never see a grub menu [03:04] gregf: need to install grub on the boot device. [03:04] need to be able to add myself to the sudo group again accidentally got removed [03:04] joules grub is installed its just going by so quickly i think on this vm i don't haev time to access it [03:04] i'm in xen [03:05] really should be a longer timeout by default [03:05] gregf: iirc hold down left shift [03:05] gregf: just append yourself to the group again (man usermod) [03:06] joules i know how to do that but i hae to be root first so i need to get into resuce mode if you don't know what your talking about please just don't speak [03:06] sarnoldty [03:06] gregf: fine [03:07] gregf: I believe these are the bits I've used in my /etc/default/grub to force the menu to show for five seconds [03:07] GRUB_TIMEOUT=5 [03:07] GRUB_RECORDFAIL_TIMEOUT=5 [03:08] I haven't used xen in ages, I can't recall if "left shift" even makes sense there.. [03:08] yep just didn't realize how low the defaults were till this problem started [03:08] i guess I just learned the hard way why i should always be testing my ansible playbooks [03:08] that's usually the way it goes :( you only realize it when you're in trouble.. [03:08] maybe spam the arrow keys on boot. [03:08] gregf: can you mount the filesystem via another instance? or the .. dom0? [03:09] my backup plan is to try to mount them with xm tool and fix the groups that way but i was thinking it would be a lot easier to just boot rescue mode from grub [03:09] i might be wrong about that though :) [03:10] hehe [03:34] Alright, wish me luck again for the umpteenth time reinstalling Ubuntu. [03:34] good luck have fun :) [03:34] I could never get our office printer to work with Ubuntu anymore. New hire took a Windows machine, and got the printer working instantly after a driver install [03:35] I give up on that. [03:35] So, yeah, thanks for the good luck [03:37] Greetings folks I am staring at a purple screen of death [03:37] Just installed Ubuntu... Whatever the latest one is [03:38] And I cannot get to a [03:38] Graphical login screen [03:38] I can control alt f2 to a text mode login [03:38] And in fact I updated all my packages with apt and rebooted. Still nothing [03:39] Are you using an nvidia card? [03:39] Nope, ATI [03:39] I mean AMD. Sorry, I'm old [03:39] I'm using a 5700 XT [03:39] ah [03:40] not sure drivers for that card are in the ubuntu kernel [03:40] which version of ubuntu? [03:40] Whatever the latest one is. 1910 I think [03:40] Oh, a quick question before I actually start reinstalling Ubuntu... [03:41] You know how we would create a live Ubuntu USB drive via the Ubuntu installation ISO, right? [03:41] AlexMax lsb_release -a will tell you what version [03:41] The funny part is that I was able to use it off the USB drive just fine [03:41] Now, lately, the minimum capacity of the cheapest USB you can buy is 16GB [03:41] 8GB is long gone from retail store shelves [03:42] hm that driver should be in the kernel then [03:42] I wanted to know, can you use the live USB as a storage media, like file transferring from Windows to Windows, etc.? [03:42] Yep, 19.10 [03:42] I don't wanted to waste 13.3GB of free space on the 16GB USB, when it's all just Ubuntu ISO [03:43] And again, when I ran it off the USB drive I had graphics just fine. [03:43] Though I don't know if they were hardware-accelerated or if it was defaulted to some VESA thing [03:44] So where do I even begin. It has been eons since I've had trouble with graphics in Linux. [03:44] This card in particular seems to be giving people a lot of trouble [03:44] since it's latest gen [03:44] !info linux-image-generic eoan [03:45] linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 5.3.0.26.30 (eoan), package size 2 kB, installed size 16 kB [03:45] https://www.reddit.com/r/linux/comments/dyoalh/ubuntu_1910_rx_5700_xt_installation_instructions/ [03:45] https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-19.10-Radeon-RX-5700 [03:46] the phoronix article has a set of commands you can run to enable additional firmware support [03:46] give those a try [03:50] So... may I ask if I can use a 16GB Ubuntu live USB as a simple storage USB device? [03:51] I have 13.3GB of free space, and it would be a waste to not use the free space for backing up data and stuffs. [03:51] You should be able to create a partition in the free space without affecting the ubuntu live portion [03:51] I would use gnome disks [03:53] Can I repartition the live usb? Currently, the live USB takes up all of the USB drive's capacity [03:54] scubasteve: [03:54] Thanks for the tip, but yeesh, kind of stinks that I have to do this [03:54] Agreed, should be fixed in 20.04 [03:55] already fixed in any rolling distro [03:56] also, gotta be honest, copying the output of some git clone into an operating-system directory like `/lib/` gives me lemon booty [03:56] haha I agree completely [03:56] at least it's directly from the kernel and not some random guy [03:58] yeah I might try a rolling release distro instead. Gonna have to figure out how to get rid of Ubuntu's EFI entry and stuff, that'll be fun [03:58] back in my day, we replaced our master boot record both ways in the snow, and we were THANKFUL [03:58] very easy, just remove the directory off the esp, and use efibootmgr to remove the boot option [03:59] Since the currently known answer is to repartition the live USB, which I am unfamiliar with the steps to do so, I'm just going to create a new directory in the Live USB's root directory, and store my data on that 1 partition. [03:59] THen reinstall Ubuntu [03:59] And then grab my data from the live USB [04:00] It's just a directory. What harm would it do, right? [04:01] oh......... UBuntu live USB partition is a read-only partition... [04:03] darn, repartitioning is the way to go... [04:03] yes, this way it also works on write-once media, and prevents unintended modifications. i'm not sure whether you can safely change the partition size, maybe using gparted when you booted off something else. [04:03] using flash storage for backup is maybe not the best way to go about backup, though [04:08] AlexMax: lol [04:11] Anyone a good cli tool for burning isos ? [04:12] wodim IIRC [04:17] okay so finally the EFI entry went away when i booted into ubuntu, found the `EFI/ubuntu` directory, and torched it. [04:17] man Windows seriously does not want you meddling with EFI stuff. [04:17] tomreyn, well, considering I had hosed my other laptop with Irish Cream liqueur... [04:18] I'm left with a measly 16GB USB [04:18] uuh sorry to hear about the liquor mishap. [04:19] Yeah, the messed up laptop is in a box. It will be delivered to FedEx tomorrow moring [04:19] morning* [04:19] thanks for yalls help [04:19] The box is sitting behind me [04:19] And I do intend to come back soon, hopefully. [04:20] But for now, time to see what fresh hell awaits inside this Manjaro ISO [04:20] AlexMax: i didn't follow the whole story, if you need more ubuntu help, just ask [04:20] Will do. [04:21] (and anything that's not directly ubuntu support related should rather go to #ubuntu-offtopic, please) [04:22] I getcha. Was just on my way out and thanking people for what help they were able to provide. [04:33] wedr: FWIW, i just created, from a running ubuntu 19.10 desktoip installation, a 19.10 desktop installer on a 6 GB usb stick, using usb-creator-gtk ("startup disk creator"). what it did is it created a 2.5 GB ISO9660 partition, a 4,1 MB FAT partition (for booting, i guess), and left 4 GB space untouched, available for further partitioning. [04:33] tomreyn, I also did that [04:33] actually the usb stick is 6,4 GB, so it does match up. [04:33] I got 2GB, and 14GB unpartitioned [04:34] good :) [04:34] So what's next? Ubuntu on my laptop has a /dev/lock on the apt-get update [04:34] so I can't get gparted [04:34] that's the drunk laptop, or another? [04:35] another [04:35] I have 2, the drunk one is in the box [04:35] and the one with broken apt, have you tried to fix this? [04:35] nope, hence the reinstallation plan [04:35] for the umpteenth time [04:36] hmm, do you want to diagnose this or just reinstall? [04:36] I went from 19.04 to 18.04LTS to 16.04LTS, and I'm crippled with using Metacity fallback. I can't use the Ubuntu 16.04 Unity [04:36] I'm sick of life [04:36] reinstall [04:37] Ok, so I need to figure out how to set up a persistent partition for the remaining 14GB on this USB [04:37] so you have an usb installation stick, can you just install from there now or do you need to 'backup' data from the previous installation to the usb stick first? [04:38] okay then you should have "gdisk" already installed? [04:38] aka "Disks" [04:39] need to backup data from the laptop to this live USB drive, before I reinstall the Ubuntu on this laptop to a fresh new state [04:39] ah, Disks [04:40] I'm just going to use 4GB of the 13GB free partition. Maybe this USB can be used on Windows machine in the future, when my work place is slowly transitioning to a Windows environment [04:42] ok. i suggest you format the new partition as type "internal disk for use with Linux systems only (Ext4)" and optionally "password protect volume (LUKS)" [04:43] hmm it fails to create this partiton here :-/ [04:43] tomreyn, ugh, 16.04 has this bug: It is setting improper block-size during the creation of bootable media. [04:44] 2048 in USB, 512bytes in Linux [04:47] Ugh, it's a bug in 16.04 and it seems to be fixed in 17.04... https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1708881 [04:47] Launchpad bug 1589028 in parted (Ubuntu) "duplicate for #1708881 Improper blocksize set by usb-creator, leads to problems during formatting" [High,Confirmed] [04:48] I'm getting out of 16.04, but I need my data... [04:48] i still see this issue on 19.04, though [04:48] oh.... [04:49] see comment 21 at bug 1589028 [04:49] bug 1589028 in parted (Ubuntu) "Improper blocksize set by usb-creator, leads to problems during formatting" [High,Confirmed] https://launchpad.net/bugs/1589028 [04:50] yeah. that's back to square 1 [04:50] the /dev/lock is on apt update [04:51] so you're working on an ubuntu 16.04 and are trying to create an additional partition on this usb storage? [04:52] if so, is the new installation meant to boot in uefi or bios mode? [04:52] I'm assuming uefi. This laptop is a work laptop, so I have no idea what it was configured to before [04:53] the new installation is not meant for booting [04:53] wait, new installation of Ubuntu on laptop is to be booting into UEFI [04:53] ok, that makes more sense ;) [04:54] I'm creating an additional partition on the usb storage, to make it as if it's a simple storage USB device [04:54] The USB storage is just a drive stick [04:54] It is meant to be a recovery / emergency use only drive stick [05:01] okay, i got so much [05:01] i'm looking for a way to creater this extra partition without breaking the hybrid boot [05:02] wedr: you don't have another storage you can write the backup, to, right? since i guess that'd be easier [05:02] That got hosed with the Irish Cream too [05:03] or less error prone [05:03] i see [05:04] Basically, I broke the Irish Cream glass bottle, the liquid went into my USB 1TB, the laptop, cables, lots of USBs, mouse, keyboard on the desk, and the wall [05:04] USB 1TB WD Elemetns [05:04] looks like you're a very thorough person. ;-) [05:07] you got Kaluha? [05:08] just go for the full mudlside [05:10] wedr: okay, fdisk can do it, at least on this 19.10 system i have [05:11] tomreyn, Also playing with fdisk [05:11] I felt like you and I are the same person [05:11] but more unfortunate [05:11] :) [05:11] and out $500 bucks [05:13] so i did sudo fdisk /dev/sdb (the usb stick is sdb here, substitute the proper drive as needed, "sudo fdisk -l" to identify it), then did "n" and went with defaults for all the prompts, and finally did "w" [05:13] then mkfs.ext4 /dev/XXX (was sdb3 here) [05:16] yeah, the partition type though... [05:17] I was thinking of making it a storage USB, so I'm thinking if I should use NTFS. [05:17] primary worked for me, which was default [05:17] No, the partition type [05:17] In fdisk, if you use "t" [05:17] it suggested ext2, i said ext4, so i guess i got "Linux" [05:17] yes i did [05:18] you can always repartition this thing later, right? [05:18] ext4 is linux, yes, but I wanted to make it compatible with both work laptop and the new Window workstation I will be getting at this year's Q3 [05:19] I'm not sure if repartitioning the type is a thing [05:19] you mean, wiping out the partition and repartition a new one? [05:19] yes, you do it now, why couldn#t you do it again later? [05:19] Wouldn't that degrade the USB's lifespan? [05:20] every write does. to any storage media. [05:20] ok then, it's set to the default, which I think the default is ext4 [05:20] will it die because you update the partition table? no. [05:20] I got Linux [05:21] so "w" on fdisk to write and quit, then make a file system on the new partition. [05:21] supply a file system --label when you do [05:22] I'm trying to cancel a command [05:22] How do I jump out of the fdisk command [05:22] q [05:22] I see [05:23] Is your Linux partition type ID 83 [05:23] ? [05:23] Just wanted to make sure [05:24] can't say right now, i'm just trying to boot off it [05:28] Let me know if you can boot off of it [05:29] i did uefi boot off it fine [05:29] hi, i'm on WSL and whenever I run apt-get to try to install something, it doesn't work and then prints this twice at the end: `E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt 2>/dev/null || true: Success` [05:29] !wsl | SirNapkin1334 [05:29] SirNapkin1334: Windows 10 has a feature called Windows Subsystem for Linux, which allows it to run Ubuntu (and other Linux distro) userspace programs without porting/recompliation. For discussion and support, see #ubuntu-on-windows or ##windows. For installation instructions, see https://msdn.microsoft.com/en-us/commandline/wsl/install_guide [05:29] hmm, don't know if that was supposed to format, but it didn't include the backticks [05:29] okay, thanks [05:31] wedr: how do i print the partition id using fdisk? can't seem to find it. [05:31] fdisk p [05:31] inside fdisk, type the command, p [05:32] it doesn't show the ID there, just "Linux" [05:33] ah "i" does it [05:33] and yes it's 83 [05:34] ok [05:34] now I need to use mkfs ext4 [05:34] I think ext2 is fine, right? [05:34] ugh, I still need to read up what's the difference between ext2, ext3, and ext4... [05:36] basically, the higher the number the better [05:37] ext2 lacks journalling, it's almost as simple as fat32 [05:38] ext3/4 aren't as complicated as ntfs, but have similar features. [05:44] darn, I'm still hit with the partprobe saying the sector is 2048 but it's 512 bytes error [05:44] wedr: fwiw, bios booting works, too, off the usb stick. [05:44] Can't use mkfs [05:45] why not? [05:45] The file /dev/sdb3 does not exist and no size was specified. [05:45] That's the error message I got when running mkfs [05:45] sdb3 is my new partition [05:45] so after creating the partition in fdisk, partprobe failed? [05:45] yes [05:46] maybe reboot then [05:46] ok then, see you in a bit. [05:50] wedr: so does ls -l /dev/sdb3 exist now? [05:51] i actually need to wrap it up here for now, it's very early where i am. [05:51] nope [05:52] yeah, it's fine... [05:52] but sudo fdisk -l /dev/sdb lists the partition you created? [05:53] wdr: ...and doesn't print a warning about the sector size mismatch? [05:53] * wedr [05:53] really, no [05:53] oh, it does print about a warning [05:54] i/o all 512 bytes [05:54] fidk prints a warning? okay then your fdisk is just too old, basically what you found earlier. [05:55] consider backing up to a smartphone instead, or to cloud storage. [05:55] fidk -> fdisk [05:55] ok... [05:55] or recreate the live usb... [05:56] i don'T see how this would enable you to create the partition then. [05:57] though you could try booting off the live usb and use its more current fdisk to create the third partition [05:57] anyways, good luck. [06:21] thanks [07:59] anyone have any suggestions on getting bluetooth to work again [09:11] Some of you use MyPaint? for the life of me I'm incapable to merge 2 existing images (trying to copy paste the second into the first whose canvas size were increased) [09:12] you can resize the canvas with the rectanglish icon [09:19] Hello. Is there a way to have individual command-history- and log-files for parallel running bash-windows? Possibly so that each one can have an individual name that is somehow carried over to the logfile and be re-opened later? Or are there other tools for this? [09:20] Mrokii: there is a variable to set the name of the history file, iirc. should be in the manual [09:20] ah, HISTFILE [09:20] ducasse: Thanks, I'll take a look. [09:21] what do you guys use for basic image editing? [09:22] I don't often have to, need somethign simple [09:22] pxlr [09:22] pixlr [09:22] online is the future [09:22] oh, interesting [09:23] I know abot Krita too, a good local software [09:23] thx will try pixlr [09:23] anyone have any suggestions on getting bluetooth to work again [09:24] Depends on what you mean with "basic", I guess. For very simple things like cropping and resizing I use Gwenview, as I'm on Kubuntu. [09:24] qswz: got to admit, i'd reach straight for the gimp [09:24] yea gimp is the comon alternative [09:25] feels bit too complex to me :) [09:30] "You'll need Flash Player to run Pixlr Editor." what.. [09:30] oh, fortunately there's a beta without flash [09:31] lol [10:11] does ubuntu stop build i386 kernel since 5.3.6? Can we waite fix? https://kernel.ubuntu.com/~kernel-ppa/mainline/ [10:13] !i386 | JohnDoe_71Rus [10:13] JohnDoe_71Rus: For information about the future of support for i386 packages in Ubuntu 19.10 Eoan Ermine and onward, please read the following official statement: https://ubuntu.com/blog/statement-on-32-bit-i386-packages-for-ubuntu-19-10-and-20-04-lts . Note this applies only to i386 (Intel/AMD) builds, not other 32-bit architectures like arm. === Lantizia_ is now known as Lantizia [10:36] maybe I'm going insane here (as I can't find any evidence of this when searching online)... but in gedit (or Pluma if you're a MATE user) when the document you've got open has "changed on disk" and you get a banner asking you if you want to "Reload" or "Cancel"... I swear at some point I've seen a third option that loads Meld and compares the "on disk" version to the text you have open in gedit/Pluma [10:36] does anyone else remember seeing this or have I dreamt it? [10:37] ducasse: ok. This message was in June 2019, kernel v5.3.7 with i386 build error was in october. This time they build i386 kernel till error [10:47]