I have been trying to install a new version of Flash, first on 13.2 and then on Tumblewood. I always get an error message:
Header: An internal system error occurred - Apper
Body: A problem that we were not expecting has occurred. Please report this bug with the error description.
Details: Installation aborted by user
I did not abort the installation!!!
>:(
Flash will not play at all on Chrome. It will play with a warning about outdated Flash app in Firefox.
Seems like a real bug to me. Please help me make progress.
Recent news warnings relate to security issues with Flash, with Google and Mozilla believing Flash no longer essential for users so encouraging users to make the change.
Admit this encouraged self to remove Flash, result is am finding fewer than expected issues whether watching YouTube or other sites.
Interesting that Tumbleweed (and presumably 13.2 as well?) keep it nicely up to date:
john@Tumbleweed132:~> zypper se flash | grep 'i |'
i | chromium-pepper-flash | Chromium Flash player plugin | package
i | flash-player | Adobe Flash Plugin and Standalone Player | package
i | flash-player-kde4 | Adobe Flash Plugin and Standalone Player Settings | package
i | pullin-flash-player | Placeholder for Adobe Flash PlugIn | package
I like that because I’d rather have no issues with my browsing.
So @klwilcoxon, in Tumbleweed, did you run ‘zypper dup’ or did you try to upgrade a single RPM using the Yast Software interface? The theory is that ‘zypper dup’ takes care of everything neatly.
Except your list of installed packages doesn’t show them as all up to date, and in fact flash-player on Tumbleweed is not yet at 13.1’s updated version for example. I’m hoping the next snapshot will see it updated as currently it is in factory’s multimedia:apps repo.
On 2015-07-18 04:06, klwilcoxon wrote:
>
> I have been trying to install a new version of Flash, first on 13.2 and
> then on Tumblewood. I always get an error message:
>
> Header: An internal system error occurred - Apper
> Body: A problem that we were not expecting has occurred. Please report
> this bug with the error description.
> Details: Installation aborted by user
>
> I did not abort the installation!!!
>>
That’s a known problem with apper, and is not related to Flash. Simply
apper aborts when it finds a conflict. Instead, you have to do it with
Yast Online Update or with “zypper patch”.
On 2015-07-18 13:56, consused wrote:
>
> robin_listas;2719989 Wrote:
>>
>> That’s a known problem with apper, and is not related to Flash.
> On which version? 13.2 or Tumbleweed? If it’s a “known problem”, can you
> provide a reference/citation for that?
You can search the forums here as well as I can. It has been commented
several times here.
For instance, search for tittle “Apper Error - Installation Aborted by
User”, this month, under applications. But this other (boot-login) is
more to the point: “opensue stops to refresh the system - 349 packages
still left in the queue - so what?”, which even points to a bugzilla on it.
I started out with Apper turned on for 13.2. And I still have it turned on for one 13.1 system.
It mostly works. But, if there are conflicts, it fails. There’s no conflict resolution possible, at least in my experience.
That’s not a big problem, but it does agree with Carlos. Conflicts don’t happen often. When they happen, I use Yast online-update or zypper for that update. Then I go back to Apper thereafter.
But I ran into a different problem with Apper in 13.2. It was a while ago, so I don’t remember the details. Somehow it got into a lockup situation where it made no progress but it still locked out Yast and zypper. So that’s when I disabled it for 13.2.
I only use it for updates and it never fails on 13.1, and on 13.2 (VM only). Conflicts (if any) are IME extremely rare for updates i.e. equivalent to zypper up, and don’t remember any for a very long time here.
That’s not a big problem, but it does agree with Carlos.
Sorry, but both are relying on memory/impressions, and mine is not infallible.
Doesn’t mean it didn’t happen, but best to see a thread or bug report reference, mainly for context and relevance now. For example:
But I ran into a different problem with Apper in 13.2. It was a while ago, so I don’t remember the details…
There is always the “swift justice” option, I’ve used it on many occasion.
Without reading back, my impression still is that the OP told us the result, but not exactly what he did in the steps taken on 13.2 or Tumbleweed. In that context, don’t be surprised if I think the answer “it’s a known problem” isn’t enough.
On 2015-07-18 22:16, consused wrote:
> robin_listas;2720022 Wrote:
>> On 2015-07-18 13:56, consused wrote:
>>> robin_listas;2719989 Wrote:
>>>>
>>>> That’s a known problem with apper, and is not related to Flash.
>>> On which version? 13.2 or Tumbleweed? If it’s a “known problem”, can you
>>> provide a reference/citation for that?
>>
>> You can search the forums here as well as I can. It has been commented
>> several times here.
> So once again you don’t have it. In other words you mean the OP can
> search the forum, or wherever.
No, I posted the precise references… it is trivial to find them.
Do you really want me to go the extra work of also locating the URLS?
On 2015-07-19 11:26, consused wrote:
>
> robin_listas;2720084 Wrote:
>>
>> Do you really want me to go the extra work of also locating the URLS?
> Well since you ask the question, you could avoid posting and move onto
> another thread where your special knowledge might solve the problem.
So, you still deny that it is a known problem, after the evidence?
Firstly, I don’t see a connection between your new question and the the Q & A you quoted.
Secondly, the evidence provided will allow the OP to compare circumstances and problem statements for similarities, and possible solutions/workarounds if included. After all that’s the most important reason for providing it.
Thirdly, as I don’t have the problem, I might read it later so I know where to look if it ever happens on my system.
:-p
