What Are You Doing Right Now
-
@scottalanmiller said in What Are You Doing Right Now:
Celebrated my youngest's birthday. Now family video game time.
My oldest’s birthday was today.
-
Time for me to buy some new drives and make a software raid for my plex server.
One of the old ass drives must have puked.
And the even older raid card is such a piece of shit now. It was never “good” but it has worked for for than a decade. Came out of a backup appliance we bought in 2008.
-
Did some research on getting a 3D printer. But decided not to bother as once I've used it to print a few things we wouldn't use it again
-
@hobbit666 said in What Are You Doing Right Now:
Did some research on getting a 3D printer. But decided not to bother as once I've used it to print a few things we wouldn't use it again
Find a local makerspace. Should be a few near you.
-
@travisdh1 said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Did some research on getting a 3D printer. But decided not to bother as once I've used it to print a few things we wouldn't use it again
Find a local makerspace. Should be a few near you.
Those seem so expensive and time consuming. Not much better than just buying a 3D printer for a month of use and then selling it used or just holding on to it.
-
@scottalanmiller said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Did some research on getting a 3D printer. But decided not to bother as once I've used it to print a few things we wouldn't use it again
Find a local makerspace. Should be a few near you.
Those seem so expensive and time consuming. Not much better than just buying a 3D printer for a month of use and then selling it used or just holding on to it.
maintaining a 3D printer can be a HUGE PITA, for a small number of prints definitely makes it worth paying others to just handle the print, you only pay for a successful print, if you own the printer, and it fails, you loose those funds, etc.
-
monday morning. counting my blessings.
-
Server updates.
-
Trying to figure out what is causing my laptop to completely lock up with Pop_OS 19.10 (did this with Fedora 31 as well).
-
Just finished writing a little saxophone duet that came to mind tonight. I'll try to make time this week to record it and upload to YouTube.
-
Ubuntu 20.04 - Firefox
By default in the Ubuntu Software store only shows snap version of Firefox but the installed version is is a deb file app.
-
@EddieJennings said in What Are You Doing Right Now:
Trying to figure out what is causing my laptop to completely lock up with Pop_OS 19.10 (did this with Fedora 31 as well).
Recently started locking up on you?
-
@black3dynamite said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
Trying to figure out what is causing my laptop to completely lock up with Pop_OS 19.10 (did this with Fedora 31 as well).
Recently started locking up on you?
-ish
It started a over a month ago with Fedora 31, and I was able to narrow it down to likely something in the kernel not playing nice with Intel graphics chips starting with kernel 5.4+ (rather than Firefox causing the problem, which was the first seemingly common denominator in all of this). Because I was itching to give Pop_OS a try, I hopped to it at the start of April. All's been fine until the last week or so. Currently my Pop_OS 19.10 installation is using kernel 5.3.
When I gather some more information, I'll probably make a thread about it here.
-
@Dashrender said in What Are You Doing Right Now:
maintaining a 3D printer can be a HUGE PITA, for a small number of prints definitely makes it worth paying others to just handle the print, you only pay for a successful print, if you own the printer, and it fails, you loose those funds, etc.
This was another reason. After reading about setup and just running the things seemed to much hard work. If I got a hobby that would use it more often I would get one.
-
Taking Avixa online courses for AV certifications my company now wants everyone to have; seems like that's the new direction.
-
@hobbit666 said in What Are You Doing Right Now:
@Dashrender said in What Are You Doing Right Now:
maintaining a 3D printer can be a HUGE PITA, for a small number of prints definitely makes it worth paying others to just handle the print, you only pay for a successful print, if you own the printer, and it fails, you loose those funds, etc.
This was another reason. After reading about setup and just running the things seemed to much hard work. If I got a hobby that would use it more often I would get one.
Denver's library system has several printers that are free to use by any library card holder. Check your local library.
-
@hobbit666 Our library (if it was open) has a weekly maker space evening. Also ask around maybe someone in you neighborhood has one already. Found out my neighbor got one at Christmas time and he's already printed a couple small projects (namely Raspbery Pi cases) for me
-
Wishing that I had fewer house projects and financial plans so I could get this and try my usa 4 corners ride again. It's even in my color. -
Discovering a new tool to determine boot-up performance.
systemd-analyze
https://www.freedesktop.org/software/systemd/man/systemd-analyze.html# systemd-analyze time Startup finished in 4.036s (kernel) + 2min 20.304s (initrd) + 11.208s (userspace) = 2min 35.549s graphical.target reached after 11.191s in userspace# systemd-analyze blame 2min 18.965s dracut-initqueue.service 2min 18.179s systemd-cryptsetup@luks\x2d99ed47f8\x2dcd75\x2d4967\x2d90fa\x2dcec132c959e4.service 16.359s dnf-makecache.service 6.377s plymouth-quit-wait.service 6.192s NetworkManager-wait-online.service 4.200s dnf-automatic.service 2.359s systemd-udev-settle.service 1.005s systemd-logind.service 981ms initrd-switch-root.service 767ms fwupd.service 757ms lvm2-monitor.service 735ms upower.service 626ms tuned.service 584ms firewalld.service 550ms udisks2.service 430ms snap.lxd.activate.service 383ms systemd-machined.service 366ms systemd-udevd.service 349ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1502.mount 347ms sssd.service 343ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-116.mount 332ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1506.mount 312ms libvirtd.service 298ms var-lib-snapd-snap-snap\x2dstore-209.mount 288ms snapd.service 280ms var-lib-snapd-snap-core18-1705.mount 267ms var-lib-snapd-snap-snapd-6953.mount 238ms systemd-journald.service 238ms var-lib-snapd-snap-lxd-14804.mount 231ms var-lib-snapd-snap-snapd-7264.mount 209ms polkit.service 203ms var-lib-snapd-snap-core-8935.mount 191ms var-lib-snapd-snap-lxd-14709.mount 168ms systemd-journal-flush.service 165ms var-lib-snapd-snap-snap\x2dstore-415.mount 153ms [email protected] 149ms ModemManager.service 145ms initrd-parse-etc.service 138ms abrtd.service 135ms sysroot.mount 121ms var-lib-snapd-snap-multipass-2006.mount 120ms var-lib-snapd-snap-hello\x2dworld-29.mount 114ms var-lib-snapd-snap-core-9066.mount 101ms var-lib-snapd-snap-multipass-1784.mount 95ms systemd-udev-trigger.service 90ms dracut-cmdline.service 87ms teamviewerd.service 85ms chronyd.service 82ms smartd.service 73ms geoclue.service 73ms bluetooth.service 72ms systemd-tmpfiles-setup.service 71ms systemd-rfkill.service 68ms avahi-daemon.service 66ms systemd-vconsole-setup.service 63ms cups.service 63ms switcheroo-control.service 61ms cockpit-motd.service 60ms iio-sensor-proxy.service 53ms lm_sensors.service 52ms dev-loop4.device 51ms dev-loop9.device 50ms lvm2-pvscan@253:0.service 49ms dev-loop11.device 47ms dev-loop8.device 46ms dev-loop6.device 44ms systemd-tmpfiles-clean.service 42ms gssproxy.service 42ms colord.service 42ms dbus-broker.service 41ms rtkit-daemon.service 41ms NetworkManager.service 41ms var-lib-nfs-rpc_pipefs.mount 40ms dev-loop3.device 40ms auditd.service 39ms dev-loop2.device 36ms import-state.service 34ms sshd.service 34ms dev-loop5.device 33ms systemd-fsck@dev-disk-by\x2duuid-39E5\x2d838F.service 33ms dev-loop10.device 32ms dracut-pre-pivot.service 32ms systemd-tmpfiles-setup-dev.service 31ms dev-loop0.device 31ms livesys.service 31ms dev-loop12.device 29ms gdm.service 27ms cockpit.socket 27ms boot.mount 26ms sssd-kcm.service 23ms dmraid-activation.service 23ms dev-loop1.device 23ms livesys-late.service 22ms accounts-daemon.service 22ms dev-loop7.device 21ms wpa_supplicant.service 18ms plymouth-switch-root.service 18ms dracut-pre-udev.service 16ms [email protected] 16ms flatpak-system-helper.service 15ms systemd-fsck-root.service 15ms plymouth-read-write.service 15ms systemd-random-seed.service 15ms initrd-cleanup.service 14ms swapfile.swap 14ms plymouth-start.service 14ms systemd-update-utmp-runlevel.service 14ms boot-efi.mount 12ms dev-hugepages.mount 12ms systemd-remount-fs.service 12ms dev-loop13.device 12ms dev-mqueue.mount 11ms kmod-static-nodes.service 11ms sys-kernel-debug.mount 10ms nfs-convert.service 10ms systemd-sysctl.service 9ms tpm2-abrmd.service 9ms systemd-modules-load.service 8ms rpc-statd-notify.service 7ms systemd-update-utmp.service 7ms systemd-backlight@backlight:intel_backlight.service 7ms systemd-user-sessions.service 5ms initrd-udevadm-cleanup-db.service 5ms snapd.socket 4ms dracut-shutdown.service 3ms dev-loop14.device 3ms sys-fs-fuse-connections.mount 3ms tmp.mount 1ms sys-kernel-config.mount 81us iscsi-shutdown.service# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @11.191s └─multi-user.target @11.191s └─plymouth-quit-wait.service @4.812s +6.377s └─systemd-user-sessions.service @4.788s +7ms └─remote-fs.target @4.771s └─remote-fs-pre.target @4.771s └─iscsi-shutdown.service @4.771s +81us └─network.target @4.768s └─wpa_supplicant.service @5.475s +21ms └─basic.target @3.910s └─dbus-broker.service @3.866s +42ms └─dbus.socket @3.857s └─sysinit.target @3.850s └─systemd-update-utmp.service @3.842s +7ms └─auditd.service @3.801s +40ms └─systemd-tmpfiles-setup.service @3.726s +72ms └─import-state.service @3.688s +36ms └─local-fs.target @3.685s └─run-snapd-ns-lxd.mnt.mount @5.033s └─run-snapd-ns.mount @4.948s └─local-fs-pre.target @3.323s └─lvm2-monitor.service @835ms +757ms └─dm-event.socket @828ms └─-.mount └─systemd-journald.socket └─-.mount └─... -
Not on the latest? If you go into the app itself, it confirms we are on the latest. And the scan doesn't even get the same version as the app! WTF
