You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
don't know if this is the right place, but if not, could you please direct me to a place whrer it might be better suited?
Our problem:
We do have an headleass appliance, that used to work with centOS 6.9. Now we updated to AlmaLinux 8.9 and have a problem regarding udev-notifications for inserting media into the slot-in drive.
Secnario A: CentOs 6.9 behaviour:
As soon as "something" was going on with the drive, there were couple of udev "change" events (disc inserted, disc spinning, reading, ejecting,...)
Scenario B: AlmaLinux 8.9 No KDE: (same hardware)
only if a correct filesystem is present, the udev "change" event is fired. If a heavily scratched disc, an empty on, or a disc inserted upside-down is inserted into the device, no notificaiton is triggered at all. The disc stays in the device indefinetly
Scenario C: AlmaLinux 8.9 KDE: (same hardware)
also no events are triggerd, but somehow after some time the disc will be ejcted.
We are kind of puzzled cause of the 2 questions:
why are there no change events for interacions of the device with the media
who triggers the eject in Scenario C?
thank you, if you could help us and get us in the right direction!
Poidi
The text was updated successfully, but these errors were encountered:
Hi There,
don't know if this is the right place, but if not, could you please direct me to a place whrer it might be better suited?
Our problem:
We do have an headleass appliance, that used to work with centOS 6.9. Now we updated to AlmaLinux 8.9 and have a problem regarding udev-notifications for inserting media into the slot-in drive.
Secnario A: CentOs 6.9 behaviour:
As soon as "something" was going on with the drive, there were couple of udev "change" events (disc inserted, disc spinning, reading, ejecting,...)
Scenario B: AlmaLinux 8.9 No KDE: (same hardware)
only if a correct filesystem is present, the udev "change" event is fired. If a heavily scratched disc, an empty on, or a disc inserted upside-down is inserted into the device, no notificaiton is triggered at all. The disc stays in the device indefinetly
Scenario C: AlmaLinux 8.9 KDE: (same hardware)
also no events are triggerd, but somehow after some time the disc will be ejcted.
We are kind of puzzled cause of the 2 questions:
thank you, if you could help us and get us in the right direction!
Poidi
The text was updated successfully, but these errors were encountered: