Apper 0.7.1 released


I’ll be short: a new Apper version is out, but don’t expect much it has only 2 new features and a bunch of bugfixes, I’ve made a small lists of what have changed:

– Added a origin column
– Added a “Installed Version” column to updater UI
– Fix bug on exiting when the origns model had changes to do
– Fix bug that prevented EULA/GPG key from being accepted
– Fix tray icon to properly show a restart action
– Fix Session Interface not to crash, and respond to button clicks when no package was to be installed
– Fix bug when clicking on a file to install

You can download it here.

I’m planning another big interface change, but I had not draw it yet since a few components are not yet clear to me how to be handled…

I was to give special thanks for Matthias Klumpp for preparing and uploading Apper’s and PackageKit’s packages to Debian (yes they are on the repos – not this version yet but his is already uploading).

I want also thank Fedora and openSUSE guys that helped testing some of the above bugs so we could fix then faster.

Enjoy this new release 😀

Apper 0.7.1 released

18 thoughts on “Apper 0.7.1 released

  1. Wishlist.

    1. I think a “Download automatically but don’t install” option is needed. You have the choice of either install automatically, or don’t do anything. Please, give me the intermediate choice!

    2. You can add an easy feature to help the adoption of Apper in rolling releases: the ability to show (optionally, and distro-dependent) a RSS feed in your main interface. There are breaks sometimes in those distros, and they are usually advertised to users through a RSS feed (thinking about Arch Linux and Chakra, at least), along with instructions about what to do. That info is essential for upgrading a rolling release.

    1. dantti says:

      1. It’s not as easy as adding an option to download updates for later installation, the problem is that each distro has it own backend that has to deal with this updates, so we first need a feature on these backends and on PackageKit then the gui wins the feature…
      2. IMO RSS is not a nice way of advertising problems, the right thing imo is for the backend emit a changelog that tell the package can break the system.
      Both things should be discussed at PackageKit level, send a mail to the mailing list.

  2. Robert says:

    Thanks a lot for this nice tool!

    My little wish list (actually just one wish):
    On the Software Origins tab you can either select a Origin or de-select it. Either way it is a system wide setting, that means a Origing de-selected in apper will also be de-selcted eg. in SUSEs YaST Package Manager.

    Is it possible to add a more differentiated selection, like keep Origin active for PackageKit/ YaST, etc., but let apper only inform and install selected Origins?

    I personally would like to be informed in the Taskbar about critical updates from my distro and have a more or less one click option to install these – this is what I intend to use apper for.
    For intallation or updates of all other packages, I do prefer the original tool of the distribution, eg. YaST.

    1. dantti says:

      Hmm well there is one option to Automatically install Security updates, I’m not sure fine graining which updates it should show on the taskbar is good, it’s also hard to tell show only updates from these repos, would make the ui a lot more complicated since you will have a large list to choose from, and them it would need to filter them. I can’t think of a simple ui to provide this filtering, if you have some simpler idea please say..

      1. Robert says:

        Hm, true.

        How about a litle re- arrangement of the “Software Origins” tab: one line per origin, shift the tick- boxes to the right and name the column “Active Origins” and introduce a second column with tick- boxes named “Monitored by apper” or similar.

    2. dantti says:

      It’s not the “monitored by Apper” that is the problem, the problem is knowing which package belongs to which repo. Since each distro use it’s way on that. I don’t have enough data to know this…

  3. Thijs says:

    Awesome. Especially the restart icon bug. Small, but it was very visible. Thanks a lot for your work on this, you make a lot of lives across the distributions a lot easier (mine in Fedora and Arch).

    As for the rolling release issue: It would be nice. But, automatic install is not exactly advisable in Arch anyway, subscribing to the email list is, and apper manages to make a nice exclamation point message with the output of the installer. If something can be improved there, fine, but to me it is not a deal braker. Just keep it fast and bloat free, I’d say!

    1. anonymity is great (and facebook ain't) says:

      You’re telling me that Apper also shows the messages which pacman shows in the console? If so, cooool! I must try Apper out again on Arch then. You are right, in Arch, you should always read the email list or the news on Arch’s front page before upgrading. In the old days, shaman (which unfortunately died together with KDEmod) downloaded the news and you could read it by pressing a button in shaman’s GUI. This approach would however likely not fit in a general framework like Apper.

      1. dantti says:

        No, I’m not telling it does, it can show the package’s changelog, but it is up to the backend to do that, if the pacman backend download the rss feed the it will be shown on the update’s description…

      2. anonymity is great (and facebook ain't) says:

        Hmm. I was actually hoping that the following would happen: when Apper has finished installing the packages, then pacman’s messages would appear in the window. When using pacman on the console, it sometimes happens that pacman says “Warning: new /etc/rc.conf installed as /etc/rc.conf.pacnew” or “Warning: the configuration of … has changed, please do the following modifications: …” (or something like that). Then it is the responsibility of the user to make sure that the new configuration doesn’t break his system, and to transpose his modifications of the settings to the new configuration files (see This information is vital if you don’t want to end up with a screwed (or even non-working) system. The mailing list and Arch’s news page tell about such changes, but they tell only part of the story (warnings about *.pacnew files are only shown in pacman’s output). In order for Apper to be usable in Arch Linux, it would be necessary to show pacman’s messages after everything has been installed (before is also good, but then the messages shouldn’t disappear when installation has finished). Could this be implementable (if the backend manages to get those messages from the pacman libs)?

      3. dantti says:

        Apper doesn’t need to change, it’s just an UI, the backend just has to emit messages and the user will be informed. So file a bug agains pacman backend on your distro if it doesn’t do that.

  4. Jim Kirkey says:

    Hello Dantti:
    I would like to thank you for Apper. I am using Debian Wheezy KDE and had looked all over for a nice GUI for package management. I tried for the longest time (a month or two), to get Muon for Debian and finally found it. I like the interface. Then I found Apper and like it better. It seems to be more native Debian? Anyway, thanks man. You are doing a great job and I appreciate all of the work you put into it.
    Jim Kirkey

    1. dantti says:

      You are welcome, I can’t say that Apper is more native since both use apt, Apper has more abstractions so it can be used on many others distros, I could say it it’s bit more integrated with KDE but mostly UI changes I think…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s