Announcement

**oshunluvr** · May 01, 2016, 02:36 PM

Ok, been working on it.

Figured out the the change to SDDM showing the login on all screens was a fix to a complaint about it showing up on the wrong screen in some usercases. I would have preferred a user configurable option instead of the shotgun approach.

It's locked up on me three times today, but I'm also doing a lot of changes so some of it could be my fault. Only one of the crashes required the reset button. For the other two RSEIUB worked fine.

Today I got bonding setup, enabled samba and nfs clients, installed a few more programs. HP Systray no longer fails at log in like it did in 15.04 and I switched to "Dashboard" menu, which is cool. Not only is it different, you don't have to install extra widgets - just right-click on the K-Menu icon and select what you like.

**elijathegold** · May 01, 2016, 03:34 PM

My experience seems to be a bit smoother than most; this is likely because those for whom it worked don't want to jinx things by speaking too soon. It may also be that I had decided to do a fresh installation when Kubuntu reached 16.04. It has not been without its problems though.

The laptop monitor would randomly refuse to wake up from a sleep, while the external monitors attached to the VGA and HDMI ports would. This was a potential show stopper but installing the intel-microcode package fixed that problem.
The external monitor on the HDMI port loses it's background, widgets and right click menu sometimes when it wakes up. If the monitor sleeps without these it may get them back when waking up! I think this is a bug worth filing, if I can figure out a pattern.
The Device Driver Manager is completely broken but at least the terminal version of ubuntu-drivers is available to get things installed. It's how I identified the intel-microcode package mentioned earlier.
This one is so minor but so bloody annoying. I run yauake with three terminals ready to go but when I hit F12, I get dropped in to a random one, not the one I was using last. It may be a setting somewhere but it has already caused a couple of minor tantrums and nearly one major error on my part!
Dolphin has crashed a few times as has System Settings. In all those cases, I have let it send a report.

@oshunluvr: I always REISUB as the mnenomic I was taught is BUSIER backwards but it can't hurt syncing earlier in the process. I'm trying out the Dashboard menu and I quite like it. I miss the Application Menu (QML) though.

I think that if I had been in charge of the release at Canonical I would have held it for one or maybe two more weeks even if that meant drifting slightly in to May. This would have allowed for a few more fixes to be applied and hopefully a smoother experience for more people. It's mostly been a trouble free transition for me so I'll end this with a thank you to the people at Canonical and the dedicated community who put together Kubuntu.

**vinnywright** · May 01, 2016, 04:10 PM

ya ,,regarding those magic keys ,,,,,,the only ones that still work are "S,U.B" with B being the "emergency reboot" so don't use it first

my experience is well with it ,,,,,,,,,but I have Neon added to it as well,,,,,,, /dev/stable .

VINNY

**elijathegold** · May 01, 2016, 04:14 PM

Originally posted by vinnywright View Post

ya ,,regarding those magic keys ,,,,,,the only ones that still work are "S,U.B" with B being the "emergency reboot" so don't use it first

my experience is well with it ,,,,,,,,,but I have Neon added to it as well,,,,,,, /dev/stable .

VINNY

You had me franticly re-reading my post. To my relief I did say BUSIER backwards

**vinnywright** · May 01, 2016, 04:20 PM

Originally posted by elijathegold View Post

You had me franticly re-reading my post. To my relief I did say BUSIER backwards

LOL ,,,,yes ,,,yes you did ,,,,sory

but I did clear that up a bit for someone new to the game reading it

VINNY

**GreyGeek** · May 01, 2016, 05:18 PM

Since my install of 16.04 a month ago I have been very pleased with its overall stability and speed. FF works fine, but I use Chromium most of the time. I have never had a lockup. I am still getting this message in the system log every hour, regularly:

Code:

(colord:933): Cd-WARNING **: failed to get session [pid 4279]: No such device or address

but nothing appears to be malfunctioning. It seems to coordinate with this message:

Code:

[system] Failed to activate service 'org.bluez': timed out

I don't use BlueTooth.

I also get this error:

Code:

BTRFS error (device sda1): could not find root 8

but a scrub of /dev/sda1 (my only partition on the HD) revealed no errors.
It is a known error but on my system it doesn't seem to be the cause of any problems. I suspect that it is a false flag.

Doing a sudo cat /proc/mounts was interesting:

Code:

[FONT=monospace][COLOR=#000000]jerry@jerry-Aspire-7739:~$ sudo cat /proc/mounts[/COLOR]
[sudo] password for jerry:  
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=3899572k,nr_inodes=974893,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=783812k,mode=755 0 0
[B]/dev/sda1 / btrfs rw,relatime,space_cache,subvolid=257,subvol=/@ 0 0[/B]
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent
,name=systemd,nsroot=/ 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,nsroot=/ 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids,nsroot=/ 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio,nsroot=/ 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct,nsroot=/ 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb,nsroot=/ 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio,nsroot=/ 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory,nsroot=/ 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event,nsroot=/ 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer,nsroot=/ 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices,nsroot=/ 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
tracefs /sys/kernel/debug/tracing tracefs rw,relatime 0 0
[B]/dev/sda1 /home btrfs rw,relatime,space_cache,subvolid=258,subvol=/@home 0 0[/B]
tmpfs /run/user/118 tmpfs rw,nosuid,nodev,relatime,size=783812k,mode=700,uid=118,gid=126 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=783812k,mode=700,uid=1000,gid=1000 0 0
jerry@jerry-Aspire-7739:~$  
[/FONT]

So, regardless of what's happening under the hood Xerus is working fine for me. My principle apps are Chromium, Stellarium, the SAGE Math engine, Steam's Universe^2 and the usual utilities: Dolphin, MC, Konsole, KSysGuard, KSystemLog, K3B, LibreOffice, Synaptic, Kate, Audacity and, or course, SystemSettings. All run quickly, without failures. Booting up and shutting down is relatively quick. The QuickLauncher, HPLIP and the ThermalMonitor widgets all work great. My SIXX IPv6 tunnel works great (but SIXX is no longer taking new signups and sooner or later I will have to get an IPv6 router, when RR gets on the ball and delivers IPv6 to our area.

**elijathegold** · May 02, 2016, 02:23 PM

Originally posted by elijathegold View Post

The laptop monitor would randomly refuse to wake up from a sleep, while the external monitors attached to the VGA and HDMI ports would. This was a potential show stopper but installing the intel-microcode package fixed that problem.

It seems that it has only been partially solved.

**oshunluvr** · May 02, 2016, 03:18 PM

Originally posted by GreyGeek View Post

Code:

(colord:933): Cd-WARNING **: failed to get session [pid 4279]: No such device or address

This message is related to a bug that is fixed in colord v. 1.3.1 but we're still on 1.2.12. Seems like it's harmless.

Originally posted by GreyGeek View Post

I also get this error:

Code:

BTRFS error (device sda1): could not find root 8

but a scrub of /dev/sda1 (my only partition on the HD) revealed no errors.
It is a known error but on my system it doesn't seem to be the cause of any problems. I suspect that it is a false flag.

From what I read this is related to systemd triggering btrfs quota (which is still a bit buggy). Again, safe to ignore. I get the same one.

I'm got a segfault and "QT bearer thread" error relating to libgcc_s.so.1. I have no idea what the culprit is here but it occurs early in the boot process and doesn't reoccur.

One of my port aggregation options that I carried over from 15.04 is deprecated and generates and error. I'll fix that in a bit.

The other issue I'm having is related to using sysctl.conf to set various options (on another thread). It seems that systemd has changed the way of doing business and so I have some learnin' to do. They like to keep us old guys on our toes, right Jerry?

**GreyGeek** · May 02, 2016, 05:23 PM

Originally posted by oshunluvr View Post

...
They like to keep us old guys on our toes, right Jerry?

My toes don't work very well and it's worse on the other end!

I feel fortunate that Kubuntu is so easy to use.

**GreyGeek** · May 04, 2016, 09:09 PM

Originally posted by GreyGeek View Post

....
I also get this error:

Code:

BTRFS error (device sda1): could not find root 8

but a scrub of /dev/sda1 (my only partition on the HD) revealed no errors.
It is a known error but on my system it doesn't seem to be the cause of any problems. I suspect that it is a false flag.
...

Not a false flag, just a harmless bug.
http://thread.gmane.org/gmane.comp.f...ms.btrfs/50672

On a btrfs that has never had quota enabled:

# btrfs qgroup show /

Results in kernel message:
[ 378.103836] BTRFS: could not find root 8

Each time I issue the same command, I get another "could not find..." message. This is rather indirect, but probably means quotas aren't enabled, and I'd expect you get this message every boot, and that it can be ignored.

Someone checked systemd code and found:

Code:

Looking at the systemd source, it seems that it could enable quota when playing with the "machine":

See src/shared/machine-pool.c:

int setup_machine_directory(uint64_t size, sd_bus_error *error) {
        _cleanup_release_lock_[U]file[/U]_ LockFile lock_file = LOCK_FILE_INIT;
        struct loop_info64 info = {
                .lo_flags = LO_FLAGS_AUTOCLEAR,
[...]
        r = check_btrfs();
        if (r < 0)
                return sd_bus_error_set_errnof(error, r, "Failed to determine whether /var/lib/machines is located on btrfs: %m");
        if (r > 0) {
                (void) btrfs_subvol_make_label("/var/lib/machines");

                [B]r = btrfs_quota_enable("/var/lib/machines", true);[/B]
[...]

But I was unable to understand if:
- enabling quota is a "per filesystem" attribute or per "subvolume attribute"
- when systemd invokes setup_machine_directory()

Does someone have more information ?

BR

In response Qu said:

Code:

Btrfs quota is a "per filesystem" attribute.
Yeah, it's filesystem level.

And the root reason for the "could not find root" error message is: btrfs doesn't have a good enough ioctl API for btrfs qgroup.

Currently, btrfs already has several IOCTLs, but only covers the following operations:
1) Enable/disable quota -> IOC_QUOTA_CTL
2) Rescan and rescan status -> IOC_QUOTA_RESCAN* (3 ioctls)
3) Qgroup create/remove/assign -> IOC_[U]QGROUP[/U]_* (3 ioctls)

It does [B]*NOT*[/B] include the most used operation, show qgroup accounting.

And "btrfs qgroup show" commands uses the generic tree search facility to manually get needed qgroup info.

Unfortunately, generic tree search will output such error if one is searching for a non-exist tree.

So the result is, either we find a good idea to create a dedicated qgroup ioctl(either new ioctl number or integrate it into existing one), 
[B]or just ignore the error message.
[/B]
Thanks,
Qu

So, everytime systemd provokes a btrfs quota on a system that doesn't have quotas enabled that "root 8" message appears in the logs.

**oshunluvr** · May 05, 2016, 05:39 AM

Wow, nice research. I enable quota once (not on this install) and found it interesting but there is/was some issues with leaving it enabled. I don't recall what exactly, but I know it was recommended not to have it enabled full time.

**elijathegold** · May 05, 2016, 09:06 AM

Well, I'm preparing to go back to 14.04 on my main computer. It turns out that Xenial is just too exciting to be used on it. I'm keeping it on my second computer though as some excitement is a good thing.

**GreyGeek** · May 05, 2016, 03:54 PM

Thanks, oshunluvr!

Originally posted by elijathegold View Post

Well, I'm preparing to go back to 14.04 on my main computer. It turns out that Xenial is just too exciting to be used on it. I'm keeping it on my second computer though as some excitement is a good thing.

You can't go wrong with 14.04, especially if you need reliability and stability to get work done. However, I have to say that on MY hardware (Acer Aspire 7739-6830, i3-370M, 8GB RAM, Intel Corporation Core Processor Integrated Graphics Controller (rev 02)) 16.04 has been VERY fast and increasingly stable. I've never had the system or kernel crash, only the occasional app. Strangely, the apps continue to work even following a crash report. I just close the crash report and continue using the app. The crash reports cause me to investigate dmesg and KSystemLog to see what's going on. There I see the following "error"s or "fail"s:

Code:

[  554.263838] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[  554.264342] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun

0: _OSC failed (AE_ERROR); disabling ASPM

BTRFS error (device sda1): could not find root 8

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(colord:930): Cd-WARNING **: failed to get session [pid 6595]: No such device or address

[system] Failed to activate service 'org.bluez': timed out
0:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads

None cause any problems in the operation of this laptop.

The bluez msg is immaterial since I don't have any Bluetooth devices, and the last msg is a timing problem during boot that resolves itself after the i915 mod loads.

Btrfs has been stellar in its performance. A couple days ago I loaded 7,985 emails into kate and searched them for a phrase. The results came back in a few seconds and I could jump from one selection to the other in a blink. Gotta love kate! Steam runs great. The Universal Sandbox^2 simulation runs several times faster under 16.04 than it did under 14.04. The only change is Plasma5. GL 2.0 or XRaster both give excellent speed and behavior for graphic apps. GL 3.0 causes blinking of Stellarium.

The other msgs relate to "problems" which have no apparent effect on the operation of my installation, which is running faster, and as smooth, as any previous version of Kubuntu or other distros I have installed on the bare metal of this laptop. I am very pleased with 16.04 and am glad I overcame my dislike of Plasma5 to install it.

**oshunluvr** · May 05, 2016, 04:18 PM

Nice report Jerry. I jumped from 15.04 to here (15.10 had too many bad reports for my taste) and 16.04 is way faster than 15.04 was. I can power up and be logged into my desktop in 40 seconds or less. Amazing. The last couple niggling issues I had were Synergy and HP Systray not loading at login on 15.04 but on 16.04 they both work correctly. Bluetooth is more stable (on 15.04 about every fourth boot my bluetooth dongle would not be recognized required a manual re-load of bluetooth) and Dropbox icons are there without help from me, although the cloud icon for dropbox is not to my liking - I actually liked the open box icon better.

I've had a couple of odd lockups over the last couple of days, but nothing serious. I've been mucking about a bit so I usually expect a random freeze or crash once in awhile. My biggest issue right now is sudoers is not working on this install at all. I have another thread devoted to this problem, but I may end up doing a new install to see if the issue is related to an installer problem. My Vbox 16.04 sudoers works. Here on bare metal it does not. Weird...

Announcement

My Xerus experience so far....

My Xerus experience so far....

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment