heynnema's questions

Ubuntu 24.10
Wayland
Nvidia MX330
Nvidia 560.35.03

I was led to believe that the prior problems of running a Nvidia card were fixed under Wayland in Ubuntu 24.10.

So I upgraded from 24.04 to 24.10 and ran under Xorg, solved some various upgrade issues, and it seemed to run fine.

Then I enabled Wayland. With some minor problems, it ran fine. I decided to put the Nvidia into "Performance mode", and it seemed fine until I checked nvidia-smi and noted that only gnome-shell was being accelerated.

Here I show via the cli that the Nvidia Performance Mode is selected...

Here is show the GUI showing Performance Mode under Xorg...

Here is nvidia-smi running under Xorg... note the full compliment of processes that are accelerated... whereas under Wayland it only shows gnome-shell...

So my question is... is this a Wayland or Nvidia problem? What steps might I take to further troubleshoot this and fix it?

Update: So I upgraded from 24.04 to 24.10 and ran under Xorg, solved some various upgrade issues, and it seemed to run fine.

I find that I can't open folders on my Desktop, in Xorg, in "Performance Mode". "On-Demand" works fine.

Every time I boot/reboot my computer, it runs fsck, and I don't know why.

If I boot to a Ubuntu USB stick, and manually run fsck on my Linux partitions, it comes clean.

Below is my super-block. I've tried changing the "Maximum mount count" and the "Check interval" with no change in behaviour.

Any idea why this happens?

$ sudo tune2fs -l /dev/nvme0n1p6

tune2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   Ubuntu
Last mounted on:          /
Filesystem UUID:          f0db2226-e28d-46dd-9b5a-457c87987ed2
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              40845312
Block count:              163380224
Reserved block count:     8169011
Overhead clusters:        2844802
Free blocks:              57597994
Free inodes:              40012689
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stride:              4
RAID stripe width:        32
Flex block group size:    16
Filesystem created:       Fri Sep 24 20:06:49 2021
Last mount time:          Sun Oct  6 17:47:34 2024
Last write time:          Sun Oct  6 18:01:39 2024
Mount count:              5
Maximum mount count:      23
Last checked:             Sun Oct  6 10:00:35 2024
Check interval:           0 (<none>)
Lifetime writes:          10 TB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:           256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
First orphan inode:       17714152
Default directory hash:   half_md4
Directory Hash Seed:      7e1d3c28-3106-4408-8132-4b574d84a675
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0xce551aef

Ubuntu 23.10/24.04
Dell Inspiron 7700 AIO
6.5.0-35-generic/6.8.0-31-generic
X11

Some recent 23.10/24.04 update has broken my system. The brightness slider is no longer visible. And the directory /sys/class/backlight/ is empty.

The backlight driver dell_uart_backlight is not loaded on my 24.04 system. It's not even present on the 24.04 distribution.

If I boot to a Ubuntu 23.10.1 flash drive, it all works fine. So the problem has occurred since the 23.10.1 version.

[Update] Turns out that booting to the 23.10.1 flash drive only partially fixes the problem. The brightness slider appears, but it really doesn't update the screen brightness when moved. Booting to a 23.04 flash drive, and everything works as its supposed to.

[Update] Brightness control no longer working after update to Ubuntu 23.10 in computer Dell OptiPlex 7780 AIO

The command gdbus call --session --dest org.gnome.SettingsDaemon.Power --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepUp returns:

GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_5fpower_5fmanager_5ferror.Code1: No usable backlight could be found!

[Update] Adding the acpi_backlight=vendor kernel parameter in /etc/default/grub makes no difference.

[Update] I am able to set backlight brightness with the following xrandr command:

xrandr --output HDMI-1 --brightness 0.85

[Update] It seems that the dell_uart_backlight driver is missing on my 24.04 system.

ls -alR /lib/modules/6.5.0-35-generic/ | grep dell
-rw-r--r--   1 root root 13689 Apr 26 02:32 dell-smm-hwmon.ko.zst
drwxr-xr-x  3 root root  4096 May 15 19:10 dell
/lib/modules/6.5.0-35-generic/kernel/drivers/platform/x86/dell:
-rw-r--r-- 1 root root 18647 Apr 26 02:32 dell-laptop.ko.zst
-rw-r--r-- 1 root root  6158 Apr 26 02:32 dell-rbtn.ko.zst
-rw-r--r-- 1 root root  8431 Apr 26 02:32 dell_rbu.ko.zst
-rw-r--r-- 1 root root 13963 Apr 26 02:32 dell-smbios.ko.zst
-rw-r--r-- 1 root root  4432 Apr 26 02:32 dell-smo8800.ko.zst
-rw-r--r-- 1 root root  7762 Apr 26 02:32 dell-uart-backlight.ko.zst
-rw-r--r-- 1 root root  3799 Apr 26 02:32 dell-wmi-aio.ko.zst
-rw-r--r-- 1 root root  9209 Apr 26 02:32 dell-wmi-ddv.ko.zst
-rw-r--r-- 1 root root  4532 Apr 26 02:32 dell-wmi-descriptor.ko.zst
-rw-r--r-- 1 root root 11198 Apr 26 02:32 dell-wmi.ko.zst
-rw-r--r-- 1 root root  3115 Apr 26 02:32 dell-wmi-led.ko.zst
drwxr-xr-x 2 root root  4096 May 15 19:10 dell-wmi-sysman
/lib/modules/6.5.0-35-generic/kernel/drivers/platform/x86/dell/dell-wmi-sysman:
-rw-r--r-- 1 root root 18312 Apr 26 02:32 dell-wmi-sysman.ko.zst

