Aaryan BHAGAT's questions

My ubuntu 20.04 has a slow boot up time. Here is what I did:

• Using systemd-analyze blame identified 31s for networkd-dispatcher.service.
• Upon doing journalctl -b -u networkd.dispatcher.service this is the log:

15:39:11 systemd[1]: Starting Dispatcher daemon for systemd-networkd...
15:39:42 networkd-dispatcher[1144]: DEBUG:Performed interface scan; state: <Dispatcher({'script_dir': '/etc/networkd-dispatcher:/usr/lib/networkd-dispatcher'})>
15:39:42 networkd-dispatcher[1144]: INFO:Triggering scripts for last-known state for allinterfaces
15:39:42 networkd-dispatcher[1144]: DEBUG:Running immediate triggers for NetworkctlListState(idx=1, name='lo', type='loopback', operational='carrier', administrative='unmanaged')
15:39:43 networkd-dispatcher[1144]: DEBUG:Path '/etc/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:39:43 networkd-dispatcher[1144]: DEBUG:Path '/usr/lib/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:39:43 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='carrier', administrative='unmanaged') entering state 'unmanaged': no triggers
15:39:43 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='carrier', administrative='unmanaged') entering state 'carrier': no triggers
15:39:43 networkd-dispatcher[1144]: DEBUG:Running immediate triggers for NetworkctlListState(idx=2, name='enp2s0', type='ether', operational='no-carrier', administrative='unmanaged')
15:39:43 networkd-dispatcher[1144]: DEBUG:Path '/etc/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:39:43 networkd-dispatcher[1144]: DEBUG:Path '/usr/lib/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:39:43 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=2, name='enp2s0', type='ether', operational='no-carrier', administrative='unmanaged') entering state 'unmanaged': no triggers
15:39:44 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=2, name='enp2s0', type='ether', operational='no-carrier', administrative='unmanaged') entering state 'no-carrier': no triggers
15:39:44 networkd-dispatcher[1144]: DEBUG:Running immediate triggers for NetworkctlListState(idx=3, name='wlp3s0', type='wlan', operational='off', administrative='unmanaged')
15:39:44 networkd-dispatcher[1144]: DEBUG:Path '/etc/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:39:44 networkd-dispatcher[1144]: DEBUG:Path '/usr/lib/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:39:44 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=3, name='wlp3s0', type='wlan', operational='off', administrative='unmanaged') entering state 'unmanaged': no triggers
15:39:44 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=3, name='wlp3s0', type='wlan', operational='off', administrative='unmanaged') entering state 'off': no triggers
15:39:44 systemd[1]: Started Dispatcher daemon for systemd-networkd.
15:39:44 networkd-dispatcher[1144]: INFO:Startup complete
15:39:45 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('CarrierState'): dbus.String('carrier', variant_level=1), dbus.String('OperationalState'): dbus.String('carrier', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_32')
15:39:45 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=2, name='enp2s0', type='ether', operational='carrier', administrative='unmanaged') entering state 'carrier': no triggers
15:39:45 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Manager'), data=dbus.Dictionary({dbus.String('OperationalState'): dbus.String('carrier', variant_level=1), dbus.String('CarrierState'): dbus.String('carrier', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1')
15:39:45 networkd-dispatcher[1144]: DEBUG:Ignoring signal received with unexpected typ dbus.String('org.freedesktop.network1.Manager')
15:39:46 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AddressState'): dbus.String('routable', variant_level=1), dbus.String('OperationalState'): dbus.String('routable', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_32')
15:39:46 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=2, name='enp2s0', type='ether', operational='routable', administrative='unmanaged') entering state 'routable': no triggers
15:39:46 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Manager'), data=dbus.Dictionary({dbus.String('OperationalState'): dbus.String('routable', variant_level=1), dbus.String('AddressState'): dbus.String('routable', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1')
15:39:46 networkd-dispatcher[1144]: DEBUG:Ignoring signal received with unexpected typ dbus.String('org.freedesktop.network1.Manager')
15:40:21 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('CarrierState'): dbus.String('off', variant_level=1), dbus.String('OperationalState'): dbus.String('off', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_34')
15:40:21 networkd-dispatcher[1144]: WARNING:Unknown index 4 seen, reloading interface list
15:40:21 networkd-dispatcher[1144]: DEBUG:Performed interface scan; state: <Dispatcher({'script_dir': '/etc/networkd-dispatcher:/usr/lib/networkd-dispatcher'})>
15:40:21 networkd-dispatcher[1144]: DEBUG:No change represented by operational state 'off' for interface 'docker0'
15:40:21 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AddressState'): dbus.String('routable', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_34')
15:40:21 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('AdministrativeState'): dbus.String('unmanaged', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_34')
15:40:21 networkd-dispatcher[1144]: DEBUG:Path '/etc/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:40:21 networkd-dispatcher[1144]: DEBUG:Path '/usr/lib/networkd-dispatcher/unmanaged.d' does not exist; skipping
15:40:21 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=4, name='docker0', type='bridge', operational='off', administrative='unmanaged') entering state 'unmanaged': no triggers
15:40:21 networkd-dispatcher[1144]: DEBUG:Signal: typ=dbus.String('org.freedesktop.network1.Link'), data=dbus.Dictionary({dbus.String('CarrierState'): dbus.String('no-carrier', variant_level=1), dbus.String('OperationalState'): dbus.String('no-carrier', variant_level=1)}, signature=dbus.Signature('sv')), path=dbus.ObjectPath('/org/freedesktop/network1/link/_34')
15:40:21 networkd-dispatcher[1144]: DEBUG:Ignoring notification for interface NetworkctlListState(idx=4, name='docker0', type='bridge', operational='no-carrier', administrative='unmanaged') entering state 'no-carrier': no triggers

