Lightroom Classic CC problem

On Fri, 16 Feb 2018 11:40:07 +1300, Eric Stevens
wrote:

On Wed, 14 Feb 2018 17:09:06 -0800, Bill W
wrote:

On Thu, 15 Feb 2018 11:47:09 +1300, Eric Stevens
wrote:

On Mon, 12 Feb 2018 12:58:23 -0800, Bill W
wrote:

On Tue, 13 Feb 2018 09:26:10 +1300, Eric Stevens
wrote:

rOn Mon, 12 Feb 2018 15:12:13 -0500, nospam
wrote:

In article , Eric Stevens
wrote:

crash reporters are *very* simple tools and there's not a lot to go
wrong.

They have to start first.

if it doesn't start, then it can't be an adobe problem, since the adobe
component isn't even running.

From what has been posted it seems to be somehow tied up with
permissions. I imagine these are probably set by the software
installer.

nothing more than a wild ass guess.

Nope. Other people have found out how to fix the problem.

only the symptoms, not the underlying cause.

in other words, a workaround.

The symptom is that the program doesn't run.

The 'work around' as you call it is a changed setting which allows the
program to run. In other words, something was stopping the program
from running. Fixing that solved the problem. and from then on the
program ran perfectly satisfactorily.

What setting is changed to what?

My tenses have probably become confused along the way. I haven't had
time to get at it yet. In the article I read the change was of a
setting to allow the program to run as administrator. But that was
Windows 7. I have yet to discover the equivalent action in Windows 10.

Should be the same, and it's a trivial matter to change.

I agree. All I need is the time to investigate exactly how the Crash
Reporter works.

But is that not working, or is the LR issue failing to trigger crash
reporter? And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

In article , Bill W
wrote:

The symptom is that the program doesn't run.

The 'work around' as you call it is a changed setting which allows the
program to run. In other words, something was stopping the program
from running. Fixing that solved the problem. and from then on the
program ran perfectly satisfactorily.

What setting is changed to what?

My tenses have probably become confused along the way. I haven't had
time to get at it yet. In the article I read the change was of a
setting to allow the program to run as administrator. But that was
Windows 7. I have yet to discover the equivalent action in Windows 10.

Should be the same, and it's a trivial matter to change.

I agree. All I need is the time to investigate exactly how the Crash
Reporter works.

But is that not working, or is the LR issue failing to trigger crash
reporter? And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

On Thu, 15 Feb 2018 19:54:53 -0500, nospam
wrote:

In article , Bill W
wrote:

The symptom is that the program doesn't run.

The 'work around' as you call it is a changed setting which allows the
program to run. In other words, something was stopping the program
from running. Fixing that solved the problem. and from then on the
program ran perfectly satisfactorily.

What setting is changed to what?

My tenses have probably become confused along the way. I haven't had
time to get at it yet. In the article I read the change was of a
setting to allow the program to run as administrator. But that was
Windows 7. I have yet to discover the equivalent action in Windows 10.

Should be the same, and it's a trivial matter to change.

I agree. All I need is the time to investigate exactly how the Crash
Reporter works.

But is that not working, or is the LR issue failing to trigger crash
reporter? And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

Does that actually happen? Sometimes I think they just make this stuff
up.

In article , Bill W
wrote:

And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

Does that actually happen? Sometimes I think they just make this stuff
up.

sending the report definitely happens. actually fixing the problem
depends on its priority and how hard it is to fix.

one major benefit from crash reports is determining just how widespread
a given problem actually is.

On Thu, 15 Feb 2018 20:24:43 -0500, nospam
wrote:

In article , Bill W
wrote:

And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

Does that actually happen? Sometimes I think they just make this stuff
up.

sending the report definitely happens. actually fixing the problem
depends on its priority and how hard it is to fix.

one major benefit from crash reports is determining just how widespread
a given problem actually is.

In that case, Eric needs to fix his damn PC. Eric, are you listening?

I really should go check to see if mine is working...

In article , Bill W
wrote:

And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

Does that actually happen? Sometimes I think they just make this stuff
up.

sending the report definitely happens. actually fixing the problem
depends on its priority and how hard it is to fix.

one major benefit from crash reports is determining just how widespread
a given problem actually is.

In that case, Eric needs to fix his damn PC. Eric, are you listening?

he's convinced nothing is wrong.

On Thu, 15 Feb 2018 20:57:56 -0500, nospam
wrote:

In article , Bill W
wrote:

And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

Does that actually happen? Sometimes I think they just make this stuff
up.

sending the report definitely happens. actually fixing the problem
depends on its priority and how hard it is to fix.

one major benefit from crash reports is determining just how widespread
a given problem actually is.

In that case, Eric needs to fix his damn PC. Eric, are you listening?

he's convinced nothing is wrong.

Mine works, so he's right...

On Thu, 15 Feb 2018 17:49:25 -0500, nospam
wrote:

In article , Eric Stevens
wrote:

relevant part:
...It started crashing
again. That must mean something.

It means you have not understood what I wrote. Two separate problems:
only one of which involves a crash.

a crash is never acceptable.



you didn't actually fix the crash. only adobe or microsoft can do that.

Now you are talking about the LR PRINT problem. Are you really
suggesting that LR should be able to run with a corrupted data base?

no, but it should not crash just because the catalogue is corrupt.




lightroom could check on launch or ideally, windows could have a
maintenance task that checks.

How the hell would Windows know what permissions are required? If it's
an installation problem it's up to Adobe's installer to get them
right.

and it does. otherwise hundreds of millions of users would not be able
to use their software.

Check the forums and find out how many users of a variety of Adobe
apps are now complainining that Crash Reporter isn't working. Bearing
in mind that you have to have a crash to find that out, there must be
very many more who have the same problem but haven't found out yet.
--

Regards,

Eric Stevens

On Thu, 15 Feb 2018 16:28:47 -0800, Bill W
wrote:

--- snip ---

I agree. All I need is the time to investigate exactly how the Crash
Reporter works.

But is that not working, or is the LR issue failing to trigger crash
reporter? And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

I suspect the crash reporter doesn't start and run until it is
triggered by some trivial service somewhere. Whether the fault is in
the service or in the CR is something I do not know. Life has been so
hectic lately that I have just about given up trying to find out.
--

Regards,

Eric Stevens

On Thu, 15 Feb 2018 20:24:43 -0500, nospam
wrote:

In article , Bill W
wrote:

And what good is crash reporter anyway? It has never helped
me to be told that "XXX has stopped working". I already knew that, and
it has never found a solution. It really just wastes my time.

to send a crash report to adobe so that they can fix the problem.

Does that actually happen? Sometimes I think they just make this stuff
up.

sending the report definitely happens. actually fixing the problem
depends on its priority and how hard it is to fix.

one major benefit from crash reports is determining just how widespread
a given problem actually is.

Unless, as in the present case, the problem is the Crash Reporter not
working.
--

Regards,

Eric Stevens