Lightroom Classic CC problem

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.

.... but only after learning that the problem seems to be widespread.
--

Regards,

Eric Stevens

In article , Eric Stevens
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.

... but only after learning that the problem seems to be widespread.

nowhere near as widespread as you think and you're assuming it's with
adobe, not windows itself.

In article , Eric Stevens
wrote:




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.

that doesn't mean what you think it means.

On Tue, 20 Feb 2018 16:57:48 -0500, nospam
wrote:

In article , Eric Stevens
wrote:




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.

that doesn't mean what you think it means.

Then you explain what you think it means.
--

Regards,

Eric Stevens

On Tue, 20 Feb 2018 16:57:48 -0500, nospam
wrote:

In article , Eric Stevens
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.

... but only after learning that the problem seems to be widespread.

nowhere near as widespread as you think and you're assuming it's with
adobe, not windows itself.

You are the one assuming it is with Windows.

I have said that some of the accounts I have read suggest that the
problem is with incorrectly set file permissons, in which case the
problem is not caused by Windows.
--

Regards,

Eric Stevens

In article , Eric Stevens
wrote:

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.

that doesn't mean what you think it means.

Then you explain what you think it means.

people like to complain and post about problems. they don't normally
post when things run smoothly. you're not getting the full picture (no
pun intended).

most people wouldn't even know there is something called crash reporter
if they don't experience a crash.

In article , Eric Stevens
wrote:

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

he's convinced nothing is wrong.

... but only after learning that the problem seems to be widespread.

nowhere near as widespread as you think and you're assuming it's with
adobe, not windows itself.

You are the one assuming it is with Windows.

nope. i said it can be any of a number of things.

nothing can be ruled out without extensive analysis, and by those who
know what to look for (i.e., not you). this is best done by adobe &
microsoft, who have the source code to their respective parts and a
deep familiarity of what *should* happen.

tl;dr - you're guessing.

I have said that some of the accounts I have read suggest that the
problem is with incorrectly set file permissons, in which case the
problem is not caused by Windows.

as i said before, apps that crash with incorrectly set permissions is a
bug with the app, but the true problem is that windows gets into that
situation.

tl;dr you're treating the symptom, not the disease.

On Tue, 06 Feb 2018 16:05:42 +1300, Eric Stevens
wrote:

My Lightroom Classic CC seems to have decided to give up printing.
When I select Print it brings up the appropriate screen identifying
the printer and the paper size and then a notice pops up which says
something like:

Adobe Photoshop Lightroom has stopped working.

A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is
available.

As far as I know all my software is up to date. Is this just my
problem or have other people also experienced it?

W10 of course.

Update - skipping all the twaddle which has emerged since the
beginning of this thread:

As you know, I eventually found that my problem of LR locking up (more
accurate description than 'crashing) when selecting the PRINT module
was overcome by creating a new empty catalog and then copying the
contents of the old catalog into it.

Adobe has been of no great help but neither have been my personal
circumstances.

Today I found I had two updates, one for PS and the other for LR. I
have installed both and tried starting LR once again. Same result: LR
comes up with PRINT selected and immediately locks up.

Oh ****!

Then I found it was starting on the old (corrupt?) catalog and that
when I switched to the new copy catalog it all seems to work as it
should.

I am interested to note that the the Adobe Crash Reporter files
CRWindowsClientServices.exe, a copy of which lies in C:\Program
Files\Adobe\Adobe Photoshop and another copy in C:\Program
Files\Adobe\Adobe Lightroom Classic have each been updated from early
December 2017 to 6 Feb 2018 and 9 Feb 2018 respectively.

I suspect my problems continue to be a work in progress.
--

Regards,

Eric Stevens

On Tue, 20 Feb 2018 20:22:58 -0500, nospam
wrote:

In article , Eric Stevens
wrote:

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.

that doesn't mean what you think it means.

Then you explain what you think it means.

people like to complain and post about problems. they don't normally
post when things run smoothly. you're not getting the full picture (no
pun intended).

most people wouldn't even know there is something called crash reporter
if they don't experience a crash.

Are you trying to claim that the complaints about Crash Reporter not
working are being made by people who don't know there is such a thing
as Crash Reporter?
--

Regards,

Eric Stevens

On Tue, 20 Feb 2018 20:22:59 -0500, nospam
wrote:

In article , Eric Stevens
wrote:

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

he's convinced nothing is wrong.

... but only after learning that the problem seems to be widespread.

nowhere near as widespread as you think and you're assuming it's with
adobe, not windows itself.

You are the one assuming it is with Windows.

nope. i said it can be any of a number of things.

nothing can be ruled out without extensive analysis, and by those who
know what to look for (i.e., not you). this is best done by adobe &
microsoft, who have the source code to their respective parts and a
deep familiarity of what *should* happen.

tl;dr - you're guessing.

I have said that some of the accounts I have read suggest that the
problem is with incorrectly set file permissons, in which case the
problem is not caused by Windows.

as i said before, apps that crash with incorrectly set permissions is a
bug with the app, but the true problem is that windows gets into that
situation.

tl;dr you're treating the symptom, not the disease.

What do you reckon should be done to Windows to avoid the problem of
people incorrectly setting file access permissons?
--

Regards,

Eric Stevens