As you can see it started on 15:39:11 and startup complete was at 15:39:44, even between 1st and the 2nd log line there is a time lag of 31s.

I do not know how to go deeper than this and Identify the problem for the time lag.

Any pointers and resources to solutions will be appreciated.

My wired earphones are giving me static noise, I am writing this after I tried everything on this site and nothing worked. This involves:

• Using the famous pulseaudio -k option ( it just transfers the sound to my PC speakers, and there is no static there, as soon I connect the earphones it starts again ).
• Using echo "0" | sudo tee /sys/module/snd_hda_intel/parameters/power_save , nothing changed.
• Using alsamixer, here the default volume of headphones section is full, whenever I change the master volume using the "f2" and "f3" keys the headphones section always goes very high directly as well as the PCM section, so this tool does not change anything.

So as the end option I just opened the pulseaudio logs, I used Does pulseaudio have an error log? stackoverflow post to help debug pulseaudio.

When I give the pulseaudio --verbose command, this is the output:

https://pastebin.com/XMPqCTX2 (Using this pastebin because my total post will exceed the characters limit)

When I connect the earphones these extra logs appear:

I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-speaker.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-speaker.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-speaker.
I: [pulseaudio] module-device-restore.c: Synced.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-speaker.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port source:alsa_input.pci-0000_00_1f.3.analog-stereo:analog-input-internal-mic.
I: [pulseaudio] alsa-sink.c: Successfully enabled deferred volume.
I: [pulseaudio] alsa-sink.c: Hardware volume ranges from -181.50 dB to 0.00 dB.
I: [pulseaudio] alsa-sink.c: Fixing base volume to 0.00 dB
I: [pulseaudio] alsa-sink.c: Using hardware volume control. Hardware dB scale supported.
I: [pulseaudio] alsa-sink.c: Using hardware mute control.
I: [pulseaudio] sink.c: Changed port of sink 0 "alsa_output.pci-0000_00_1f.3.analog-stereo" to analog-output-headphones
I: [pulseaudio] alsa-source.c: Successfully enabled deferred volume.
I: [pulseaudio] alsa-source.c: Hardware volume ranges from -17.25 dB to 60.00 dB.
I: [pulseaudio] alsa-source.c: Fixing base volume to -60.00 dB
I: [pulseaudio] alsa-source.c: Using hardware volume control. Hardware dB scale supported.
I: [pulseaudio] alsa-source.c: Using hardware mute control.
I: [pulseaudio] source.c: Changed port of source 1 "alsa_input.pci-0000_00_1f.3.analog-stereo" to analog-input-headphone-mic
I: [pulseaudio] alsa-source.c: Successfully enabled deferred volume.
I: [pulseaudio] alsa-source.c: Hardware volume ranges from -17.25 dB to 60.00 dB.
I: [pulseaudio] alsa-source.c: Fixing base volume to -60.00 dB
I: [pulseaudio] alsa-source.c: Using hardware volume control. Hardware dB scale supported.
I: [pulseaudio] alsa-source.c: Using hardware mute control.
I: [pulseaudio] source.c: Changed port of source 1 "alsa_input.pci-0000_00_1f.3.analog-stereo" to analog-input-headset-mic
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port source:alsa_input.pci-0000_00_1f.3.analog-stereo:analog-input-headset-mic.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port source:alsa_input.pci-0000_00_1f.3.analog-stereo:analog-input-headset-mic.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Storing volume/mute for device+port sink:alsa_output.pci-0000_00_1f.3.analog-stereo:analog-output-headphones.
I: [pulseaudio] module-device-restore.c: Synced.
I: [pulseaudio] sink-input.c: Freeing input 0 "Valorant: *NEW* Butterfly Knife is SO AMAZING! - Recon Skin Bundle! - YouTube"
I: [pulseaudio] sink-input.c: Trying to change sample spec
I: [pulseaudio] module-stream-restore.c: Restoring volume for sink input sink-input-by-application-name:Firefox.
I: [alsa-sink-ALC3246 Analog] alsa-sink.c: Trying resume...
I: [alsa-sink-ALC3246 Analog] alsa-sink.c: Resumed successfully...
I: [alsa-sink-ALC3246 Analog] alsa-sink.c: Starting playback.
I: [pulseaudio] resampler.c: Forcing resampler 'copy', because of fixed, identical sample rates.
I: [pulseaudio] sink-input.c: Created input 1 "AudioStream" on alsa_output.pci-0000_00_1f.3.analog-stereo with sample spec float32le 2ch 48000Hz and channel map front-left,front-right
I: [pulseaudio] sink-input.c:     media.name = "AudioStream"
I: [pulseaudio] sink-input.c:     application.name = "Firefox"
I: [pulseaudio] sink-input.c:     native-protocol.peer = "UNIX socket client"
I: [pulseaudio] sink-input.c:     native-protocol.version = "33"
I: [pulseaudio] sink-input.c:     application.process.id = "4565"
I: [pulseaudio] sink-input.c:     application.process.user = "aaryan"
I: [pulseaudio] sink-input.c:     application.process.host = "aaryan-Inspiron-5577"
I: [pulseaudio] sink-input.c:     application.process.binary = "firefox"
I: [pulseaudio] sink-input.c:     application.language = "en_IN"
I: [pulseaudio] sink-input.c:     window.x11.display = ":1"
I: [pulseaudio] sink-input.c:     application.process.machine_id = "45ccba0212de46e1ae093c22cc4dfe12"
I: [pulseaudio] sink-input.c:     application.icon_name = "firefox"
I: [pulseaudio] sink-input.c:     module-stream-restore.id = "sink-input-by-application-name:Firefox"
I: [pulseaudio] protocol-native.c: Requested tlength=200.00 ms, minreq=25.00 ms
I: [pulseaudio] protocol-native.c: Final latency 249.91 ms = 99.96 ms + 2*25.00 ms + 99.95 ms
I: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-0000_00_1f.3.analog-stereo idle for too long, suspending ...
I: [alsa-sink-ALC3246 Analog] alsa-sink.c: Device suspended...
I: [pulseaudio] core.c: All sinks and sources are suspended, vacuuming memory

