[SOLVED] notification daemon

Hi,
I am currently on the switch to a "none DE" window manager.
I have some notifications send to me using "notify-send"
How can I get this notifications? I know there is noteo. Is it the only option?
Thanks!
Nathan
Last edited by LonelyStar (2009-05-21 17:26:51)

The package is called notification-daemon ...

Similar Messages

  • Notification-daemon: clearing the notifications queue

    I'm using notification-daemon (0.7.3-1) and libnotify (0.7.4-1), calling notify-send from an external program. After several notifications have popped up (not sure of the number), they stop appearing, but still show up in the queue, which is accessible from the notification area (using GNOME 3 with xmonad). The only way I've found to clear the queue and have the notifications start appearing again is to click the "Clear Notifications" button in the system tray queue window.
    You'd think notify-send would have an option to do this. I would love to just use dbus directly, but can't seem to find anything in the doc for clearing the queue (best I could find was http://www.galago-project.org/specs/notification/0.9/ ). The queue viewer is clearly able to do it, so there's got to be a mechanism.

    Hi,
    Thank you for your post.
    I am trying to involve someone to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Regards,
    Lily Wu
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • SiND, a Simple, textbased, Notification Daemon

    Alright. I've just gotten the notification daemon I've been writing into a solid spot, so I'd thought I'd share!
    SiND is a [basically] freedesktop-compliant notification daemon. It receives notifications from dbus, and, well, just spits them out to stdout.
    It does so in a buffered way, printing all the current notifications whenever a new one arrives or one expires.
    Using the --lines option, you get a psuedo-curses program , free to display your notifications in whatever terminal you want.
    This also means you can pipe it into a dzen slave window. or whatever other panel you want.
    Or whatever else you want to do!
    You can format how each notification is printed (app-name, summary, body, id) and you can also spit out an extra line (a... status line ) containing some extra information, like how many active notifications there are and custom strings if you get new ones. So you can stick it in your panel's title bar. Or whatever.
    SiND - Github
    Personally, I've never been a fan of desktop notifications, but since I can just output into any old terminal, I've found myself using it for short-term todolists and stuff using notify-send. I've also found not being tied down to a gui makes 'regular' notifications a lot less annoying, too (and you can pipe em through grep!)
    Basically, I wanted to write a notification daemon that lets you do whatever you want to do to desktop notifications. If you need help making SiND do whatever you want, lemme know.
    Want more flair? See also:
    dunst
    twmn
    Last edited by wretch (2013-04-09 23:49:35)

    Army wrote:Your PKGBUILD isn't working this way, your _gitroot only works for yourself. And please don't add stuff like "pwd" to the build function, there's no use for it! Here's a working PKGBUILD I made which follows the packaging standards.
    Ahh, thanks! Shoulda checked that out before. Thanks a bunch for your version.
    I wont be able to update the aur pkgbuild for a day or two, so if anyone else is interested in trying this out, just try Army's pkgbuild.
    Army wrote:I probably won't use sind, because I'm very happy with dunst, but I like yours as well, because it can be used in scripts for e.g. conky, like your script shows. I like that!
    Indeed! Dunst and twmnd are both really nice. I was using twmnd for a while.
    I personally found myself wanting to use something even simpler, so I wrote sind, hopefully others here will enjoy the scripting capabilities of sind as well. That was my main intent in writing it.

  • [HELP] good old fashion notification-daemon

    Hi:
    I recently install Archlinux with Openbox. I'm looking for the old style notification daemon: A simple square box in the corner. Like in gnome 2. There any way to get it back?
    thxs

    Raynman wrote:Try notification-daemon from the extra repository.
    this is the ugly black semi-transparent rounded box that i hate xD

  • Dunst - a dmenu-ish notification daemon

    Hello everybody,
    The information in this post is very out of date. Have a look at the homepage for a more up to date introduction.
    I've spend the last day creating a simple notification-daemon. It uses the drawing code from dmenu and because of that looks a lot like it.
    It can listen to notifications from libnotify or be used standalone to display messages (maybe useful in some scripts).
    Originally it was suppost to be a patch for dwm and I just used the drawing code from dmenu to prevent constant restarting of dwm to test it.
    But in the end i figured it would be more usefull as a standalone application.
    homepage
    The source is available at http://github.com/knopwob/dunst
    If you're interested in this kind of notification-daemon make sure you also check out twmn .
    Here are a few screenshots of dunst at work:
    critic, suggestions, and so on is welcome, of course.
    Last edited by knopwob (2012-08-23 19:18:00)

    you've got good points here.
    ninian wrote:
    Aha ... you're well ahead of me there! I completely appreciate your priorities. But here are my thoughts ...
    I think the two functions of Dunst need to be considered almost separately:
    1) The daemon function, which for compatibility should follow the Desktop Notifications Specification as far as the Dmenu-ish programming allows (eg, probably no icons!). This would allow Dunst to be used as a lightweight drop-in replacement for notification-daemon, xfce4-notifyd, etc. In particular, notify-send should produce similar notification messages with Dunst as can be achieved with the other notification daemons (including timeout options, eg critical messages remain on screen, but others timeout with the normal defaults or whatever is specified with the -to option).
    complying to specifications is always a good thing   I think, we are on the same page concerning urgency-levels and timeouts. This will be implemented in the near future.
    About the issue with notify-send's name being displayed. It don't like the idea of hardcoding an exception for one application. As far as I know, no other notification daemon displays the name of the Application, which sended the message. But actually I like it. So how about making it optional. I've got something like this in mind:
    dunst -format "%a: %s -- %b" <-- This would be the current state
    %a -> application name
    %s -> summary
    %b -> message body.
    This way, if you don't want the application name displayed, you could change the option to something like this:
    dunst -format "%s: %b"
    This way only the summary and the body of the message will be displayed. As it is (as far as I know) the state with the other notification-daemons around.
    ninian wrote:Having different colours for different calling applications wouldn't be of much use to me, because it's the category of message which is usually more important than the application name itself. For example, a reminders program can issue standard or urgent reminders. I might like the ordinary ones in blue, but the urgent ones in red.
    Yes I agree with you that there should be a visual clue for the urgency-level of a message. I guess an additional option for the color of urgend messages would be appropriate.
    At this point I think I should also think about adding a config file, because the commandline could grow fairly large if you use all the available options.
    ninian wrote:
    2) The direct messaging function, using -msg, can be formatted much more flexibly as it doesn't need to conform to the standard above. But as long as it produces similar results which "fit in" with the notifications produced by the Dunst daemon, I'd be happy, no matter the bells and whistles available for formatting the message.
    At the moment I use dzen2 for home-made notifications, categorized by different colours and timeouts into: errors (with or without an alarm bell), warnings, information messages, standard messages. Other formal notifications (from Thunderbird, Osmo, etc) are handled by xfce4-notifyd. What I'd love is just to use Dunst for everything, probably via notify-send.
    I guess this is where you found the issue about multiple messages being displayed on top of each other? As soon as I found a way to make dunst notice, that there's already a message displayed by another instance of dunst and make it act accordingly (either add the message to the existing message or add another message next to it) this should be possible.
    Last edited by knopwob (2011-09-13 17:00:03)

  • NotifyOSD look-alike theme engine for the notification daemon

    I've started to work on a theme engine named "coco" for the notification daemon, and I'm sharing what I have so far in case someone finds it useful. My goal is to make it look like NotifyOSD (https://wiki.ubuntu.com/NotifyOSD). I'm taking the notification-daemon-engine-nodoka source code as a starting point, so you can follow the same steps that are on the AUR to install it.
    Here is a screenshot of what I have so far:
    And here is the git repository with all the source code:
    http://github.com/tatofoo/notification- … ngine-coco
    Keep in mind that I've disabled all kind of buttons for now, and the icon that appears on the screenshot is from NotifyOSD (https://launchpad.net/ubuntu/+source/no … -icons/0.3).

    Hey, thanks for adding it to the AUR.
    I don't have my computer here right now, so I can't really test it, but do you have composition enabled? Also, which version of notification-daemon do you have?
    I haven't really cleaned the nodoka code that coco doesn't use, maybe when I do that the bug goes away, I'll try to do that before the weekend and I'll let you know so you can try again.

  • Notification Daemon Themes not Working

    Hey all-
    I'm running arch64 and have been trying to get the nodoka notification daemon theme from Fedora to work for the past few days now. I install it like any other source file and it ends up in /usr/lib/notification-daemon-1.0/engines, but when I enable it in gconf, the theme stays the same. This worked on arch32, so what is the deal now? Has anyone experienced something similar/know how to fix this?
    Peter

    I have the same problem. Theres an error when you try to use the nodoka engine in 64 bit. I know theres an rpm floating around to install the engine for x86_64 but im not sure hoe to install it.

  • Notipy: A minimalistic gtk3 notification daemon written in python.

    Hello fellow archers,
    with noteo seemingly dead and all other available notification daemons being
    more or less tightly coupled to a window manager, I thought it would be cool
    to have a (hopefully) worthy successor.
    Introducing notipy:
    As its github page states, notipy is an implementation of the
    Desktop Notification Specification. It shows message popups using gtk3, allowing
    for pango marked up message bodies and icons that can be specified in various
    ways.
    For more information, please refer to the github page. I hope some people will
    find it helpful. Any comments, feature requests or bug reports should go either
    to this thread or directly to github.
    Kind greetings!
    Last edited by the_isz (2011-05-31 08:04:24)

    quigybo wrote:
    Very cool, I like it. One minor issue though:
    $ notipy.py -a NORTH_WEST
    usage: notipy.py [-h] [-l {DEBUG,INFO,WARNING,ERROR,CRITICAL}]
    [-t EXPIRETIMEOUT] [-m MARGINS]
    [-a {NORTH_WEST,SOUTH_WEST,SOUTH_EAST,NORTH_EAST}]
    [-d {VERTICAL,HORIZONTAL}]
    notipy.py: error: argument -a/--layout-anchor: invalid choice: 0 (choose from 'NORTH_WEST', 'SOUTH_WEST', 'SOUTH_EAST', 'NORTH_EAST')
    Same issue with -d. Also, I think you have your east and west mixed up.
    Thanks for the hints. Wonder why that didn't occur to me during testing, but I
    can definitely reproduce it. Will fix it soon, tomorrow, if not today.
    Also thanks for the compliment about the comments. I'm trying to code up to what
    my software-engineering professor used to hammer into our heads:
    "THE CODE IS NOT YOURS! So write code that is readable by others, too."
    Lastly, I just noted that the notipy package should probably provide
    notification-daemon. I will add that to the PKGBUILD for the next version.

  • Notification-daemon / deadbeef --- modification

    Hi ppl.
    I am using Gnomes notification daemon and a DeadBeef player.
    On screen display notifications are working, but all of the notification messages goes to letter envelope icon in system tray.
    Is there a way to keep OSD notifications from DeadBeef, but NOT to send them to notification icon in system tray?
    Last edited by webmasteryoda (2011-06-25 22:15:25)

    http://bharathi.posterous.com/change-gn … n-position ? i'm using xfce4, so I don't really know if it is position what concerns you, nevertheless gconf is your hope.
    if not, consider switching to notify-osd-customizable and using notifyconf (both in AUR), it's more... customizable

  • Notification-daemon-xfce not working with hal

    Hi,
    I am using xfce-notification-daemon-svn from community and have dbus and hal running.
    Now when i run notify-send "test" everything is fine and the notification appears.
    But in Thunar i don't get any notifications (eg. when unmounting a device).
    I looked into messages.log / daemons.log / errors.log and there was no error regarding dbus, hal or notification-daemon.
    PS: I am running Arch64.
    Does someone have an idea?

    It is an Arch64 problem -- I just filed a bug report about this: http://bugs.archlinux.org/task/9893?str … &closedto=
    Simple solution seems to be to rebuild exo package using ABS.

  • Cow-notify - customizable notification daemon

    cow-notify, fork from dwmstatus
    Notification daemon that runs on background and executes configured command (If there isn't any executes xsetroot -name)
    parses following tags:
    [summary] - Replace with summary
    [body] - Replace with body
    [expire] - Replace with expiritation time (milliseconds)
    By default there is no config file, if you want to execute custom command, then create this file :
    $XDG_CONFIG_HOME/cow-notify/config and type command eg. "xcowsay --image myimage.png '[summary]' '[body]'"
    I suggest making the config file read only for everyone expect you, so other users can't go and change it to something more dangerous.
    !IMPORTANT! Execution
    if(!(sh = getenv("SHELL"))) sh = "/bin/sh";
    execlp(sh, sh, "-c", parsed, (char*)NULL);
    Since it exectues shell, all shell rules also apply.
    So make sure your [body] and [summary] are enclosed with single quotes, otherwise notify events can execute commands.
    cow-notify escapes all single quote characters inside [body] and [summary], so you don't have to worry about those. However if you have shell that does not use single quotes for strong quoting then you might want to edit the source.
    Issues :
    * Fails to reply on some python programs (?)
    https://github.com/Cloudef/cow-notify # Github
    https://aur.archlinux.org/packages.php?ID=52751 # AUR, thanks synorgy
    Last edited by Cloudef (2011-11-29 19:00:31)

    ArchArael wrote:
    That's really cute. ^______^
    How do I proceed to enable the mascot?
    OT: I like your avatar.
    You can either grab the original macopix
    Or fork I've made here with few bugs fixed and animation signaling added.
    Then setup your macopix run at startup with --sockmsg option, and set cow-notify send messages to it like in my example.
    cow-notify might fail on system startup sometimes for some reason, and this can be fixed with delay (sleep 50 && cow-notify) &
    You can grab the dancing miku mascot from here
    Also I suggest setting slight startup delay for macopix too if you autostart it. (sleep 20 && macopix) & is fine.
    Some references which might help you further:
    My openbox autostart.sh # See the cow-notify and macopix lines.
    https://github.com/Cloudef/dotFiles/blo … tostart.sh
    Cow-notify config:
    https://github.com/Cloudef/dotFiles/blo … ify/config
    Deadbeef conky script that also makes the miku dance :
    https://github.com/Cloudef/dotFiles/blo … b-cover.sh

  • XFCE notification daemon

    I have notification-daemon-xfce and libnotify installed but when I unmount or mount a drive, there is no notification of this. In the past it would say something like "this drive is now safe to remove". The only setting I have found is to change the position. How to I customize what it shows, when it shows it?

    The function of the notification daemon is *only* to display those little boxes, nothing more.  The fact that it's xfce's is immaterial; basically there is a libnotify spec that the daemon can follow as closely as it wishes, implementing niceties like html markup in your little popup boxes, or other such things.
    The responsibility for putting something you want in the box lies with thunar, or probably thunar-volman.  As far as I know the your customisation options lie somewhere between a) filing a bug and b) editing the libnotify call in thunar's code yourself.
    There are also "themes" for libnotify popups...good luck compiling them.
    (Sorry, I have no love for libnotify)

  • XDG Autostart for Notification Daemon

    Arch installs some .desktop files in /etc/xdg/autostart as it should. Examples include
    wicd-tray.desktop
    pulseaudio.dekstop
    parcellite-startup.desktop
    at-spi-dbus-bus.desktop
    polkit-gnome-authentication-agent-1.desktop
    but not
    notification-daemon.desktop
    Why does Arch put that one in /usr/share/applications? Does it not belong in autostart with other desktop daemons? I actually made a symlink by hand from /usr/share/applications to /etc/xdg/autostart just for this daemon.
    Thanks

    I have the same problem. Theres an error when you try to use the nodoka engine in 64 bit. I know theres an rpm floating around to install the engine for x86_64 but im not sure hoe to install it.

  • [SOLVED] transmission-daemon segfaulting, trapped, and others

    Hey guys,
    Originally I was having the same problem with Rtorrent when I hit about 4000 torrents. Now I'm slightly above 6000 torrents with Transmission, and it has recently started crashing with messages like these in the syslog:
    [1556037.507253] traps: transmission-da[2855] general protection ip:457c12 sp:7fc301ad7b00 error:0 in transmission-daemon[400000+75000]
    [1784992.236136] transmission-da[2884]: segfault at 4377000043e4 ip 0000000000457c12 sp 00007f07c5134b00 error 4 in transmission-daemon[400000+75000]
    [2030052.408358] traps: transmission-da[13344] general protection ip:457c12 sp:7fab58b66b00 error:0 in transmission-daemon[400000+75000]
    and these are the 3 just from this boot. I have a theory it only starts to happen after the system has been running for a few days, but I've just rebooted it to see if crashes in the same fashion.
    Regardless, since this also happened with rtorrent at fewer torrents, I'm thinking I could be experiencing memory corruption. Is there a reliable way to check for this, without putting down the system for too long? I have a webserver serving 2 sites, which I'd prefer didn't stay offline for too long - but if there are no alternatives, then so be it.
    Thanks,
    gonX
    Last edited by gonX (2013-05-18 14:17:40)

    Solved, it was a RAM issue. Replaced all the sticks and now it has been running for weeks without a crash.

  • [SOLVED] apache daemon fails to start on boot, but rc.d restart works?

    I installed apache from the official repos and followed the instructions in the wiki for configuring it. I checked to make sure the http user exists, and I /etc/hosts looks good (to me). Upon boot, the daemon fails to start and I can't load local web pages, but running "rc.d restart httpd" works just fine. Since I'd rather not start it manually every time I boot, is there a way to fix this? Also, httpd is the last daemon in my DAEMONS array.
    /etc/httpd/conf/httpd.conf:
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
    # with ServerRoot set to "/etc/httpd" will be interpreted by the
    # server as "/etc/httpd//var/log/httpd/foo_log".
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk. If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "/etc/httpd"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 127.0.0.1:80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_anon_module modules/mod_authn_anon.so
    LoadModule authn_dbd_module modules/mod_authn_dbd.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule file_cache_module modules/mod_file_cache.so
    LoadModule cache_module modules/mod_cache.so
    LoadModule disk_cache_module modules/mod_disk_cache.so
    LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule dbd_module modules/mod_dbd.so
    LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule reqtimeout_module modules/mod_reqtimeout.so
    LoadModule ext_filter_module modules/mod_ext_filter.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    LoadModule substitute_module modules/mod_substitute.so
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule log_forensic_module modules/mod_log_forensic.so
    LoadModule logio_module modules/mod_logio.so
    LoadModule env_module modules/mod_env.so
    LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule ident_module modules/mod_ident.so
    LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule ssl_module modules/mod_ssl.so
    LoadModule mime_module modules/mod_mime.so
    LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule info_module modules/mod_info.so
    LoadModule suexec_module modules/mod_suexec.so
    LoadModule cgi_module modules/mod_cgi.so
    LoadModule cgid_module modules/mod_cgid.so
    LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    #php
    LoadModule php5_module modules/libphp5.so
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock /var/run/httpd/cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # MaxRanges: Maximum number of Ranges in a request before
    # returning the entire resource, or one of the special
    # values 'default', 'none' or 'unlimited'.
    # Default setting is to accept 200 Ranges.
    #MaxRanges unlimited
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    #PHP
    Include conf/extra/php5_module.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    /etc/hosts
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost laptop
    ::1 localhost.localdomain localhost
    # End of file
    Per the wiki, I also tried commenting out the line that reads
    LoadModule unique_id_module modules/mod_unique_id.so
    Either way, it still fails on boot.
    Last edited by pythonscript (2012-06-10 21:14:44)

    The SIGTERM are from reboots, yes. I'm not absolutely sure that the process isn't running; I just know that I can't access http://localhost immediately upon reboot. I have to restart the httpd daemon, which works fine. How would I be able to tell if it's just hung?
    I checked everything.log, and I don't see anything that leaps off the page to me.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1930 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 2 threads of 1 processes of 1 users.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Successfully made thread 1931 of process 1908 (/usr/bin/pulseaudio) owned by '120' RT at priority 5.
    Jun 9 22:29:30 localhost rtkit-daemon[1910]: Supervising 3 threads of 1 processes of 1 users.
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=RegisterClient
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: RegisterClient 106d33cade29b1ba713392593689729000000018320001
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689729000000018320001 to session
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): uid = 120
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): pid = 1842
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client2 to store
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client2
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): App gnome-settings-daemon.desktop registered
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase INITIALIZATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase WINDOW_MANAGER
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase PANEL
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase DESKTOP
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting app '/org/gnome/SessionManager/App1'
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): Starting app: /org/gnome/SessionManager/App1
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: starting gnome-shell.desktop: command=gnome-shell --gdm-mode startup-id=106d33cade29b1ba713392593689681600000018320000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmAutostartApp: started pid:1936
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase APPLICATION
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase RUNNING
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmPresence: adding idle watch
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for positive transition wait=600000
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GSIdleMonitor: creating new alarm for negative transition wait=599999
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:30 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:31 localhost kernel: [ 29.003352] wlan0: no IPv6 routers present
    Jun 9 17:29:31 localhost NetworkManager[765]: <warn> could not commit DNS changes: (0) Could not replace /etc/resolv.conf: Operation not permitted
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) successful, device activated.
    Jun 9 17:29:31 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: accept_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: auth_ice_connection()
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Setting up new connection
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: New client '0x7f9ff0004e60 []'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client3 to store
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client3
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Initializing client 0x7f9ff0004e60 []
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 []' received RegisterClient(106d33cade29b1ba713392593689681600000018320000)
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmManager: Adding new client 106d33cade29b1ba713392593689681600000018320000 to session
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Sending RegisterClientReply to '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Set properties from client '0x7f9ff0004e60 [106d33cade29b1ba713392593689681600000018320000]'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Program = 'gnome-shell'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: UserID = 'gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 0
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: ProcessID = '1936'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: CurrentDirectory = '/var/lib/gdm'
    Jun 9 17:29:31 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: _GSM_Priority = 20
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: sending IPv6 Router Solicitation
    Jun 9 17:29:31 localhost dhcpcd[1640]: eth0: no IPv6 Routers available
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: sending IPv6 Router Solicitation
    Jun 9 17:29:33 localhost dhcpcd[1677]: wlan0: no IPv6 Routers available
    Jun 9 17:29:33 localhost NetworkManager[765]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:34 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:35 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> (eth0): IP6 addrconf timed out or failed.
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:40 localhost NetworkManager[765]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> (wlan0): IP6 addrconf timed out or failed.
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    Jun 9 17:29:41 localhost NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: handling signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Found 1 callbacks
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x41c9e0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Got callback for signal 15
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Logout called
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: requesting logout
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase RUNNING
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: sending query-end-session to clients (logout mode: forceful)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.8
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: sending QueryEndSession signal to :1.2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to query clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Caught signal 15, shutting down normally.
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GdmSignalHandler: Done handling signals
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, 9, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: query end session complete
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmShell: Connected to the shell
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received SaveYourselfDone(success = True)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXsmpServer: sms_error_handler (0x1491c70, FALSE, 3, c, 32771, 0)
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect for app 'at-spi-registryd.desktop'
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: unable to find application for client - not restarting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428a40
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase END_SESSION
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Using ConsoleKit for session tracking
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: starting phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_stop ('0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]')
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: Client '0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000]' received CloseConnection
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x7f9ff0004e60
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client3
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x7f9ff0004e60 [gnome-shell 106d33cade29b1ba713392593689681600000018320000])
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: in shutdown, not restarting application
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1428ac0
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: last client disconnected - exiting
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: ending phase EXIT
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): Unreffing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmManager: disposing manager
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473070
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Unreffing object: 0x1473150
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App2
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/App1
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gnome-session[1832]: DEBUG(+): GsmStore: Clearing object store
    Jun 9 17:29:42 localhost gdm-simple-slave[1728]: WARNING: Child process 1832 was already dead.
    Jun 9 17:29:43 localhost gnome-session[1970]: EggSMClient-WARNING: Desktop file '/home/ak5791/.config/autostart/dropbox.desktop' has malformed Icon key 'dropbox.png'(should not include extension)
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2022 of process 2022 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 4 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2023 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 5 threads of 2 processes of 2 users.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Successfully made thread 2024 of process 2022 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
    Jun 9 22:29:43 localhost rtkit-daemon[1910]: Supervising 6 threads of 2 processes of 2 users.
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
    Jun 9 17:29:44 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Jun 9 17:29:44 localhost dbus[739]: [system] Activating service name='org.freedesktop.colord-sane' (using servicehelper)
    Jun 9 17:29:45 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.colord-sane'
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Successfully made thread 2079 of process 2079 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    Jun 9 22:29:46 localhost rtkit-daemon[1910]: Supervising 7 threads of 3 processes of 2 users.
    Jun 9 17:29:46 localhost pulseaudio[2079]: [pulseaudio] pid.c: Daemon already running.
    Jun 9 17:29:48 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
    Jun 9 17:29:48 localhost udisksd[2110]: udisks daemon version 1.94.0 starting
    Jun 9 17:29:48 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    Jun 9 17:29:48 localhost udisksd[2110]: Acquired the name org.freedesktop.UDisks2 on the system message bus
    Jun 9 17:29:48 localhost kernel: [ 46.319778] gnome-shell-cal[2103] trap int3 ip:7ff3f55b85e1 sp:7fff94941890 error:0
    Jun 9 17:30:19 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:40:53 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:47:15 localhost kernel: [ 1092.983585] usb 8-1.4.1: new high-speed USB device number 8 using ehci_hcd
    Jun 9 22:47:15 localhost mtp-probe: checking bus 8, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1/8-1.4/8-1.4.1"
    Jun 9 22:47:15 localhost mtp-probe: bus: 8, device: 8 was not an MTP device
    Jun 9 22:47:15 localhost kernel: [ 1093.132002] usbcore: registered new interface driver uas
    Jun 9 22:47:15 localhost kernel: [ 1093.135601] Initializing USB Mass Storage driver...
    Jun 9 22:47:15 localhost kernel: [ 1093.135785] scsi6 : usb-storage 8-1.4.1:1.0
    Jun 9 22:47:15 localhost kernel: [ 1093.135905] usbcore: registered new interface driver usb-storage
    Jun 9 22:47:15 localhost kernel: [ 1093.135913] USB Mass Storage support registered.
    Jun 9 22:47:16 localhost kernel: [ 1094.137579] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2 1.00 PQ: 0 ANSI: 2
    Jun 9 22:47:16 localhost kernel: [ 1094.140133] sd 6:0:0:0: [sdb] 15636304 512-byte logical blocks: (8.00 GB/7.45 GiB)
    Jun 9 22:47:16 localhost kernel: [ 1094.140631] sd 6:0:0:0: [sdb] Write Protect is off
    Jun 9 22:47:16 localhost kernel: [ 1094.140634] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
    Jun 9 22:47:16 localhost kernel: [ 1094.141128] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.141132] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.144916] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.144921] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.146680] sdb: sdb1
    Jun 9 22:47:16 localhost kernel: [ 1094.151407] sd 6:0:0:0: [sdb] No Caching mode page present
    Jun 9 22:47:16 localhost kernel: [ 1094.151411] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Jun 9 22:47:16 localhost kernel: [ 1094.151414] sd 6:0:0:0: [sdb] Attached SCSI removable disk
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Version 2012.1.15 external FUSE 29
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mounted /dev/sdb1 (Read-Write, label "kingstonGB", NTFS 3.1)
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks2
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
    Jun 9 22:47:17 localhost ntfs-3g[2636]: Global ownership and permissions enforced, configuration type 7
    Jun 9 22:47:17 localhost udisksd[2110]: Mounted /dev/sdb1 at /run/media/ak5791/kingstonGB on behalf of uid 1000
    Jun 9 22:47:28 localhost dbus[739]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
    Jun 9 22:47:28 localhost dbus[739]: [system] Successfully activated service 'org.freedesktop.UDisks'
    Jun 9 22:47:46 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 22:57:59 localhost dbus[739]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
    Jun 9 23:01:02 localhost /USR/SBIN/CROND[5529]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 9 23:21:02 localhost -- MARK --
    All I notice is that my system's time is having a few problems, since you'll notice that events occur at 22:00 and change, then 17:00 and change, then back to 22:00 and change afterwards. Could this be the problem? I've had the CMOS batteries peg out on me suddenly in the last few weeks. I would hope this sytem is not also suffering a similar fate. Nothing else was happening on my system except for the standard processes from /etc/rc.conf and other standard ones, since I've just been rebooting, checking the logs, then posting here.

Maybe you are looking for