chromium will not start

[Michael Hennebry]

I recently installed the chromium browser on F38.
It won't start.  At least it won't stay started very long.

When I start it from the command line, I get this:
$ chromium-browser
[297210:297210:1123/181637.109041:ERROR:process_singleton_posix.cc(353)] The 
profile appears to be in use by another Chromium process (2215) on another 
computer (localhost-live.midcoip.net). Chromium has locked the profile so that 
it doesn't get corrupted. If you are sure no other processes are using this 
profile, you can unlock the profile and relaunch Chromium.
[297210:297210:1123/181637.109237:ERROR:message_box_dialog.cc(146)] Unable to 
show a dialog outside the UI thread message loop: Chromium - The profile appears 
to be in use by another Chromium process (2215) on another computer 
(localhost-live.midcoip.net). Chromium has locked the profile so that it doesn't 
get corrupted. If you are sure no other processes are using this profile, you 
can unlock the profile and relaunch Chromium.

I don't even know what that means.
What profile?
What is Midcontinent doing with it?  How?
Why is a "profile" even involved?
Who is making money off my "profile"?  How?
I have no idea how I would unlock my "profile".
I suppose the claim will be made that it is for security.

Grrr.

[ToddAndMargo]

On 11/23/23 17:04, Michael Hennebry wrote:
> I recently installed the chromium browser on F38.
> It won't start.  At least it won't stay started very long.
>
> When I start it from the command line, I get this:
> $ chromium-browser
> [297210:297210:1123/181637.109041:ERROR:process_singleton_posix.cc(353)] 
> The profile appears to be in use by another Chromium process (2215) on 
> another computer (localhost-live.midcoip.net). Chromium has locked the 
> profile so that it doesn't get corrupted. If you are sure no other 
> processes are using this profile, you can unlock the profile and 
> relaunch Chromium.
> [297210:297210:1123/181637.109237:ERROR:message_box_dialog.cc(146)] 
> Unable to show a dialog outside the UI thread message loop: Chromium - 
> The profile appears to be in use by another Chromium process (2215) on 
> another computer (localhost-live.midcoip.net). Chromium has locked the 
> profile so that it doesn't get corrupted. If you are sure no other 
> processes are using this profile, you can unlock the profile and 
> relaunch Chromium.
>
> I don't even know what that means.
> What profile?
> What is Midcontinent doing with it?  How?
> Why is a "profile" even involved?
> Who is making money off my "profile"?  How?
> I have no idea how I would unlock my "profile".
> I suppose the claim will be made that it is for security.
>
> Grrr.

Restart you computer and try again.  Let us know
<win><R> shutdown /r /f /t 00

[Michael Hennebry]

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.

[Roger Heflin]

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
 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   [e-mail]
> "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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Michael Hennebry]

OOn Fri, 24 Nov 2023, Roger Heflin wrote:
> It means likely it crashed while it had the profile locked and the
> program is too stupid to reclaim the lost lock.

So while did it fail the first time?
> 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

What's a profile and how do I unlock it>
> 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

hennebry@2001-48F8-3004-2CE-0-0-0-284-dynamic ~]$ nslookup 
localhost-live.midcoip.net
Server:		127.0.0.53
Address:	127.0.0.53#53

** server can't find localhost-live.midcoip.net: NXDOMAIN

I realize 127.0.0.1 is my computer,
but I'm not clear on how 127.0.053 and 127.0.0.53#53 are used.
> Best guess is do a find ~/ -iname "*lock*" -ls    and see if there is
> a file that looks like a lock.

I got 36 lock files all with hromi in the name.
> 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.

How do I unlock?

[Roger Heflin]

A profile (for a browser) is where you bookmarks/cookies/cache and
other associated stuff needed exist.

You can typically (on most browsers) have more than one profile.

If you aren't running chromium currently then you delete the files.
You might do a "ps -elf | grep -i chromium" and make sure you only see
the grep.

On Fri, Nov 24, 2023 at 4:43 PM Michael Hennebry
 wrote:
> OOn Fri, 24 Nov 2023, Roger Heflin wrote:
> > It means likely it crashed while it had the profile locked and the
> > program is too stupid to reclaim the lost lock.
>
> So while did it fail the first time?
> > 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
>
> What's a profile and how do I unlock it>
> > 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
>
> hennebry@2001-48F8-3004-2CE-0-0-0-284-dynamic ~]$ nslookup
> localhost-live.midcoip.net
> Server:         127.0.0.53
> Address:        127.0.0.53#53
>
> ** server can't find localhost-live.midcoip.net: NXDOMAIN
>
> I realize 127.0.0.1 is my computer,
> but I'm not clear on how 127.0.053 and 127.0.0.53#53 are used.
> > Best guess is do a find ~/ -iname "*lock*" -ls    and see if there is
> > a file that looks like a lock.
>
> I got 36 lock files all with hromi in the name.
> > 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.
>
> How do I unlock?
>
> --
> Michael   [e-mail]
> "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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Mike Wright]

On 11/24/23 14:43, Michael Hennebry wrote:
> I realize 127.0.0.1 is my computer,
> but I'm not clear on how 127.0.053 and 127.0.0.53#53 are used.

All addresses from 127.0.0.0 to 127.255.255.255 are on your machine. 
They are called loopback addresses (because they loop back to you).

Usually the machine grabs the first routable address, 127.0.0.1, and 
uses that for itself.  Sometimes services will pick one of your 
268,435,454 available addresses to use as its own.

In this case it's probably some sort of DNS.  (DNS runs on port #53).
Here whatever it is is running on 127.0.0.53 port 53.

I use port numbers in my localhost services all the time.

127.53.0.0 authoritative DNS
127.0.53.0 resolver/caching DNS
127.0.0.80 webserver

You get the idea.

[Michael Hennebry]

On Fri, 24 Nov 2023, Roger Heflin wrote:
> A profile (for a browser) is where you bookmarks/cookies/cache and
> other associated stuff needed exist.
>
> You can typically (on most browsers) have more than one profile.
>
> If you aren't running chromium currently then you delete the files.
> You might do a "ps -elf | grep -i chromium" and make sure you only see
> the grep.

After removing all thing chromium under my home directory,
I got the authentication required message.
Of course, it didn't like any password I had,
but it ran after I gave up and clicked on cancel.

Chromium sure has some crappy code in it.

[Jonathan Billings]

On Nov 24, 2023, at 17:43, Michael Hennebry  wrote:
> I realize 127.0.0.1 is my computer,
> but I'm not clear on how 127.0.053 and 127.0.0.53#53 are used.

Systemd’s dns service (systemd-resolved) uses 127.0.0.53, and it’s enabled by default on Fedora, so this is expected.