ls -alR /lib/modules/6.8.0-31-generic/ | grep dell
-rw-r--r--   1 root root 15140 Apr 19 14:46 dell-smm-hwmon.ko.zst
drwxr-xr-x  3 root root  4096 May 25 10:15 dell
/lib/modules/6.8.0-31-generic/kernel/drivers/platform/x86/dell:
-rw-r--r-- 1 root root 18629 Apr 19 14:46 dell-laptop.ko.zst
-rw-r--r-- 1 root root  6180 Apr 19 14:46 dell-rbtn.ko.zst
-rw-r--r-- 1 root root  8582 Apr 19 14:46 dell_rbu.ko.zst
-rw-r--r-- 1 root root 14726 Apr 19 14:46 dell-smbios.ko.zst
-rw-r--r-- 1 root root  4433 Apr 19 14:46 dell-smo8800.ko.zst
-rw-r--r-- 1 root root  3790 Apr 19 14:46 dell-wmi-aio.ko.zst
-rw-r--r-- 1 root root  9166 Apr 19 14:46 dell-wmi-ddv.ko.zst
-rw-r--r-- 1 root root  4492 Apr 19 14:46 dell-wmi-descriptor.ko.zst
-rw-r--r-- 1 root root 11306 Apr 19 14:46 dell-wmi.ko.zst
-rw-r--r-- 1 root root  3108 Apr 19 14:46 dell-wmi-led.ko.zst
drwxr-xr-x 2 root root  4096 May 25 10:15 dell-wmi-sysman
/lib/modules/6.8.0-31-generic/kernel/drivers/platform/x86/dell/dell-wmi-sysman:
-rw-r--r-- 1 root root 18307 Apr 19 14:46 dell-wmi-sysman.ko.zst

Removing acpi_backlight=vendor from /dev/default/grub makes no difference. However, adding acpi_backlight=video gives me the appropriate files in /sys/class/backlight, and I now get a brightness slider... although changing the slider doesn't actually change the brightness.

[Update] Submitted bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067498

I'm trying to adjust the color calibration for my LCD video display.

I purchased a Datacolor Spyder X Pro colorimeter which is supposed to be supported.

I installed argyll 2.3.1 and its support files, colord-sensor-argyll 1.4.6-3, icc-profiles 2.1-2, gnome-color-manager 3.36.0-2, and displaycal 3.9.11-1.

I open Settings and go to the Color section, select my display, and click on the calibrate button. I go through the following steps...

And here's where I get stopped. Where is the Start button?

Update #1 - 2/21/24:

This appears to be a bug that goes all the way back to Ubuntu 22.10. I'm told that it works fine in 22.04, but I haven't verified that yet.

Post note: I just installed 22.04 in a Virtualbox VM, and the Start button appears, when it should, during calibration.

Update #2 - 2/22/24:

After implementing the patch from the answer by Daniel T (thanks BTW), it does now get a "Start" button, but after clicking it, the color patch remains white, and it errors out with "internal error".

See the following information from the terminal, and syslog.

al@al-Inspiron-7700-AIO:~/Desktop$ sh askubuntu_color_calibration_fix.sh 
09:18:10.5465       cc-color-panel[18961]: WARNING: calibration failed with code 1: Timeout was reached

al@al-Inspiron-7700-AIO:~/Desktop$ cd /var/log
al@al-Inspiron-7700-AIO:/var/log$ tail syslog
2024-02-22T09:18:26.993688-08:00 al-Inspiron-7700-AIO ubuntu-report[3390]: level=error msg="data were not delivered successfully to metrics server, retrying in 120s"
2024-02-22T09:18:35.407512-08:00 al-Inspiron-7700-AIO systemd[3355]: Started app-gnome-org.gnome.Settings-19159.scope - Application launched by gnome-shell.
2024-02-22T09:18:35.707775-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00004
2024-02-22T09:19:21.000134-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x56149c6b1f90] is on because it needs an allocation.
2024-02-22T09:19:21.000796-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x56149e0ec310] is on because it needs an allocation.

Post note: I have a Dell AIO with a touch screen.

Update #3 - 2/22/24:

Here's the screenshot that Daniel T's patch created...

Update #4 - 2/22/24:

After installing gnome-color-manager, DisplayCAL worked. GNOME Settings still fail.

I just upgraded from Ubuntu 21.10 to 22.04.

sudo apt update ends with the following warnings...

