![](https://seccdn.libravatar.org/avatar/9a8f1dab91209201c3262fe5ca01ef60.jpg?s=120&d=mm&r=g)
On Wed, Feb 03, 2016 at 07:20:55AM -0500, Patrick Shanahan wrote:
Just did an update which included: akregator5-15.12.1-34.4.x86_64 kmail5-15.12.1-34.4.x86_64 kaddressbook5-15.12.1-34.4.x86_64 korganizer5-15.12.1-34.4.x86_64 kontact5-15.12.1-34.4.x86_64 knotes5-15.12.1-34.4.x86_64 kdepim-15.12.1-34.4.x86_64 libkdepim-15.12.1-34.4.x86_64 konqueror-15.12.1-7.4.x86_64 konqueror-plugins-15.12.1-7.4.x86_64 kdebase4-libkonq-15.12.1-7.4.x86_64 akonadi_resources-15.12.1-34.4.x86_64 ...
And now the device notifier which is set to "Removable devices only" shows \ and home partitions on my ssd drive ????
Does this need a bug report or ....?
Me too, so please file a bug report :) My systems's being doing that since I installed TW. I did wonder if it was confused by the default partitioning for UEFI/GPT, but haven't got around to investigating. Is your setup similar? I accepted the partitioning recommended by yast2 which created sda1 as vfat for the EFI System Partition, some swap and sda3 as btrfs for / . Probably unrelated, but I also noticed whines in the journal on each boot, like: Feb 01 12:00:12 chunk kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. I figured it would be best to boot cleanly from a rescue disk to check that partition with /boot umounted, but intended to read up a bit more before doing this, UEFI, GPT & btrfs are new to me. I've had a few kernel crashes so it is quite possible that /boot has got mangled. Daniel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org