| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
they were lost due to stupid/gratuitous breakage in commit
d67b95af569556af4a4b333e1707fdbc34c447e5
|
| | |
|
| | |
|
| |
|
|
| |
issues mga#11184 mga#12364
|
| | |
|
| |
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
basically reverting commit 56bcaff85b7b8a98ffdf67118a4df873fe301882
from Nov 24 2009 ("(configure) make it work on 2008.x & 2009.x")
|
| |
|
|
|
|
|
|
| |
bug introduced in commit 56bcaff85b7b8a98ffdf67118a4df873fe301882
on Nov 24 2009 (was: "(configure) make it work on 2008.x & 2009.x")
it wasn't visible in newer distro as we were relying on the other code
path
|
| |
|
|
|
|
| |
regression introduced in commit 6c1fa5cd83b0d46528ee8cecda42f9b1adca0b32
on Nov 18 2013 ("use (my|u)gtk3 instead of *tk2") when switching from
gtk2 to gtk3
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
set_authors() needs an array ref with Gtk3
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
We like to be able to run this command without any user interaction
when checking for package updates.
It's somewhat awkward to keep the policy and the binary in separate
repositories, but keeping this split will prevent pulling in mgaonline
during priority updates section of the distro upgrade.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(mga#6083)
|
| |
|
|
|
|
|
|
| |
Patch from Maarten Vanraes and Dave Hodgins and tweaked by me for
trunk.
mga#6061
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(mga#6083)
|
