It means likely it crashed while it had the profile locked and the program is too stupid to reclaim the lost lock. That seems to be a really common bug in a lot of programs. They test the lock/unlock and make sure other separate copies won't use the profile when another process is using it, but developers all think their program won't crash so there is no way to lose a lock. and so they forget to handle the program crashing with the profile being locked and lose the lock. And there are cases that lock reclaim can fail on if the lock reclaim process suspects that the holder is not the same host. The hostname referenced is probably another name for your IP address of your workstation. try a dig <name> and or a ping name and see if it comes back as your IP address Best guess is do a find ~/ -iname "*lock*" -ls and see if there is a file that looks like a lock. THese are the ones I find 24 Nov 24 14:35 ./.config/chromium/SingletonLock -> mylaptop2023-laptop-1663681 0 Nov 24 14:35 ./.config/chromium/Default/Feature\ Engagement\ Tracker/EventDB/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Feature\ Engagement\ Tracker/AvailabilityDB/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/coupon_db/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/PersistentOriginTrials/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Extension\ State/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/shared_proto_db/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/shared_proto_db/metadata/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Extension\ Scripts/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Session\ Storage/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/commerce_subscription_db/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Site\ Characteristics\ Database/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/optimization_guide_hint_cache_store/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Local\ Extension\ Settings/gphhapmejobijbbhgpjhcjognlahblep/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/optimization_guide_model_metadata_store/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/GCM\ Store/Encryption/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Download\ Service/EntryDB/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/AutofillStrikeDatabase/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/BudgetDatabase/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Sync\ Extension\ Settings/gphhapmejobijbbhgpjhcjognlahblep/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Extension\ Rules/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/parcel_tracking_db/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Segmentation\ Platform/SignalDB/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Segmentation\ Platform/SegmentInfoDB/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Segmentation\ Platform/SignalStorageConfigDB/LO 0 Nov 24 14:35 ./.config/chromium/Default/Local\ Storage/leveldb/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/Sync\ Data/LevelDB/LOCK 0 Nov 24 14:35 ./.config/chromium/Default/discounts_db/LOCK And it may be that the first lock in my list has a name (on yours) that confuses the lock reclaim. Possibly the ip address does not resolve to the same name both forward and reverse, and/or it resolves to several different names/ips. On Fri, Nov 24, 2023 at 12:21 PM Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > On Thu, 23 Nov 2023, ToddAndMargo via users wrote: > > > Restart you computer and try again. Let us know > > <win><R> shutdown /r /f /t 00 > > Did that. Didn't help. > > -- > Michael hennebry@xxxxxxxxxxxxxxxxxxxxxx > "I was just thinking about the life of a pumpkin. Grow up in the sun, > happily entwined with others, and then someone comes along, > cuts you open, and rips your guts out." -- Buffy > -- > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
