Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Notification is both defined by Notify and the latest GLib, resulting in
a build failure. Use Notify.Notification instead to avoid this
ambiguity.
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746130
|
|
|
|
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=980204
|
|
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=980203
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=980207
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=874988
|
|
When the user hits the Cancel button no action should be triggered.
|
|
Add a button "Enter password" to the notification, so that the user can
directly react to the notification and does not have to use the tray icon.
|
|
This fixes an issue where the tray icon disappears after the notification is
closed, though no action has been triggered and there is still a password to
enter.
|
|
pkexec does not like being a lonely child:
"Refusing to render service to dead parents."
Do not double fork when spawning the process by using the DO_NOT_REAP_CHILD
flag. Clean up manually using a child watch.
|
|
When a GLib.Error happens, it is likely that showing a message box
would fail too.
Solution copied from systemadm and
https://bugzilla.redhat.com/show_bug.cgi?id=716663.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716369
|
|
|
|
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=62736
|
|
|
|
Based on basic patch by Marc-Antoine Perennou in bug #41814
* Replaces the gtk2-specific WrapLabel with normal Label. Wrap+resize
works reasonably well in gtk3.
* Simplifies layout by using Grid instead of Table
* Replaces use of various deprecated objects
|
|
- Use default sh
- Fail on error
|
|
The rules in Makefile.am are reordered and simplified a bit.
|
|
There is no need to AC_DEFINE it.
|
|
"Libgee version numbers are a little confusing. In libgee 0.5 and 0.6,
the package name was gee-1.0, identified by a file gee-1.0.pc. In
libgee 0.7, the package name changed to gee-0.8 (since the library
changed incompatibly)."
Since systemadm seems to work fine with newer libgee (found in Fedora 17),
let's check for both versions, starting with the newer one.
Between 1.0 and 0.8 there seems to have been 0.7, but since I don't
have one at hand, I'm not adding a check for it. If necessary,
configure.ac can be extended to check for that version too.
|
|
Makefile.am:62: EXTRA_DIST multiply defined in condition TRUE ...
Makefile.am:23: ... EXTRA_DIST previously defined here
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hi,
during the builds for Fedora/s390x I've found that systemd v38 fails to
build on big-endian platforms.
...
make[2]: Entering directory `/root/systemd'
CC src/journal/libsystemd_journal_la-sd-journal.lo
src/journal/sd-journal.c: In function 'init_location':
src/journal/sd-journal.c:69:22: error: incompatible types when
initializing type 'long unsigned int' using type 'sd_id128_t'
src/journal/sd-journal.c:69:20: error: incompatible types when assigning
to type 'sd_id128_t' from type 'long unsigned int'
make[2]: *** [src/journal/libsystemd_journal_la-sd-journal.lo] Error 1
I see the problem in using le64toh() on the 16 bytes boot_id structure
in init_location()
Please see
http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=544375 for a
full build log and attachment for a proposed fix.
With regards
Dan
|
|
|
|
|
|
|
|
|
|
|
|
Albert Strasheim reported a socket unit with Accept=yes was failing
sometimes.
getpeername() returns ENOTCONN if the connection was killed by TCP RST.
The socket unit must not fail when it happens.
Reproducer available at:
https://bugzilla.redhat.com/show_bug.cgi?id=783344
|
|
Since the addition of ControlGroupPersistent, systemd is trivially
killed by "systemctl status any.service".
bus_property_append_bool must not be used for a tri-state int.
Also, should it really "b", or do we want the tri-state nature to be seen?
For now just comment out the buggy DBus property.
|
|
The pid file watch could outlive the service unit if a daemon-reload
request came at the right time. The inotify event would then be
delivered to who knows where.
Fix it by unwatching in the service destructor.
Further changes will be needed to preserve the state of the pid file
watch across daemon-reload. For now let's just fix the crash observed
by Jóhann Guðmundsson:
Assertion 's->state == SERVICE_START || s->state == SERVICE_START_POST'
failed at src/service.c:2609, function service_fd_event(). Aborting
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=783118
|
|
Koen reported errors with gcc 4.5.4 for arm:
src/log.c:624:9: error: #pragma GCC diagnostic not allowed inside
functions
|
|
|
|
manipulations at boot time, a la sysctl
|
|
|
|
early boot operation, even if it sucks
|
|
|
|
|
|
|