| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The transition is not complete, mgaapplet still needs fixed to lookup the icons
in the theme paths and no in a hardcoded /usr/share/mgaonline
|
|
|
|
|
|
| |
Move the mgaonline icon in the hicolor theme with the proper SVG
variant installed too.
Also fixed a typo in a rpmdrake icon and updated copyright year.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
new icons for mgaonline
note: looks like enhancement.png is not used anymore,
at least a search didn't find the word enhancement used anywhere in this repo.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
wrongly went with commit 87813dd7cfa302347b06cd9b0675d18577a2be11
|
|
|
|
|
|
| |
in order to prevent glib-threading segfaults (mga#10289), just block the
CHLD signal during the window where glib create threads behind our back
(RT-120951)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
previous fixes for mga#12280 resulted in Colin reporting mgaapplet
exiting (not segfaulting):
"When updates a bubble pops up:
- If you click on the background of this bubble, mgaaplet exits
- If you click on the "Install Updates" button, it pops up the password
dialog. Without touching anything, about 1s later the dialog seems to
be replaced with another that says "Sorry, that didn't work, please
try again". When this dialog appears, mgaapplet exits."
So let's clean the pile of fixes and:
- have only _one_ gtk+ main loop
- creating _one_ hidden notification before entering the main loop
- never destroy it, but use >close + >clear_actions() then ->update()
prior calling >show() when one need to show a notification again
|
|
|
|
|
|
|
|
| |
The old method worked on older gnome-shells, this new method works
on newer gnome-shells (see bgo#706783)
Ideally neither hacks should be necessary and maybe (eventually) we can
remove them, but for now...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit 95b9cd06f14a9817090584d72830df870c591acc, we run a gtk
main loop after displaying a notification, else actions when clickong
notification buttons are ignored by gtk+/libnotify
However, if the notification is not manually closed, we never exit
this main loop.
In that case, gtk+ fails with:
(mgaapplet:9060): Gtk-CRITICAL **: gtk_window_set_accept_focus: assertion 'GTK_IS_WINDOW (window)' failed
from:
data=<optimized out>, destroy=0x0, button=3, activate_time=5407876) at gtkmenu.c:1613
And X11 is stuck.
As a workaround, since libnotify offers no way to be notified when
notification is automatically closed, just add a timeout for exiting
the main loop.
At worse, X11 will be stuch only 5 seconds.
|
|
|
|
| |
thus fixing segfault on startup
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
since we cannot prevent glib/gtk to spawn threads behind our back, we
can at least try to prevent segfaults due to mixing threads with secular
forks by exec()ing immediately
|
|
|
|
| |
(needed for next commit)
|
| |
|
|
|
|
| |
set_authors() needs an array ref with Gtk3
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Not sure how that happened :s
|
|
|
|
| |
(mga#6083)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The basic principle of this is to do the following:
1. Check the releases webservice API to see if the distro version 'needs_preparation'.
2. If it does, check for a file /var/lib/mageia-prepare-upgrade/state.
If it says 'ready' then we are ready and the user is not questioned further.
3. If it does not exist or says anything else, the user is prompted to install the
package 'mageia-prepare-upgrade'.
4. After package installation, check the state file again as this may be
all that is required. If the state file does not yet say 'ready', then
display the text from the /usr/share/doc/mageia-prepare-upgrade/README.prepare
file (todo: add i18n)
5. Assuming that further action is required by the user (e.g. rebooting to
convert the filesystem), then the upgrade helper will exit.
6. After the user has taken the action required to do the preparation,
the state file should contain 'ready'. The next time the distro upgrade
dialog shows, the preparation checks will pass and the user can continue.
TODO:
Handle i18n in the README.prepare file.
v1: First Revision
v2: Check immediately if an upgrade state file exists (don't wait 5 mins)
Ensure config file is parsed (ensures the testing variable is read)
Show user-visible messages when bailing out due to unexpected errors
|
| |
|
| |
|
|
|
|
|
| |
should have went off along commit r3432
(Mar 12 2012 : "drop support for mdv2007.x/2008.x/2009.x")
|
|
|
|
| |
(mga#6083)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(simplify code and increase perl_checker's SNR)
|
| |
|