When connected the noise stops but as soon as I play anything the static noise start in the background with the video sound also.

You can see in the last logs the line Freeing input 0 "Valorant: *NEW* Butterfly Knife is SO AMAZING! - Recon Skin Bundle! - YouTube" as that video is the one I am using for testing.

When I stop the video, these extra lines appear after a few seconds

I: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-0000_00_1f.3.analog-stereo idle for too long, suspending ...
I: [alsa-sink-ALC3246 Analog] alsa-sink.c: Device suspended...
I: [pulseaudio] core.c: All sinks and sources are suspended, vacuuming memory

and then the static stops.

I am at a loss here on how to fix this, any pointers will be helpful thanks!

So I am on this problem for quite some time now. After setting up my printer it does not print at all!

I am putting the necessary information out here for anyone to give me some leads

The output of tail -f /var/log/syslog when I connect the USB of the printer:

Inspiron-5577 update-notifier.desktop[116391]: /var/cache/apt/archives/lock:
Inspiron-5577 kernel: [ 5676.034111] usb 1-2: new high-speed USB device number 33 using xhci_hcd
Inspiron-5577 kernel: [ 5676.185754] usb 1-2: New USB device found, idVendor=04a9, idProduct=271a, bcdDevice= 1.00
Inspiron-5577 kernel: [ 5676.185759] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Inspiron-5577 kernel: [ 5676.185762] usb 1-2: Product: Canon CAPT USB Device
Inspiron-5577 kernel: [ 5676.185765] usb 1-2: Manufacturer: Canon
Inspiron-5577 kernel: [ 5676.185767] usb 1-2: SerialNumber: 0000A1C5TEPh
Inspiron-5577 kernel: [ 5676.189182] usblp 1-2:1.0: usblp1: USB Bidirectional printer dev 33 if 0 alt 0 proto 2 vid 0x04A9 pid 0x271A
Inspiron-5577 systemd-udevd[116545]: 1-2: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 32 00' failed with exit code 1.
Inspiron-5577 systemd[1]: Started Configure Plugged-In Printer.
Inspiron-5577 udev-configure-printer: add usb-001-033
Inspiron-5577 udev-configure-printer: device devpath is /devices/pci0000:00/0000:00:14.0/usb1/1-2
Inspiron-5577 udev-configure-printer: MFG:Canon MDL:LBP6000/LBP6018 SERN:- serial:0000A1C5TEPh
Inspiron-5577 kernel: [ 5682.147082] usblp1: removed
Inspiron-5577 kernel: [ 5682.151195] usblp 1-2:1.0: usblp1: USB Bidirectional printer dev 33 if 0 alt 0 proto 2 vid 0x04A9 pid 0x271A
Inspiron-5577 udev-configure-printer: URI contains USB serial number
Inspiron-5577 udev-configure-printer: URI match: usb://Canon/LBP6000/LBP6018?serial=0000A1C5TEPh
Inspiron-5577 udev-configure-printer: URI of detected printer: usb://Canon/LBP6000/LBP6018?serial=0000A1C5TEPh, normalized: canon lbp6000 lbp6018 serial 0000a1c5teph
Inspiron-5577 udev-configure-printer: URI of print queue: ipp://Canone5f13e.local:631/ipp/print, normalized: ipp canone5f13e local 631 ipp print
Inspiron-5577 udev-configure-printer: URI of print queue: ipps://EPSON869F11.local:631/ipp/print, normalized: ipps epson869f11 local 631 ipp print
Inspiron-5577 udev-configure-printer: URI of print queue: ipps://EPSON869F11.local:631/ipp/print, normalized: ipps epson869f11 local 631 ipp print
Inspiron-5577 udev-configure-printer: URI of print queue: usb://Canon/LBP6000/LBP6018?serial=0000A1C5TEPh, normalized: canon lbp6000 lbp6018 serial 0000a1c5teph
Inspiron-5577 udev-configure-printer: Queue ipp://localhost/printers/LBP6000-LBP6018 has matching device URI
Inspiron-5577 udev-configure-printer: Re-enabled printer ipp://localhost/printers/LBP6000-LBP6018
Inspiron-5577 udev-configure-printer: URI of print queue: cups-pdf:/, normalized: cups pdf
Inspiron-5577 systemd[1]: [email protected]: Succeeded.

From the output above it seems it is correctly recognizing my printer.

The output of lsusb also gave:

Bus 001 Device 033: ID 04a9:271a Canon, Inc. LBP6000

The output sudo lpstat -s:

system default destination: LBP6000-LBP6018
device for Canon_MF633C_635C: ipp://Canone5f13e.local:631/ipp/print
device for EPSON_L605_Series: ipps://EPSON869F11.local:631/ipp/print
device for [email protected]: ipps://EPSON869F11.local:631/ipp/print
device for LBP6000-LBP6018: usb://Canon/LBP6000/LBP6018?serial=0000A1C5TEPh
device for PDF: cups-pdf:/

So you can see it is the default set.

Output of sudo lpinfo -v:

network http
network https
network ipp
file cups-brf:/
direct hp
network ipps
serial serial:/dev/ttyS4?baud=115200
direct usb://Canon/LBP6000/LBP6018?serial=0000A1C5TEPh
direct hpfax
file cups-pdf:/
network beh
network lpd
network socket
network smb

Output of ls -l /dev/usb/lp1 gives:

crw-rw---- 1 root lp 180 /dev/usb/lp1

The problem arises when I go to any text file and do the print option my syslog says:

Inspiron-5577 kernel: [ 6061.033928] usblp1: removed

and in the settings of the ubuntu where the driver is shown which is a simple Generic CUPS-PDF printer driver (w/options) there the job is shown to always be in the "processing" state.

I do not have any clue now, maybe the cups log will show something? I am not sure.

Any leads after this will be appreciated.

EDIT

Output of lpstat -t as requested:

scheduler is running
system default destination: LBP6000-LBP6018
device for Canon_MF633C_635C: ipp://Canone5f13e.local:631/ipp/print
device for EPSON_L605_Series: ipps://EPSON869F11.local:631/ipp/print
device for [email protected]: ipps://EPSON869F11.local:631/ipp/print
device for LBP6000-LBP6018: usb://Canon/LBP6000/LBP6018?serial=0000A1C5TEPh
device for PDF: cups-pdf:/
Canon_MF633C_635C accepting requests since Sunday 05 May 2019 11:10:25 AM
EPSON_L605_Series accepting requests since Friday 11 January 2019 12:12:31 PM
[email protected] accepting requests since Friday 11 January 2019 12:16:03 PM
LBP6000-LBP6018 accepting requests since Tuesday 08 March 2022 10:26:49 AM
PDF accepting requests since Tuesday 08 June 2021 02:34:05 PM
printer Canon_MF633C_635C is idle.  enabled since Sunday 05 May 2019 11:10:25 AM
printer EPSON_L605_Series is idle.  enabled since Friday 11 January 2019 12:12:31 PM
printer [email protected] is idle.  enabled since Friday 11 January 2019 12:16:03 PM
printer LBP6000-LBP6018 now printing LBP6000-LBP6018-20.  enabled since Tuesday 08 March 2022 10:26:49 AM
    Sending data to printer.
printer PDF is idle.  enabled since Tuesday 08 June 2021 02:34:05 PM
LBP6000-LBP6018-18      anonymous         1024   Tuesday 08 March 2022 12:39:55 AM
LBP6000-LBP6018-20      aaryan          136192   Tuesday 08 March 2022 01:30:24 AM

Actually I do not know what the 2 different "anonymous" and "aaryan" are for 18 and 20 though.

I had slow bootup recently and found using systemd-analyze that postfix-service is taking almost 25 s to start, critical-chain told me it was specifically postfix@-service.

PS: I also do not know what is postfix@

Upon using journalctrl -u [email protected] it shows the following

Jan 28 12:24:10 aaryan-Inspiron-5577 systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
Jan 28 12:24:35 aaryan-Inspiron-5577 postfix/postfix-script[1641]: warning: symlink leaves directory: /etc/postfix/./makedefs.out
Jan 28 12:24:35 aaryan-Inspiron-5577 postfix/postfix-script[1657]: warning: /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ
Jan 28 12:24:35 aaryan-Inspiron-5577 postfix/postfix-script[1662]: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ

One can clearly see the 25 sec time delay, however I am somewhat of lost here as what how to debug deeper as this log was not much helpful. I have an idea that somehow if I debug the system calls during the start of this service ( during boot ) and see their time lag I will be able to pin point what is the problem.

I can also just remove this service since it is a private laptop but since this might be a good exercise to learn hence I posted here!

Before anyone asks, I have already tried the existing solutions and to no avail.

I will however provide full information for debugging.

• lsusb recognizes my printer
  • Bus 001 Device 023: ID 04a9:271a Canon, Inc. LBP6000
• Cups also recognizes my printer, when going into the Printer options on http://localhost:631/ it the printer is shown. The details are:
  • LBP6000-LBP6018 (Idle, Accepting Jobs, Not Shared, Server Default).
  • Description: LBP6000-LBP6018
  • Location:
  • Driver: Generic Text-Only Printer (grayscale)
  • Connection: usb://Canon/LBP6000/LBP6018?serial=*****
  • Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided

Doing the lp command gives the error mentioned above. Inspecting by tail -f /var/log/cups/error_log gives:

Returning IPP client-error-document-format-not-supported for Send-Document (ipp://localhost:631/printers/LBP6000-LBP6018) from localhost.

Upon checking the /usr/share/cups/mime/mime.types file at line 69 the following line is there and not commented

application/pdf pdf regex(0,^[\n\r]*%PDF)

So I do not know why it is happening.

Do I need a specific driver since this printer is old ( maybe 2010, I do not remember clearly )?

My shell always takes a couple of seconds to load the first time when I boot up, after boot up, when I open up the terminal multiple times to load the shell again and again the boot time decreases to around 1.5 second.

Upon following the advice of this on another question relating to slow loading of shell.

I found that npm config --loglevel=warn get prefix takes the longest time always, rest commands load instantaneously every time.

I was not able to find some pointers on the net and hence I asked here.

My npm version is 6.12.0

I realize this comes when bash loads the nvm.sh script, but how can this be made faster, if at all?

On a reddit post on r/Ubuntu titled Short guide to improve slow boot on Ubuntu (>=18.04) one of the options provided is:

Disable networkd services: If you are not a system admin you don't need this. Gui uses network-manger (and it has it's own dispatcher) anyway.

And the following commands:

sudo apt-get remove networkd-dispatcher
sudo systemctl stop systemd-networkd.service
sudo systemctl disable systemd-networkd.service

In my case network-dispatcher service is also causing slow boot around 20 sec but I was not able to understand the reason given above simply stopping it, are there any downsides to the above mentioned suggestion I should be aware of?

Pointers and resources would be great!

So in the new Ubuntu 20.04 (which I have) it is written on their blog page that

Ubuntu 20.04 LTS ships with a newer ZFS which features native, hardware-enabled encryption, device removal, pool trim and improved performance. While still experimental, we’ve built upon this feature with the addition of zsys.

I wanted to understand this 'support' and what actually they mean by that.

So upon doing df -T I got the following output (of which I am posting the first 2 relevant columns):

