View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002624Kali LinuxGeneral Bugpublic2015-09-07 07:102015-09-07 07:32
ReporterFulgur Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Product Version2.0 
Summary0002624: Gnome Doesn't start when create symlink: /var/tmp to /tmp
Description

Kali 2.0 installed from ISO on hard drive.
Trying to link /var/tmp to /tmp folder cause gnome failure to start GUI.

Steps To Reproduce
  • rm -fr /var/tmp
  • ln -s /tmp /var/tmp
  • reboot

SYSLOG:

...
Sep 7 08:41:58 localhost gnome-session[2532]: E: [pulseaudio] main.c: Daemon startup failed.
Sep 7 08:41:58 localhost systemd[3130]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Sep 7 08:41:58 localhost systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE
Sep 7 08:41:58 localhost systemd[1]: Failed to start RealtimeKit Scheduling Policy Service.
Sep 7 08:41:58 localhost systemd[1]: Unit rtkit-daemon.service entered failed state.
Sep 7 08:42:23 localhost dbus[929]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out
Sep 7 08:42:23 localhost dbus[929]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Sep 7 08:42:23 localhost systemd[3146]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Sep 7 08:42:23 localhost systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE
Sep 7 08:42:23 localhost systemd[1]: Failed to start RealtimeKit Scheduling Policy Service.
Sep 7 08:42:23 localhost systemd[1]: Unit rtkit-daemon.service entered failed state.
Sep 7 08:42:48 localhost dbus[929]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out
Sep 7 08:42:48 localhost dbus[929]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Sep 7 08:42:48 localhost systemd[3150]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Sep 7 08:42:48 localhost systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE
Sep 7 08:42:48 localhost systemd[1]: Failed to start RealtimeKit Scheduling Policy Service.
Sep 7 08:42:48 localhost systemd[1]: Unit rtkit-daemon.service entered failed state.
Sep 7 08:43:13 localhost dbus[929]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out
Sep 7 08:43:13 localhost dbus[929]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Sep 7 08:43:13 localhost systemd[3154]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Sep 7 08:43:13 localhost systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE
Sep 7 08:43:13 localhost systemd[1]: Failed to start RealtimeKit Scheduling Policy Service.
Sep 7 08:43:13 localhost systemd[1]: Unit rtkit-daemon.service entered failed state.
...

Additional Information

To solve the problem you have to recreate /var/tmp folder.
When the system is rebooted you have to reinsert application & places button on panel bar with Tweak Tool.

Activities

rhertzog

rhertzog

2015-09-07 07:32

administrator   ~0003958

It's your fault if you break your system that way. /var/tmp and /tmp do not have the same use case and should not be symlinked. It's not a bug and particularly not a Kali one.

Issue History

Date Modified Username Field Change
2015-09-07 07:10 Fulgur New Issue
2015-09-07 07:32 rhertzog Note Added: 0003958
2015-09-07 07:32 rhertzog Status new => closed
2015-09-07 07:32 rhertzog Assigned To => rhertzog
2015-09-07 07:32 rhertzog Resolution open => won't fix