[00:36] <xubuntu51w> I came back to my PC running xubuntu (latest version) from usb, so i restarted and now it’s in emergency mode and failing to reboot. what do I do?
=== brainwash_ is now known as brainwash
[03:11] <xubuntu73w> hello, I'm curious if the software updater or apt-get dist-upgrade is supposed to not recognize the availability of 19.10 yet
[03:11] <xubuntu73w> I do have the setting set to notify me for "any new version"
[03:16] <xubuntu73w> I'm about to manually edit my sources.list but it is unclear if the auto updater is intentionally not working or if this is a bug
[03:20] <xubuntu73w> do-release-upgrade reports No new release found.
[03:22] <Bashing-om> xubuntu73w: Try as ' sudo apt update; sudo apt full-upgrade ' sudo do-release-upgrade -d ' -  19.10 will keep the (d)evelopment designation until the 1st point release.
[03:25] <xubuntu73w> oh that would explain it
[03:25] <xubuntu73w> I was unaware it stayed as devel until then, thanks
[03:30] <Bashing-om> xubuntu73w: :D - let us know how it goes :)
[08:11] <xubuntu22w> Hi I'm trying to install xubuntu 19.1 but when booting from usb stick I see the logo and then a blank screen
[08:15] <tomreyn> xubuntu22w: there is no "xubuntu 19.1", though. do you mean 19.10?
[08:15] <tomreyn> (where 10 stands for october, 19 for 2019)
[08:16] <xubuntu22w> yes
[08:16] <tomreyn> did you previously run linux on this system? if so, which ubuntu version or distribution and kernel version?
[08:17] <xubuntu22w> I have neptune installed on SSD, kernel 4.19
[08:19] <tomreyn> hmm, that's a linux distro, i assume?  i'll look it up shortly.
[08:20] <xubuntu22w> yes https://neptuneos.com/en/start-page.html
[08:21] <tomreyn> xubuntu22w: thanks. do you know whether you'Re eufi or bios booting?
[08:21] <tomreyn> *uefi or bios
[08:21] <tomreyn> and what your hardware is?
[08:21] <xubuntu22w> my hardware: mobo Gigabyte B450, AMD Ryzen 3, SSD Kingston A2000 UEFI
[08:24] <diogenes_> xubuntu22w, try nomodeset.
[08:24] <tomreyn> okay, so somewhat new, but not the very latest. do you have a separate graphics card?
[08:24] <xubuntu22w> OK thank you.
[08:25] <xubuntu22w> No the graphics is incorporated into the CPU
[08:27] <tomreyn> okay, so just the amd gpu. nomodeset may enable you to boot in low graphics mode. another option can be amdgpu.dc=0
[08:27] <xubuntu22w> I'll try now thanks
[08:28] <xubuntu14w> How to connect USB to serial 9 pin port?
[08:28] <tomreyn> what'S the goal, a serial console?
[08:28] <xubuntu14w> I can't connect it.
[08:29] <tomreyn> why are you trying to connect it, what's going to be achieved by that?
[08:29] <tomreyn> is there some device on the other end of the wire?
[08:29] <henrebotha[m]> Good morning #xubuntu. I'm trying to upgrade to 19.10, but running /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d gives me a popup that says "Welcome to the Ubuntu 'Eoan Ermine' development release". How do I make it detect the 19.10 regular release?
[08:30] <tomreyn> henrebotha[m]: you wait a few days and run without -d
[08:30] <xubuntu14w> yes!
[08:31] <henrebotha[m]> Ah, didn't think to check what the -d flag does lol, my bad. But why do I need to "wait a few days"? If the release is out, what's the hold up?
[08:31] <tomreyn> xubuntu14w: would you mind disclosing what that device is?
[08:31] <Bashing-om> henrebotha[m]: 19.10 will be designated developer until the .1 point release.
[08:32] <tomreyn> Bashing-om: there'll be a .1?
[08:32] <henrebotha[m]> Oh, weird. So the "development" release I'm seeing now is actually the stable release? Or do I misunderstand
[08:33] <tomreyn> henrebotha[m]: it is, but using an untested upgrade path. if running without -d doesn'T offer you to upgrade, yet, then just retry in a frew days.
[08:33] <tomreyn> *few
[08:34] <tomreyn> usually, for non LTS releases, upgrades will be available after a few days.
[08:35] <tomreyn> make sure that     software-properties-gtk --open-tab=2    has you notified of 'any new version' on the bottmo.
[08:36] <tomreyn> *bottom ;)
[08:36] <henrebotha[m]> I'm way too impatient
[08:37] <henrebotha[m]> Going to try the dev release
[08:37] <tomreyn> you're not alone in this. many people run into some articles, don't read them properly, and do an unsupported upgrade (and some articles don't even mention what -d does).
[08:44] <henrebotha[m]> The thing that actually made me pause now is: "Installing the upgrade can take several hours"
[08:44] <henrebotha[m]> I have work to do, can't really afford several hours 😅
[08:45] <henrebotha[m]> So I guess I'll try the dev release on the weekend then
[08:46] <xubuntu97w> I'm back Installation to SSD was succesful by selecting safe graphics in grub menu, but when booting now from SSD still blank screen
[08:47] <tomreyn> henrebotha[m]: it doesn't usually take this long, but certainly it depends much on how fast your download and disks are, and whether the system has sufficient RAM available, too. waiting for the weekend is a good plan, amy also enable you to take the supported upgrade path.
[08:47] <henrebotha[m]> Yeah that's kinda my thinking
[08:47] <diogenes_> xubuntu97w, you need some firmware.
[08:48] <xubuntu97w> how to install?
[08:49] <diogenes_> first check driver manager.
[08:49] <tomreyn> it's amdgpu, won't be there
[08:49] <xubuntu97w> I dont have the xfce desktop just blank screen
[08:50] <xubuntu97w> also selected download firmware during install so what is wrong?
[08:50] <tomreyn> you can bring up the grub menu during boot by pressing escape, then choose to boot into recovery, then continue booting from there.
[08:50] <tomreyn> !recovery
[08:50] <ubottu> If your system fails to boot normally, it may be useful to boot it into recovery mode. For instructions, see https://wiki.ubuntu.com/RecoveryMode
[08:52] <xubuntu97w> I'll give it a try and update you thanks
[09:08] <xubuntu97w> I'm back, with recovery mode the desktop is visible but the resolution needs to be adjusted, how do I install AMD firmware?
[09:10] <tomreyn> xubuntu97w: great, so you got a graphical desktop for now. do you also have internet access there now?
[09:10] <tomreyn> xubuntu97w: can you copy and paste commands to the chat from there?
[09:11] <xubuntu97w> yes and yes
[09:12] <tomreyn> xubuntu97w: first let's make sure it's really about firmware:    journalctl | grep -i firmware | nc termbin.com 9999
[09:12] <tomreyn> if you'd like a better chat 'experience' you can install an irc client such as hexchat.
[09:13] <xubuntu97w> I got this: https://termbin.com/nzgm
[09:14] <tomreyn> there's no missing firmware, so it's something else. this output suggests you have booted this system three times so far. can you say which oif these boots you did without going through the grub menu?
[09:16] <xubuntu97w> no, in the latest I selected recovery mode and via a menu got the current desktop I'm now using
[09:17] <JohnWknd> hey guys
[09:17] <tomreyn> would you mind sharing your hardware serial numbers and local ip addresses with us? if you don't please post a full system log:  journalctl -b -1 | nc termbin.com 9999
[09:17] <tomreyn> xubuntu97w: ^
[09:17] <tomreyn> hi JohnWknd
[09:18] <xubuntu97w> how do I do that?
[09:19] <JohnWknd> i can't upgrade my xubuntu to a newer version (19.10) my current version is 19.4. Can you please explain me what is my problem?
[09:19] <xubuntu97w> never mind, here it is:https://termbin.com/jj9k
[09:20] <tomreyn> JohnWknd: upgrades aren't enabled, yet, it's usually enabled a few days after release.
[09:20] <JohnWknd> ok, thank you
[09:20] <tomreyn> xubuntu97w: thanks, it'll take me a couple minutes to review it. i recommend you do a full system update in the meantime, installing all the pending updates (if any)
[09:21] <xubuntu97w> OK
[09:24] <tomreyn> xubuntu97w: looks like you never upgraded your bios: you're on version F2, the latest is F42d (must step through version F32) https://www.gigabyte.com/Motherboard/B450-AORUS-M-rev-10/support#support-dl-bios
[09:26] <tomreyn> i'll read on, it may be possible to make it work without the bios upgrade, though i really would recommend doing that
[09:27] <xubuntu97w> downloaded the file from Gigabyte website but never done this before how do I update the bios?
[09:28] <tomreyn> you need to step through version F32, so you should have two downloads
[09:29] <xubuntu97w> OK I'll give it a try
[09:30] <tomreyn> if you don't have windows or dos installed you should be able to place the extracted files on a fat32 file system on the first msdos partition on an usb stick, then boot to the bios setup and select the "qflash" option there to select the firmware to upgrade to from the usb stick
[09:31] <tomreyn> https://www.gigabyte.com/FileUpload/global/WebPage/20/images/utiltiy_qflash_uefi.pdf
[09:31] <tomreyn> or rather start here https://www.gigabyte.com/microsite/121/tech_qflash.htm
[09:34] <tomreyn> xubuntu97w: ^
[09:39] <coblloy> Hi, I just installed Ubuntu, current lts version, I tried to run the updated and it asked me to authenticate but it won’t accept my password
[09:39] <coblloy> im tearing my hair out, don’t know what to do
[09:40] <coblloy> Sorry, autocorrect - xubuntu
[09:40] <coblloy> and ‘updater ‘ is what I wrote 😖
[09:42] <coblloy> I can’t boot into grub menu, pressing shift key does nothing
[09:42] <coblloy> I tried changing the password from a live disk, that didn’t help either
[09:43] <tomreyn> coblloy: if you'Re UEFI booting, you need to hit escape to bring up the grub menu
[09:44] <coblloy> The esc key triggers the bios menu
[09:44] <tomreyn> then do it a little later ;)
[09:45] <coblloy> It boots really fast, I’ve been trying to hit esc but it either goes to bios or boots to xubuntu
[09:46] <tomreyn> are you uefi booting, though?
[09:46] <coblloy> how would I find that out?
[09:46] <tomreyn> echo -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
[09:46] <coblloy> also fast boot is disabled already
[09:47] <coblloy> do I type that line in verbatim?
[09:47] <tomreyn> better copy and paste it if you can, to a temrinal
[09:48] <coblloy> I’m chatting on the iPad, gotta type it in
[09:48] <tomreyn> alternatively, if you'd have to type it out, you can just check what this returns:   ls /sys/firmware/efi
[09:49] <tomreyn> it will either return a list of files or an error message
[09:49] <tomreyn> list of files means uefi mode, error message means legacy bios / csm
[09:50] <coblloy> Yes, booted by UEFI according to the reply in terminal
[09:50] <coblloy> i just typed in the whole thing
[09:51] <coblloy> FYI I don’t know what UEFI is, I really stopped paying attention to tech in the 90s
[09:51] <tomreyn> so then pressing shift during boot cannot work, and escape would be your ownly option.
[09:52] <coblloy> Ok, esc is just impossible, Inhave no idea how to get the right moment, it’s always either bios or normal boot
[09:52] <tomreyn> uefi is the 'new' way of initializing those ultracomplex computer hardwares we have, then passing control to the operating system
[09:52] <coblloy> oh ok, like an extra bios
[09:52] <tomreyn> it replaces bios
[09:53] <coblloy> bios with extra steps lol
[09:53] <coblloy> oh ok, so the ‘bios’ menu is really a UEFI menu then?
[09:53] <coblloy> So is there anything else I can do?
[09:54] <tomreyn> yes, there are really no more computers getting sold with a real bios anymore for years now
[09:54] <coblloy> is reinstalling likely to change anything?
[09:54] <coblloy> I read there isn’t supposed to be an admin password in xubuntu?
[09:54] <tomreyn> sure reinstalling could let you set a new password
[09:55] <tomreyn> there's no root password, but there is a user password, and this user password is requested when you try to do stuff as root
[09:55] <coblloy> im pretty sure of the user password, I don’t think I’m getting it wrong tho
[09:55] <diogenes_> you can boot a live system and chroot.
[09:55] <tomreyn> yes that'S the only other option next to reinstalling
[09:55] <coblloy> I already tried that chroot
[09:56] <coblloy> but can you give me the commands - maybe I did that wrong?
[09:56] <diogenes_> first boot a live system.
[09:56] <coblloy> I live booted the USB and opened a terminal in the root dir of the installed OS
[09:57] <tomreyn> https://help.ubuntu.com/community/LiveCdRecovery#Lost_Password
[09:57] <coblloy> And did a password change, after reboot, nothing had changed
[09:57] <tomreyn> /dev/sda1 *may* not be correct, though
[09:58] <coblloy> If I go to that link am I pushed off the chat?
[09:58] <tomreyn> not if you do it in a new tab
[09:58] <tomreyn> i assume it will open it in a new tab by default
[09:59] <coblloy> Fkn iPad won’t let me open it in new tab
[09:59] <tomreyn> long press doesn't bring up the context menu?
[09:59] <coblloy> Ok I’m gunna open it, but I think I already saw that page
[09:59] <coblloy> No long press isn’t doing the long press thing
[09:59] <tomreyn> i see, a pity.
[10:00] <coblloy> It’s ok it opened a new tab on its own
[10:00] <xubuntu66w> I'm back bios updated to latest version
[10:00] <coblloy> Ok hang on I’ll try this again
[10:00] <tomreyn> xubuntu66w: nice! did it help with the boot?
[10:01] <xubuntu66w> don't know I'm in recovery mode
[10:01] <xubuntu66w> shall I restart?
[10:01] <tomreyn> xubuntu66w: sure, give it a try.
[10:01] <xubuntu66w> OK
[10:04] <coblloy> Uhh, ctrl-alt-f1 crashed it
[10:04] <tomreyn> what is "it"?
[10:05] <coblloy> The computer, now it’s shutting down
[10:05] <coblloy> Fck, now it won’t see the live usb
[10:06] <xubuntu49w> I'm back, no luck - normal boot gives me blank screen, desktop reachable only via recovery mode
[10:07] <tomreyn> xubuntu49w: okay, are you back to desktop from recovery mode now?
[10:07] <xubuntu49w> yes I'm writing from desktop in recovery mode
[10:08] <tomreyn> xubuntu49w: let's see the failed boots' (last but one boot's) system log:   journalctl -b -1 | nc termbin.com 9999
[10:08] <xubuntu49w> https://termbin.com/qmf4
[10:10] <tomreyn> looking
[10:18] <tomreyn> we have this, which is probably not ideal, but may not be related at all: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[10:18] <tomreyn> and then we have this, which is related:
[10:18] <tomreyn> [drm] pstate TEST_DEBUG_DATA: 0xB6F60000
[10:18] <xubuntu49w> what does it mean?
[10:18] <tomreyn> kernel: WARNING: CPU: 2 PID: 255 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu]
[10:19] <xubuntu49w> is there a remedy for this?
[10:19] <tomreyn> what it means and what to do about it i need yet to find out.
[10:21] <tomreyn> this has been previously reported here: https://bugs.freedesktop.org/show_bug.cgi?id=109628
[10:21] <ubottu> Freedesktop bug 109628 in DRM/AMDgpu "WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()" [Normal,New]
[10:21] <xubuntu49w> Ok I'll check again later (my PSU is dying, turning on the PC is possible only through the on off switch on the PSU itself, so it might be in a few days
[10:22] <tomreyn> oh :-/ well, good luck then!
[10:22] <xubuntu49w> for now it is only recovery mode for me?
[10:23] <cobelloy> Am I back on?
[10:23] <tomreyn> i haven't finished reading the bug report, yet.
[10:23] <cobelloy> did any of my messages go through?
[10:23] <xubuntu49w> I stay connected
[10:24] <tomreyn> cobelloy: yes we can read you
[10:24] <cobelloy> i followed the first instruction - ctrl-alt-f1 and the computer crashed, now it won’t boot to usb
[10:25] <cobelloy> and the installed os now has a ‘system problem’ which it (of course) wants my password for
[10:25] <tomreyn> xubuntu49w: ok. if you're still around: do you have auto-login enabled so you don't need to enter your password when you start up?
[10:25] <cobelloy> then my chat window decided to crap itself
[10:26] <xubuntu49w> yes auto login
[10:26] <tomreyn> cobelloy: the system problem is ubuntu's semi-automatic crash bug reporter, you can just choose to not report those and should not require root for that
[10:27] <cobelloy> yes, except that it won’t see any USB drives now
[10:27] <cobelloy> either in bios or OS
[10:28] <cobelloy> whatever ctrl-alt-f1 did has forked up something royally
[10:29] <tomreyn> xubuntu49w: okay, from what i read on this bug report this is related to xfwm, the xubuntu window manager. this means that you could possibly boot to other window managers fine. it would be good to create a standard ubuntu (not xubuntu) 19.10 live / installer usb just to test whether you can boot to that without needing to resort to reovery / failsafe graphics.
[10:29] <cobelloy> also it does the system problem thing every boot, I’ve rebooted 3x and it comes up every time
[10:29] <tomreyn> cobelloy: hmm this then rather sounds like a hardware or firmware issue.
[10:30] <xubuntu49w> Is it possible to roll back from 4.14 to 4.12? I do want to use xfce...
[10:30] <cobelloy> just to be clear, it had NO hardware or firmware issues this morning
[10:31] <tomreyn> cobelloy: i mean the fact that you'r enot seeing the usb drive from bios now *may* mean it's a firmware / bios issue.
[10:31] <tomreyn> xubuntu49w: are those xfwm version numbers? if so, no, you#d need to use an older xubuntu version. maybe try xubuntu 19.04 until this is solved.
[10:32] <cobelloy> A firmware issue that just happened to occur after the live boot crashed?
[10:33] <tomreyn> cobelloy: i'm just working with the information you're providing, that you don't see devices on the bios which you used to see there in the past.
[10:33] <xubuntu49w> Thank you! god bless, goodbye
[10:33] <tomreyn> xubuntu49w: you're welcom, good luck!
[10:33] <cobelloy> *after the live image crashed on ctrl-alt-f1
[10:35] <cobelloy> I’ve unplugged the USB, rebooted and replugged the USB and now it sees it again
[10:35] <tomreyn> cobelloy: give me a minute to recap, i had my head dug in xubuntu49w's issue
[10:35] <cobelloy> Ok
[10:36] <cobelloy> I can just reinstall, if this password roadblock happens again I will give up on xubuntu
[10:37] <tomreyn> if reinstalling is easy for you then that's probably the easier option compared to the chroot recovery
[10:38] <cobelloy> im doing it already, about to hit confirm
[10:38] <tomreyn> what may have happened about your password:
[10:38] <cobelloy> But I don’t think I had the password wrong, I reuse the same password on a lot of systems
[10:38] <tomreyn> you may have had a different keyboard layout on the installer where you typed your password, and then a another keyboard layout upon login to the installed system
[10:39] <cobelloy> hmmm, ok - that’s possible
[10:39] <tomreyn> this is a common issue when you have passwords containing characters which are mapped differently on e.g. US english vs. your localized layout
[10:39] <cobelloy> Installer used the au English layout but I’ve always chosen us English...
[10:40] <tomreyn> try, at leats for the installation, to set a simple password which could be entered by pressing the same keys on either layout
[10:40] <cobelloy> ill try installing with us English, I haven’t gone too far yet
[10:40] <tomreyn> another issue could be caps lock, but you know enough that i assume this will not have happened
[10:40] <cobelloy> Yeah I checked caps each time, tried on and off
[10:41] <tomreyn> if you like you can edit the grub configuration after installation so that the grub menu will show up either way
[10:42] <cobelloy> This keyboard thing could be the problem, it certainly matches the problem, I’m 99.9% sure I didn’t get the password wrong
[10:43] <tomreyn> well give it a try then, i can't think of anything else. it's rather unlikely that a generic password issue had made it through testing
[10:44] <cobelloy> Ok installing, will take 15-20min
[10:45] <cobelloy> I’ve already partially bricked my favourite laptop with the Ubuntu installer - when I looked up the issue on the internet it’s a logged bug
[10:46] <cobelloy> very annoying and another uefi think that I only half understand 😡
[10:46] <cobelloy> It is locked into a loop calling a file on restart that was not copied to the hard drive
[10:47] <cobelloy> Only fix is to remove and wipe the hdd, but I don’t have a bloody torx screwdriver to open the damn thing up
[10:48] <cobelloy> it also now refuses to acknowledge any other boot media 😡
[10:48] <tomreyn> hmm, that's indeed annoying. but if it's this complicated it's usually a result of firmware doing things wrong, and linux / ubuntu having to work around it.
[10:49] <tomreyn> if you like, post a link to the bug report and i'll see if i can suggest an easier workaround
[10:49] <cobelloy> Sort of, it’s a big common on Acer laptops apparently, but I don’t have the bios setting that can fix it
[10:50] <cobelloy> thanks, maybe tomorrow, I’d have to locate all the info and the relevant bug report again and I just can’t be fckd now
[10:51] <cobelloy> ill probably just buy the bloody screwdriver, that will no doubt be a quicker option
[10:51] <cobelloy> From memory it has something to do with the combination of incorrect hdd formatting and then selectin
[10:51] <tomreyn> acer is not the primary choice when you want hardware which will work well with linux.
[10:51] <cobelloy> installing the extra drivers and software
[10:52] <cobelloy> i don’t have Acer, I have hp spectre
[10:52] <tomreyn> oh okay i was assuming you're referring to a different system there because you mentioned acer
[10:52] <cobelloy> But the only relevant info I could find was for Acer laptops, but they have some troublesome bios setting that can be turned off to bypass the issue
[10:52] <cobelloy> my laptop seems to have it hardwired in
[10:53] <cobelloy> two systems, yes
[10:53] <cobelloy> the one I’m having this keyboard(?) issue with and my favourite hp laptop from yesterday
[10:54] <cobelloy> tried installing Ubuntu on the good laptop yesterday now that I don’t need windows and more
[10:54] <cobelloy> big mistake
[10:55] <cobelloy> this one is a lower powered cheap Chinese tiny computer that also had win10 but struggled a bit
[10:55] <cobelloy> a real little trooper tho
[10:55] <cobelloy> nstall has finished, again
[10:58] <cobelloy> It was the keyboard, password problem solved 🥳
[10:59] <tomreyn> ah nice
[10:59] <cobelloy> Thanks for that, don’t think I would’ve thought about the keyboard choice, how bloody frustratng
[11:01] <cobelloy> I’m not at all impressed with this uefi business though, it doesn’t seem very robust
[11:01] <tomreyn> you're welcome
[11:03] <tomreyn> uefi is way too powerful, way too complex. it does add some nice features, but there are also a lot of different implementations, behaving differently, and many not according to the specification.
[11:05] <cobelloy> Right, I’m just reading the Wikipedia page, I think I’m a bit too legacy now
[11:07] <tomreyn> don't try to understand uefi too much, rather focus on understanding GPT vs msdos partition tables, this will be more useful.
[11:07] <cobelloy> Oh interesting - https://en.m.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Secure_boot_2
[11:07] <tomreyn> and how uefi *booting* works very differently to bios booting
[11:07] <cobelloy> It’s this ‘secure boot’ hats at the heart of my dead laptop
[11:08] <tomreyn> secure boot can usually be disabled, but not always.
[11:08] <cobelloy> Ok, GPT - another trip to Wikipedia then...
[11:08] <cobelloy> Yes, apparently not on my laptop
[11:09] <cobelloy> But I did discover too late there is a firmware update for my laptop, that may add the ability to turn off secure boot
[11:10] <cobelloy> so once I get a torx screwdriver I might be able to fix it all
[11:27] <cobelloy> After all that, I have no sound
[11:32] <cobelloy> Nope, my bad, speakers unplugged duh
[15:10] <vsdfd> I can't seem to find how to disable the sound that backspace does when the text input is empty. Does someone know which sound is it and how to disable it?
[15:10] <vsdfd> would save my day
[15:11] <vsdfd> I tried running: "dconf write /org/gnome/desktop/sound/event-sounds false" to disable everything but it didn't work
[15:11] <diogenes_> vsdfd, blacklist pcspkr.
[15:14] <vsdfd> on the file "/etc/modprobe.d/blacklist.conf", the line "blacklist pcspkr" is not commented
[15:15] <diogenes_> lsmod | grep pcspkr
[15:16] <vsdfd> "lsmod | grep pcspkr" has no output
[15:18] <diogenes_> apt list --installed | grep sox
[15:18] <vsdfd> libsoxr0/bionic,now 0.1.2-3 amd64 [installed,automatic]
[15:18] <vsdfd> do you think I could delete the audio file
[15:19] <vsdfd> for the beep, or rename it, or change in some configuration file
[15:20] <diogenes_> you could try remove sox (if it's not used by something else).
[15:21] <diogenes_> also in dconf-editor look for:
[15:21] <diogenes_>  /org/cinnamon/settings-daemon/peripherals/keyboard/bell-mode
[15:22] <diogenes_>  /org/cinnamon/desktop/wm/preferences/bell-sound
[15:22] <diogenes_> insteam of cinnamln look in gnome.
[18:05] <Noboru55> Hello,
[18:05] <Noboru55> please, how do i know if i am using the correct video driver in xubuntu ?
[18:05] <Noboru55> someone can help me?
[18:06] <Noboru55> this is what the lspci shows
[18:06] <Noboru55> 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
[18:07] <Noboru55> is it right or only compatible?
[18:13] <diogenes_> Noboru55, inxi -G
[18:49] <Noboru55> diogenes_ hello, inxi -G ?
[18:54] <Noboru55> diogenes_ inxi -GGraphics:  Card: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller           Display Server: x11 (X.Org 1.20.4 ) drivers: modesetting (unloaded: fbdev,vesa)           Resolution: 1366x768@60.01hz           OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (Braswell) version: 4.5 Mesa 19.0.8
[18:55] <Noboru55> i guess its right  inel hd graphics 400
[18:56] <diogenes_> drivers: modesetting i guess it's ok.
[20:21] <Noboru55> diogenes_it's ok my video driver... inxi -G