Bug 324915 - Permanent "Failed to initialize" notifications due to "Apper Monitor" interfering with zypper
Summary: Permanent "Failed to initialize" notifications due to "Apper Monitor" interfe...
Status: RESOLVED WORKSFORME
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-14 18:19 UTC by squan
Modified: 2023-02-11 03:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description squan 2013-09-14 18:19:16 UTC
1) I'm a happy user of the zypper and since KDE-4.11 some formerly unknown "Software Updater" component comes up with periodic "System management is locked" messages, when i have zypper running.
2) This component has many notification options, but the "initialization failure" one is not among them.
3) Removing the "Software Updater" from the system tray, does not stop periodic popup messages.
  This is consequent as this Updater seems to be a daemon, but is counter intuitive for the unknowing user.
3) In systemsettings there is a closely related entry called "Apper Software Management", 
  which turns out to offer no options to configure this "Software Updater"
4) Only after considering that this is some kind of desktop service, I found my way to systemsettings' less obvious
     Startup and Shutdown -> Service Manager
  and finally a way to stop this desktop service.


Reproducible: Always

Steps to Reproduce:
1. Start KDE
2. Do 'zypper sh' on the command line



Expected Results:  
1) "Apper Monitor" aka "Software Updater" should not interfere with other software management utilities and/or
2) there should be a more obvious way to disable this.
Comment 1 Andrew Crouthamel 2018-11-10 03:21:22 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:42:34 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-12 01:58:12 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-27 05:07:37 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-02-11 03:52:19 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!