W: https://linux.teamviewer.com/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://apt.keepsolid.com/ubuntu/dists/groovy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://linux.dropbox.com/ubuntu/dists/disco/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://download.virtualbox.org/virtualbox/debian/dists/hirsute/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://download.opensuse.org/repositories/home:/IBBoard:/cawbird/xUbuntu_22.04/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://ppa.launchpad.net/solaar-unifying/stable/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

Synaptic shows the same warnings on a reload.

Reviewing man apt-key doesn't clarify this for me.

I think this is because Ubuntu 22.04 has transitioned from using /etc/apt/trusted.gpg to using individual .gpg files located in /etc/apt/trusted.gpg.d.

Can these keys be converted from one to the other, or must I delete these keys and reimport them?

Thunderbird 91.3.1

If I start Thunderbird from the terminal, and then select any email message to read, I see the following error...

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Google doesn't give any real clue about what an "IPDL protocol error" is.

To troubleshoot, I logged into a separate Ubuntu account where Thunderbird had never been used. I started Thunderbird from the terminal and created a mail account using one of my Google gmail accounts. Read any message, and got the same problem. So it's not an account-specific problem.

Partial log from terminal...

~$ thunderbird
[calBackendLoader] Using Thunderbird's libical backend
[LDAPModuleLoader] Using LDAPDirectory.jsm
[MsgSendModuleLoader] Using MessageSend.jsm
[SmtpModuleLoader] Using SmtpService.jsm
console.debug: WebExtensions: 
  Compact Headers loaded
1642775310275   tbsortfolders.folderPane    DEBUG   Init
1642775310275   tbsortfolders.folderPane    DEBUG   Add observer
console.debug: "Trying to load /usr/lib/thunderbird/libotr.so"
console.debug: "Trying to load libotr.so from system's standard library locations"
console.debug: "Trying to load libotr.so.5 from system's standard library locations"
console.debug: "Successfully loaded OTR library libotr.so.5 from system's standard library locations"
console.debug: "Successfully loaded OpenPGP library librnp.so version 0.15.2+git20210806.dd923a4e.MZLA from /usr/lib/thunderbird/librnp.so"
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)"
console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11 from system's standard library locations"
console.debug: "gpgme version: 1.14.0-unknown"

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Any ideas what this error is about?

I feel a little silly asking this question... as the answer may be quite simple... but searching here on AU, or on Google, or man mail, hasn't given me the answer.

If I start mail, I see this:

"/var/mail/al": 8 messages 8 unread
>U   1 root@al-Inspiron-7 Sun Nov 28 06:01 156/5409  Logwatch for al-Inspiron-
 U   2 root@al-Inspiron-7 Mon Nov 29 06:11 173/6447  Logwatch for al-Inspiron-
 U   3 root@al-Inspiron-7 Tue Nov 30 05:23 149/5261  Logwatch for al-Inspiron-
 U   4 root@al-Inspiron-7 Wed Dec  1 01:53 215/9228  Logwatch for al-Inspiron-
 U   5 root@al-Inspiron-7 Thu Dec  2 02:27 187/7610  Logwatch for al-Inspiron-
 U   6 root@al-Inspiron-7 Fri Dec  3 05:42 204/8129  Logwatch for al-Inspiron-
 U   7 root@al-Inspiron-7 Sat Dec  4 06:37 143/5074  Logwatch for al-Inspiron-
 U   8 root@al-Inspiron-7 Sun Dec  5 07:09 170/5922  Logwatch for al-Inspiron-
?

After I read the first message, I get this:

? h
>R   1 root@al-Inspiron-7 Sun Nov 28 06:01 156/5409  Logwatch for al-Inspiron-
 U   2 root@al-Inspiron-7 Mon Nov 29 06:11 173/6447  Logwatch for al-Inspiron-
 U   3 root@al-Inspiron-7 Tue Nov 30 05:23 149/5261  Logwatch for al-Inspiron-
 U   4 root@al-Inspiron-7 Wed Dec  1 01:53 215/9228  Logwatch for al-Inspiron-
 U   5 root@al-Inspiron-7 Thu Dec  2 02:27 187/7610  Logwatch for al-Inspiron-
 U   6 root@al-Inspiron-7 Fri Dec  3 05:42 204/8129  Logwatch for al-Inspiron-
 U   7 root@al-Inspiron-7 Sat Dec  4 06:37 143/5074  Logwatch for al-Inspiron-
 U   8 root@al-Inspiron-7 Sun Dec  5 07:09 170/5922  Logwatch for al-Inspiron-
?

If I quit mail, and restart mail, I see this:

? q
Saved 1 message in /home/al/mbox
Held 7 messages in /var/mail/al
al@al-Inspiron-7700-AIO:~$ mail
"/var/mail/al": 7 messages 7 unread
>U   1 root@al-Inspiron-7 Mon Nov 29 06:11 174/6491  Logwatch for al-Inspiron-
 U   2 root@al-Inspiron-7 Tue Nov 30 05:23 149/5261  Logwatch for al-Inspiron-
 U   3 root@al-Inspiron-7 Wed Dec  1 01:53 215/9228  Logwatch for al-Inspiron-
 U   4 root@al-Inspiron-7 Thu Dec  2 02:27 187/7610  Logwatch for al-Inspiron-
 U   5 root@al-Inspiron-7 Fri Dec  3 05:42 204/8129  Logwatch for al-Inspiron-
 U   6 root@al-Inspiron-7 Sat Dec  4 06:37 143/5074  Logwatch for al-Inspiron-
 U   7 root@al-Inspiron-7 Sun Dec  5 07:09 170/5922  Logwatch for al-Inspiron-
?

How can I list/read the previous message #1 (no longer in the list)?

I just upgraded from Ubuntu 21.04 to Ubuntu 21.10.

Baring a few glitches here and there, it's now running ok.

However, I just discovered that Thunderbird 91.x.x removed movemail support! That means that I've lost support for my /var/mail/* mboxes!

Other than installing another mail program, like possibly Evolution, is there any way to get to my mboxes again?

Don't know why, but they decided to add sssd (System Security Services Daemon) to the standard Ubuntu 20.10 upgrade and fresh install. It fails to start, and generates lots of error messages. It's not configured at install time, as it's missing the required /etc/sssd/sssd.conf file.

SSSD is a system daemon. Its primary function is to provide access to local or remote identity and authentication resources through a common framework that can provide caching and offline support to the system. It provides several interfaces, including NSS and PAM modules or a D-Bus interface.

You can see the failure with:

systemctl status sssd

When I wish to create a Wi-Fi Hotspot in 20.04, the option is greyed out.

If I view/edit any ethernet/wi-fi connection profile, the panel is compressed, as seen in the image below. The "Last Used" field is too low in the window. I have two Ubuntu 20.04 laptops showing the same problem.

I don't use a custom theme (I use yaru-light). Font sizes make no difference. Scaling=1.00. Intel video.

I believe this started after some Software Update.

Any ideas why this is happening, and how to fix it?

Just updated to 20.04 final release, and I'm seeing these messages in /var/log/auth.log...

May 14 06:29:52 Satellite-E55 gdm-password]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
May 14 07:40:14 Satellite-E55 su: pam_unix(su:auth): Couldn't open /etc/securetty: No such file or directory

I looked back at a 19.10 VM, and /etc/securetty was there. All my 20.04 systems are missing this file. Two 20.04 installations are upgrades, and one installation is a fresh install VM.

What's up with this file missing in 20.04? Should I restore a copy from 19.10?

Update #1:

The same problem occurs in 20.10, in both upgrades and fresh installs.

On Ubuntu 19.04 I had current rtl8812au (AC1200) and rtl8814au (AC1750) dkms drivers for my USB wireless dongles installed and running fine.

They both broke after I upgraded to Ubuntu 19.10.

I've been able to find a replacement/newer rtl8812au driver that works with kernel 5.3 on Ubuntu 19.10.

I haven't been able to find a replacement/newer rtl8814au driver that works with kernel 5.3 on Ubuntu 19.10.

Github.com has a number of rtl8814au drivers available, even some that proport to compile with kernel 5.2. I believe that I've tried about 6 different rtl8814au drivers from github, but none of them work, even though some of them do compile with kernel 5.3.

Does anybody know of a working rtl8814au driver that works with kernel 5.3 on Ubuntu 19.10?

I'm seeing a lot of repetitive colord errors in /var/log/syslog. I've reinstalled colord and colord-data with no help. Anybody have any ideas on how to cure this?