Filesystem     Type    
udev           devtmpfs   
tmpfs          tmpfs      
/dev/sdb2      ext4     
tmpfs          tmpfs      
tmpfs          tmpfs      
tmpfs          tmpfs      
/dev/loop0     squashfs   
/dev/loop4     squashfs   
/dev/loop3     squashfs   
/dev/loop2     squashfs   
/dev/loop5     squashfs   
/dev/loop7     squashfs   
/dev/loop11    squashfs    
/dev/loop9     squashfs    
/dev/loop10    squashfs    
/dev/loop1     squashfs    
/dev/loop12    squashfs    
/dev/loop8     squashfs     
/dev/loop13    squashfs     
/dev/loop14    squashfs     
/dev/loop18    squashfs     
/dev/loop17    squashfs     
/dev/loop16    squashfs     
/dev/loop15    squashfs     
/dev/loop6     squashfs     
/dev/loop19    squashfs    
/dev/sda2      vfat         
tmpfs          tmpfs       
tmpfs          tmpfs
/dev/sdb1      fuseblk

So I can see ext4 not zfs, then I got to know that we have zfs module but not loaded as lsmod | grep zfs gave nothing, so I did sudo modprobe zfs (now I could see it upon doing lsmod) but upon loading it, zfs command was still unrecognized and I found in this Getting Started With ZFS Ubuntu 20.04 article that I have to install it using apt.

Also on a side note if I try to find ext modules then lsmod | grep ext4 gives nothing.
So what purpose does the module serve? Why the whole thing is not already pre-installed? Am I missing something here?

So I have understood that why and where ZFS is configured when installed, but what I do not understand is, suppose you do not configure ZFS upon installation and now want to do it, then first you have to load some modules and then install zfsutils. Why is that? Why it is not build like we can just load the whole thing?

Also, currently I am not able to find the ext4 modules

The problem is resolveconf-pull-resolved.service and plymouth-quit-wait.service are taking a lot of time to start making the overall boot process slow. The first one upon searching, I found various issues where it caused the boot to stuck there but none where it caused the boot to be slow overall, for the 2nd one I found this answer which says that this service is not at fault as it just waits for others to complete.
The whole process of my investigation is explained below:

systemd-analyze time gives the following output:

Startup finished in 7.870s (firmware) + 3.118s (loader) + 19.467s (kernel) + 1min 56.978s (userspace) = 2min 27.435s 
graphical.target reached after 1min 56.840s in userspace

Upon following this answer regarding slow userspace, mine problem was similar (meaning snapd was one of the main culprits for slow down ) as systemd-analyze blame | grep snapd gave the following output:

26.656s snapd.service                                                            
      1.011s snapd.apparmor.service                                                   
       915ms snapd.seeded.service                                                     
         1ms snapd.socket

and systemd-analyze blame | grep dev-loop gave

10.384s dev-loop19.device                                                        
     10.236s dev-loop9.device                                                         
     10.155s dev-loop0.device                                                         
     10.151s dev-loop16.device                                                        
     10.110s dev-loop14.device                                                        
      9.776s dev-loop13.device                                                        
      9.470s dev-loop15.device                                                        
      9.294s dev-loop12.device                                                        
      9.106s dev-loop6.device                                                         
      8.982s dev-loop17.device                                                        
      8.873s dev-loop11.device                                                        
      8.864s dev-loop10.device                                                        
      8.738s dev-loop8.device                                                         
      8.731s dev-loop18.device                                                        
      8.724s dev-loop21.device                                                        
      8.052s dev-loop3.device                                                         
      8.017s dev-loop2.device                                                         
      5.861s dev-loop5.device                                                         
      5.374s dev-loop1.device                                                         
      4.883s dev-loop4.device 

But if we look at the whole plot in the svg file ( I have posted the link as uploading the whole image here would make it unreadable because of the size compression ) resolveconf-pull-resolved.service and plymouth-quit-wait.service still take more time than them. Below I have posted a screenshot showing the relevant section of the svg file.