Home / user-372312

JamesIsIn's questions

Martin Hope
JamesIsIn
Asked: 2023-09-24 10:43:51 +0800 CST
  • 5

I have an HP EliteDesk 800 GM D1 mini box where I have (repeatedly) installed Ubuntu 22.04.1 and 22.04.3 (both fresh and fully updated) on its internal SSD. In all cases the USB3 ports fail to recognize USB3 drives. I have swapped this internal SSD with an SSD (Ubu 22.04.3) from a Lenovo W500 lappy and the USB issue stays with the HP box (all drives automount in the Lenovo box).

To eliminate the ports as culprits, which were working fine with the previous Ubuntu (16.04), I tried several different drives attached to each of the ports (the same ports supporting this USB3 keyboard and mouse and the USB3 hub connecting them). The results were a bit confusing.

Only two drives were able to automount; both Kingston USB2 drives each formatted as an installer (Ubuntu 22.04.1 and ProxMox). The other drives (USB3 WD with EXT4 and UDF, USB3 thumbs with FAT32 and UDF, a memory card with FAT32 (USB3 card reader)) all failed to mount. Further, tools like lsusb, lsblk, blkid, Disks, and GParted show no attached anything for these failures. Finally, dmesg shows no entries surrounding the attaching and detaching of any of these failures, and journalctl shows no activity for them either.

I took one of the USB3 thumbs with UDF and created an Ubu 22.04.3 installer. It remained unrecognized. I then took the USB2 Ubu 22.04.1 installer (these installers are all ISO9660) and created that as 22.04.3. This automounted.

Edit 2: Looks like the drives which function are USB2 while those that fail are trying to run over USB3. However, USB3 hubs work as expected; I can even attached the USB2 installer and it automounts via the USB3 hub.

The below output is with a Kingston USB2 installer (22.04.3) and a WD USB3 EXT4 attached.

$ sudo lsblk 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0     4K  1 loop /snap/bare/5
loop1    7:1    0    62M  1 loop /snap/core20/1587
loop2    7:2    0  63.5M  1 loop /snap/core20/2015
loop3    7:3    0  73.9M  1 loop /snap/core22/864
loop4    7:4    0 163.3M  1 loop /snap/firefox/1635
loop5    7:5    0 236.9M  1 loop /snap/firefox/3131
loop6    7:6    0 400.8M  1 loop /snap/gnome-3-38-2004/112
loop7    7:7    0 349.7M  1 loop /snap/gnome-3-38-2004/143
loop8    7:8    0 485.5M  1 loop /snap/gnome-42-2204/126
loop9    7:9    0 496.9M  1 loop /snap/gnome-42-2204/132
loop10   7:10   0  91.7M  1 loop /snap/gtk-common-themes/1535
loop11   7:11   0  45.9M  1 loop /snap/snap-store/582
loop12   7:12   0  12.3M  1 loop /snap/snap-store/959
loop13   7:13   0  40.8M  1 loop /snap/snapd/20092
loop14   7:14   0   284K  1 loop /snap/snapd-desktop-integration/14
loop15   7:15   0   452K  1 loop /snap/snapd-desktop-integration/83
sda      8:0    0 119.2G  0 disk 
├─sda1   8:1    0   512M  0 part /boot/efi
└─sda2   8:2    0 118.7G  0 part /var/snap/firefox/common/host-hunspell
                                 /
sdb      8:16   1  14.5G  0 disk 
├─sdb1   8:17   1   4.7G  0 part /media/X/Ubuntu 22.04.3 LTS amd64
├─sdb2   8:18   1   4.9M  0 part 
└─sdb3   8:19   1   300K  0 part 

$ sudo blkid 
/dev/sda2: UUID="87549ab1-a5e5-4de2-ba03-d7379bd2107d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="80e7635e-d96e-4b12-af65-6eb1cbddcbdb"
/dev/loop1: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="ESP" LABEL="ESP" UUID="F7DB-4D56" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Appended2" PARTUUID="f45e2fa1-c5a6-4d79-876d-c8245af921e0"
/dev/sdb3: PARTLABEL="Gap1" PARTUUID="f45e2fa1-c5a6-4d79-876c-c8245af921e0"
/dev/sdb1: BLOCK_SIZE="2048" UUID="2023-08-08-01-19-05-00" LABEL="Ubuntu 22.04.3 LTS amd64" TYPE="iso9660" PARTLABEL="ISO9660" PARTUUID="f45e2fa1-c5a6-4d79-876e-c8245af921e0"
/dev/loop15: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="665D-3D08" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="26c459fa-c12f-4bd2-b634-742e3371f6a4"
/dev/loop14: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"

$ sudo lsusb 
Bus 001 Device 009: ID 0930:6544 Toshiba Corp. TransMemory-Mini / Kingston DataTraveler 2.0 Stick
Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This output does not change with or without the WD USB3 EXT4 drive attached:

$ ls -l /dev/* | wc -l 
514

(With the Kingston USB2 attached it raises to 528.)

What is the next step to unpack or solve this mystery?

Edit: Requested in comments (@waltinator).

$ sudo journalctl  --follow 
Sep 23 23:34:48 MYMACHINE kernel: usb 1-1.5.4: USB disconnect, device number 27
Sep 23 23:34:48 MYMACHINE kernel: usb 1-1.5.4.1: USB disconnect, device number 28
Sep 23 23:34:48 MYMACHINE acpid[565]: input device has been disconnected, fd 15
Sep 23 23:34:48 MYMACHINE acpid[565]: input device has been disconnected, fd 16
Sep 23 23:34:49 MYMACHINE kernel: usb 1-1.5.4.2: USB disconnect, device number 29
Sep 23 23:34:49 MYMACHINE kernel: usb 1-1.5.4.4: USB disconnect, device number 30
Sep 23 23:34:49 MYMACHINE acpid[565]: input device has been disconnected, fd 17
Sep 23 23:34:49 MYMACHINE acpid[565]: input device has been disconnected, fd 18
Sep 23 23:34:53 MYMACHINE sudo[5048]: pam_unix(sudo:session): session closed for user root
Sep 23 23:35:02 MYMACHINE sudo[5192]: ME : TTY=pts/1 ; PWD=/home/ME ; USER=root ; COMMAND=/usr/bin/journalctl --follow
Sep 23 23:35:02 MYMACHINE sudo[5192]: pam_unix(sudo:session): session opened for user root(uid=0) by ME(uid=1000)

__detached and re-attached EXT4__ 

__detached and re-attached installer__ 

Sep 23 23:35:49 MYMACHINE kernel: usb 1-1.2: USB disconnect, device number 25
Sep 23 23:35:49 MYMACHINE udisksd[604]: Cleaning up mount point /media/ME/Ubuntu 22.04.3 LTS amd64 (device 8:17 no longer exists)
Sep 23 23:35:49 MYMACHINE systemd[1]: media-ME-Ubuntu\x2022.04.3\x20LTS\x20amd64.mount: Deactivated successfully.
Sep 23 23:35:55 MYMACHINE kernel: usb 1-1.2: new high-speed USB device number 31 using ehci-pci
Sep 23 23:35:55 MYMACHINE kernel: usb 1-1.2: New USB device found, idVendor=0930, idProduct=6544, bcdDevice= 1.00
Sep 23 23:35:55 MYMACHINE kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 23 23:35:55 MYMACHINE kernel: usb 1-1.2: Product: DataTraveler 2.0
Sep 23 23:35:55 MYMACHINE kernel: usb 1-1.2: Manufacturer: Kingston
Sep 23 23:35:55 MYMACHINE kernel: usb 1-1.2: SerialNumber: 50E549C6942EC1B1E9025DA5
Sep 23 23:35:55 MYMACHINE kernel: usb-storage 1-1.2:1.0: USB Mass Storage device detected
Sep 23 23:35:55 MYMACHINE kernel: scsi host6: usb-storage 1-1.2:1.0
Sep 23 23:35:55 MYMACHINE mtp-probe[5218]: checking bus 1, device 31: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2"
Sep 23 23:35:55 MYMACHINE mtp-probe[5218]: bus: 1, device: 31 was not an MTP device
Sep 23 23:35:55 MYMACHINE mtp-probe[5222]: checking bus 1, device 31: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2"
Sep 23 23:35:55 MYMACHINE mtp-probe[5222]: bus: 1, device: 31 was not an MTP device
Sep 23 23:35:56 MYMACHINE kernel: scsi 6:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 4
Sep 23 23:35:56 MYMACHINE kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
Sep 23 23:35:56 MYMACHINE kernel: sd 6:0:0:0: [sdb] 30310400 512-byte logical blocks: (15.5 GB/14.5 GiB)
Sep 23 23:35:56 MYMACHINE kernel: sd 6:0:0:0: [sdb] Write Protect is off
Sep 23 23:35:56 MYMACHINE kernel: sd 6:0:0:0: [sdb] Mode Sense: 45 00 00 00
Sep 23 23:35:56 MYMACHINE kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Sep 23 23:35:56 MYMACHINE kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.
Sep 23 23:35:56 MYMACHINE kernel: GPT:9839183 != 30310399
Sep 23 23:35:56 MYMACHINE kernel: GPT:Alternate GPT header not at the end of the disk.
Sep 23 23:35:56 MYMACHINE kernel: GPT:9839183 != 30310399
Sep 23 23:35:56 MYMACHINE kernel: GPT: Use GNU Parted to correct GPT errors.
Sep 23 23:35:56 MYMACHINE kernel:  sdb: sdb1 sdb2 sdb3
Sep 23 23:35:56 MYMACHINE kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Sep 23 23:35:56 MYMACHINE systemd-udevd[5216]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
Sep 23 23:35:56 MYMACHINE systemd-udevd[5229]: sdb3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb3' failed with exit code 1.
Sep 23 23:35:56 MYMACHINE systemd-udevd[5228]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb2' failed with exit code 1.
Sep 23 23:35:56 MYMACHINE systemd-udevd[5216]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
Sep 23 23:35:56 MYMACHINE kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Sep 23 23:35:56 MYMACHINE kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Sep 23 23:35:56 MYMACHINE kernel: ISO 9660 Extensions: RRIP_1991A
Sep 23 23:35:57 MYMACHINE udisksd[604]: Mounted /dev/sdb1 at /media/ME/Ubuntu 22.04.3 LTS amd64 on behalf of uid 1000

__detached and re-attached EXT4__ 

^C

You can see detaching and attaching the USB2 installer shows output but not the USB3 EXT4 drive.

drivers
Martin Hope
JamesIsIn
Asked: 2021-01-15 10:33:36 +0800 CST
  • 0

I have a backup script which I'm asking now to (offer to) call a git pull script before actually running the syncs (when run interactively). The syncs are done thusly:

rsync aiSP --delete

The backup contains this redirection:

exec 2> "${const_logfile}"

The git pull script has these two lines:

printf '%s\n' "Shall we pull all the gits?  " 
read -rep "(You will have to enter your git password for each one.)  (y or N) " -n1

When rsync runs, all of its progress output shows in the terminal (and doesn't get stuffed into the log file). Any error in rsync is added to the logfile.

When the git pull script is called by the backup script the printf line displays in the terminal, but the read text gets stuffed into the log file (and not displayed). This doesn't happen when that script is called directly.

So I pulled that line of redirect code into a test script that contained only that and the git pull script call, so I'm certain that's the culprit. Finally, I added the redirect code directly into the git pull script and called that directly, and the read text again failed to show in the terminal and was sent to the log file.

I would expect the printf text and the read text to go the same route?

I'm sure there's a simple explanation. Or complex. Enlighten me, please.

EDIT:

Raj was helpful; thanks, Raj!

However, there is more I'd like to understand; so, if anyone knows of an article that talks about what qualifies as these extraordinary messages (as Raj has called them) and why it's useful to send them to stderr, I'd love to read more about this.

Also, someone following along may like to know about the -p aspect of read (from here):

-p prompt Display prompt on standard error, without a trailing newline, before attempting to read any input. The prompt is displayed only if input is coming from a terminal.

bash
Martin Hope
JamesIsIn
Asked: 2020-12-14 09:29:10 +0800 CST
  • 2

I have two laptops which are exhibiting the same behavior (which is to say no behavior at all) when I attach either to my projector. I have two available cable paths for testing, both yielding the same results.

Lenovo w530 (mini-display port --> DVI) Ubuntu 18.04

Lenovo x220 (display port --> DVI) Ubuntu 20.04

I have tried two different DVI cables (with an appropriate set of adapters for each set-up). This is the same cable used to test the external monitors (well, one of the two is but neither work with the projector so I didn't haul the 15' garden hose of a cable in to test it as well).

If I attach any external monitor, I get the expected behavior: There is a brief flicker and the second monitor appears in the Displays settings area. By contrast, if I attach either laptop to my projector nothing happens to either. There is no flicker (of recognition); there is no change in Displays; xrandr shows no changes. Google was fruitless.

What do I need to do to make this work?

I was able to confirm this is a digital connection issue. I cobbled together and tested a VGA solution and it behaved just like the monitor connections have.

EDIT:

I have included output from sudo journalctl --follow:

Output from two separate laptops attempting to connect to an Optoma projector via a DVI cable.

This first one is running Ubuntu 18.04. I added the gap in the middle when I connected the cable with a mini-display port adapter. (There is likely superfluous output at the end as I was checking the projector and not looking at the output directly.):

Also, this first laptop is running a special driver (the second laptop is not). Per Software and Updates:

Software & Updates
NVIDIA Corportation:  GK107GLM [Quadro K1000M]
This device is using an alternative driver.  
Using NVIDIA binary driver - version 340.108 from nvidia-340 (proprietary) 

sudo journalctl --follow
-- Logs begin at Sun 2020-06-28 04:15:21 PDT. --
Dec 19 11:56:31 archer dbus-daemon[1795]: [session uid=1000 pid=1795] Activating via systemd: service name='org.freedesktop.Telepathy.AccountManager' unit='telepathy-mission-control-5.service' requested by ':1.89' (uid=1000 pid=2372 comm="telepathy-indicator " label="unconfined")
Dec 19 11:56:31 archer systemd[1771]: Starting Telepathy Mission Control service...
Dec 19 11:56:31 archer dbus-daemon[1795]: [session uid=1000 pid=1795] Successfully activated service 'org.freedesktop.Telepathy.AccountManager'
Dec 19 11:56:31 archer systemd[1771]: Started Telepathy Mission Control service.
Dec 19 11:56:31 archer dbus-daemon[1795]: [session uid=1000 pid=1795] Activating service name='org.freedesktop.Telepathy.Client.Vino' requested by ':1.90' (uid=1000 pid=2376 comm="/usr/lib/telepathy/mission-control-5 " label="/usr/lib/telepathy/mission-control-5 (enforce)")
Dec 19 11:56:31 archer org.freedesktop.Telepathy.Client.Vino[1795]: Unknown option --tube
Dec 19 11:56:31 archer org.freedesktop.Telepathy.Client.Vino[1795]: Run 'vino-server --help' to see a full list of available command line options
Dec 19 11:56:31 archer dbus-daemon[1795]: [session uid=1000 pid=1795] Activated service 'org.freedesktop.Telepathy.Client.Vino' failed: Process org.freedesktop.Telepathy.Client.Vino exited with status 1
Dec 19 11:56:34 archer sudo[2384]: jamesisin : TTY=pts/0 ; PWD=/home/jamesisin ; USER=root ; COMMAND=/bin/journalctl --follow
Dec 19 11:56:34 archer sudo[2384]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 19 11:56:36 archer zeitgeist-daemon[2287]: [19:56:36.645847 WARNING] zeitgeist-daemon.vala:127: Unable to parse version info!
Dec 19 11:56:36 archer zeitgeist-datah[2386]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!





Dec 19 11:56:47 archer /usr/lib/gdm3/gdm-x-session[1789]: (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-1
Dec 19 11:56:47 archer /usr/lib/gdm3/gdm-x-session[1789]: (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
Dec 19 11:56:47 archer /usr/lib/gdm3/gdm-x-session[1789]: (**) NVIDIA(0):     device DFP-1 (Using EDID frequencies has been enabled on
Dec 19 11:56:47 archer /usr/lib/gdm3/gdm-x-session[1789]: (**) NVIDIA(0):     all display devices.)
Dec 19 11:56:47 archer /usr/lib/gdm3/gdm-x-session[1789]: (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @800x600 +1920+0 {ViewPortIn=800x600, ViewPortOut=800x600+0+0}"
Dec 19 11:56:47 archer /usr/lib/gdm3/gdm-x-session[1789]: (II) NVIDIA(0): Setting mode "NULL"
Dec 19 11:57:17 archer gnome-software[2408]: enabled plugins: systemd-updates, packagekit-url-to-app, packagekit-refresh, packagekit, fwupd, ubuntuone, packagekit-local, packagekit-refine-repos, os-release, shell-extensions, packagekit-proxy, packagekit-upgrade, packagekit-offline, desktop-categories, appstream, packagekit-refine, odrs, desktop-menu-path, steam, hardcoded-featured, generic-updates, modalias, rewrite-resource, hardcoded-popular, hardcoded-blacklist, packagekit-history, snap, provenance, provenance-license, icons, key-colors, key-colors-metadata
Dec 19 11:57:17 archer gnome-software[2408]: disabled plugins: dpkg, repos, dummy, epiphany
Dec 19 11:57:17 archer dbus-daemon[1058]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.122' (uid=1000 pid=2408 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined")
Dec 19 11:57:17 archer systemd[1]: Starting Firmware update daemon...
Dec 19 11:57:18 archer fwupd[2430]: 19:57:18:0244 FuPluginUefi         kernel efivars support missing: /sys/firmware/efi/efivars
Dec 19 11:57:18 archer dbus-daemon[1058]: [system] Successfully activated service 'org.freedesktop.fwupd'
Dec 19 11:57:18 archer systemd[1]: Started Firmware update daemon.
Dec 19 11:57:18 archer PackageKit[1653]: get-updates transaction /14842_edddaebe from uid 1000 finished with success after 941ms
Dec 19 11:57:18 archer gnome-software[2408]: Only 0 apps for recent list, hiding
Dec 19 11:57:19 archer PackageKit[1653]: resolve transaction /14843_ceaccbcd from uid 1000 finished with success after 516ms
Dec 19 11:57:19 archer gnome-shell[1931]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.93/org/ayatana/NotificationItem/software_update_available
Dec 19 11:57:19 archer gnome-shell[1931]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.93/org/ayatana/NotificationItem/livepatch
Dec 19 11:57:21 archer PackageKit[1653]: search-file transaction /14844_edbdddcd from uid 1000 finished with success after 1521ms
Dec 19 11:57:21 archer PackageKit[1653]: search-file transaction /14845_aabbecad from uid 1000 finished with success after 601ms
Dec 19 11:57:22 archer PackageKit[1653]: search-file transaction /14846_aecdeaca from uid 1000 finished with success after 557ms
Dec 19 11:57:23 archer PackageKit[1653]: search-file transaction /14847_daadbcbb from uid 1000 finished with success after 578ms
Dec 19 11:57:23 archer PackageKit[1653]: search-file transaction /14848_bebbedeb from uid 1000 finished with success after 555ms
Dec 19 11:57:24 archer PackageKit[1653]: search-file transaction /14849_bebedecc from uid 1000 finished with success after 556ms
Dec 19 11:57:24 archer PackageKit[1653]: search-file transaction /14850_dcbcadac from uid 1000 finished with success after 555ms
Dec 19 11:57:25 archer PackageKit[1653]: search-file transaction /14851_aabcdccd from uid 1000 finished with success after 556ms
Dec 19 11:57:25 archer PackageKit[1653]: search-file transaction /14852_aeebddde from uid 1000 finished with success after 554ms
Dec 19 11:57:26 archer PackageKit[1653]: search-file transaction /14853_eaaaedad from uid 1000 finished with success after 555ms
Dec 19 11:57:27 archer PackageKit[1653]: search-file transaction /14854_cdeaebad from uid 1000 finished with success after 573ms
Dec 19 11:57:27 archer PackageKit[1653]: search-file transaction /14855_eccdedce from uid 1000 finished with success after 557ms
Dec 19 11:57:28 archer PackageKit[1653]: search-file transaction /14856_adbaedec from uid 1000 finished with success after 560ms
Dec 19 11:57:28 archer PackageKit[1653]: search-file transaction /14857_adddedab from uid 1000 finished with success after 556ms
Dec 19 11:57:29 archer PackageKit[1653]: search-file transaction /14858_bedcdbda from uid 1000 finished with success after 570ms
Dec 19 11:57:30 archer PackageKit[1653]: search-file transaction /14859_eaeedccd from uid 1000 finished with success after 572ms
Dec 19 11:57:30 archer PackageKit[1653]: search-file transaction /14860_adbdabdb from uid 1000 finished with success after 578ms
Dec 19 11:57:31 archer PackageKit[1653]: search-file transaction /14861_dcbaaeea from uid 1000 finished with success after 579ms
Dec 19 11:57:31 archer PackageKit[1653]: search-file transaction /14862_dbeaabad from uid 1000 finished with success after 554ms
Dec 19 11:57:32 archer PackageKit[1653]: search-file transaction /14863_cacdbced from uid 1000 finished with success after 571ms
Dec 19 11:57:32 archer PackageKit[1653]: search-file transaction /14864_bedbdcbe from uid 1000 finished with success after 573ms
Dec 19 11:57:33 archer PackageKit[1653]: search-file transaction /14865_ebacceea from uid 1000 finished with success after 576ms
Dec 19 11:57:34 archer PackageKit[1653]: get-details transaction /14866_cdaadbda from uid 1000 finished with success after 524ms
Dec 19 11:57:34 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:34 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:36 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:37 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:37 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:37 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:37 archer gnome-software[2408]: Failed to load snap icon: local snap has no icon
Dec 19 11:57:38 archer gnome-software[2408]: ignoring non-installed app GsApp: [0x7efcec10b820]
                                             kind:                desktop
                                             state:               available
                                             quirk:               provenance
                                             id:                  org.kde.marble
                                             unique-id:           system/package/ubuntu-bionic-universe/desktop/org.kde.marble/*
                                             scope:               system
                                             bundle-kind:         package
                                             kudos:               my-language|hi-dpi-icon
                                             kudo-percentage:     40
                                             name:                KDE Marble
                                             pixbuf:              0x7efcf01a4d80
                                             icon-kind:           stock
                                             icon-name:           marble
                                             icon-prefix:         /var/lib/app-info/icons/ubuntu-bionic-universe
                                             icon-kind:           cached
                                             icon-name:           marble_marble.png
                                             icon-prefix:         /var/lib/app-info/icons/ubuntu-bionic-universe
                                             icon-kind:           remote
                                             version:             4:17.12.3-0ubuntu1
                                             summary:             Navigation and Maps
                                             description:         Marble is a generic geographical map widget and framework for KDE applications. The Marble widget shows the earth as a sphere but does not require hardware acceleration.  A minimal set of geographical data is included, so it can be used without an internet connection.
                                             
                                             This package is part of the KDE education module.
                                             source-00:           marble
                                             source-id-00:        marble;4:17.12.3-0ubuntu1;amd64;ubuntu-bionic-universe
                                             url{homepage}:       http://edu.kde.org/
                                             license:             LicenseRef-free=https://www.ubuntu.com/about/about-ubuntu/licensing
                                             license-is-free:     yes
                                             management-plugin:   packagekit
                                             origin:              ubuntu-bionic-universe
                                             origin-appstream:    ubuntu-bionic-universe
                                             reviews:             0
                                             provides:            0
                                             install-date:        1
                                             size-installed:      unknowable
                                             size-download:       181.4 kB
                                             category:            Education
                                             category:            Geoscience
                                             category:            Geography
                                             category:            Science
                                             category:            Maps
                                             {GnomeSoftware::Creator}: appstream
^C

This second one is running Ubuntu 20.04 (I added the gap in the middle when I connected the cable with a display port adapter):

sudo journalctl --follow 
-- Logs begin at Fri 2020-04-24 16:20:06 PDT. --
Dec 19 19:00:54 phoenix sudo[11767]: pam_unix(sudo:session): session closed for user root
Dec 19 19:00:54 phoenix sudo[11801]: jamesisin : TTY=pts/1 ; PWD=/home/jamesisin ; USER=root ; COMMAND=/usr/bin/apt autoremove
Dec 19 19:00:54 phoenix sudo[11801]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 19 19:00:55 phoenix sudo[11801]: pam_unix(sudo:session): session closed for user root
Dec 19 19:00:55 phoenix sudo[11829]: jamesisin : TTY=pts/1 ; PWD=/home/jamesisin ; USER=root ; COMMAND=/usr/bin/apt autoclean
Dec 19 19:00:55 phoenix sudo[11829]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 19 19:00:55 phoenix sudo[11829]: pam_unix(sudo:session): session closed for user root
Dec 19 19:01:03 phoenix systemd[1]: zsysd.service: Succeeded.
Dec 19 19:01:25 phoenix sudo[12005]: jamesisin : TTY=pts/0 ; PWD=/home/jamesisin ; USER=root ; COMMAND=/usr/bin/journalctl --follow
Dec 19 19:01:25 phoenix sudo[12005]: pam_unix(sudo:session): session opened for user root by (uid=0)




Dec 19 19:01:35 phoenix kernel: i915 0000:00:02.0: HDMI-A-1: EDID is invalid:
Dec 19 19:01:35 phoenix kernel:         [00] BAD  00 ff ff ff ff ff ff 00 3e 8d 48 33 ae 04 00 00
Dec 19 19:01:35 phoenix kernel:         [00] BAD  35 0f 01 03 80 00 00 78 0a 64 fe a4 59 4e a7 22
Dec 19 19:01:35 phoenix kernel:         [00] BAD  12 4b 50 af de 00 31 59 3b d9 45 59 61 59 81 80
Dec 19 19:01:35 phoenix kernel:         [00] BAD  01 01 01 01 01 01 2f 0d 50 f0 30 e0 25 10 10 70
Dec 19 19:01:35 phoenix kernel:         [00] BAD  68 00 00 00 00 00 00 18 00 00 00 ff 00 4f 38 31
Dec 19 19:01:35 phoenix kernel:         [00] BAD  47 35 35 33 41 31 31 39 38 0a 00 00 00 fc 00 4f
Dec 19 19:01:35 phoenix kernel:         [00] BAD  70 74 6f 6d 61 20 48 33 31 0a 20 20 00 00 00 fd
Dec 19 19:01:35 phoenix kernel:         [00] BAD  00 2b 55 10 45 11 00 0a 20 20 20 20 20 20 a1 ff
^C
video hdmi projector dvi
Martin Hope
JamesIsIn
Asked: 2016-10-28 22:32:02 +0800 CST
  • 1

I have a fresh installation of Ubuntu (several versions) and I want to discover which version of Samba/CIFS it is using to mount drives. I have installed nothing since the OS installation (except gksu and cifs-utils) and I have not yet run updates. It is mounting a couple of CIFS shares via fstab as expected. How do I discover what version the OS is using to establish these mounts?

For those interested, the problem/bug is as follows.

Files and folders which include a : or a ? in their titles are not accessed from certain versions of Ubuntu. The server is correctly serving the files because up until at least Ubu 12.04.5 the files/folders were accessible. By 14.04.5 any file or folder with these characters (and perhaps others considered dangerous by Windows) act thus: folders display and show contents = 0 but cannot be accessed; files display but throw an error when clicked upon. I am seeking the exact point of breakage.

samba