http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c1 Luca Beltrame changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbeltrame@kde.org --- Comment #1 from Luca Beltrame --- I saw this issue yesterday. Apparently udisks mis-identifies the stick as an ISO-9660 volume. Can you try pasting the output of udisksctl info -b <partition> ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c3 --- Comment #3 from Luca Beltrame --- Comment on attachment 730531 --> http://bugzilla.opensuse.org/attachment.cgi?id=730531 Output of udisksctl info -b /dev/sdb1

IdType: iso9660

Looks like it's being mis-identified. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c5 Pierre Bonamy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |flyos@mailoo.org --- Comment #5 from Pierre Bonamy --- Most likely a problem in the partition table and formatting of the key see the duplicate here: https://bugzilla.opensuse.org/show_bug.cgi?id=1046096 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c7 Andrei Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #7 from Andrei Borzenkov --- (In reply to Luca Beltrame from comment #4)

It looks to me like a possible issue with udisks,

The only way I can reproduce this behavior is when I do *NOT* create filesystem on partition. Then filesystem on this partition gets misidentified (due to udev properties inherited by partition from containing block device). If I create filesystem on partition, it is also correctly shown by udev. and udiskctl Neither of these bugs reports contains actual instructions how to reproduce it. Please provide exact steps how to do it on command line showing exact commands (or better capturing the whole session). Of course the problem of leaked properties should be fixed too. In particular it means partition inherits iso9660 label unless it is explicitly set in partition filesystem. But it still *is* mounted here on XFCE. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c33 Mark Hounschell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmarkh@cfl.rr.com --- Comment #33 from Mark Hounschell --- I can verify that this bug is also present in Leap 42.3. Leap 42.2 does not have this issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c35 Anton Aylward changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@antonaylward.com --- Comment #35 from Anton Aylward --- (In reply to Mark Hounschell from comment #33)

I can verify that this bug is also present in Leap 42.3. Leap 42.2 does not have this issue.

Then its a DIFFERENCE in the rules between 42.2 and 42.3. As such, I'm not sure that this constitutes a bug when it's a difference in the installed configuration. Both rules make sense. Yes, its an inconsistency, but it could be argued that 42.3 was correcting an error in 42.2. I've looked at my hard disk which is outside the rules and OBVIOUSLY I get different results if I run blkid on /dev/sda and /ded/sda1. Which is as it should be. Inconsistency between releases that constituent corrections are sometimes a matter of opinion. Let me ask an awkward question. My main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that partition should the KDE popup select? Whichever one, it might not be the one I want and hence it is "misidentified by the device notifier". In this case, recognizing the device makes sense. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c37 --- Comment #37 from Mark Hounschell --- Anton, "Let me ask an awkward question. My main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that partition should the KDE popup select?" It should show ALL of them (/dev/sdX#). No matter what /dev/sdX says. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c39 --- Comment #39 from Anton Aylward --- (In reply to Lucifer Watson from comment #38)

(In reply to Anton Aylward from comment #35)

...

Let me ask an awkward question.

My main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that partition should the KDE popup select?

Whichever one, it might not be the one I want and hence it is "misidentified by the device notifier". In this case, recognizing the device makes sense.

Let me ask you an awkward question:

Would you expect the 1T USB drive to be correctly identified and mounted or not?

You don't mount a DRIVE, you mount a partition. Let us assume that the rules identify it as a USB drive. in order to mount a partition it has to determine the partition table entries, gpt or whatever. if there is more than one partition then a selection of which partition to use has to be made. I repeat, you don't mount a drive, you mount a partition. (or, if you're using LVM a LV, but lets not make this more complicated than it has to be) I think that this has already been answered, the popup offers the user a choice, its not an automated decision. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c41 --- Comment #41 from Lucifer Watson --- (In reply to Anton Aylward from comment #39)

(In reply to Lucifer Watson from comment #38)

...

(In reply to Anton Aylward from comment #35)

...

Let me ask an awkward question.

My main drive that my system is installed on, the 1Terabyte SATA, has three partitions. I could equally buy a 1T USB drive and format that with three, or more, partitions. When I plug that in that partition should the KDE popup select?

Whichever one, it might not be the one I want and hence it is "misidentified by the device notifier". In this case, recognizing the device makes sense.

Let me ask you an awkward question:

Would you expect the 1T USB drive to be correctly identified and mounted or not?

You don't mount a DRIVE, you mount a partition.

Let us assume that the rules identify it as a USB drive. in order to mount a partition it has to determine the partition table entries, gpt or whatever. if there is more than one partition then a selection of which partition to use has to be made.

I repeat, you don't mount a drive, you mount a partition. (or, if you're using LVM a LV, but lets not make this more complicated than it has to be)

I think that this has already been answered, the popup offers the user a choice, its not an automated decision.

I plug in my USB key with the line in the file /usr/lib/udev/rules.d/61-persistent-storage-compat.rules uncommented and the device is mis-identified and not mounted. See the image below. https://i.imgur.com/5OTuz0f.png I comment out that line and reload the rules then plug in the same key and voilà! it is recognised and mounted correctly. See the image below. https://i.imgur.com/r8kIVrp.png If a repeatable and consistent error doesn't match your definition of a bug, could you please explain what does. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c44 --- Comment #44 from Mark Hounschell --- (In reply to Thomas Blume from comment #42)

(In reply to Wolfgang Bauer from comment #40)

...

But the problem in this bug report is that the device notifier doesn't show any partitions because the drive is misidentified as CD by udisks2.

The udisks2 issue should be fixed by comment#29. Can you confirm?

I can confirm that it fixes the issue on Leap 42.3 and a recently updated Leap 42.2 but I have no TW installation to test it on. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1046268 http://bugzilla.opensuse.org/show_bug.cgi?id=1046268#c55 François Valenduc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |francois.valenduc@tvcablene | |t.be --- Comment #55 from François Valenduc --- As far as I can see, no new version has appeared in opensuse 42.3 to solve this problem. Is this normal ? -- You are receiving this mail because: You are on the CC list for the bug.