$ systemctl status colord
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled)
   Active: active (running) since Wed 2018-12-19 08:36:40 PST; 7h ago
 Main PID: 29950 (colord)
    Tasks: 3 (limit: 4915)
   Memory: 6.1M
   CGroup: /system.slice/colord.service
           └─29950 /usr/lib/x86_64-linux-gnu/colord

Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyShutdown ::= { netSnmpNotifications 2 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyRestart ::= { netSnmpNotifications 3 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laErrMessage ::= { laEntry 101 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laLoadFloat ::= { laEntry 6 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laLoadInt ::= { laEntry 5 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laConfig ::= { laEntry 4 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laLoad ::= { laEntry 3 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laNames ::= { laEntry 2 }
Dec 19 08:36:40 Satellite-E55 colord[29950]: Cannot adopt OID in UCD-SNMP-MIB: laIndex ::= { laEntry 1 }

Here's a snippet of what's in syslog...

Dec 18 06:25:26 Satellite-E55 colord[1309]: failed to get session [pid 10755]: No data available
Dec 18 06:25:26 Satellite-E55 colord[1309]: failed to get session [pid 10755]: No data available
Dec 18 07:02:11 Satellite-E55 colord[1309]: MIB search path: /var/lib/colord/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IF-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IP-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (TCP-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (UDP-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (MTA-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 15 in /usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-SMI): At line 34 in /usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 37 in /usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'TruthValue' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in UCD-SNMP-MIB: ucdavis ::= { enterprises 2021 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: enterprises near line 39 of /usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'ucdExperimental' in module UCD-SNMP-MIB (/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in UCD-DISKIO-MIB: ucdDiskIOMIB ::= { ucdExperimental 15 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: ucdExperimental near line 19 of /usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 10 in /usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'ucdExperimental' in module UCD-SNMP-MIB (/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in UCD-DLMOD-MIB: ucdDlmodMIB ::= { ucdExperimental 14 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: ucdExperimental near line 13 of /usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 15 in /usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'ucdExperimental' in module UCD-SNMP-MIB (/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in LM-SENSORS-MIB: lmSensors ::= { ucdExperimental 16 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: ucdExperimental near line 32 of /usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'ucdavis' in module UCD-SNMP-MIB (/usr/share/snmp/mibs/UCD-DEMO-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in UCD-DEMO-MIB: ucdDemoMIB ::= { ucdavis 14 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: ucdavis near line 7 of /usr/share/snmp/mibs/UCD-DEMO-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-FRAMEWORK-MIB): At line 9 in /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-SMI): At line 8 in /usr/share/snmp/mibs/NET-SNMP-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-MIB: netSnmp ::= { enterprises 8072 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: enterprises near line 10 of /usr/share/snmp/mibs/NET-SNMP-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 21 in /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'SnmpAdminString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpObjects' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpModuleIDs' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpNotifications' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpGroups' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'RowStatus' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'TruthValue' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsAgentNotifyGroup ::= { netSnmpGroups 9 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpGroups near line 545 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsTransactionGroup ::= { netSnmpGroups 8 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpGroups near line 536 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsConfigGroups ::= { netSnmpGroups 7 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpGroups near line 515 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsCacheGroup ::= { netSnmpGroups 4 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpGroups near line 505 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsModuleGroup ::= { netSnmpGroups 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpGroups near line 495 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: netSnmpAgentMIB ::= { netSnmpModuleIDs 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpModuleIDs near line 24 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsTransactions ::= { netSnmpObjects 8 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 55 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsConfiguration ::= { netSnmpObjects 7 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 54 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsErrorHistory ::= { netSnmpObjects 6 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 53 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsCache ::= { netSnmpObjects 5 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 52 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsDLMod ::= { netSnmpObjects 4 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 51 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsExtensions ::= { netSnmpObjects 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 50 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsMibRegistry ::= { netSnmpObjects 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 49 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsVersion ::= { netSnmpObjects 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 48 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsNotifyRestart ::= { netSnmpNotifications 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpNotifications near line 482 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsNotifyShutdown ::= { netSnmpNotifications 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpNotifications near line 476 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-AGENT-MIB: nsNotifyStart ::= { netSnmpNotifications 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpNotifications near line 470 of /usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-MPD-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-USER-BASED-SM-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-FRAMEWORK-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-COMMUNITY-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IPV6-ICMP-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IPV6-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IPV6-TCP-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IPV6-UDP-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (IP-FORWARD-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-FRAMEWORK-MIB): At line 10 in /usr/share/snmp/mibs/NET-SNMP-PASS-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-FRAMEWORK-MIB): At line 10 in /usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 12 in /usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (INET-ADDRESS-MIB): At line 13 in /usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'SnmpAdminString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmp' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'RowStatus' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'StorageType' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'InetAddressType' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'InetAddress' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-EXAMPLES-MIB: netSnmpExamples ::= { netSnmp 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmp near line 16 of /usr/share/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'SnmpAdminString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-PASS-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpExamples' in module NET-SNMP-EXAMPLES-MIB (/usr/share/snmp/mibs/NET-SNMP-PASS-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-PASS-MIB: netSnmpPassExamples ::= { netSnmpExamples 255 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpExamples near line 14 of /usr/share/snmp/mibs/NET-SNMP-PASS-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 16 in /usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'nsExtensions' in module NET-SNMP-AGENT-MIB (/usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'RowStatus' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'StorageType' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-EXTEND-MIB: nsExtendGroups ::= { nsExtensions 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: nsExtensions near line 39 of /usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-EXTEND-MIB: nsExtendObjects ::= { nsExtensions 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: nsExtensions near line 38 of /usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-EXTEND-MIB: netSnmpExtendMIB ::= { nsExtensions 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: nsExtensions near line 19 of /usr/share/snmp/mibs/NET-SNMP-EXTEND-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-NOTIFICATION-MIB): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TM): At line 1 in (none)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-FRAMEWORK-MIB): At line 9 in /usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 16 in /usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot find module (SNMPv2-TC): At line 25 in /usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'SnmpAdminString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpObjects' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'netSnmpGroups' in module NET-SNMP-MIB (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'vacmGroupName' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'vacmAccessContextPrefix' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'vacmAccessSecurityModel' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'vacmAccessSecurityLevel' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'DisplayString' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'RowStatus' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Did not find 'StorageType' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt)
Dec 18 07:02:11 Satellite-E55 colord[1309]: Unlinked OID in NET-SNMP-VACM-MIB: netSnmpVacmMIB ::= { netSnmpObjects 9 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Undefined identifier: netSnmpObjects near line 28 of /usr/share/snmp/mibs/NET-SNMP-VACM-MIB.txt
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchRegExCompilation ::= { logMatchEntry 101 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchErrorFlag ::= { logMatchEntry 100 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchCycle ::= { logMatchEntry 11 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchCount ::= { logMatchEntry 10 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchCounter ::= { logMatchEntry 9 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchCurrentCount ::= { logMatchEntry 8 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchCurrentCounter ::= { logMatchEntry 7 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchGlobalCount ::= { logMatchEntry 6 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchGlobalCounter ::= { logMatchEntry 5 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchRegEx ::= { logMatchEntry 4 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchFilename ::= { logMatchEntry 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchName ::= { logMatchEntry 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: logMatchIndex ::= { logMatchEntry 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-VACM-MIB: nsVacmAccessEntry ::= { nsVacmAccessTable 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extErrFixCmd ::= { extEntry 103 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extErrFix ::= { extEntry 102 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extOutput ::= { extEntry 101 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extResult ::= { extEntry 100 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extCommand ::= { extEntry 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extNames ::= { extEntry 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: extIndex ::= { extEntry 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-DEMO-MIB: ucdDemoPublic ::= { ucdDemoMIBObjects 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-DLMOD-MIB: dlmodTable ::= { ucdDlmodMIB 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-DLMOD-MIB: dlmodNextIndex ::= { ucdDlmodMIB 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-EXAMPLES-MIB: netSnmpExamples ::= { netSnmp 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-MIB: netSnmpConformance ::= { netSnmp 5 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-MIB: netSnmpNotificationPrefix ::= { netSnmp 4 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-MIB: netSnmpExperimental ::= { netSnmp 9999 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-MIB: netSnmpEnumerations ::= { netSnmp 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-MIB: netSnmpObjects ::= { netSnmp 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionDoDebugging ::= { version 20 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionSavePersistentData ::= { version 13 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionRestartAgent ::= { version 12 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionUpdateConfig ::= { version 11 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionClearCache ::= { version 10 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionConfigureOptions ::= { version 6 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionIdent ::= { version 5 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionCDate ::= { version 4 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionDate ::= { version 3 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionTag ::= { version 2 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in UCD-SNMP-MIB: versionIndex ::= { version 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-EXAMPLES-MIB: netSnmpExampleHeartbeatNotification ::= { netSnmpExampleNotificationPrefix 1 }
Dec 18 07:02:11 Satellite-E55 colord[1309]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsCacheStatus ::= { nsCacheEntry 3 }

New problem in >18.04...

I just discovered that the way I've always used fsck at the root access in recovery mode no longer works. It used to be:

fsck -f /

But now it tells me that the disk is mounted r/w, and it won't run. Sure enough the disk IS mounted r/w. This is new behavior. Trying to remount the disk as ro doesn't work either.

mount -o remount,ro /

And, running fsck from the recovery mode menus doesn't work either.

Running fsck while booted to a Ubuntu Live USB works of course.

Anybody got an idea why I can't fsck in recovery mode, and what's changed that causes the disk to be mounted r/w?

I just took a working Gateway P4 desktop computer and upgraded it from 16.04LTS all the way to 17.10 without any problem. As soon as I tried to install 18.04LTS, I had trouble booting.

I've reinstalled in many different ways, with no improvement in the boot problem. The Ubuntu logo appears and the dots flash a few times, then the mouse pointer freezes and the system is totally unresponsive. If I boot with the "quiet splash" removed from the kernel line in grub, I can see that it just stops shortly after starting the first user account 120.

Here is a clue... If I replace "quiet splash" with nomodeset, it boots fully, but it's in 640x480 mode only.

Here's the i915 video information...

  *-display UNCLAIMED
       description: VGA compatible controller
       product: 82945G/GZ Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 02
       width: 32 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:e0300000-e037ffff ioport:20e0(size=8) memory:d0000000-dfffffff memory:e0380000-e03bffff memory:c0000-dffff

I suspect that I need to add a special i915 video controller kernel parameter to grub to make the video work properly. Any ideas on what parameter that might be... or any other ideas?

Update #1: I just discovered that if I boot into "Recovery Mode", and then choose "Resume normal boot", it boots fully, to a 1024x768 4:3 (should be 16:9) desktop.

Update #2: Upgrading from 17.10 to 18.04, booting fails. Reinstalling 18.04, booting fails. Disk partition delete and clean 18.04, booting fails. Installing 18.04 "proposed" software, booting still fails. Ubuntu Live DVD works fine.

Update #3: I found a list of i915 parameters...

~$ modinfo -p i915
modeset:Use kernel modesetting [KMS] (0=disable, 1=on, -1=force vga console preference [default]) (int)
panel_ignore_lid:Override lid status (0=autodetect, 1=autodetect disabled [default], -1=force lid closed, -2=force lid open) (int)
semaphores:Use semaphores for inter-ring sync (default: -1 (use per-chip defaults)) (int)
enable_rc6:Enable power-saving render C-state 6. Different stages can be selected via bitmask values (0 = disable; 1 = enable rc6; 2 = enable deep rc6; 4 = enable deepest rc6). For example, 3 would enable rc6 and deep rc6, and 7 would enable everything. default: -1 (use per-chip default) (int)
enable_dc:Enable power-saving display C-states. (-1=auto [default]; 0=disable; 1=up to DC5; 2=up to DC6) (int)
enable_fbc:Enable frame buffer compression for power savings (default: -1 (use per-chip default)) (int)
lvds_channel_mode:Specify LVDS channel mode (0=probe BIOS [default], 1=single-channel, 2=dual-channel) (int)
lvds_use_ssc:Use Spread Spectrum Clock with panels [LVDS/eDP] (default: auto from VBT) (int)
vbt_sdvo_panel_type:Override/Ignore selection of SDVO panel mode in the VBT (-2=ignore, -1=auto [default], index in VBT BIOS table) (int)
reset:Attempt GPU resets (default: true) (bool)
error_capture:Record the GPU state following a hang. This information in /sys/class/drm/card<N>/error is vital for triaging and debugging hangs. (bool)
enable_hangcheck:Periodically check GPU activity for detecting hangs. WARNING: Disabling this can cause system wide hangs. (default: true) (bool)
enable_ppgtt:Override PPGTT usage. (-1=auto [default], 0=disabled, 1=aliasing, 2=full, 3=full with extended address space) (int)
enable_execlists:Override execlists usage. (-1=auto [default], 0=disabled, 1=enabled) (int)
enable_psr:Enable PSR (0=disabled, 1=enabled - link mode chosen per-platform, 2=force link-standby mode, 3=force link-off mode) Default: -1 (use per-chip default) (int)
alpha_support:Enable alpha quality driver support for latest hardware. See also CONFIG_DRM_I915_ALPHA_SUPPORT. (bool)
disable_power_well:Disable display power wells when possible (-1=auto [default], 0=power wells always on, 1=power wells disabled when possible) (int)
enable_ips:Enable IPS (default: true) (int)
fastboot:Try to skip unnecessary mode sets at boot time (default: false) (bool)
prefault_disable:Disable page prefaulting for pread/pwrite/reloc (default:false). For developers only. (bool)
load_detect_test:Force-enable the VGA load detect code for testing (default:false). For developers only. (bool)
force_reset_modeset_test:Force a modeset during gpu reset for testing (default:false). For developers only. (bool)
invert_brightness:Invert backlight brightness (-1 force normal, 0 machine defaults, 1 force inversion), please report PCI device ID, subsystem vendor and subsystem device ID to [email protected], if your machine needs it. It will then be included in an upcoming module version. (int)
disable_display:Disable display (default: false) (bool)
enable_cmd_parser:Enable command parsing (true=enabled [default], false=disabled) (bool)
use_mmio_flip:use MMIO flips (-1=never, 0=driver discretion [default], 1=always) (int)
mmio_debug:Enable the MMIO debug code for the first N failures (default: off). This may negatively affect performance. (int)
verbose_state_checks:Enable verbose logs (ie. WARN_ON()) in case of unexpected hw state conditions. (bool)
nuclear_pageflip:Force enable atomic functionality on platforms that don't have full support yet. (bool)
edp_vswing:Ignore/Override vswing pre-emph table selection from VBT (0=use value from vbt [default], 1=low power swing(200mV),2=default swing(400mV)) (int)
enable_guc_loading:Enable GuC firmware loading (-1=auto, 0=never [default], 1=if available, 2=required) (int)
enable_guc_submission:Enable GuC submission (-1=auto, 0=never [default], 1=if available, 2=required) (int)
guc_log_level:GuC firmware logging level (-1:disabled (default), 0-3:enabled) (int)
guc_firmware_path:GuC firmware path to use instead of the default one (charp)
huc_firmware_path:HuC firmware path to use instead of the default one (charp)
enable_dp_mst:Enable multi-stream transport (MST) for new DisplayPort sinks. (default: true) (bool)
inject_load_failure:Force an error after a number of failure check points (0:disabled (default), N:force failure at the Nth failure check point) (uint)
enable_dpcd_backlight:Enable support for DPCD backlight control (default:false) (bool)
enable_gvt:Enable support for Intel GVT-g graphics virtualization host support(default:false) (bool)

Update #4: I'm currently running with i915.modeset=0 in my grub kernel line, it's booting, and I'm getting 1024x768 (4:3).

Update #5: Updating to kernel 4.16.9 doesn't fix the problem.

Update #6: A portion of @karel's answer provided a good enough workaround. Switching from gdm3 display manager to lightdm display manager works. I could then also remove i915.modeset=0 from my grub kernel line.

sudo apt-get update
sudo apt-get install lightdm
# if lightdm wasn't already installed, it'll ask which dm you want
# if lightdm was already installed, then you need to:
sudo dpkg-reconfigure lightdm
# and choose lightdm over gdm3
reboot

Update #7:

Turns out that the problem isn't a gdm3 vs lightdm problem. It's a gdm3/wayland problem with older Intel GPU's. To fix...

In terminal...

• cd /etc/gdm3 # change directory
• sudo pico custom.conf # edit this file

Find and change:

#WaylandEnable=false

To this:

WaylandEnable=false

Save the file.

• sudo dpkg-reconfigure gdm3 # select gdm3 DM

Select gdm3 and OK.

• reboot # reboot the computer

Notes:

https://feeding.cloud.geek.nz/posts/linux-kernel-module-options-on-debian/

Setting kernel options for the i915

How can I fix broken i915 drivers for Intel GPUs?

I have gdebi set as the default application to install .deb files. This way, I can just double-click on a .deb file and the gdebi installer will do the rest.

It seems that since 17.10, or one of its updates, this no longer works. I double-click on a .deb file, gdebi launches, showing the appropriate .deb file information, I click INSTALL, and gdebi just exits.

I have reinstalled all of the gdebi software components. No change.

However, in terminal, I type sudo gdebi some_filename.deb, it all works fine.

Any idea why the GUI doesn't work any more? I'm using xorg, not wayland.

Update #1: I have two machines with this problem. Both were upgrades to 17.10.

Update #2: If I manually open gdebi and manually select the .deb file to install, it all works fine.

Update #3: If I show properties of any .deb file, and try to change the "Open With" application, GDebi doesn't show up in the list of available applications.

Final Update: Late postnote... gdebi has problems in 18.xx too. It won't install .deb files when you double-click them... if they're on the desktop... it never asks for admin password. Anywhere else, it works as it should.

I accidentally installed ubuntu-gnome-desktop (initially with lightdm, and later switched to gdm3) on my heavily customized Ubuntu (Unity) 16.10 environment. Yikes! Now a bunch of stuff in Unity doesn't work as it did before. I need help fixing some unresolved problems. Can you please help?

1. Desktop problems

   • In Unity, I can't set desktop background
   • In Unity, the superkey doesn't bring up dashboard unless another application is in the foreground
   • In Unity, the desktop files and folders are gone
   • In Unity, I can't right-click on the desktop and bring up the contextual menu

2. Font problem

   • In Unity, the default fonts have changed

3. Touchpad problems

   • In Unity, the touchpad-indicator crashes, looking for Synaptics touchpad driver
   • In Unity, the touchpad "tap to single-left-click" no longer works
   • In Unity, the touchpad preferences are missing in System Settings/Mouse & Touchpad panel
   • In Gnome, the touchpad preferences do show up in System Settings

I believe that this is because xserver-xorg-input-libinput got installed, thereby disabling the Synaptics touchpad driver. Can I safely uninstall this, and hopefully re-enable the Synaptics driver, without breaking anything in the Unity desktop, or the Gnome desktop?

4. Login screen problem

   • The main login screen background is black. How do I get any background to show again?

5. Default DE problem

   • The login area always shows "Gnome (Default)" in the list of desktop environments. How do I change the default to "Ubuntu (Default)"?

6. Boot/shutdown screens problem

   • Boot and shutdown screens are Gnome animation/text screens. How do I bring back normal Ubuntu/Unity boot/shutdown screens?

I'm running Ubuntu 16.10, and I'm trying to hide my GRUB menu at power on/boot time, and wish the menu to appear only when I hit the Shift or Esc keys.

I change the appropriate options in /etc/default/grub and it still won't hide the menu.

In researching this, I found this post from 2013 GRUB hidden menu not working that indicates that the problem has been around for a while, and suggests a change to /etc/grub.d/30_os-prober which I'd rather not do. That code suggests that since its found multiple OS's, it's going to set the GRUB_TIMEOUT=10 anyway.

Here's a snippet of what I have now in /etc/default/grub... a menu with a 10 second countdown...

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_HIDDEN_TIMEOUT_QUIET=true
#GRUB_HIDDEN_TIMEOUT=0
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

If I uncomment #GRUB_HIDDEN_TIMEOUT=0, then sudo update-grub insists that I also set GRUB_TIMEOUT=10 to GRUB_TIMEOUT=0. I do that, and I still see the GRUB menu.

In terminal, typing info -f grub -n 'Simple configuration' describes the various options, and at the very end of the info, it shows that some of the current commands have been depreciated, and suggests that the newer replacements are better.

Does anybody know how I can get my GRUB menu to hide in 16.10 AND have it recognize Shift or Esc keys at boot time?

New problem. Ubuntu 16.04/16.10. Now, whenever I start gparted, new disk partition icons appear, just above the trash can icon, in the Unity launcher. I have to "unlock from launcher" to get rid of them.

Older posts for older versions of Ubuntu propose various fixes that no longer apply in 16.04/16.10. Any ideas of how to permanently get rid of these pesky icons?

Here's a screenshot that shows the 3 icons, just above the trash can icon: