[00:08] <sla3k> leftyfb: there we go, it happened again
[00:08] <sla3k> Literally nothing logged in journalctl window
[00:09] <leftyfb> sla3k: there's nothing in the log when you attempt to login?
[00:10] <sla3k> When I attempt to login before, it would log, but not now..just says connection refused on client
[00:10] <leftyfb> sla3k: from another linux machine on the same network, run: nmap -p22 <ip-of-VM>
[00:12] <sla3k> leftyfb:
[00:12] <sla3k> dnet: Failed to open device ens18
[00:12] <sla3k> QUITTING!
[00:12] <leftyfb> try sudo
[00:12] <sla3k> not related to the problem at hand..but let me figure this one out first
[00:13] <sla3k> ^^ already running as root
[00:13] <sla3k> I'll be back
[00:35] <ruronike> help
[00:36] <ruronike> sorry bad typo
[00:50] <Jazzy_J> whois #ubuntu
[00:58] <last1> I had an unexpected power loss on my computer and since then it boots properly maybe once every 5 times. most of the time I get to the GRUB Ubuntu selection screen but it freezes shortly thereafter
[00:59] <last1> it says mpt2sas_cm0, overriding nvdata eedptagmode setting and just stays there, I can reboot and it might work...or most of the time, not
[01:00] <last1> I booted using USB key and I can mount the drive just fine and see all the data
[01:03] <rfm> last1, sounds like the NVRAM got a little scrambled in the power glitch.  If you can reset NVRAM (on desktop compulters there's often a jumper, or take the lithium battery out for a bit)
[01:06] <rfm> last1, on a laptop I dunno (probably *could* disassemble it far enough to get to the battery)  Maybe just boot into the rom setup screen and saving changes would fix it.
[01:08] <last1> thanks, let me try that
[01:08] <rfm> last1, in any case it doesn't sound like a ubuntu problem, maybe ##hardware could help
[01:15] <last1> nope, same problem, maybe the ssd drive is hosed
[01:15] <last1> I reseated the battery and I get the same problem
[01:16] <last1> can I get ubuntu to boot my hard-drive but from the usb key somehow ?
[01:16] <last1> it boots just fine from usb, that's what I don't get
[01:17] <Bashing-om> last1: Have you ran a file system check on the root partition ?
[01:19] <last1> I didn't, I thought it did it automatically once it boots up
[01:19] <last1> I can boot again from the usb key
[01:19] <last1> is there anything else I can rewrite except the grub installed ?
[01:19] <last1> installer
[01:20] <Bashing-om> last1: From the USB key - so that the target is not mounted - run 'fsck' on the target partition. (sudo fdisk -lu to know that target name).
[01:21] <last1> ok, will do that now
[01:58] <last1> that fsck ran without issues, anything else I can rewrite on the main drive besides grub ?
[02:30] <last1> I also chose to boot in rescue mode and it appears to be doing something on Loading essential drivers...
[02:30] <last1> it's flashing on that line for like 10 minutes now
[03:09] <isapgswell> USC ubuntu software 7+ seconds delay
[03:10] <isapgswell> ubuntu 20.04.2
[03:10] <isapgswell> nvidia 460.73.1 ondemand profile
[03:11] <isapgswell> main apt server
[03:12] <isapgswell> snapstore 563MB
[03:12] <isapgswell> any idea?
[03:12] <isapgswell> internet 240Mb
[03:12] <isapgswell> link
[04:01] <MrMobius> I have cmake 3.16.3 installed and this script requires at least 3.18. how can I upgrade? sudo apt install cmake says I have the latest version
[04:32] <DumbLDoor> Anyone has an update on the EFI 1.10 issue? Can I update to 21.04 from 20.10 on an old system which does not support EFI variables?
[04:36] <DumbLDoor> Does it affect clean install or an upgrade too?
[07:31] <txtsd> Can someone help me fix my laptop? It keeps freezing for 5-10 seconds multiple times a minute.
[07:31] <txtsd> Here's a dmesg log: https://0x0.st/-aYB.log
[07:31] <txtsd> Please help me troubleshoot this
[07:31] <txtsd> It happens on stock kernel as well as liquorix kernel which it is currently running.
[07:31] <txtsd> Makes the system literally unusable.
[07:32] <txtsd> I can provide whatever logs y'all require to help me troubleshoot.
[07:37] <Maik> liquorix kernel isn't supported here afaik. As for the rest you'll have to wait for someone  with the right knowledge
[07:41] <txtsd> Then I'll switch back to stock for debugging
[07:42] <txtsd> The point is it happens regardless of which kernel I use
[07:42] <txtsd> CPU usage is normal, RAM usage is minimal, disk usage is minimal, and there isn't any other obvious thing that I could check that's causing the intermittent freezes
[07:43] <txtsd> It's running 20.10
[07:44] <possiblealian> made a new server-installation (2TB disc, no-UEFI, with GPT), but the HD didn't boot: "no bootable device found", tried different things: AHCI on/off; EFI on/off in CMOS-SETUP, nothing worked. last thing i did was install "hybride&protective MBR" with gdisk but with 2 times 0xEE type part-entries (!), now the system didn't even reach the CMOS-setup-press-F2-screeen, if that HD is connected on power ON!! in anoth
[07:44] <possiblealian> er system it just boot (old BIOS system)
[07:45] <possiblealian> can i clear the MBR in sector NULL, and this won't interfere with the GPT? like dd if=/dev/zero of=/dev/sda bs=512b count=1 ?
[07:45] <Maik> txtsd: swap full? any exotic video card in it, nVidia or AMD?
[07:45] <txtsd> Maik: SWAP is not even being used because RAM usage is not high at all.
[07:46] <txtsd> It has an AMD card and Intel iGPU.
[07:46] <Maik> hybrid? Then i'd search for bug reports on launchpad
[07:46] <possiblealian> txtsd: freezing could be caused by HD reallocation/read-retries, did u checked the smartctl -A /dev/sdX output? Run a smart-test long version
[07:47] <txtsd> But it worked smooth as butter when I first installed 20.04 a few months ago. I doubt it's graphics related.
[07:47] <txtsd> I'll try smartctl
[07:47] <Maik> why didn't you stick with 20.04 then
[07:47] <possiblealian> txtsd, i think dmesg would print out the reading errors, i'm not sure
[07:48] <txtsd> Because it previously had windows. It's actually my brother's laptop. Not mine.
[07:49] <Maik> that doesn't answer my question and it seems to get a bit weird imho. But ok
[07:49] <Maik> anyway, good look. I'm off to work. I hope someone else is able to help you
[07:52] <possiblealian> txtsd, check Reallocated_Event_Count in the -A output, also check the drives log: smartctl -l error /dev/sdX ; smartctl -l selftest /dev/sdX
[07:59] <polve> Hi. Would you rather recommend Virtualbox or Xen to an overall noob that aims at getting familiar with other distributions?
[08:00] <viktor_> polve: why would you use Xen?
[08:02] <polve> I just thought it being the first mentioned in [1] meant that it's super popular. 1: https://help.ubuntu.com/community/VirtualMachines
[08:05] <possiblealian> polve, virtualbox is better for fooling araound, xen is professional and better controlled via cmdl
[08:05] <viktor_> polve: i'm honestly not familiar, but just looking into it, it seems a lot more complex than Virtualbox. If you say yourself you're a noob and your goal is to try out other distro's, i'd definitifly recommend VB
[08:06] <polve> well maybe noob it's exaggerated, but still I think both of your observations are of point. Basically what I want to do is get familiar with RHEL based distros for job experience
[08:07] <polve> s/of point/on point/
[08:07] <siwica> Unfortunately my nvidia graphic card stopped working. When running `nvidia-smi` I get: "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." and I find the following line in dmesg: "Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7"
[08:07] <siwica> Kernel modules + drivers are installed and I think the problem is connected to secure boot being enabled.
[08:08] <siwica> Could anyone help me on that?
[08:09] <Bullrich> siwica: in my opinion u should switch to "legacy boot" thats all what i can say....
[08:10] <siwica> Bullrich: I tried this. This caused a lot of other problems: Touchpad not working, Wifi-connection got worse, Could not use my regular window manager, ...
[08:11] <siwica> Is there no way to get this working with secure boot
[08:11] <siwica> The whole thing is extremly frustrating and time consuming
[08:12] <Bullrich> well, i cant help you because i dont run Windows on my machines, only Linux
[08:12] <viktor_> siwica: how did you install the Nvidia driver?
[08:13] <siwica> Well I am running ubuntu...
[08:13] <siwica> viktor_: via ubuntu-drivers
[08:13] <viktor_> siwica: have you tried changing the driver?
[08:14] <siwica> It's on the most recent version. I also followed some other advise and installed all the respective kernel headers as well
[08:14] <siwica> The problem is that the kernel module cannot be loaded I think
[08:16] <viktor_> what's the driver called?
[08:16] <siwica> nvidia-driver-460
[08:22] <viktor_> siwica: how do you know the card stopped working?
[08:29] <siwica> viktor_: Well running `nvidia-smi` fails, I can't connect to my external monitor, ...
[08:40] <viktor_> siwica: switch to opensource driver for test and see if that works better
[08:47] <tuxinator> Hi everybody
[08:48] <tuxinator> Any reason why changelog for package nginx is unavailable?
[08:48] <tuxinator> See https://packages.debian.org/stretch/nginx
[08:48] <tuxinator> changelog link
[08:48] <tuxinator> also apt changelog nginx gives an error
[08:49] <tuxinator> the url it tries to open https://metadata.ftp-master.debian.org/changelogs/main/n/nginx/nginx_1.10.3-1+deb9u5_changelog
[08:58] <tuxinator> a guy on #debian helped out, it seems to be a known issue
[09:41] <Thaurwylth> I have the ExpressVPN Ubuntu client installed and recently I have noticed this: my laptop gets constant DNS errors if the ExpressVPN VPN is not set up. The name resolution errors happen on all possible services, including ping, Apt update, and web page browsing. The DNS problem appears both right after boot before ExpressVPN is started up, and after manually closing down ExpressVPN. There was an update
[09:41] <Thaurwylth> ...
[09:41] <Thaurwylth> ... recently, but this doesn't sound like an intended feature of a new version of ExpressVPN, huh?
[09:42] <Thaurwylth> Let's say this might be a problem that can be addressed from the system and not EVPN. What to try first?
[09:47] <Thaurwylth> Is the problem here, somehow? cat resolv.conf | #Generated by expressvpn | search expressvpn | nameserver <IP_ADDRESS>
[09:53] <ogra> Thaurwylth, definitely ... talk to the expressvpn deveelopers/support ...
[09:54] <ogra> *nothing* should touch resolv.conf directly ... that very likely clashes with the built in resolvers of the system
[09:55] <ogra> (instead it should talk to the respective resolver tool (systemd-resolved, dnsmasq, whatever else manages your resolution) to properly add/remove the expressvpn entries as needed
[09:55] <ogra> )
[09:59] <tuxinator> imho i hate the stuff like systemd-resolved etc. long live the oldstyle /etc/hosts
[10:00] <tuxinator> :D
[10:00] <tuxinator> and /etc/resolv.conf
[10:00] <tuxinator> Never had any issue with dns-configurations before all those unneeded dns-revold-daemons appeared :D
[10:06] <Thaurwylth> So should I not add some backup global DNS addresses there as a temporary fix? Other than that I guess I'll just have to wait till I get into their chat. I have a couple of other things to do right now so it'll take a while.
[10:10] <TheBigK> i have a lenovo thinkpad and the fwuptmgr tells me to update the intel management engine fw... but when i reboot nothing happens. any idea? i did change the boot order bringing linux firmware updater to the top but that seemed to not be the trick.
[10:21] <gebruiker> Ubuntu fonts are ugly espesially when browsing. How can I make it more like windows 10?
[10:22] <gebruiker> so my eyes stop bleeding
[10:29] <giaco> if I mount an sshfs directory and I move files inside that mount, will it copy back and forth the ssh client machine?
[10:40] <swensson> Know I've asked this before but now I got my workstation at work and it's more relevant. On windows there is a app "Your phone" Where I can connect to the phone from the computer to control it, use apps etc... Is there anything like that but for Ubuntu?
[10:46] <guiverc> gebruiker, change your fonts if you don't like them... https://www.omgubuntu.co.uk/2016/03/how-to-change-ubuntu-desktop-font or https://askubuntu.com/questions/19770/how-do-i-change-fonts-and-adjust-their-size or any of many sites available via a search online
[10:49] <PeGaSuS> swensson: probably scrcpy (https://github.com/Genymobile/scrcpy)?
[10:58] <kyentei> Hi! I'm trying to upgrade a bunch of Ubuntu VDIs from 18.04 to 20.04 remotely. Thus far I've tried "do-release-upgrade -f DistUpgradeViewNonInteractive" and setting the debian_frontend to noninteractive. But it seems as though they both crash on libc errors and require a dpkg reconfigure. Whereas when I run do-release-upgrade in a terminal myself, I get no crashes at all. Is there something I am overlooking?
[11:47] <Stoiss> Anyone using wickr ? Im having issues that i just cant even see my way around
[11:47] <Stoiss> Basically wickr wont start at all. It throws errors that ends with sigkill
[11:50] <swensson> Anyone have any tip for "Snipping tool" for ubuntu? Something like greenshot?
[11:52] <kyentei> @swensson flameshot
[11:54] <Stoiss> Anyone using wickr here ? Id like to see if its just me who simply cant make Wickr snap run on any linux platform.
[12:12] <FurretUber> Hi, I'm having a problem with Chromium: the first time it opens it takes 3 minutes until the window appear and, in nearly the entire time, it is using 100% CPU
[12:13] <FurretUber> I can see the flies slowly being generated at $HOME/snap/chromium/.cache/fontconfig
[12:14] <FurretUber> Firefox (deb) takes 20 seconds for the first startup. Is there a way to speed up the cache generation process for Chromium?
[12:14] <Deano59> FurretUber: you're using snap. reboot, and open with; https://github.com/iSc0ttyathon/custom-rpi4-os/blob/main/Chromium
[12:15] <EriC^> FurretUber: maybe try the repo version as Deano59 is suggesting, except use sudo apt-get install chromium not github
[12:16] <Deano59> EriC^: did you check the link? it's *also* installed with apt. there was a post over at ubuntu forums about it. makes chromium open/load faster. :)
[12:19] <EriC^> FurretUber: this might solve the issue, https://ubuntu.com/blog/the-hunt-for-rogue-time-how-we-investigated-and-solved-the-chromium-snap-slow-startup-problem
[12:20] <remline> Do flatpaks have the same startup performance issue that snaps have?
[12:22] <FurretUber> The chromium deb on 20.04 installs the snap too
[12:22] <BluesKaj> Hi folks
[12:27] <Deano59> FurretUber: do as I said above, problem solved. :)
[12:27] <FurretUber> Deano59: using that command, it opens quickly (8s vs. 160s on just booted). Is that bypassing the snap process and just opening the program?
[12:27] <Deano59> check ~about
[12:27] <FreeBDSM> I need some help with zfs after all. I have a disk sdb that lsblk weirdly shows of size 465.8G yet consisting of sdb1 (465.8G), sdb5 (2G), sdb6 (2G) and sdb7 (461.8G) which doesn't sum up to 465.8G :/
[12:28] <FreeBDSM> `parted -ls` shows it as 500GB with  `1      32.8kB  500GB  500GB  primary  zfs          boot`
[12:29] <FreeBDSM> and partition table: msdos
[12:29] <FreeBDSM> which is all so weird
[12:29] <FreeBDSM> I don't really remember what's on that disk and I wanted to mount it to peek
[12:29] <clarkk> I'm using 20.04. I have a .desktop file, in a directory in ~/Downloads. The file has execute file permissions and I've set the "Allow executing file as a program" setting. When I double-click on it, it opens in my text editor. I've right-clicked on it, and reset the "Open with" setting. It still opens with my text editor. Can anyone tell me how to make it run?
[12:30] <freddyb> hi folks. Any particular reason why I'm not offered the 21.04 download? afaiu the meta file in https://changelogs.ubuntu.com/meta-release isn't updated. - what's the current blocker? :)
[12:30] <FreeBDSM> I installed zfsutils-linux and none of the zfs-related commands I googled seem to return anything meaningful
[12:32] <freddyb> clarkk: AFAIU a .desktop file is not an executable. if you want gnome to recognize it as one of the installed application (e.g., in search & the dock) you need to install it with "desktop-file-install <path>"
[12:32] <remline> freddyb: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010
[12:34] <freddyb> remline: thank you. that looks like quite the blocker. is there a specific page you used to a search for a release that I could look at (for the broader part of the question)?
[12:35] <clarkk> freddyb, thank you for the help
[12:39] <FurretUber> I can see why I'm hitting this scenario so often: the user data is deleted on logout or reboot, so the caches are all deleted
[12:40] <remline> freddyb: I expect this bug represents a unique situation. i.e., the 21.04 release is done, but upgrades are not yet enabled.
[13:35] <tdm4> Hi.. does anyone know a way to automatically process files in /var/crash and get automatic backtraces of core dumps and have them emailed somewhere?
[14:06] <ksynwa> Can someone help me solve this issue I get while trying to install python3-dev? https://termbin.com/syg2
[14:06] <ksynwa> It says you have held broken packages but I checked and no packages are being held.
[14:07] <ksynwa> Earlier I tried to `dpkg --enable-architecture i386` then then removed it. Maybe it's causing that? But I don't know how to undo any damage it could have done.
[14:08] <leftyfb> ksynwa: ( cat /etc/os-release  ; apt-cache policy python3-dev ) | nc termbin.com 9999
[14:09] <ksynwa> leftyfb: First of all sorry for not mentioning the Ubuntu version. https://termbin.com/dlsw
[14:11] <leftyfb> ksynwa: apt-cache policy python3.8-dev | nc termbin.com 9999
[14:12] <leftyfb> ksynwa: your python3.8-dev should be up to 3.8.5-1~20.04.2 from focal-updates/focal-security
[14:12] <ksynwa> leftyfb: https://termbin.com/287h
[14:13] <leftyfb> ksynwa: try installing 3.8.5-1~20.04.2
[14:13] <leftyfb> er
[14:13] <leftyfb> python3.8-dev
[14:13] <ksynwa> Lemme try
[14:15] <ksynwa> This doesn't work either: https://termbin.com/xyrxe
[14:15] <ksynwa> Maybe I have messed up my sources list?
[14:16] <leftyfb> ksynwa: what did you do to the sources.list? The fact that it's complaining about libc means you headed in a very bad direction
[14:17] <ksynwa> I didn't do anything substantial that I can remember. --add-architecture and --remove-architecture as I said before. And added some PPAs.
[14:17] <ksynwa> But I must have done something to cause this. Don't think this would happen out of nowhere.
[14:18] <leftyfb> ksynwa: apt-cache policy libpython3.8-dev libexpat1-dev zlib1g-dev libc6-dev
[14:20] <ksynwa> leftyfb: https://termbin.com/tfqx
[14:20] <ksynwa> BTW thanks for giving some of your time. Really appreciate it.
[14:22] <leftyfb> ksynwa: in.archive.ubuntu.com   that is the issue
[14:23] <ksynwa> I can try changing mirrors
[14:23] <leftyfb> ksynwa: more specifically, that mirror is outdated. It's got 2.31-0ubuntu9 of the libc6-dev package where it should be 2.31-0ubuntu9.3
[14:24] <ksynwa> Ok thanks. I will try that. Meanwhile these are the enabled sources if you want to peruse: https://termbin.com/waz3
[14:27] <leftyfb> ksynwa: pick a different ubuntu mirror and run: sudo apt update # then you should be good
[14:27] <ksynwa> I did `s/in\.//` to /etc/apt/sources.list, updated and it still gives that error
[14:27] <leftyfb> ksynwa: though, I would run this right after, before installing anything else: sudo apt full-upgrade
[14:30] <leftyfb> ksynwa: please put in us.archive.ubuntu.com
[14:31] <leftyfb> ksynwa: I'm pretty sure just using archive.ubuntu.com uses your location to pick the best/closest mirror. In your case it might still be trying in.archive.ubuntu.com
[14:32] <ksynwa> Ok let's try
[14:38] <ksynwa> Still the same error
[14:38] <ksynwa> I think I will just reinstall
[14:38] <ksynwa> Ubuntu
[14:38] <ksynwa> Thanks for trying to help though. Really appreciate it.
[15:02] <LuckyMan> Good Afternoon, I have an energy problem on 21.04, when I start the computer and I don't login, after a while the screen is black and nothing seems to turn it on.
[15:04] <LuckyMan> I've even tried CTRL ALT F4 to go to tty4 and then CTRL ALT DEL but nothing happens
[15:04] <LuckyMan> screen keeps black, I had to hard reboot
[15:04] <LuckyMan> reset, I mean
[15:14] <lordcirth> LuckyMan, your hardware may have a bug with sleep. Try "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target"
[15:16] <LuckyMan> lordcirth, but I don't have sleep active on settings, this is a desktop
[15:17] <lordcirth> LuckyMan, Ok. Anything in logs? You may need to mkdir /var/log/journal to get persistent logs on desktop
[15:23] <LuckyMan> lordcirth, IDK what to look for
[15:25] <lordcirth> LuckyMan, whatever the last lines are before you rebooted it
[15:26] <LuckyMan> lordcirth, audit: type=1400 audit(1620656204.633:107): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=3271 comm="snap-confine" capability=4  capname="fsetid"
[15:27] <lordcirth> Yeah, that's not related
[15:27] <LuckyMan> before that I have rfkill: input handler enabled
[15:27] <LuckyMan> and Syncing filesystems and block devices.
[15:28] <LuckyMan> the first is Sending SIGTERM to remaining processes...
[15:28] <lordcirth> that SIGTERM is a clean shutdown
[15:29] <LuckyMan> that's strange because I did press the power button for more than 5 seconds
[15:29] <LuckyMan> and I got a Journal recovery message on start
[15:34] <ioria> LuckyMan, might be a lock screen issue rather than sleep
[15:34] <ioria> LuckyMan, try to disable it in Settings
[15:35] <tdm4> can Apport be configured to email backtraces (from gdb) of the coredumps?
[15:35] <tdm4> or at least the text logged someplace?
[15:36] <LuckyMan> ioria, doing that. Hope the issue goes away.
[15:37] <ioria> LuckyMan, logout, wait and see
[15:40] <LuckyMan> ioria, I'll do it later, I have course I'm doing running.
[15:40] <ioria> ok
[15:44] <tdm4> when I run apport-retrace -s on a .crash file I get the message: ERROR: report file does not contain one of the required fields: Package
[15:44] <tdm4> any idea how to fix?
[16:06] <lotuspsychje> tdm4: does it need the packagename of the bug or the bug ID perhaps>?
[16:09] <tdm4> lotuspsychje: I dunno.. it's just a php-fpm crash.. I wanted to get a gdb backtrace automatically logged somewhere for me to review later.. but apport-retrace doesn't seem to handle that properly
[16:09] <tdm4> it's not for an Ubuntu developer, per se.. it'd be more for our PHP developers
[16:10] <tdm4> only thing is, I don't think Ondrej Sury's PHP repo has the debug packages :/
[16:13] <lotuspsychje> tdm4: what about trying the -R option to rebuild the package?
[16:14] <lotuspsychje> tdm4: http://manpages.ubuntu.com/manpages/bionic/man1/apport-retrace.1.html
[16:15] <lotuspsychje> tdm4: and adding the dir might perhaps help too /var/crash/your-crash
[16:19] <tdm4> yeah I added the full path to the .crash file
[16:19] <tdm4> I'll try the -R option
[16:21] <tdm4> I take it --gdb can't be used non-interactively :)
[16:22] <lotuspsychje> tdm4: here was a command on a thread; apport-retrace --confirm --gdb --sandbox system --verbose --cache /my/path/cache/apport-retrace --output /mypath/apport-retrace/appname.1000.crash /var/crash/_usr_bin_appname.1000.crash
[16:26] <tdm4> lotuspsychje: --gdb can't be used with --output
[16:26] <tdm4> apport-retrace: error: argument -o/--output: not allowed with argument -g/--gdb
[16:38] <tdm4> well.. I ran: apport-retrace --confirm  --sandbox system --verbose --cache /root/.cache/apport-retrace --output /root/crash.log -R /var/crash/_usr_sbin_php-fpm7.
[16:39] <tdm4> (oops it truncated the path to the .crash file).. and it sits there for a while.. then comes back failed with: ERROR: Package download error, try again later: Untrusted packages: (and lists a whole bunch of -dbgsym packages)
[16:39] <tdm4> I guess apport-retrace just doesn't do what it says on the tin.. :/
[16:47] <TJ-> tdm4: do you have both the ddeb repo in sources lists, AND the ddeb signing keyring?
[17:00] <tdm4> TJ-: I think I'm missing deb-src for the main one
[17:00] <tdm4> so I guess I have to add that as well
[17:06] <gnutec> Just a clue. openspade <-- I have to shutdown the audio but is great.
[17:06] <gnutec> *openspades
[17:08] <warsoul> hello
[17:08] <warsoul> im currently using Ubuntu 20.04.2 LTS
[17:08] <warsoul> how do i upgrade to latest version
[17:09] <Walex2> warsoul: just 'apt dist-upgrade' for the latest version 20.04 LTS
[17:10] <warsoul> Walex2 im using 20.04
[17:10] <warsoul> 21.04 is not latest
[17:10] <warsoul> ?
[17:11] <Walex2> warsoul: it is the latest LTS version. If you are unfamiliar with Ubuntu staying on LTS is usually a good idea.
[17:12] <warsoul> whats the difference?
[17:13] <leftyfb> warsoul: to be clear, the in-place upgrade from 20.04 to 21.04 is not yet available. You'll either need to know what you're doing (not recommended) or reinstall 21.04 from scratch
[17:13] <Walex2> warsoul: https://askubuntu.com/questions/16366/whats-the-difference-between-a-long-term-support-release-and-a-normal-release
[17:13] <leftyfb> warsoul: 20.04 is supported till 2025 which 21.04 will be end of life in January
[17:13] <Walex2> warsoul: https://www.howtogeek.com/162768/should-you-use-ubuntu-lts-or-upgrade-to-the-latest-release/
[17:15] <warsoul> long term support think will be better lol
[17:15] <warsoul> thanks fam
[17:15] <tdm4> TJ-: which package do I need to install? I added ubuntu-dbgsym-keyring but I still get the untrusted packages list..
[17:16] <TJ-> tdm4: can you get that error just calling "sudo apt update" so we can isolate the issue?
[17:20] <tdm4> TJ-: no errors in apt update
[17:20] <TJ-> tdm4: hmmph! so it is specific to apport?
[17:21] <tdm4> but apport-retrace has the error: ERROR: Package download error, try again later: Untrusted packages: https://launchpad.net/ubuntu/+archive/primary/+files/apt-dbgsym_1.6.13_amd64.ddeb and others (apt-utils-dbgsym_1.6.13_amd64.ddeb, etc)
[17:21] <tdm4> about 65 packages
[17:21] <tdm4> yeah it's specific to apport
[17:22] <TJ-> tdm4: why is it trying to pull apt from launchpad? and v1.6.13 --- what ubuntu release are you on?
[17:22] <txtsd> I'm back to troubleshoot my laptop!
[17:22] <txtsd> https://bpa.st/DZIQ
[17:22] <txtsd> https://bpa.st/DPPQ
[17:22] <TJ-> !info apt xenial
[17:22] <txtsd> Is this serious?
[17:23] <TJ-> !info apt bionic
[17:23] <TJ-> aha
[17:23] <txtsd> My laptop keeps freezing intermittently
[17:23] <tdm4> TJ-: 18.04.5
[17:24] <tdm4> I'm using apport-retrace -R
[17:25] <TJ-> tdm4: I'm wondering why the .ddeb is trying to fetch from launchpad. I'd have expected that to be ddebs.ubuntu.com
[17:28] <tdm4> yeah I'm not too sure.. this just seems like too many hoops to jump through just to try and get an accurate php-fpm gdb backtrace :(
[17:28] <lotuspsychje> adding the bug ID it wants to interact with launchpad probably
[17:28] <TJ-> tdm4: I've got an 1804 container at the same state as your system should be. Can you show me what this reports "apt-cache policy apt-dbgsym"
[17:28] <TJ-> tdm4: here, the package is on ddebs.ubuntu.com
[17:33] <tdm4> N: Unable to locate package apt-dbgsym
[17:33] <tdm4> hmm
[17:34] <ioria> tdm4, how did you set the dbgsym repositories ?
[17:35] <TJ-> tdm4: I don't think you have the dbgsym archive added correctly. show us this: "pastebinit <( grep -rn ddeb /etc/apt/ )"
[17:36] <ioria> tdm4, you can use /etc/apt/sources.list  or /etc/apt/sources.list.d/ddebs.list
[17:37] <TJ-> tdm4: this is what it should be http://paste.ubuntu.com/p/YrfpnZZxjH/
[17:40] <tdm4> TJ-: empty
[17:40] <tdm4> I don't want to make huge sweeping changes to apt on this box.. I'll have to think of another way
[17:40] <tdm4> thanks for the help though!
[17:40] <TJ-> tdm4: so you don't have the dbgsym archive added
[17:41] <TJ-> tdm4: why? this isn't a huge change, just add the archive!
[17:41] <TJ-> it only gets used when you install a -dbgsym package
[17:42] <TJ-> once added just "apt update" to fetch the package lists and you're good to go
[17:46] <tdm4> ok I'll look into that thanks!
[18:06] <RJ45> qUwUestion; I am planning on building a new PC with an NVME SDD, will I face any issues if I just $ dd if=/dev/(sata_ssd) of=/dev/(nvme_ssd)
[18:07] <RJ45> also, current PC is AMD FX , new pc will be AMD Ryzen
[18:07] <lotuspsychje> RJ45: are they the same size?
[18:07] <TJ-> RJ45: yes, you'll need to tell the PC's firmware where to find the bootloader
[18:07] <RJ45> the NVME SSD will be 4 times larger than the SATA SSD
[18:08] <RJ45> TJ-: never had an issue like that when dd-ing between sata hdds
[18:08] <RJ45> is that an NVME thing?
[18:08] <TJ-> RJ45: I'd suggest being a bit more sophisticated, and preparing the NVME with LVM first
[18:08] <TJ-> RJ45: no, it is a UEFI thing
[18:08] <TJ-> RJ45: if the new PC still uses BIOS/CSM/Legacy boot then it should be OK
[18:09] <RJ45> are you trying to say, simply go into UEFI BIOS, and set the NVME SSD as the 1st boot option?
[18:09] <TJ-> RJ45: but... before you go ahead you need to compare the logical/physical sector sizes of the source and destination devices to ensure they match
[18:09] <RJ45> 'cos if you're trying to say that, yo made it sound way more complicated than it is
[18:09] <TJ-> RJ45: no, you'd need to add an entry to the UEFI menu using Linux's efibootmgr tool
[18:10] <Walex2> RJ45: duplicating by 'dd' of the whole thing will obviously succeed, but there are many corner cases and as "TJ-" says your existing SATA might not be bootable in a EUFI way.
[18:10] <RJ45> TJ-: dafuk
[18:10] <RJ45> never had-to do that on UEFO boards in the past
[18:10] <RJ45> uefi*
[18:10] <Walex2> RJ45: another corner case happens with duplicate UUIDs.
[18:10] <TJ-> If the SATA has an EFI-SP, it will only be booted in UEFI mode if there's a removable-media path boot loader installed (/EFI/BOOT/BOOTX86.EFI) if the firmware doesn't have a menu entry for the OS
[18:11] <Walex2> RJ45: in some cases duplicate UUIDs or labels for filesystems will cause problems.
[18:12] <Walex2> RJ45: if one of the partitions is a MS-Windows system partition there are additional considerations, also related to UUIDs.
[18:13] <TJ-> If SATA currently boots using BIOS/UEFI-CSM *and* the sector sizes match, then the NVME should boot if the new PC also has CSM enabled
[18:13] <Walex2> TJ-: good points!
[18:13] <RJ45> Walex2: I can't imagine that'll be an issue for me at-all, I'd be doing the  dd  operation booted from a live USB, and will be wiping the old SSD after
[18:14] <Walex2> RJ45: you don't need to wipe the old SSD, just they should not be booted at the same time to be sure,
[18:14] <TJ-> *connected at the same time
[18:14] <RJ45> Walex2: noted
[18:14] <maxFlexGuest> How do I list the number of installed fonts on Ubuntu Linux? (I have tried fc-list, but that command listed the names of the fonts and not the total number)
[18:15] <Walex2> RJ45: I would personally do it the safe way and partition and prepare the NVME, and then 'dd' each partition separately.
[18:15] <TJ-> maxFlexGuest: pipe the output through wc -l as in "fc-list | wc -l"
[18:15] <TJ-> maxFlexGuest: that assumes fc-list only outputs a single line per font, and no other info at all
[18:16] <Walex2> RJ45: or even just 'rsync -axHOAXJ' them. between flash devices that is going to be very fast, especially writing to an NVME SSD.
[18:17] <Walex2> that's how I do my backups too.
[18:18] <lotuspsychje> maxFlexGuest: there's a handy fontmatrix package, but not sure it counts total
[18:18] <RJ45> Walex2: if I manually prepared the partitions after formatting the partition table, wouldn't I then have-to re-install GRUB using a special tool on a live USB?
[18:20] <TJ-> RJ45: not if it is UEFI - the EFI-SP is just a FAt file-system
[18:20] <TJ-> RJ45: but, as we said earlier, for UEFI boots you'll have to run 'efibootmgr' in order to add the OS entry to the firmware boot menu
[18:20] <RJ45> huh?
[18:21] <remline> Fontmatrix Програма для керування шрифтами у Linux
[18:21] <RJ45> UEFI doesn't boot to GRUB?
[18:21] <TJ-> In UEFI, boot files are regular PEs on a FAT file-system, not hidden away as in BIOS/MBR
[18:21] <RJ45> it just has its own boot menu?
[18:22] <RJ45> well that sounds like a feature that was intended to be simple, but in reality is frustratingly annoying
[18:22] <TJ-> RJ45: UEFI has a boot manager built in, that is stored in NVRAM, each entry points to the location of the boot-loader for the OS, in the case of GRUB/Linux it'll point to something like /EFI/ubuntu/shimx64.efi (or grubx64.efi)
[18:23] <TJ-> RJ45: this allows one to have multiple OSes without them overwriting each other fighting for sector 0 or whatever, as we had with BIOS mode boot
[18:24] <TJ-> e.g. with Windows dual boot there will also be an /EFI/windows/efibootldr.efi or some-such (note the different path in the EFI-SP)
[18:24] <remline> fontmatrix malloc(): unaligned tcache chunk detected Aborted
[18:24] <RJ45> TJ-: we already had that feature before UEFI, it's called re-installing grub
[18:24] <TJ-> No
[18:25] <RJ45> grub is the best bootloader
[18:25] <TJ-> In BIOS mode each boot-loader on the same device overwrote any previous boot-loader's bootstrap code in sector 0
[18:25] <TJ-> so last installed always boots
[18:26] <TJ-> UEFI prevents any overwriting and allows all OSes to sit alongside each other without fighting
[18:26] <RJ45> yeah, then simply boot into a live USB and update grub
[18:27] <remline> lotuspsychje: Thanks for the recommendation, fontmatrix looks pretty neat. I had been trying font-manager, which was underwhelming.
[18:28] <RJ45> if every OS after 2010 just agreed to use only grub, this wouldn't need to be a UEFI feature
[18:29] <lotuspsychje> remline: welcome, someone of the volunteers is dev of it, reccomended to me once
[18:30] <remline> lotuspsychje: Alright, if he returns, I'll send him my bug report. ;)
[18:56] <wuzamarine> I cannot initialize my builtin microphone  https://askubuntu.com/questions/1337235/no-microphone-exist-on-a-brand-new-inspiron-5509 I think I am mssing a driver. arecord -l shows input devices.
[18:57] <wuzamarine> How do I turn my microphone on?
[19:01] <Walex2> wuzamarine: depends, try looking at 'alsamixer' and/or 'pavucontrol'
[19:02] <wuzamarine> Walex2: I tried both
[19:02] <Walex2> wuzamarine: then try to ask more informative questions...
[19:04] <wuzamarine> Walex2: I apologize. But all that info is in the URL I posted
[19:04] <Walex2> try to ask in #ALSA with a better worded question.
[19:04] <wuzamarine> That's what the url is for. It has all the details
[19:05] <Walex2> wuzamarine: then you should have said that "I don't want to wait to an answer on ASkUbuntu and all the details are there"
[19:05] <Walex2> but #ALSA is probably the best place.
[19:06] <wuzamarine> Any place I ever go wants the full details in a bpaste or better.
[19:13] <wuzamarine> fuck it, I'll just delete the os
[19:13] <Steauxback> Hi
[19:14] <dev4449> Hi, Steauxback
[19:16] <Steauxback> I have an issue with package distro-info-data on Ubuntu 18.04 and not sure where I should report it? http://security.ubuntu.com/ubuntu bionic-updates/main amd64 distro-info-data all 0.37ubuntu0.9 seem to have been replaced by distro-info-data_0.37ubuntu0.10_all.deb 22-04-2021 but even after apt-get update it still try to grab the old one.
[19:17] <sarnold> Steauxback: how about sudo apt update && sudo apt install distro-info-data  ?
[19:19] <TJ-> !info distro-info-data bionic
[19:20] <Steauxback> issue stay with sudo and when running as root, if I go on an installation that already have the package and do apt install --reinstall distro-info-data I am getting the issue too
[19:20] <bumblefuzz> I'm booted into an ubuntu livedisk and try to format a brand new hard drive
[19:20] <bumblefuzz> and I'm getting errors I don't understand
[19:21] <bumblefuzz> if I try to delete partitions, I get `failed to read partition table on device`
[19:21] <TJ-> Steauxback: what repository server(s) are your apt sources.lust pointing to? could it be a mirror that is behind?
[19:22] <bumblefuzz> if I try to format disk I get `error synchronizing after initial wipe: timed out waiting for object`
[19:22] <TJ-> bumblefuzz: whaat tool are you using to do that?
[19:22] <bumblefuzz> the disks app
[19:22] <bumblefuzz> got any fancy CLI stuff for me to try?
[19:22] <TJ-> bumblefuzz: don't know it. Not gPartEd then?
[19:23] <TJ-> bumblefuzz: it sounds rather like an I/O error so I'd check the kernel log "journalctl -k -f" in a terminal then retry the commands and see what appears in the logs, if anything
[19:23] <bumblefuzz> gparted gives an error too
[19:24] <Steauxback> I get the error on a different mirror each time I run it. my sources :
[19:24] <Steauxback> deb http://azure.archive.ubuntu.com/ubuntu/ focal main restricted
[19:24] <Steauxback> deb http://azure.archive.ubuntu.com/ubuntu/ focal-updates main restricted
[19:24] <Steauxback> deb http://azure.archive.ubuntu.com/ubuntu/ focal universe
[19:24] <Steauxback> deb http://azure.archive.ubuntu.com/ubuntu/ focal-updates universe
[19:24] <Steauxback> deb http://azure.archive.ubuntu.com/ubuntu/ focal multiverse
[19:24] <Steauxback> deb http://azure.archive.ubuntu.com/ubuntu/ focal-updates multiverse
[19:24] <bumblefuzz> it says it can't inform the kernel of the change
[19:25] <bumblefuzz> if I create a partition table or a partition, it says it wrote it to the device but it can't inform the kernel of the change
[19:25] <bumblefuzz> it's a brand new drive, why am I getting errors?
[19:25] <dev4449> bumblefuzz: Are you sure about the physical health of your drive?
[19:25] <bumblefuzz> it's brand new
[19:26] <dev4449> bumblefuzz: It seems like a broken hard drive
[19:26] <bumblefuzz> can I check?
[19:26] <TJ-> bumblefuzz: that means something else has a reference to the device
[19:26] <TJ-> bumblefuzz: can you show us "pastebinit <( journalctl -k )"
[19:27] <sarnold> msg Sigyn unkline Steauxback
[19:27]  * TJ- hands sarnold  a /
[19:28] <sarnold> TJ-: alas it wasn't the only thing I missed :) hehe
[19:29] <bumblefuzz> the device I was trying it on isn't connected to the internet
[19:29] <bumblefuzz> lemme try this one
[19:31] <bumblefuzz> this device worked
[19:31] <bumblefuzz> it appears the livedisk is acting up
[19:31] <steauxback> hi again
[19:32] <bumblefuzz> how can I check the health of the drive?
[19:37] <TJ-> bumblefuzz: install smartmontools and then "sudo smartctl --all /dev/sdX" to see the overview of the SMART data
[19:39] <bumblefuzz> TJ- https://paste.ubuntu.com/p/tQWpWF5Q8S/
[19:40] <TJ-> bumblefuzz: nothing apparently wrong there
[19:40] <bumblefuzz> does that check everything?
[19:41] <bumblefuzz> I'll try it again on the livedisk
[19:41] <TJ-> bumblefuzz: it's the device's internal monitoring
[19:42] <bumblefuzz> yeah, now it's saying failed to meet partition size on device
[19:43] <bumblefuzz> trying it again on the laptop
[19:43] <bumblefuzz> laptop says the same thing
[19:43] <bumblefuzz> lemme try gparted
[19:44] <bumblefuzz> ok gparted is reading the device as 953869 MB
[19:45] <bumblefuzz> while disks is read the device as 1,000,204,886,016 bytes
[19:45] <bumblefuzz> ?
[20:04] <RedNifre> How do I add custom fonts to the terminal? It doesn't let me choose from all fonts that I have installed.
[20:11] <rifle> Hi!  I've a bit of a problem that I don't know how to get out of.
[20:12] <rifle> I've an older version of 20.10 installed (last used in December).  I'm trying to update it to the latest iteration of 20.10, but cannot because it wants to restore linux-headers-5.8.0-31-generic ... which doesn't exist any longer in the archives
[20:12] <rifle> s/restore/reinstall
[20:13] <ravage> You did try apt update?
[20:13] <rifle> yes
[20:13] <ravage> Uninstall the package
[20:14] <rifle> I'm presenting running the kernel 5.8.0-31
[20:14] <ravage> If it is an older headers package you don't need it anyway
[20:14] <ravage> I'm sure you will get a newer one anyway
[20:15] <rifle> every single thing I try to do... I see 'E: The package linux-headers-5.8.0-31 needs to be reinstalled, but I can't find an archive for it.'
[20:15] <physikoi> hi #ubuntu. I'm trying ubuntu server 20 in virtual box. All was good until after I installed Guest Additions. What happens now is that instead of loading me into a shell, i'm presented with a basic GUI where I can login. It looks like this
[20:15] <physikoi> https://www.icloud.com/iclouddrive/09HYfjDIurT9c7saHvn8klbyA#Screen_Shot_2021-05-10_at_3.39.10_PM
[20:16] <leftyfb> !yy.mm | physikoi
[20:16] <physikoi> If i click on the "activities" tab at the top, i get some other options, including a link to dashboard menu of apps. None of these apps seem to launch. What is this? Some minimalized ubuntu desktop? How do i get back to loading into shell on boot? Thank you!
[20:17] <physikoi> I did try asking at #vbox, but no response. I'm wondering if this is just an ubuntu thing I don't get.
[20:18] <sarnold> rifle: the usual approach is to apt-purge that package, then apt-purge whatever package complains next, etc, and repeast that a few times -- and then you'll be able to reinstall whatever meta-package you need for your kernel, and that'll work again pretty quick
[20:18] <jjbuggle> I'm getting this error from software updater: grub-efi-amd64-signed: Depends: grub2-common (>= 2.02~beta2-36ubuntu3.31) but 2.04-1ubuntu26.11 is to be installed
[20:19] <sarnold> physikoi: I can't get that image thingy to work, maybe try imgur?
[20:19] <jjbuggle> I don't understand it.  I might be able to run apt-get upgrade from cli.  Should I just do that? or try to report the error as a bug?
[20:19] <physikoi> sarnold: trying now
[20:20] <leftyfb> jjbuggle: which version of ubuntu?
[20:20] <leftyfb> sarnold: ^ this could be a VERY big bug that I ran into this weekend and haven't had time to dig into
[20:20] <jjbuggle> leftyfb: xubuntu 20.04
[20:21] <leftyfb> hm, maybe bot
[20:21] <leftyfb> not*
[20:21] <physikoi> https://imgur.com/a/yviAndD
[20:21] <leftyfb> I ran into this issue with 16.04. I had to enable the proposed repo to get the proper packages updated
[20:21] <jjbuggle> leftyfb: an upgrade from 18.04.  Fresh install of 18.04, but a 10+ year old /home directory
[20:21] <rifle> sarnold: I found a dpkg command that seems to have helped.  `dpkg --remove --force-remove-reinstreq linux-headers-5.8.0-31`
[20:22] <sarnold> leftyfb: it's strange, I tripped over something very similar on one of my boxes that I ignore for ages.. I wound ujp needing to uninstall all the way to the main linux-generic package. I figured I'd just ignored that machine for way too long
[20:22] <leftyfb> sarnold: I'm referring to jjbuggle's issue
[20:22] <sarnold> physikoi: sheeeesh, that's *confusing* :)
[20:22] <sarnold> leftyfb: oh :) heh, sorry
[20:22] <rifle> sarnold: then I ran `apt --fix-broken install`
[20:22] <rifle> It's processing now.
[20:23] <rifle> but better than constantly getting an error
[20:23] <sarnold> rifle: woo, that might be way easier if that works out :)
[20:23] <physikoi> sarnold: yeah, i don't get it. I'm very familiar with macos and *nix terminal, but not ubuntu gui
[20:24] <rifle> It may have worked
[20:24] <rifle> I'm not getting blocked on updating now
[20:24] <sarnold> leftyfb: so, ,with jjbuggle's issue, I was wondering if those version numbers indicate mixed apt source lines, eg both focal and xenial configured at once, or something ismilar
[20:25] <leftyfb> sarnold: it wasn't in my case. In fact, the installer failed for basically the same issue when told to download updates during the install
[20:25] <jjbuggle> leftyfb: well, I'm looking at the package info, best as I know how, with apt-cache policy/show/depends, and I can't even find the problematic dependency.  It just looks like Software Updater is confused.  Anyway, thanks for talking with me.  I might just try ubuntu-bug on software updater, and let that program catch whatever it can, and call it a day.  apt-get looks like it might be fine
[20:25] <sarnold> leftyfb: eek.
[20:25] <leftyfb> sarnold: I need to get around to replicate this issue and report the bug, I'm just swampped. But if it's a bug, it's a doozy
[20:25] <leftyfb> jjbuggle: try enabling the proposed repo
[20:26] <sarnold> jjbuggle: could I get you to run ubuntu-bug grub-efi-amd64-signed   before enabling that repo? it'd be nice to capture one 'clean' bug report before trying to troubleshoot the solution
[20:26] <jjbuggle> woops, I already enabled it.  I can just disable it though
[20:27] <TJ-> !info grub2-common bionic
[20:27] <leftyfb> sarnold: the only way I could get the installer to work was to not enable networking. When the system booted, if I ran update/full-upgrade, I got the same failure. Enabling proposed got me by it
[20:28] <leftyfb> sarnold: granted, this was on xenial
[20:29] <physikoi> thanks, but gotta log out
[20:32] <TJ-> jjbuggle: see this https://askubuntu.com/questions/1335521/ubuntu-20-04-upgrade-failure-concerning-grub-efi-amd64-signed
[20:33] <TJ-> what is weird is where it is getting the dependency from
[20:33] <jjbuggle> TJ-: yeah, that's it.  And I also find that weird.  I alread have 2.04 installedd, so I don't even understand what the error is saying.
[20:34] <TJ-> jjbuggle: can you show use "pastebinit <( apt-cache show grub-efi-amd64-signed ) "
[20:34] <jjbuggle> I feel like this is a bug in software-updater
[20:34] <rifle> sarnold: Looks like that did the trick for me today.  After upgrading and rebooting, I'm no longer on the 5.8.0-31 kernel.
[20:34] <jjbuggle> TJ-: https://paste.ubuntu.com/p/KP6tbrXz2z/
[20:35] <TJ-> aha " Depends: grub-efi-amd64-bin (= 2.04-1ubuntu44), grub-efi-amd64 | grub-pc, grub2-common (>= 2.02~beta2-36ubuntu3.31)"
[20:35] <sarnold> rifle: wonderful, thanks for reporting back :)
[20:36] <TJ-> on my updated 20.04 install I see " grub2-common (= 2.04-1ubuntu26) "
[20:37] <rifle> sarnold: for the record... that was `dpkg --remove --remove-roce-reinstreq pkg_name` followed by `apt --fix-broken install`
[20:37] <rifle> sarnold: then I could `apt upgrade` without issue
[20:38] <rifle> sarnold... typo.  `dpkg --remove --remove-force-reinstreq pkg_name`
[20:38] <jjbuggle> sarnold: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1928011               sorry it took awhile.  I had to track down my password
[20:39] <bumblefuzz> how do I run an app as sudo?
[20:39] <jjbuggle> bumblefuzz: what app?
[20:39] <bumblefuzz> system profiler
[20:40] <jjbuggle> bumblefuzz: is this not on cli?
[20:40] <bumblefuzz> if it is, I don't know it
[20:40] <bumblefuzz> that's why I asked
[20:40] <bumblefuzz> and there's no obvious way to run a GUI app as sudo
[20:40] <bumblefuzz> so I'm stuck
[20:40] <TJ-> jjbuggle: leftyfb  sarnold  I can see the problem. it's the onegrub builds for i386 going back to 16.04 ... the updater is picking the FIRST in the list which is for Version: 1.167+2.04-1ubuntu44
[20:41] <TJ-> bumblefuzz: "pkexec ..."
[20:42] <sarnold> jjbuggle: excellent, thanks
[20:43] <bumblefuzz> what do I do with pkexec?
[20:43] <dostoyevsky> Any idea how I could get libboost1.71-all-dev on ubuntu 18.04?  It's available for 20.04 but not for 18.04 in the default repos
[20:44] <jjbuggle> bumblefuzz: how did you get this system profiler?  I'm just not familiar with the program
[20:44] <sarnold> dostoyevsky: I'd try to use backportpackage to rebuild that package, it feels like it'd work out okay
[20:44] <bumblefuzz> it's in the app store
[20:44] <bumblefuzz> under 'system profiler'
[20:45] <bumblefuzz> why is it so hard to run a GUI app as sudo?
[20:45] <jjbuggle> bumblefuzz: "System Profiler and Benchmark"?
[20:45] <bumblefuzz> yes
[20:46] <jjbuggle> bumblefuzz: personally, I would just do: gksu hardinfo            from a terminal
[20:46] <bumblefuzz> is hardinfo system profiler?
[20:46] <sarnold> bumblefuzz: because none of the tooling was designed to let you do that
[20:46] <TJ-> bumblefuzz: pkxec is an alternative/replacement for sudo (Policy Kit Exec) and given the path to an executable it'll prompt for a password (with a GUI if using desktop)
[20:46] <jjbuggle> bumblefuzz: yeah, that's what I see is the name looking at my app store, for System Profiler and Benchmark
[20:47] <bumblefuzz> gksu throws an error
[20:47] <bumblefuzz> some GUI apps need to be run as sudo
[20:47] <bumblefuzz> wireshark
[20:47] <TJ-> oops, pkexec even
[20:47] <leftyfb> TJ-: should you add your grub finding to the bug?
[20:47] <TJ-> bumblefuzz: wireshark does not; there's an option to add your user to a group that gets the privileges
[20:48] <jjbuggle> bumblefuzz: maybe try pkexec, or just use sudo.  I don't know.  I thought gksu was safer for gui apps
[20:48] <bumblefuzz> still, if I want to run a GUI app as sudo, it shouldn't be this hard
[20:48] <TJ-> leftyfb: I'm busy trying to repair my 12 year old linux repo
[20:48] <bumblefuzz> gksu doesn't work
[20:48] <TJ-> bumblefuzz: it isn't as 'sudo' it's 'as root' and the tool is pkexec
[20:48] <jjbuggle> bumblefuzz: it usually isn't.  hardinfo might just not be setup that well
[20:49] <bumblefuzz> ok got it
[20:49] <bumblefuzz> I just ran 'sudo hardinfo'
[20:49] <bumblefuzz> thanks
[20:59] <bumblefuzz> ok, I was able to write a new partition table and partition to this drive
[21:00] <bumblefuzz> but it seems undersized
[21:00] <bumblefuzz> it's supposed to be 1TB
[21:00] <bumblefuzz> how can I check if it's 'missing' any space?
[21:05] <jjbuggle> bumblefuzz: did you buy this drive recently? as a 1 TB?
[21:05] <bumblefuzz> yeah
[21:05] <bumblefuzz> microcenter just a week or two ago
[21:05] <TJ-> bumblefuzz: drives are measured in base 10 but many tools report in base 2 - base 2 values are larger than base 10
[21:06] <bumblefuzz> I know the diff b/t gigabytes and gibibytes
[21:06] <TJ-> bumblefuzz: so what are the numbers you're concerned about?
[21:06] <bumblefuzz> I'm trying to figure why disks shows one size and gparted shows another
[21:06] <bumblefuzz> and df -h shows another
[21:07] <jjbuggle> bumblefuzz: how much is missing?
[21:09] <TJ-> capacity is 1,000,204,886,016 bytes
[21:10] <TJ-> which is 931GiB
[21:11] <bumblefuzz> `df -h` https://paste.ubuntu.com/p/pPJ8WdRDvD/
[21:11] <bumblefuzz> 870G available?
[21:16] <bumblefuzz> and it says only 916GB total
[21:16] <bumblefuzz> ?!
[21:16] <jjbuggle> bumblefuzz: does ls -al list anything in the folder?
[21:16] <TJ-> on large file-systems the reserved blocks will be a large chunk. If it is ext see "dumpe2fs -h /dev/sda1"
[21:16] <bumblefuzz> no, I *just* formatted it
[21:17] <bumblefuzz> it's a single, empty partition
[21:18] <bumblefuzz> https://paste.ubuntu.com/p/btPMDnBzgj/
[21:19] <TJ-> 5% is reserved for UID 0... 5% x 916G = 45.8G. 916 - 45.8G = 870.2G
[21:19] <bumblefuzz> UID?
[21:19] <TJ-> root
[21:19] <bumblefuzz> also, why is it 15G lower than the gibibyte value?
[21:19] <TJ-> user ID 0
[21:20] <bumblefuzz> 930-15=916GB
[21:20] <bumblefuzz> sorry just trying to understand
[21:20] <TJ-> used elsewhere presumably or spare space
[21:20] <dostoyevsky> I did `sudo add-apt-repository ppa:ubuntu-toolchain-r/test' but it doesn't seem to contain `libboost1.71-all-dev' --- not sure how I could get the package of ubuntu 20 in 18
[21:21] <bumblefuzz> ok, well thanks with this
[21:21] <TJ-> we're looking at partition 1... we cannot see what surrounds that
[21:21] <jjbuggle> TJ-: I'm copying your comment to my bug report.  I don't know how you see what you see   :)
[21:21] <TJ-> jjbuggle: eyes :)
[21:21] <TJ-> jjbuggle: simple grep!
[21:22] <jjbuggle> TJ-: lol, no, I mean, from earlier, the comment about onegrub builds
[21:22] <jjbuggle> TJ-: or is that what you are talking about?  lol, I don't see any references
[21:23] <TJ-> jjbuggle: that was from reading the changelog "less /usr/share/doc/<package-name>/changelog.Debian.gz"
[21:23] <godane> !ao https://www.republicworld.com/india-news/general-news/chinas-coronavirus-weaponisation-report-fuels-questions-on-covids-resurgence-mutants.html
[21:23] <godane> sorry
[21:23] <TJ-> jjbuggle: "...to make it available in bionic and earlier as part of onegrub builds"
[21:24] <TJ-> jjbuggle: from "less /usr/share/doc/grub-efi-amd64/changelog.Debian.gz "
[21:25] <TJ-> jjbuggle: alternatively, "apt-get changelog <package-name>" but that has to go out on the net, and it fetches the entire changelog from year zero, whereas the one on the system is nicely truncated to a reasonable length
[21:26] <jjbuggle> TJ-: thanks, I'm taking a look
[21:29] <jjbuggle> TJ-: ah, omg, well, one reason I don't see what you see is that I haven't upgraded yet, so my local changelogs don't have that last comment
[21:30] <jjbuggle> TJ-: anyway, thanks for the education
[21:31] <TJ-> jjbuggle: ahhh! then Changelog link on the right here https://packages.ubuntu.com/focal-updates/grub-efi-amd64
[21:31] <jjbuggle> TJ-: no, I already can see it, with the apt-get changelog command
[21:31] <TJ-> jjbuggle: ahh yeah, of course, that fetches the same thing, silly me ^^^ but this is useful to know
[22:50] <nerdcore> trying to upgrade 18.04 => 20.04 using `do-release-upgrade` I'm getting this; any ideas? https://paste.ubuntu.com/p/rkkz3N6kgp/
[23:01] <TJ-> nerdcore: try this "python3 -m pip uninstall distro-info"
[23:02] <TJ-> nerdcore: it looks like there's a version of distro-info masking the proper one; this command will remove it, if it exists
[23:02] <TJ-> nerdcore: if that does remove the package, then do "sudo apt reinstall python3-distro-info"
[23:03] <sarnold> TJ-: oh wow, that'll be some serious good crystal ball work if that's it :)
[23:12] <DumbLDoor> Hi everyone! Anyone has anything on upgrade to 21.04 on "non-UEFI" systems?
[23:18] <nerdcore> TJ-: looks good, thanks!
[23:18] <TJ-> nerdcore: working now?
[23:20] <nerdcore> yeah seems alright
[23:26] <skeeter> Can anyone pushing in the right direction? I am attempting to open a port for external access. I have opened the port within the router and sudo ufw allow <port-number> - But still not gaining access?
[23:27] <sarnold> skeeter: you'll need to address every firewall between the two computers, and if there's any NAT firewalls between them, those might need some configuration as well
[23:32] <skeeter> sarnold, NAT is enabled on the router, I will look that over
[23:33] <sarnold> skeeter: are you trying to contact this ip,port from 'within' the local network? or are you trying to traverse that NAT router / firewall, too?
[23:33] <skeeter> External - It's a IRCD
[23:34] <skeeter> Local is working fine.
[23:35] <sarnold> skeeter: is it running on 'typical irc' ports? I wouldn't be surprised if an ISP blocks those for incoming use
[23:36] <skeeter> For example 6667
[23:36] <skeeter> That's what I am trying for
[23:36] <sarnold> if nothing else is making sense, do consider that your isp might be blocking it
[23:37] <skeeter> ok good information
[23:37] <sarnold> (no need to jump to that conclusion right away! but if you're stuck, it's a possibility)
[23:42] <DumbLDoor> Hi everyone! Anyone has anything on upgrade to 21.04? I have an old Gigabyte Z-68 chipset with the latest BIOS firmware.
[23:43] <leftyfb> DumbLDoor: can you rephrase your question?
[23:44] <DumbLDoor> lefty: I am trying to upgrade my 20.10 groovy gorilla to 21.04 H H. There are multiple websites asking to hold on that till the shim package is fixed for a certain bug which renders chipsets with EFI 1.10 and earlier versions unbootable
[23:44] <skeeter> sarnold, another question, I cannot ping my linux to windows or windows to linux machine. Both on the same network. Why?
[23:45] <leftyfb> DumbLDoor: you mentioned non-UEFI. If your system is non-UEFI, then an EFI bug won't affect you
[23:45] <sarnold> DumbLDoor: I believe some vendors encode the efi version somewhere, you can check with dmesg | grep -i efi , and see if yours reports a version
[23:46] <sarnold> skeeter: some wifi router things have a "protect wireless clients" button or osmething similar that drops a lot of that kind of traffic even within one network
[23:46] <sarnold> skeeter: can you ssh to them or http to them or similar?
[23:46] <DumbLDoor> leftyfb: i get two lines o/p : clocksource and tsc
[23:47] <leftyfb> DumbLDoor: I have no idea what you're talking about
[23:47] <DumbLDoor> leftyfb :  [    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>211568 ns
[23:47] <DumbLDoor> [    1.316048] tsc: Refined TSC clocksource calibration: 3410.013 MHz
[23:47] <leftyfb> !paste | DumbLDoor
[23:48] <leftyfb> DumbLDoor: What commands are you running for these lines to show up exactly?
[23:48] <DumbLDoor> https://paste.ubuntu.com/p/3ZmV64Z8pp
[23:48] <leftyfb> DumbLDoor: those look like kernel messages, not necessarily error messages
[23:49] <DumbLDoor> leftyfb: What does it mean in my sys upgrade context?
[23:49] <leftyfb> DumbLDoor: what exactly are you trying to accomplish and how are you trying to accomplish it? The do-release-upgrade for 20.10 to 21.04 isn't available as of yet as far as I know
[23:50] <DumbLDoor> leftyfb: The system gave me an option to upgrade to 21.04 and I canceled
[23:53] <TJ-> DumbLDoor: try this to identify the version " journalctl -k | grep EFI.*v "
[23:54] <TJ-> DumbLDoor: e.g. I get a line that shows "efi: EFI v2.70 by Lenovo"
[23:54] <leftyfb> DumbLDoor: journalctl -k | grep EFI.*v | nc termbin.com 9999
[23:54] <DumbLDoor> leftyfb: nothing
[23:55] <leftyfb> DumbLDoor: please copy and paste the termbin.com URL here from the command
[23:55] <TJ-> DumbLDoor: how about "journalctl -l | grep DMI:"
[23:55] <TJ-> oops,  typo
[23:55] <TJ-> DumbLDoor: how about "journalctl -k | grep DMI:"
[23:56] <DumbLDoor> tj, leftyfb: DMI: Gigabyte Technology Co., Ltd. Z68MX-UD2H-B3/Z68MX-UD2H-B3, BIOS F12 10/12/2011
[23:56] <TJ-> DumbLDoor: judging by the age it could be v1.x but we'd need to look deeper
[23:58] <DumbLDoor> TJ: ls: cannot access '/sys/firmware/efi': No such file or directory... BIOS system, no EFI?
[23:59] <TJ-> DumbLDoor: that or simply booted in BIOS mode, which'd explain why there's no EFI message
[23:59] <TJ-> DumbLDoor: I'm looking at the firmware upgrades and it seems to be UEFI


[16:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/06/%23ubuntu-classroom.html following the conclusion of the session.
[16:01] <phillw> Hi and welcome to an introduction to bugs
[16:02] <phillw> this session will run over the different types and the systems used to report them
[16:02] <phillw> Firstly, why report a bug?
[16:03] <phillw> For the testers, Often we are using the latest, unmodified alpha code for various projects during the development release
[16:03] <phillw> do not assume someone else will report a bug!
[16:03] <phillw> Another important thing to remember is that Discussing a bug on IRC, email, forum or facebook areas etc. does not raise a bug. The devs do not monitor those areas
[16:04] <phillw> By all means use them to discuss a problem. Once your discussion about the bug is at a stage where you can report it, then for it to be actioned by the devs you must raise a bug.
[16:05] <phillw> With the advent of 12.04, some of automated system of checking bugs has been changed and will continue to be enhanced.
[16:05] <phillw> There has been blog posts about a new system 'spying' on your system and sending information to Canonical.
[16:05] <phillw> To briefly touch on this system....
[16:06] <phillw> It is called whoopise, and reports errors to a database called daisy.
[16:07] <phillw> it runs in the background looking for any crash reports that get reported into your /var/crash directory. If it spots one, it goes into action.
[16:07] <phillw> Under its settings, it may also send additional information.
[16:08] <phillw> Whoopise is an ongoing and active project. Fuller details all about it can be found at https://wiki.ubuntu.com/ErrorTracker
[16:08] <phillw> More often, for testers, we need to manually raise a bug, such as for a failed test case.
[16:09] <phillw> going onto launchpad and manually creating a bug often results in a bug report that can not be actioned owing to a lack of information.
[16:09] <phillw> the best way to prevent this is to use the ubuntu-bug command.
[16:10] <phillw> It can be a bit tricky to work out to what to report the bug against... To this end, for testing of ISO's a quick list can be found at https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs
[16:11] <phillw> So, if the error occurred whilst trying to install an iso, you would issue the command ubuntu-bug ubiquity
[16:12] <phillw> if you are testing an application, e.g. GClac and it failed, you would issue the command ubuntu-bug gcalc
[16:13] <phillw> using ubuntu-bug ensures that as much information relevant to the bug is obtained and put onto the bug report.
[16:13] <phillw> Again, there is a full explanation at https://wiki.ubuntu.com/Bugs/FindRightPackage
[16:14] <phillw> If you are unsure on what package to allocate a bug against, please feel free to ask on #ubuntu-bugs and one of the people there will be more than happy to assist.
[16:15] <phillw> incomplete bugs do take time up which could be better spent actually dealing with bugs.
[16:15] <phillw> Gema will be  holding  a session immediately after this introduction to explain this further.
[16:16] <phillw> Within the quality team, we have a brief section on the basics of bug reporting as it affects quality. This can be found at https://wiki.ubuntu.com/QATeam/Overview#Bugs
[16:18] <phillw> Those are the basics for bug reporting, as I understand them. Please feel free to ask any questions on bugs (basic level, not advanced!) and I will endeavour to answer them (or get some one from the bug-squad to do so).
[16:20] <phillw> !q
[16:20] <ClassBot> Dipan asked: ug goes to Private, what does it mean?
[16:20] <TheLordOfTime> I'll take that one.
[16:21] <TheLordOfTime> Usually, when a bug is marked "Private" there's some good reason for it.  With a lot of segfault (crash) bugs I see, a lot of them get marked as private, either because they contain information that *could* be private or could identify your system, or similar reasons
[16:21] <phillw> !Q
[16:23] <TheLordOfTime> Typically, I see this with bugs which have core dumps or tracebacks which could contain information to identify someone: passwords, account numbers, etc. fall in the category of information that needs to be "removed" from the bug before it goes to a public view.
[16:24] <TheLordOfTime> Those private bugs are therefore exactly what they are: hidden from the public eye until someone's gotten to it and actually looked through to see if there's anything that needs removal on those bugs, and then we usually make the bug visible after such things.
[16:26] <phillw> Also, The bot that goes looking for duplicated bugs does not worry if the bug it is using as master is private. If this happens please go to #ubuntu-bugs and raise it with them
[16:29] <phillw> I hope that has answered the question, are there any more questions?
[16:32] <ClassBot> johnsgruber-l-lu asked: If I have a bug in the kernel that might affect only a few systems like mine should it be reported?
[16:33] <phillw> short answer? yes it should. you are not to know that it only affects 'a few' systems. there may other systems that it could also impact.
[16:34] <hggdh> indeed. Also, for kernel bugs, *always* report a new one. It is difficult to say, a priori, if your affected system is *identical* with another in an already reported bug
[16:35] <phillw> if it fixed i  a newer release, then there is always the chance of it getting an SRU raised for it (so that it can be applied to an exisiting release).
[16:36] <phillw> *if it is fixed in a *
[16:40] <phillw> I hope that has answered the question, are there any more questions?
[16:45] <phillw> Whilst we still have some time left, for discussing where 'test case' bugs should go, #ubuntu-quality is a good place to ask.
[16:45] <phillw> There is also one remaining bug type that I completely forgot about!
[16:46] <phillw> on each test case, for example, http://iso.qa.ubuntu.com/qatracker/testcases/1301/info
[16:47] <phillw> you will at the top a link to report a bug against the test case. This is for any spelling mistakes we make and if a test case is not following the order of carrying it out that you are seeing so that they can be edited and corrected.
[16:48] <phillw> it is not for reporting bugs found by using the test case.
[16:50] <ClassBot> There are 10 minutes remaining in the current session.
[16:55] <ClassBot> There are 5 minutes remaining in the current session.
[16:55] <phillw> Well, thank you everyone for attending, a special thanks to the people from bug-squad who attended to help answering your questions. Next up is gema who will discuss following a bug report.
[17:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/06/%23ubuntu-classroom.html following the conclusion of the session.
[17:00] <gema> o/ (anyone listening can you please wave in #ubuntu-classroom-chat?)
[17:01] <gema> cool, so let's get started
[17:01] <gema> I'd like to thank phillw for his introduction to bug reporting, that sets us all in the right mindset imo
[17:02] <gema> first of all I’d like to apologise for the misleading title of this talk, I am not just going to talk about what to do to follow up on your bugs, but also about how to raise good bugs in the first place
[17:02] <gema> (please, say something in #ubuntu-classroom-chat if I am too quick)
[17:02] <gema> we’ll have (hopefully) some time at the end for questions, if not, you can find me on #ubuntu-quality and ask anything any time (I am on UTC timezone)
[17:03] <gema> What is a good bug?
[17:03] <gema> A good bug is a bug that a developer or maintainer can read, reproduce and debug without requiring any additional information
[17:03] <gema> Think of the developer/maintainer as your customer: give him all he needs without him having to ask for it. After all, a happy customer improves the odds of a productive and mutually beneficial relationship
[17:04] <gema> After today's talks, I'd expect you guys to be able to raise good bugs that contain enough information for someone else to debug and possibly fix the issue
[17:04] <gema> When the software doesn't behave in the way you would expect, be sure to first check any available documentation to determine whether the behaviour is intended or not.
[17:04] <gema> Once you are fairly confident that the issue is indeed a bug, think about the following things; you'll need them when filing your bug report:
[17:05] <gema> * Steps to reproduce: How do you make the bug appear? what do you do, where to click/what to type to reproduce it?
[17:05] <gema> * Test environment: What is your hardware? Is the bug be hardware specific? Where you in an X session? What else was running on your machine? what other software is running that might interact with the software under test?
[17:06] <gema> * Repeatability: does this bug occur every time I run this software or just sometimes?
[17:06] <gema> If it doesn't occur always, you should determine the exact conditions that make it appear.
[17:06] <gema> You should be sure that it is repeatable in some way (even if it's just 1/100 runs)
[17:07] <gema> * Criticality: How bad is the bug? can people still use their systems with this bug on them or does it leave the system unusable. Are people going to lose their data if they hit this bug?
[17:07] <gema> Most of the time you won’t have enough information to judge the criticality of the bug, except in two cases:
[17:07] <gema> 1) security bug - e.g. if the software is leaking private/secure data, or allow crashing the whole OS (Denial-of-service), or... - this should be reported as a security issue and ping the security team in the process. In some cases this type of bug shouldn’t be made public straight away, to avoid putting people affected by the vulnerability at greatest risk.
[17:08] <gema> 2) critical bug - A bug that is *NOT* a security bug, but is critical in some other way, e.g. destroys a random partition by mistake.
[17:08] <gema> Other problems like typos, cosmetic fixes, etc, should likely be reported as unimportant bugs, except when they are related to explicit design requirements.
[17:09] <gema> But again, that’s not for the reporter to decide, unless the reporter is part of the design team ;)
[17:09] <gema> In any other cases, just don’t bother about criticality and let the developer decide.
[17:10] <gema> Writing a good bug report with all the information that is required for the developer to fix
[17:10] <gema> the problem is hard, but not impossible. It does, however, require some effort.
[17:10] <gema> Odds are that a report that takes you 5 minutes to write is not very useful and doesn't contain all the relevant bits we discussed earlier.
[17:10] <gema> !Q
[17:10] <gema> !q
[17:11] <gema> Dipan : QUESTION: Gema I agree with your points for good bug. But sometimes giving too
[17:11] <gema>                           much information, also creates too much confusion. What I feel, we should give
[17:11] <gema>                           the information according to the importance of the bug
[17:11] <gema> (sorry, but bot doesn't work for me)
[17:11] <gema> Dipan: it is not about giving too much information, it is about giving *the right* information
[17:12] <gema> if you don't document the bug properly (not too much, not too little, it depends on the bug and the way to reproduce it), developers won't be able to diagnost it properly
[17:13] <gema> If you stick to these guidelines, odds are your bugs will be fixed quicker than a bug that is missing half of the information.
[17:13] <gema> Nobody likes to waste their productive time trying to get details on a problem that may or may not be there.
[17:14] <gema> When a bug is poorly written, the developer cannot trust your judgement as to whether what you found was a real problem... you may have messed something up or misunderstood the intended behaviour.
[17:14] <gema> Hence repeatability, environmental information, etc, are critical. The more information you provide up-front, the easier it is for both of you.
[17:15] <gema> Anyone reading your bug familiar with the software should be able to get an idea of what went wrong and how it happened.
[17:15] <gema> If you don't think that this is the case you might be better off trying to rewrite your bug report.
[17:15] <gema> A bug report should only contain relevant information and should be clear and concise.
[17:16] <gema> A list of steps, symptoms and expected results, is preferred to a long paragraph describing them.
[17:16] <gema> Whenever you've raised a bug, you should keep track of it from start to finish - that is, until it is resolved.
[17:16] <gema> You should be prompt in replying to any questions other people may have, in particular if they affect reproducibility.
[17:16] <gema> If you stick to the guidelines I outlined before, odds are you won't have much work.
[17:17] <gema> When a fix for the issue becomes available, it should be the reporter's duty to make sure it fixes the bug, and reopen if that is not the case.
[17:17] <gema> The developer is the expert on the software code, but you are the expert on how the software really behaves under the conditions you are testing, so you are going to be required to provide feedback as the developer explores the problem.
[17:17] <gema>  Your bug report should contain enough information for the developer to understand what behaviour you expected instead and why.
[17:18] <gema> One bug needs to describe one problem.
[17:18] <gema> Unless agreed otherwise with the developer, for whichever exceptional reason, each bug has to be about one problem only.
[17:18] <gema> Having several problems in one bug makes it unmanageable and unlikely to be fixed.
[17:18] <gema> See for instance bug 746500.
[17:18] <gema> https://bugs.launchpad.net/ubuntu-translations/+bug/746500
[17:19] <gema> This bug had a lot of screenshots on a pdf.
[17:19] <gema>  You may think is useful, but the report lacks the basic information about the version of the installer or where exactly the problem was.
[17:19] <gema> It was easier for a developer to run the installer themselves than to decode what is missing from the bug. This kind of bug wastes a lot of engineering time.
[17:20] <gema> Some other examples of bad bugs:
[17:20] <gema> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1110500
[17:20] <gema> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1104683
[17:20] <ClassBot> There are 10 minutes remaining in the current session.
[17:20] <gema> When it comes to ubiquity (which is something we test for every milestone), you need to pay attention to the instructions from the developers on how to attach logs and debug:
[17:21] <gema> https://wiki.ubuntu.com/DebuggingUbiquity
[17:21] <gema> https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs
[17:21] <gema> $ ubuntu-bug ubiquity
[17:21] <gema> does correct collection of logs, as long as it's run in (a) live system after the crash/error got reproduced or (b) in the installed system when the crash/error/bug was produced during installation.
[17:21] <gema> To summarize:
[17:21] <gema> - You need to know the problem and be able to describe it clearly to another person that has never seen it.
[17:22] <gema> - You need to give clear steps to reproduce.
[17:22] <gema> - You need to say what was the behaviour you were expecting (i.e. why you think this behaviour is a problem)
[17:22] <gema> - You have to be sure the problem is reproducible and the conditions under which it is reproducible and the probability.
[17:22] <gema> - You should gather all the relevant logs either using the ubuntu-bug tool or manually, e.g. dmesg, syslog, etc.
[17:22] <gema> and once you finish reporting the bug make sure to follow up with the developers in case some questions arise.
[17:23] <gema> Be responsive so that they know it is possible to get help from you if needed.
[17:23] <gema> Make sure to test their solution so that you are satisfied it meets  your expectations, or reopen the bug if not (it is easier for the developer to deal with a second fix straight away than after two weeks).
[17:23] <gema> There are plenty of good bugs out there as well, this is one example of good bug in my opinion:
[17:23] <gema> https://bugs.launchpad.net/ubuntu/quantal/+source/ubiquity/+bug/1056707
[17:23] <gema> and that's all I have, we can have questions if you have any
[17:24] <gema> or remarks if you want to make any
[17:24] <gema> can someone make the classroom unmoderated , please?
[17:25] <gema> any questions? you can put them in #ubuntu-classroom-chat
[17:25] <ClassBot> There are 5 minutes remaining in the current session.
[17:27] <gema> ok, I will take it as a no, we can keep discussing this in #ubuntu-quality if you think of anything later
[17:27] <gema> thank you all for your time!
[17:30] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/02/06/%23ubuntu-classroom.html


[17:02] <mhall119> Bryanstein: hey, are you around? Wondering if there's going to be another fossetcon this year
[17:15] <ahoneybun> mhall119: not this year, as I've heard at SELF
[17:15] <ahoneybun> he just moved to Orlando and is very tired


[09:15] <Pali> hello, I have problem with importing git repo to launchpad via import service
[09:16] <Pali> launchpad is reporting some weird error
[09:17] <Pali> here is that repo: https://code.launchpad.net/~pali/ocl-icd/trunk
[09:17] <Pali> git clone of original git repository working fine, so there is no problem with it
[09:18] <Pali> launchpad show in log: bzrlib.errors.TransportNotPossible: Transport operation not possible: Transport  has not implemented list_dir (but must claim to be listable to trigger this error).
[09:40] <jelmer> Pali: I don't think the bzr-git used by launchpad supports "dumb" git repositories
[09:42] <Pali> jelmer: bzr branch <that git repo> working fine on my precise box
[09:43] <Pali> directly bzr can clone full that git branch
[09:43] <jelmer> Pali: yes, launchpad is not running the same version of bzr-git as your precise machiine though
[09:44] <Pali> ah, so launchpad has some older version and older version of bzr-git did not supported git reposiories via http?
[09:44] <Pali> I have 0.6.8-1
[09:44] <wgrant> The particular way that Launchpad uses bzr-git does not currently work well with dumb HTTP repositories.
[09:44] <wgrant> Smart HTTP repositories work fine.
[09:44] <wgrant> I haven't seen a dumb one in the wild for a long time..
[09:50] <Pali> so there is no way to import dump git repos over http to launchpad?
[09:50] <Pali> only smart protocol via ssh or git is supported?
[09:51] <jelmer> Pali: the smart protocol works over http too
[09:51] <Pali> how can I check if server supports smart protocol or not (via http)?