DBUS Error

Hello Everyone,
       I today did a clean install of Arch but im getting a error while boot up.Its with the "dbus" daemon.The error im getting is as follows:-
[root@Rajiv-Nair rajiv]# /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus                                      [DONE]
:: Starting D-BUS system messagebus                                        [BUSY]
   Unknown group "network" in message bus configuration file
                                                                                                   [DONE]
     This is my /etc/rc.conf file:-
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/unimaps
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Calcutta"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="Rajiv-Nair"
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="eth0 169.254.149.178 netmask 255.255.0.0 broadcast
169.254.255.255"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng acpid dbus !hotplug !pcmcia network netfs crond
portmap fam hal gdm)
# End of file
BTW im using Intel Chipset and had to edit out my fstab and /boot/grub/menu.lst for arch to work,i dont know whether its because of that or something else.
Thanks in Advance,
  Rajiv Nair

Thnx Snowman,tht worked,but...
         Here's what i have come to see tht when i did a clean install yesterday and upgraded to latest packages,certain files which had "glibc" as their dependencies got installed before glibc and were putting out some error which i'd overlooked.Today i again did a clean install but before upgrading i did a force install of "glibc" and i figured tht all the problems i had earlier were solved.
I am using a Intel Chipset ,so i dont know whether its a hardware specific problem related to kernel 2.6.19 but IMO  tht priority thingy of glibc needs to be taken care about.

Similar Messages

  • [SOLVED] DBus error when accessing "Windows Network"

    I'm getting an error when trying to access "Windows Network" from Nautilus after last Gnome (2.22 -> 2.24) update:
    Unable to mount location
    DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
    Please tell me if you need me to post any more info/logs.
    Thanks in advance
    Last edited by DingoMD (2008-10-22 08:07:36)

    Are those with a problem using share level security on the samba server?
    Have you tried accessing the share using smbclient? (smbclient //server/share)
    I have been receiving the original dbus error for some time now.
    I am using share level security on the server.
    Using smbclient results in a segfault. Using nautilus also results in an error from libsmbclient which can be seen in one of the log files.
    [mythtv@tvee ~]$ smbclient //sirschmoopy/shared
    Enter mythtv's password:
    Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.1]
    Server not using user level security and no password supplied.
    Segmentation fault
    There is a samba bug which looks similar but it only affects people with ipv6 disabled. I have disabled and enabled ipv6 several times and the errors persist.
    I think it may be related to this bug: https://bugzilla.samba.org/show_bug.cgi?id=7250
    I haven't tried the patch provided yet.

  • [SOLVED] Unable to Print from CUPS - DBus Errors?

    Hi all-
    I'm unable to print on CUPS after doing a recent system upgrade. Not excatly sure what's going on, but below is an output of the error log. Just as a side note- I have two arch machines. The one I'm having problems with has XFCE, my other arch has aweosme and cups works fine. So we can rule out the actual printer as being the problem.
    A few of the errors below are attempts to cancel a test print page job and getting forbidden. Not sure why this would happen other than possibly not logging in as root, but that's not even the main issue. So yea, any help would be appreciated.
    Just one more thing, I've noticed in /etc/cups that one of the config files was renamed to cupsd.conf.pacnew. Anyone know why pacman is over-writting those config files?
    W [27/Mar/2013:12:37:37 -0400] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_EPSON_Stylus_Photo_R220
    E [27/Mar/2013:15:37:31 -0400] Returning HTTP Forbidden for Cancel-Job (ipp://localhost/jobs/44) from localhost
    E [27/Mar/2013:15:39:22 -0400] Returning HTTP Forbidden for CUPS-Add-Modify-Printer (ipp://localhost/printers/EPSON_Stylus_Photo_R220) from localhost
    E [27/Mar/2013:15:40:34 -0400] Returning HTTP Forbidden for CUPS-Get-Devices (no URI) from localhost
    E [27/Mar/2013:15:40:34 -0400] [CGI] CUPS-Get-Devices request failed with status 401: Forbidden
    E [27/Mar/2013:15:41:19 -0400] Returning HTTP Forbidden for Cancel-Job (ipp://localhost/jobs/44) from localhost
    E [27/Mar/2013:15:42:07 -0400] Returning HTTP Forbidden for Purge-Jobs (ipp://localhost/printers/EPSON_Stylus_Photo_R220) from localhost
    E [27/Mar/2013:15:42:31 -0400] Returning HTTP Forbidden for CUPS-Get-Devices (no URI) from localhost
    E [27/Mar/2013:15:42:31 -0400] [CGI] CUPS-Get-Devices request failed with status 401: Forbidden
    Last edited by w201 (2013-03-27 21:57:26)

    Inxsible wrote:
    w201 wrote:Just one more thing, I've noticed in /etc/cups that one of the config files was renamed to cupsd.conf.pacnew. Anyone know why pacman is over-writting those config files?
    In fact, it's not overwriting the config file, which is why you have a pacnew file. You need to read up a bit more on pacman and pacnew and pacsave in general.
    You should merge any and all pacnews with your corresponding config files if pacman tells you that it has created a pacnew file during upgrade. Don't just replace them with newer versions though, because it can lead to bad things like locking you out of the system if you do that for certain files like group or gshadow etc.
    You're completely right, it's not overwriting the files, hence pacnew... bad choice of words.
    ***EDIT***
    Okay....well, I read up on pacnew and pacsave. Thanks for pointing that out, Inxsible. Merging the files solved the problem.
    Thanks again!
    Last edited by w201 (2013-03-27 21:57:00)

  • GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown error

    I recently updated my system and now it giving me an error:
    GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.cinnamon.SettingsDaemon was not provided by any .service files
    How can I easily start troubleshooting this issue?
    Pacman.log:  http://pastebin.com/BRRmuWPV
    I've got an IBM T520 laptop with built-in i915:
    [blah@blah ~]$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
    Subsystem: Lenovo Device 21cf
    Flags: bus master, fast devsel, latency 0, IRQ 28
    Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
    Memory at e0000000 (64-bit, prefetchable) [size=256M]
    I/O ports at 5000 [size=64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: <access denied>
    Kernel driver in use: i915
    Kernel modules: i915
    [blah@blah ~]$
    Any help would be appreciated
    Last edited by Anoniem (2015-02-09 13:02:53)

    Anoniem wrote:
    Haha, well:
    1. I turn on laptop
    2. Login into my desktop
    3. My display is low resolution and external display too, fonts and theme settings are gone (gnome)
    4. I want to change resolution
    5. Get error message like above
    Checked my logs, tried reverting packages I updated
    Still the same GDBUS thing.
    Maybe there is an conflict when the X starts on 2 monitors with 2 different resolutions...
    It depends from your graphic card. For example, on my nvidia when X starts with both internal and external monitors plugged in, the resolution is messed up. But when you enter to your desktop, usually it reads the last resolution states and the screen resolution problem if fixed.
    One solution is to plug the external monitor after desktop is loaded or create a config file for the monitors on the /etc/X11/... folder Xorg wiki
    Last edited by alex.theoto (2014-12-05 17:18:11)

  • Bluetooth : Blueman dbus error

    Hello dear archers,
    I am facing a problem trying to setup bluetooth at my desktop pc. It is a USB Bluetooth donge.
    I followed http://wiki.archlinux.org/index.php/Bluetooth but i cannot launch blueman-manager.
    I get the following error :
    Connection to BlueZ failed
    Bluez daemon is not running, blueman-manager cannot continue.
    Further in the wiki i tried
    [razor@RAZPC-LIN ~]$ hcitool scan
    Scanning ...
    00:25:BC:65:D3:75 anna petraki's iMac
    00:22:98:1E:E1:C7 1 mouni stin axladia
    So the bluetooth device is actually working. Then i tried using the bluez-simple-agent:
    dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
    I have installed all the python packages for bluetooth ( dbus-python pygobject python-pybluez )
    Do you have any idea what is going wrong?

    oh yes, sorry forgot to mention, both of them are started. here is my /etc/conf.d/bluetooth
    [razor@RAZPC-LIN ~]$ cat /etc/conf.d/bluetooth
    # Bluetooth configuraton file
    # Bluetooth services (allowed values are "true" and "false")
    # Run the bluetoothd daemon (default: true)
    #DAEMON_ENABLE="false"
    # Run hid2hci (default: false)
    HID2HCI_ENABLE="true"
    # Run the sdp daemon (default: false)
    # If this is disabled, hcid's internal sdp daemon will be used
    SDPD_ENABLE="true"
    # Run the bluetooth HID daemon (default: false)
    HIDD_ENABLE="true"
    # Activate rfcomm ports (default: false)
    RFCOMM_ENABLE="true"
    # Run bluetooth dial-up networking daemon (default: false)
    #DUND_ENABLE="true"
    # Run bluetooth PAN daemon (default: false)
    #PAND_ENABLE="true"
    # rfcomm configuration file (default: /etc/bluetooth/rfcomm.conf)
    RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"
    # Options for hidd, dund and pand (default: none)
    #HIDD_OPTIONS=""
    #DUND_OPTIONS=""
    #PAND_OPTIONS=""
    HAL and other services like Avahi which require dbus work as expected. Does this .service file lie anywhere so i can check if it exists or it is created dynamically uppon bluetooth daemon startup?
    Thanks for your reply.

  • Udev Mounting - DBus error RemoteVolumeMonitor.Failed

    Hello.
    I have been using thunar-git for a while and every time a mount an external media (cd/dvd, flash memory, etc....) I get this error:
    "DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending."
    The drive mounts and I don't have any problems, but the error is sort of annoying. As far as I can tell, the error doesn't bring any ill effects except having to close the dialog box. Does anyone know how I can prevent this error from showing or fix it?
    Thanks!

    Solved. I created the file
    /etc/polkit-1/localauthority/50-local.d/org.freedesktop.udisks.pkla
    Here is my file:
    [Local Users]
    Identity=unix-user:johnny
    Identity=unix-group:storage
    Action=org.freedesktop.udisks.*
    ResultAny=yes
    ResultInactive=no
    ResultActive=yes
    No more problems with thunar (there was an option to add in the "Action" section to allow the automounting of the internal drives, but i don't remember. I don't need it).
    EDIT: I think that you can also do:
    [Local Users]
    Identity=unix-user:*
    Identity=unix-group:storage
    Action=org.freedesktop.udisks.*
    ResultAny=yes
    ResultInactive=no
    ResultActive=yes
    If you want allow to a generic user this option.
    Last edited by reddhawk (2012-10-31 06:59:38)

  • [SOLVED] dbus error when taking a screenshot

    I can't take screenshots with the Gnome3 screenshot program. When I try to save a screenshot, I get this error message:
    Error while saving screenshot.
    Impossible to save the screenshot to file:///home/some/directory.
    Error was GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/nautilus exited with status 1.
    Please choose another location and retry.
    I found a thread with a similar problem (dbus error when taking a screenshot; the error message is different though) providing a solution, but I can't try that solution because I don't have a /etc/X11/xorg.conf.d/20-intel.conf file.
    How can I fix this?
    Last edited by cryptkeeper (2012-03-05 08:12:36)

    Damn, I found the solution (or better: source) of the problem... The error messages states that /usr/bin/nautilus exits with error something-something, and after thinking about that for some seconds it came to my mind that I replaced /usr/bin/nautilus with a softlink (ln -s) to /usr/bin/thunar because I didn't find a better way to totally replace Nautilus with Thunar...
    Thanks for trying to help anyway!

  • Caffeine dbus error

    When I start using gnome3, the aur program "caffeine" give me this error:
    [rmasad@myhost ~]$ caffeine
    (01 may 2011) 17:18:11 INFO: User has clicked the Caffeine icon
    (01 may 2011) 17:18:11 INFO: Attempting to detect screensaver/powersaving type... (0 dbus failures so far)
    (01 may 2011) 17:18:11 INFO: Successfully detected screensaver and powersaving type: Gnome
    Traceback (most recent call last):
    File "/usr/lib/python2.7/site-packages/caffeine/main.py", line 506, in on_L_click
    self.toggleActivated()
    File "/usr/lib/python2.7/site-packages/caffeine/main.py", line 481, in toggleActivated
    self.Core.toggleActivated()
    File "/usr/lib/python2.7/site-packages/caffeine/core.py", line 455, in toggleActivated
    self._performTogglingActions()
    File "/usr/lib/python2.7/site-packages/caffeine/core.py", line 509, in _performTogglingActions
    self._detectScreensaverAndPowersavingType()
    File "/usr/lib/python2.7/site-packages/caffeine/core.py", line 501, in _detectScreensaverAndPowersavingType
    self._performTogglingActions()
    File "/usr/lib/python2.7/site-packages/caffeine/core.py", line 513, in _performTogglingActions
    self._toggleGnome()
    File "/usr/lib/python2.7/site-packages/caffeine/core.py", line 540, in _toggleGnome
    "User has requested that Caffeine disable the screen saver")
    File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
    File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
    dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Inhibit" with signature "ss" on interface "(null)" doesn't exist

    Up!

  • Dbus error when running systemd-analyze

    I recently switched over to systemd, setting it up according to the ArchWiki. However, when I run
    systemd-analyze
    I always get the following error message:
    Traceback (most recent call last):
    File "/usr/bin/systemd-analyze", line 307, in <module>
    time()
    File "/usr/bin/systemd-analyze", line 91, in time
    initrd_time, start_time, finish_time = acquire_start_time()
    File "/usr/bin/systemd-analyze", line 32, in acquire_start_time
    properties = dbus.Interface(bus.get_object('org.freedesktop.systemd1', '/org/freedesktop/systemd1'), 'org.freedesktop.DBus.Properties')
    File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
    File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
    File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
    File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
    File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
    dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
    What can I do to fix this? Any help is greatly appreciated.
    Edit: grammar.
    Last edited by myucht (2012-07-03 02:50:48)

    The table I get an error on is not partitioned.
    I also do not get a exception when I run that procedure manually as system, but when I run it from dba_jobs, I get an insufficient privileges issue.

  • DBUS error seems to prevent proper Gnome3.2 startup

    Hi everyone,
    I've been unable to start Gnome3.2 ever since it first came out. Here's my X error log:
    X.Org X Server 1.10.4
    Release Date: 2011-08-19
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.0-ARCH x86_64
    Current Operating System: Linux blackbriar 2.6.32-lts #1 SMP Tue Aug 30 08:59:44 CEST 2011 x86_64
    Kernel command line: BOOT_IMAGE=/vmlinuz26-lts root=UUID=e09c380a-ed57-49b8-82ef-125ddd407ac4 ro quiet
    Build Date: 17 September 2011 07:42:58AM
    Current version of pixman: 0.22.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 2 14:31:16 2011
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    (EE) Failed to load module "vesa" (module does not exist, 0)
    (EE) Failed to load module "fbdev" (module does not exist, 0)
    FATAL: Module fbcon not found.
    xmodmap: commandline:1: bad add modifier name 'caps_lock', not allowed
    xmodmap: 1 error encountered, aborting.
    xset: unknown option +ft
    usage: xset [-display host:dpy] option ...
    To turn bell off:
    -b b off b 0
    To set bell volume, pitch and duration:
    b [vol [pitch [dur]]] b on
    To disable bug compatibility mode:
    -bc
    To enable bug compatibility mode:
    bc
    To turn keyclick off:
    -c c off c 0
    To set keyclick volume:
    c [0-100] c on
    To control Energy Star (DPMS) features:
    -dpms Energy Star features off
    +dpms Energy Star features on
    dpms [standby [suspend [off]]]
    force standby
    force suspend
    force off
    force on
    (also implicitly enables DPMS features)
    a timeout value of zero disables the mode
    To set the font path:
    fp= path[,path...]
    To restore the default font path:
    fp default
    To have the server reread font databases:
    fp rehash
    To remove elements from font path:
    -fp path[,path...] fp- path[,path...]
    To prepend or append elements to font path:
    +fp path[,path...] fp+ path[,path...]
    To set LED states off or on:
    -led [1-32] led off
    led [1-32] led on
    -led named 'name' led off
    led named 'name' led on
    To set mouse acceleration and threshold:
    m [acc_mult[/acc_div] [thr]] m default
    To set pixel colors:
    p pixel_value color_name
    To turn auto-repeat off or on:
    -r [keycode] r off
    r [keycode] r on
    r rate [delay [rate]]
    For screen-saver control:
    s [timeout [cycle]] s default s on
    s blank s noblank s off
    s expose s noexpose
    s activate s reset
    For status information: q
    gnome-session[1704]: EggSMClient-WARNING: Desktop file '/home/bow/.config/autostart/dropbox.desktop' has malformed Icon key 'dropbox.png'(should not include extension)
    ** (gnome-settings-daemon:1719): WARNING **: /usr/lib/gnome-settings-daemon-3.0/libcolor.so: cannot open shared object file: No such file or directory
    ** (gnome-settings-daemon:1719): WARNING **: Cannot load plugin 'Color' since file '/usr/lib/gnome-settings-daemon-3.0/libcolor.so' cannot be read.
    ** (gnome-settings-daemon:1719): WARNING **: Error activating plugin 'Color'
    GNOME_KEYRING_CONTROL=/tmp/keyring-r39ZPd
    GNOME_KEYRING_PID=1726
    GNOME_KEYRING_CONTROL=/tmp/keyring-r39ZPd
    GNOME_KEYRING_CONTROL=/tmp/keyring-r39ZPd
    SSH_AUTH_SOCK=/tmp/keyring-r39ZPd/ssh
    GNOME_KEYRING_CONTROL=/tmp/keyring-r39ZPd
    SSH_AUTH_SOCK=/tmp/keyring-r39ZPd/ssh
    GPG_AGENT_INFO=/tmp/keyring-r39ZPd/gpg:0:1
    WARNING: no socket to connect to
    common-plugin-Message: checking whether we have a device for 4: yes
    common-plugin-Message: checking whether we have a device for 5: yes
    common-plugin-Message: checking whether we have a device for 12: no
    common-plugin-Message: checking whether we have a device for 11: no
    common-plugin-Message: checking whether we have a device for 10: no
    common-plugin-Message: checking whether we have a device for 9: no
    common-plugin-Message: checking whether we have a device for 8: no
    common-plugin-Message: checking whether we have a device for 7: no
    common-plugin-Message: checking whether we have a device for 6: no
    gnome-session[1704]: WARNING: Application 'gnome-shell.desktop' failed to register before timeout
    Failed to play sound: File or data not found
    listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
    daemon: cannot init supplementary groups of user "bow": Operation not permitted
    ** Message: applet now removed from the notification area
    (nm-applet:1959): libnotify-WARNING **: Failed to connect to proxy
    (empathy:1957): libnotify-WARNING **: Failed to connect to proxy
    Traceback (most recent call last):
    File "/usr/lib/guake/guake.py", line 1353, in <module>
    if not main():
    File "/usr/lib/guake/guake.py", line 1296, in main
    instance = Guake()
    File "/usr/lib/guake/guake.py", line 649, in __init__
    notification.show()
    glib.GError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
    (empathy:1957): folks-WARNING **: Error preparing Backend 'telepathy': Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    [dix] couldn't enable device 10
    JS LOG: GNOME Shell started at Sun Oct 02 2011 14:33:03 GMT+0200 (CEST)
    ** Message: applet now embedded in the notification area
    (gnome-settings-daemon:1719): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    [1317558687,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
    xinit: connection to X server lost
    waiting for X server to shut down
    I have no idea what's wrong there. It looks like it's DBUS, but I'm not sure myself. I've waited a few days for new updates of Gnome3.2, but so far nothing's changed on my end.
    If it helps, this is my pacman -Qm
    aacgain-cvs 20101003-1
    bug-buddy 2.32.0-1
    chromium-stable-libpdf 14.0.835.186-1
    culmus 0.120-1
    dropbox 1.1.45-1
    drush 4.5-1
    easymp3gain-gtk2 0.5.0-4
    evolution-webcal 2.32.0-1
    fam 2.7.0-16
    font-arhangai 20030401-3
    jdk 7-3
    jigdo 0.7.3-2
    jre 7-3
    mendeleydesktop 1.0.1-2
    nautilus-dropbox 0.6.9-2
    newlan 1.0.0.8-3
    os-prober 1.49-3
    otf-ipafont 003.03-1
    packer 20110826-1
    perl-gtk2-imageview 0.05-2
    perl-proc-processtable 0.45-2
    prey-tracker 0.5.3-1
    pyroom-bzr 213-1
    scrobby-git 20110905-1
    tp_smapi 0.41-1
    ttf-droid-sans 1.0-1
    ttf-inconsolata-g 20090213-1
    ttf-ms-fonts 2.0-8
    ttf-sil-scheherazade 1.005-2
    ttf-ubuntu-font-family 0.80-1
    ttf-vista-fonts 1-3
    vidalia 0.2.14-1
    And I've also removed all custom extensions of Gnome3.2, all to no avail.
    What should I do?

    wonder:
    Ah shoot, that's the previous error.log , I'm sorry. I've saved too many error logs now already, it's getting out of hand. This is the correct one:
    X.Org X Server 1.11.1
    Release Date: 2011-09-24
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.0-ARCH x86_64
    Current Operating System: Linux blackbriar 2.6.32-lts #1 SMP Tue Aug 30 08:59:44 CEST 2011 x86_64
    Kernel command line: BOOT_IMAGE=/vmlinuz26-lts root=UUID=e09c380a-ed57-49b8-82ef-125ddd407ac4 ro quiet
    Build Date: 10 October 2011 08:55:30AM
    Current version of pixman: 0.22.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 12 21:01:19 2011
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    (EE) Failed to load module "vesa" (module does not exist, 0)
    (EE) Failed to load module "fbdev" (module does not exist, 0)
    FATAL: Module fbcon not found.
    xmodmap: commandline:1: bad add modifier name 'caps_lock', not allowed
    xmodmap: 1 error encountered, aborting.
    xset: unknown option +ft
    usage: xset [-display host:dpy] option ...
    To turn bell off:
    -b b off b 0
    To set bell volume, pitch and duration:
    b [vol [pitch [dur]]] b on
    To disable bug compatibility mode:
    -bc
    To enable bug compatibility mode:
    bc
    To turn keyclick off:
    -c c off c 0
    To set keyclick volume:
    c [0-100] c on
    To control Energy Star (DPMS) features:
    -dpms Energy Star features off
    +dpms Energy Star features on
    dpms [standby [suspend [off]]]
    force standby
    force suspend
    force off
    force on
    (also implicitly enables DPMS features)
    a timeout value of zero disables the mode
    To set the font path:
    fp= path[,path...]
    To restore the default font path:
    fp default
    To have the server reread font databases:
    fp rehash
    To remove elements from font path:
    -fp path[,path...] fp- path[,path...]
    To prepend or append elements to font path:
    +fp path[,path...] fp+ path[,path...]
    To set LED states off or on:
    -led [1-32] led off
    led [1-32] led on
    -led named 'name' led off
    led named 'name' led on
    To set mouse acceleration and threshold:
    m [acc_mult[/acc_div] [thr]] m default
    To set pixel colors:
    p pixel_value color_name
    To turn auto-repeat off or on:
    -r [keycode] r off
    r [keycode] r on
    r rate [delay [rate]]
    For screen-saver control:
    s [timeout [cycle]] s default s on
    s blank s noblank s off
    s expose s noexpose
    s activate s reset
    For status information: q
    gnome-session[2449]: WARNING: Session 'gnome' runnable check failed: Timed out
    GNOME_KEYRING_CONTROL=/tmp/keyring-BVlgYc
    GPG_AGENT_INFO=/tmp/keyring-BVlgYc/gpg:0:1
    GNOME_KEYRING_PID=2468
    GNOME_KEYRING_CONTROL=/tmp/keyring-BVlgYc
    GPG_AGENT_INFO=/tmp/keyring-BVlgYc/gpg:0:1
    GNOME_KEYRING_CONTROL=/tmp/keyring-BVlgYc
    GPG_AGENT_INFO=/tmp/keyring-BVlgYc/gpg:0:1
    GNOME_KEYRING_CONTROL=/tmp/keyring-BVlgYc
    GPG_AGENT_INFO=/tmp/keyring-BVlgYc/gpg:0:1
    SSH_AUTH_SOCK=/tmp/keyring-BVlgYc/ssh
    WARNING: no socket to connect to
    common-plugin-Message: checking whether we have a device for 4: yes
    common-plugin-Message: checking whether we have a device for 5: yes
    common-plugin-Message: checking whether we have a device for 12: no
    common-plugin-Message: checking whether we have a device for 11: no
    common-plugin-Message: checking whether we have a device for 10: no
    common-plugin-Message: checking whether we have a device for 9: no
    common-plugin-Message: checking whether we have a device for 8: no
    common-plugin-Message: checking whether we have a device for 7: no
    common-plugin-Message: checking whether we have a device for 6: no
    Initializing tracker-miner-fs...
    Initializing tracker-store...
    Tracker-Message: Setting up monitor for changes to config file:'/home/bow/.config/tracker/tracker-miner-fs.cfg'
    Starting log:
    File:'/home/bow/.local/share/tracker/tracker-miner-fs.log'
    Tracker-Message: Setting up monitor for changes to config file:'/home/bow/.config/tracker/tracker-store.cfg'
    Tracker-Message: Setting up monitor for changes to config file:'/home/bow/.config/tracker/tracker-store.cfg'
    Starting log:
    File:'/home/bow/.local/share/tracker/tracker-store.log'
    Failed to play sound: File or data not found
    Failed to bind to '[::]:6600': Address already in use
    ** Message: applet now removed from the notification area
    ** (gnome-fallback-mount-helper:2545): DEBUG: Starting automounting manager
    ** (gnome-fallback-mount-helper:2545): DEBUG: ScreenSaver name vanished
    ** (gnome-fallback-mount-helper:2545): DEBUG: ScreenSaver name appeared
    ** (gnome-screensaver:2546): WARNING **: Config key not handled: disable-application-handlers
    ** (gnome-screensaver:2546): WARNING **: Config key not handled: disable-command-line
    ** (gnome-screensaver:2546): WARNING **: Config key not handled: disable-log-out
    ** (gnome-screensaver:2546): WARNING **: Config key not handled: disable-print-setup
    ** (gnome-screensaver:2546): WARNING **: Config key not handled: disable-printing
    ** (gnome-screensaver:2546): WARNING **: Config key not handled: disable-save-to-disk
    ** (gnome-fallback-mount-helper:2545): DEBUG: ScreenSaver proxy ready
    ** (gnome-fallback-mount-helper:2545): DEBUG: Screensaver GetActive() returned 0
    ** (gnome-fallback-mount-helper:2545): DEBUG: Found ConsoleKit session at path /org/freedesktop/ConsoleKit/Session4
    ** (gnome-fallback-mount-helper:2545): DEBUG: ConsoleKit session is active 0
    ** (notification-daemon:2517): DEBUG: Adding id 1
    ** Message: applet now embedded in the notification area
    (empathy:2509): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 32
    (nm-applet:2512): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -8 and height 32
    ** (gnome-fallback-mount-helper:2545): DEBUG: ConsoleKit session is active 1
    [dix] couldn't enable device 10
    ** (notification-daemon:2517): DEBUG: Bubble destroyed
    ** (notification-daemon:2517): DEBUG: No queued notifications
    (tracker-miner-fs:2513): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/share/applications/brasero-nautilus.desktop': 'Desktop file doesn't contain type'
    ** (gnome-fallback-mount-helper:2545): DEBUG: ConsoleKit session is active 0
    ** (gnome-fallback-mount-helper:2545): DEBUG: ConsoleKit session is active 1
    No backlights were found on your system
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-WARNING **: The maximum number of monitors to set (7692) has been reached, not adding any new ones
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: tracker_sparql_builder_prepend: assertion `raw != NULL' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_fd_list_get: assertion `G_IS_UNIX_FD_LIST (list)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_unix_input_stream_new: assertion `fd != -1' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_new: assertion `G_IS_INPUT_STREAM (base_stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_buffered_input_stream_set_buffer_size: assertion `G_IS_BUFFERED_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_set_byte_order: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-store:2515): GLib-GIO-CRITICAL **: g_data_input_stream_read_int32: assertion `G_IS_DATA_INPUT_STREAM (stream)' failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: (Sparql buffer) Error in array-update: Pipe creation failed
    (tracker-miner-fs:2513): Tracker-CRITICAL **: Could not execute sparql: Pipe creation failed
    GLib-GIO-ERROR **: Creating pipes for GWakeup: Too many open files
    No backlights were found on your system
    No backlights were found on your system
    No backlights were found on your system
    (exe:3323): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    (chromium:3025): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_data: assertion `width > 0' failed
    [3025:3025:909905557:ERROR:browser_main.cc(1022)] Gdk: IA__gdk_cursor_new_from_pixbuf: assertion `GDK_IS_PIXBUF (pixbuf)' failed
    [3025:3025:909905591:ERROR:browser_main.cc(1022)] GLib-GObject: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    No backlights were found on your system
    No backlights were found on your system
    (exe:3323): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
    No backlights were found on your system
    PolicyKit daemon disconnected from the bus.
    We are no longer a registered authentication agent.
    ** Message: NM disappeared
    ** Message: applet now removed from the notification area
    ** Message: Got disconnected from the system message bus; retrying to reconnect every 10 seconds
    g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    (gnome-settings-daemon:3800): libupower-glib-WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
    (gedit:3277): GVFS-RemoteVolumeMonitor-WARNING **: Owner :1.36 of volume monitor org.gtk.Private.GduVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
    (gnome-panel:2500): GVFS-RemoteVolumeMonitor-WARNING **: Owner :1.36 of volume monitor org.gtk.Private.GduVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    gnome-session[2449]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    ** (gnome-panel:2500): WARNING **: Error setting property: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ":1.78" does not exist
    ** (notification-daemon:2517): DEBUG: Notification closed - removing from queue
    ** (notification-daemon:2517): DEBUG: Removing id 1
    gnome-session[2449]: WARNING: Unable to determine session: Unable to find session for cookie
    gnome-session[2449]: WARNING: Unable to determine session: Unable to find session for cookie
    gnome-session[2449]: WARNING: Unable to determine session: Unable to find session for cookie
    gnome-session[2449]: WARNING: Unable to determine session: Unable to find session for cookie
    Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
    Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
    xinit: connection to X server lost
    waiting for X server to shut down Check failed: g_shutdown_pipe_write_fd != -1
    Received signal:1->'Hangup'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Received signal:15->'Terminated'
    OK
    [3025:3025:1518677681:ERROR:browser_main_gtk.cc(75)] X IO Error detected
    g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Server terminated successfully (0). Closing log file.
    I tried doing it again (startx), after that last fallback session, it didn't work. So now I'm back to the background-only view.
    Here's my .xinitrc
    xsetroot -cursor_name left_ptr
    xmodmap -e "remove Lock = Caps_Lock"
    xmodmap -e "keysym Caps_Lock = Escape"
    xmodmap -e "add Caps_Lock = Escape"
    xset +ft /usr/share/fonts/local
    xset fp rehash
    exec ck-launch-session gnome-session
    toad: Here's my rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="localtime"
    TIMEZONE="Europe/Amsterdam"
    KEYMAP="us"
    CONSOLEFONT="ter-116n"
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=(vboxdrv vboxnetadp vboxnetflt tp_smapi)
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="blackbriar"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    interface=
    address=
    netmask=
    broadcast=
    gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    #WIRELESS_INTERFACE="wlan0"
    #WIRED_INTERFACE="eth0"
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(hwclock syslog-ng dbus acpid networkmanager netfs crond @httpd)

  • Org.freedesktop.DBus.Error.ServiceUnknown

    Hello list,
    I frequently get these org.freedesktop.DBus error messages, e.g. working in Emacs, or starting Chromium. Is that a dbus bug? Is there a remedy? Its often not critical, e.g. chromium starts up and works fine besides the error message below - but there might be a message I should read.
    Cheers
    [tj@arch ~]$ chromium
    [8025:8034:17227638682:ERROR:object_proxy.cc(239)] Failed to call method:
    org.freedesktop.DBus.Error.ServiceUnknown:
    The name org.freedesktop.NetworkManager was not provided by any .service files
    Neues Fenster in aktueller Browsersitzung erstellt.

    hadrons123 wrote:
    What version of chrome are you using?
    Here is some info from google about the bug.
    This  org.freedesktop.DBus causes errors in Emacs too. Its not fatal, but seems to be buggy somehow.
    [tj@arch ~]$ LC_ALL=C sudo pacman -Qi chromium
    Name : chromium
    Version : 17.0.963.56-1
    URL : http://www.chromium.org/
    Licenses : BSD
    Groups : None
    Provides : chromium-browser
    Depends On : gtk2 dbus-glib nss alsa-lib xdg-utils bzip2 libevent libxss libgcrypt ttf-dejavu desktop-file-utils
    hicolor-icon-theme
    Optional Deps : kdebase-kdialog: needed for file dialogs in KDE
    Required By : None
    Conflicts With : chromium-browser
    Replaces : None
    Installed Size : 96376.00 KiB
    Packager : Evangelos Foutras <[email protected]>
    Architecture : x86_64
    Build Date : Thu Feb 16 03:16:03 2012
    Install Date : Thu Feb 16 14:41:57 2012
    Install Reason : Explicitly installed
    Install Script : Yes
    Description : The open-source project behind Google Chrome, an attempt at creating a safer, faster, and more stable browser

  • GNOME: DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound

    I've been having this issue for a couple weeks now. All of my partitions in nautilus show on the side bar. But if I click to mount any of them, it does nothing. If I killed gvfs-hal-volume-monitor and start it from a console and click to mount one, this is the error I get:
    DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound: The given volume was not found
    hal and dbus are running. Any suggestions?

    Solved. I created the file
    /etc/polkit-1/localauthority/50-local.d/org.freedesktop.udisks.pkla
    Here is my file:
    [Local Users]
    Identity=unix-user:johnny
    Identity=unix-group:storage
    Action=org.freedesktop.udisks.*
    ResultAny=yes
    ResultInactive=no
    ResultActive=yes
    No more problems with thunar (there was an option to add in the "Action" section to allow the automounting of the internal drives, but i don't remember. I don't need it).
    EDIT: I think that you can also do:
    [Local Users]
    Identity=unix-user:*
    Identity=unix-group:storage
    Action=org.freedesktop.udisks.*
    ResultAny=yes
    ResultInactive=no
    ResultActive=yes
    If you want allow to a generic user this option.
    Last edited by reddhawk (2012-10-31 06:59:38)

  • [Solved] Systemd user service and timer dbus error

    I have installed arch recently and added a few of my own services, for example the acpi_call commands and such. Now I want to create a systemd service that runs every 5 minutes and execute a script.
    I searched a lot and I found that I must use timers. I got the thing with the timers working, but because my script has to do with a specific user, I want it to run only every 5 minutes when i am logged in as that user.
    I tried to put the files in /etc/systemd/users, .config/local/users and all the possibilities but everytime i want to enable it, it says dbus connection refused.
    Can somebody please provide me a way to execute a systemd service every 5 minutes while I am logged in as a specific user?
    I did follow the wiki and created a dbus service and all. Everything works on that side but i can't enable my user service.
    thanks!
    Last edited by nopemopes (2015-03-25 11:10:06)

    jasonwryan wrote:
    What errors are you getting? https://bbs.archlinux.org/viewtopic.php?id=57855
    Not a Sysadmin issue, moving to NC...
    sorry, didn't mean to be incomplete.
    The error says "Failed to get D-Bus connection: Connection refused".
    I did what the wiki said: Create the dbus files, enable them and such.
    No i put my service files + timer in the places mentioned by the wiki but everytime i try to enable them, that error shows up.
    systemctl status dbus gives me all good
    dbus.service - D-Bus System Message Bus
    Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
    Active: active (running) since ma 2015-03-23 19:39:24 CET; 1h 18min ago
    Docs: man:dbus-daemon(1)
    Main PID: 246 (dbus-daemon)
    CGroup: /system.slice/dbus.service
    └─246 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
    mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
    mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
    mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
    mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    that's the log for dbus and these are my files:
    drive_sync.service
    [Unit]
    Description=Drive sync
    [Service]
    Type=simple
    ExecStart=drive_script.sh
    drive_sync.timer
    [Unit]
    Description=Drive sync
    [Service]
    Type=simple
    ExecStart=drive_script.sh
    these files are located in ~/.config/systemd/user
    Last edited by nopemopes (2015-03-23 20:00:55)

  • KDE does no longer start - DBUS error - Awesome WM related problem

    Hi,
    so I somehow managed to screw my KDE. I can no longer log in as my standard user, when I enter my username & password into the login-manager, the start process ends with a Window showing 'Could not start D-Bus. Can you call qdbus?'. When I press ok, I land back in the log-in screen.
    The following is the content of ~/.xsession-errors:
    /usr/bin/startkde: line 22: /usr/share/config/kdm/kde4-config: No such file or directory
    Agent pid 2157
    startkde: Starting up...
    startkde: Could not start D-Bus. Can you call qdbus?
    and at the end of the /var/log/kdm.log:
    klauncher(2188) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(2182)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(2182)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Strange thing is, Dbus is running, so that should not be the problem.
    So, I have asked around in the IRC channel, and was advised to move my .kde4 config, so that kde would create a new one. That did unfortunately nothing, the same problem persists. So then I created a new user for testing and voila, KDE starts under this user with the generated configs (even with the configs from the old user, though he wants to start everything as the old one and that causes problems).
    Now my question is, what could be causing the problems? Dbus is surely running, as I can log in as the new testing-user, it also shows up in the process list, when I am logged in. Unfortunately it does not start up when I try to log in as the old user, and hence I can't start KDE. I was told, I could just delete the old user and create a new one to solve this issue, but I would like to avoid that.
    Thanks in advance for any advice.
    EDIT: Apparently the problem is related to awesome, after installing awesome, KDE seems to break after awesome is installed for every present user on the system. See also post #4.
    Last edited by Defolos (2013-05-23 07:48:09)

    berbae wrote:
    Defolos wrote:So I just though about what happened before KDE died, and I remembered that I installed awesome, logged in, logged out and after that KDE was broken.
    What happens if you reboot after uninstalling awesome, instead of just log out/log in? Does kde work again then?
    Nope, did that immediately after KDE broke. Rebooted actually several times without awesome installed and it didn't help.
    berbae wrote:You didn't say how you launched awesome: from kdm or from console or other way?
    It is started from kdm.
    berbae wrote:Say also if you have the systemd kdm.service enabled.
    Cant tell you that right now, don't have the machine at work. Will check that later.
    berbae wrote:
    Look what processes are running (especially the dbus-daemon and xorg related processes):
    before any WM/DE is launched,
    when awesome is launched and running,
    when you log out from awesome,
    when you log in again, trying to launch kde
    Use tty2 to check for the processes, when you don't have a command prompt (ctrl-alt-F2).
    Only by searching you could find a clue for the possible cause of the problem; it will be the learning way.
    As far as I remember it, dbus-daemon is launched when the system boots up. When I log in as a new user (hence with working KDE) it automatically starts another dbus process for kde as the new user. If i try that as the old (broken KDE) user, no dbus is started (and hence the problem).
    berbae wrote:...Or take the easy way: just use a new user and don't install awesome again if you don't want to use it!
    That was already suggested by some people in irc. I would like to avoid that because of two reasons:
    first, I find this very unclean and ugly, I would like to fix the problem at its root
    and second, I am afraid, that I might break the permissions in my whole home directory and nothing works anymore.
    What I am currently suspecting is that when I install awesome (and probably also log in) it runs some script that configures dbus per-user and that breaks compatibility with KDE. Could you imagine something like that?

  • Netcfg dbus error

    Upon trying to use netcfg with my profile, it gives me an error.
    File "/usr/lib/network//connections//wireless-dbus", line 3, in <module>
        import dbus
    ImportError: No module named dbus
    Help, please.

    I already have them installed, would it be my python version number?
    I have the current 2.6.4.

Maybe you are looking for

  • Error while creating customers on sales pages

    Hi Everyone, When trying the process below: Resp: Sales Online Super user Sales Online Customer tab--> Click on Create Button. Enter mandatory fields and click on Create. You will get the below error: java.sql.SQLException: ORA-06502: PL/SQL: numeric

  • Using RFC in VC model

    Hi Experts, I am doing a VC application. In this I am using Combo box in input form. I am populating this combo box with one RFC from R/3 system. I am able to see data on Development system. I have transported my VC Model and RFC to quality system bu

  • Can we Select Open Item Management for Recon Accounts??

    Hi Members, Is it necessary to select check box open item management for reconciliation accounts ??? for ex; sundry debtors, sundry creditors . If so may i know the reason. Bcz all subledger accounts are automatically maintained as open item accounts

  • (SOLVED)recent update .pacnew files what to do?

    Maybe I'm having a duh! moment but today #pacman -Syu gave me /etc/makepkg.conf and /etc/makepkg.conf.pacnew that are identical.; and /etc/pacman.conf(my edited one) and /etc/pacman.conf.pacnew(like new install file). Can I just delete the .pacnew fi

  • How to Set NLS parameters in SqlDeveloper for current and future connection

    Hi I've downloaded sqldeveloper version 1.5.4(build main-5940) when I try to set NLS parameters as following it is thrwoing following error TOOLS->PREFERENCES->DATABASE-->NLS parameters on right side pane I've changed SORT----->BINARY_CI COMP----->LI