staging.inyokaproject.org

Unity läd nach Update nicht mehr

Status: Ungelöst | Ubuntu-Version: Ubuntu 14.04 (Trusty Tahr)
Antworten |

Jam00

Anmeldungsdatum:
22. Oktober 2010

Beiträge: 83

Hallo Community,

ich habe ein Problem mit Unity. Nachdem ich durch den Updater mein Ubuntu auf den neusten Stand habe bringen lassen läd leider keine Oberfläche mehr nachdem ich mich eingeloggt habe. Ich sehe einfach nur das Standard-Hintergrundbild ☹

Leider kenne ich mich mit LigthDM/Unity nicht ausreichend aus um das Problem lösen zu können.

Daher wollte ich Frage ob mit von euch einer helfen kann. Hierzu lade ich euch meine LightDM-Logs hoch - ich hoffe, dass sind die, die wichtig sind.

lightdm.log

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=4244
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Registered seat module surfaceflinger
[+0.01s] DEBUG: Adding default seat
[+0.01s] DEBUG: Seat: Starting
[+0.01s] DEBUG: Seat: Creating greeter session
[+0.01s] DEBUG: Seat: Creating display server of type x
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.02s] DEBUG: Launching process 4250: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.12s] DEBUG: User /org/freedesktop/Accounts/User1000 changed
[+1.34s] DEBUG: Got signal 10 from process 4250
[+1.34s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1.34s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+1.35s] DEBUG: Seat: Display server ready, starting session authentication
[+1.35s] DEBUG: Session pid=4270: Started with service 'lightdm-greeter', username 'lightdm'
[+1.40s] DEBUG: Session pid=4270: Authentication complete with return value 0: Success
[+1.40s] DEBUG: Seat: Session authenticated, running command
[+1.40s] DEBUG: Session pid=4270: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+1.40s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.40s] DEBUG: Session pid=4270: Logging to /var/log/lightdm/x-0-greeter.log
[+1.42s] DEBUG: Activating VT 7
[+1.42s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c8
[+1.64s] DEBUG: Session pid=4270: Greeter connected version=1.10.1
[+1.82s] DEBUG: Session pid=4270: Greeter start authentication for anyone
[+1.83s] DEBUG: Session pid=4327: Started with service 'lightdm', username 'anyone'
[+1.84s] DEBUG: Session pid=4327: Got 1 message(s) from PAM
[+1.84s] DEBUG: Session pid=4270: Prompt greeter with 1 message(s)
[+2.34s] DEBUG: Session pid=4270: Cancel authentication
[+2.34s] DEBUG: Session pid=4327: Sending SIGTERM
[+2.35s] DEBUG: Session pid=4327: Terminated with signal 15
[+2.35s] DEBUG: Session: Failed during authentication
[+2.35s] DEBUG: Seat: Session stopped
[+2.43s] DEBUG: Session pid=4270: Greeter start authentication for anyone
[+2.43s] DEBUG: Session pid=4468: Started with service 'lightdm', username 'anyone'
[+2.45s] DEBUG: Session pid=4468: Got 1 message(s) from PAM
[+2.45s] DEBUG: Session pid=4270: Prompt greeter with 1 message(s)
[+33.80s] DEBUG: Session pid=4270: Continue authentication
[+35.73s] DEBUG: Session pid=4468: Authentication complete with return value 7: Authentication failure
[+35.73s] DEBUG: Session pid=4270: Authenticate result for user anyone: Authentication failure
[+35.73s] DEBUG: Session pid=4468: Exited with return value 1
[+35.73s] DEBUG: Seat: Session stopped
[+35.94s] DEBUG: Session pid=4270: Greeter start authentication for anyone
[+35.94s] DEBUG: Session pid=4513: Started with service 'lightdm', username 'anyone'
[+35.95s] DEBUG: Session pid=4513: Got 1 message(s) from PAM
[+35.95s] DEBUG: Session pid=4270: Prompt greeter with 1 message(s)
[+325.74s] DEBUG: Got signal 15 from process 1
[+325.74s] DEBUG: Caught Terminated signal, shutting down
[+325.74s] DEBUG: Stopping display manager
[+325.74s] DEBUG: Seat: Stopping
[+325.74s] DEBUG: Seat: Stopping display server
[+325.74s] DEBUG: Sending signal 15 to process 4250
[+325.74s] DEBUG: Seat: Stopping session
[+325.74s] DEBUG: Session pid=4270: Sending SIGTERM
[+325.74s] DEBUG: Seat: Stopping session
[+325.74s] DEBUG: Session pid=4513: Sending SIGTERM
[+325.74s] DEBUG: Session pid=4513: Terminated with signal 15
[+325.74s] DEBUG: Session: Failed during authentication
[+325.74s] DEBUG: Seat: Session stopped
[+325.76s] DEBUG: Session pid=4270: Exited with return value 0
[+325.76s] DEBUG: Seat: Session stopped
[+326.02s] DEBUG: Process 4250 terminated with signal 6
[+326.02s] DEBUG: DisplayServer x-0: X server stopped
[+326.02s] DEBUG: Releasing VT 7
[+326.02s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+326.02s] DEBUG: Seat: Display server stopped
[+326.02s] DEBUG: Seat: Stopped
[+326.02s] DEBUG: Display manager stopped
[+326.02s] DEBUG: Stopping daemon
[+326.02s] DEBUG: Exiting with return value 0

x-0.log

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu
Current Operating System: Linux UNKOWN 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=712f71d4-7f59-48e5-b9ae-3cf4c2a16b7e ro quiet splash
Build Date: 16 April 2014  01:36:29PM
xorg-server 2:1.15.1-0ubuntu2 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.30.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: Sat May 31 11:12:14 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
modprobe: FATAL: Module fglrx not found.
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
modprobe: FATAL: Module fglrx not found.
Loading extension FGLRXEXTENSION
Loading extension GLESX
[glesx] __glESXExtensionInit: No GL ES2.0 capable screen found!
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f2270006c78]
(EE) 1: /usr/bin/X (0x7f226fe5e000+0x1ac969) [0x7f227000a969]
(EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f226ef5b000+0x10340) [0x7f226ef6b340]
(EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (0x7f226f179000+0x4cce) [0x7f226f17dcce]
(EE) 4: /usr/lib/xorg/modules/drivers/fglrx_drv.so (amd_xs113_int10_x_inb+0x46) [0x7f226b3cc4a6]
(EE) 5: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f226aa31000+0x994185) [0x7f226b3c5185]
(EE) 6: /usr/lib/xorg/modules/drivers/fglrx_drv.so (X86EMU_exec+0xa5) [0x7f226b3b88d5]
(EE) 7: /usr/lib/xorg/modules/drivers/fglrx_drv.so (amd_xs113_int10_xf86ExecX86int10+0x46) [0x7f226b3cd606]
(EE) 8: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xf86ExecX86int10+0xd) [0x7f226ae1697d]
(EE) 9: /usr/lib/xorg/modules/libvbe.so (VBESetVBEMode+0x9d) [0x7f226a3d63ad]
(EE) 10: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f226aa31000+0x41a5e3) [0x7f226ae4b5e3]
(EE) 11: /usr/lib/xorg/modules/drivers/fglrx_drv.so (atiddxVBESetConsoleMode+0x44) [0x7f226ae4b434]
(EE) 12: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxFreeScreen+0x73e) [0x7f226afe445e]
(EE) 13: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxCloseScreen+0x321) [0x7f226afe3a81]
(EE) 14: /usr/lib/xorg/modules/drivers/fglrx_drv.so (0x7f226aa31000+0xa0b0c6) [0x7f226b43c0c6]
(EE) 15: /usr/bin/X (0x7f226fe5e000+0xe4446) [0x7f226ff42446]
(EE) 16: /usr/bin/X (0x7f226fe5e000+0x12bf24) [0x7f226ff89f24]
(EE) 17: /usr/bin/X (0x7f226fe5e000+0x12d773) [0x7f226ff8b773]
(EE) 18: /usr/bin/X (0x7f226fe5e000+0x59a57) [0x7f226feb7a57]
(EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f226d99aec5]
(EE) 20: /usr/bin/X (0x7f226fe5e000+0x44e7e) [0x7f226fea2e7e]
(EE) 
(EE) Segmentation fault at address 0x0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.

x-0-greeter.log

Activating service name='org.a11y.atspi.Registry'
Successfully activated service 'org.a11y.atspi.Registry'
[+0,00s] DEBUG: unity-greeter.vala:496: Starting unity-greeter 14.04.10 UID=112 LANG=en_US.UTF-8
[+0,00s] DEBUG: unity-greeter.vala:499: Setting cursor
[+0,00s] DEBUG: unity-greeter.vala:513: Loading command line options
[+0,00s] DEBUG: unity-greeter.vala:541: Setting GTK+ settings

** (at-spi2-registryd:4301): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (at-spi2-registryd:4301): WARNING **: Unable to register client with session manager
[+0,09s] DEBUG: unity-greeter.vala:564: Creating Unity Greeter
[+0,09s] DEBUG: unity-greeter.vala:57: Creating background surface
[+0,10s] DEBUG: Connecting to display manager...
[+0,10s] DEBUG: Wrote 18 bytes to daemon
[+0,10s] DEBUG: Read 8 bytes from daemon
[+0,10s] DEBUG: Read 150 bytes from daemon
[+0,10s] DEBUG: Connected version=1.10.1 default-session=ubuntu show-manual-login=false hide-users=false has-guest-account=true show-remote-login=true
[+0,15s] DEBUG: menubar.vala:335: LANG=en_US.UTF-8 LANGUAGE=(null)
[+0,16s] DEBUG: menubar.vala:367: LANG=en_US.UTF-8 LANGUAGE=(null)
[+0,17s] DEBUG: Loading users from org.freedesktop.Accounts
[+0,17s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0,20s] DEBUG: user-list.vala:1030: Adding/updating user anyone (anyone)
[+0,20s] DEBUG: Loading sessions from org.freedesktop.DisplayManager
[+0,20s] DEBUG: user-list.vala:1012: Adding guest account entry
[+0,28s] DEBUG: Loaded session /usr/share/xsessions/ubuntu.desktop (Ubuntu, This session logs you into Ubuntu)
[+0,28s] DEBUG: Starting authentication for user anyone...
[+0,28s] DEBUG: Wrote 22 bytes to daemon
[+0,28s] DEBUG: main-window.vala:185: Screen is 1366x768 pixels
[+0,28s] DEBUG: main-window.vala:193: Monitor 0 is 1366x768 pixels at 0,0
[+0,28s] DEBUG: unity-greeter.vala:567: Showing greeter
[+0,28s] DEBUG: unity-greeter.vala:252: Showing main window
[+0,29s] DEBUG: background.vala:483: Regenerating backgrounds
[+0,29s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/warty-final-ubuntu.png at 1366x768
[+0,32s] DEBUG: unity-greeter.vala:610: Starting main loop
[+0,32s] DEBUG: Read 8 bytes from daemon
[+0,32s] DEBUG: Read 36 bytes from daemon
[+0,32s] DEBUG: Prompt user with 1 message(s)
[+0,34s] DEBUG: settings-daemon.vala:75: Acquired org.gnome.SessionManager
[+0,34s] DEBUG: settings-daemon.vala:102: Acquired org.gnome.ScreenSaver
[+0,34s] DEBUG: settings-daemon.vala:159: All bus names acquired, starting unity-settings-daemon
[+0,48s] DEBUG: menubar.vala:537: Adding indicator object 0x1f35710 at position 0
[+0,49s] DEBUG: menubar.vala:537: Adding indicator object 0x1f359d0 at position 1
[+0,49s] DEBUG: Connected to Application Indicator Service.
[+0,51s] DEBUG: unity-greeter.vala:235: starting system-ready sound
[+0,62s] DEBUG: Request current apps
[+0,63s] DEBUG: background.vala:121: Render of background /usr/share/backgrounds/warty-final-ubuntu.png complete
[+0,64s] DEBUG: menubar.vala:537: Adding indicator object 0x1f35f50 at position 2
[+0,68s] DEBUG: menubar.vala:537: Adding indicator object 0x1f35450 at position 3

** (unity-settings-daemon:4351): WARNING **: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'RegisterClient'
[+0,80s] DEBUG: Wrote 8 bytes to daemon

(unity-settings-daemon:4351): color-plugin-WARNING **: failed to get edid: unable to get EDID for output

(unity-settings-daemon:4351): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS: unable to get EDID for output
[+0,88s] DEBUG: Starting authentication for user anyone...
[+0,88s] DEBUG: Wrote 22 bytes to daemon
[+0,88s] DEBUG: Building new application entry: :1.24  with icon: nm-no-connection at position 0
[+0,88s] DEBUG: menubar.vala:537: Adding indicator object 0x2034170 at position 4

** (nm-applet:4333): CRITICAL **: nm_secret_agent_register: assertion 'priv->registered == FALSE' failed
[+0,92s] DEBUG: Read 8 bytes from daemon
[+0,92s] DEBUG: Read 36 bytes from daemon
[+0,92s] DEBUG: Prompt user with 1 message(s)
[+0,93s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+0,93s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+0,93s] DEBUG: menubar.vala:537: Adding indicator object 0x1f35c90 at position 3
[+16,74s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+16,74s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+32,25s] DEBUG: Providing response to display manager
[+32,25s] DEBUG: Wrote 20 bytes to daemon
[+34,39s] DEBUG: Read 8 bytes from daemon
[+34,39s] DEBUG: Read 18 bytes from daemon
[+34,39s] DEBUG: Authentication complete for user anyone with return code 7
[+34,39s] DEBUG: Starting authentication for user anyone...
[+34,39s] DEBUG: Wrote 22 bytes to daemon
[+34,41s] DEBUG: Read 8 bytes from daemon
[+34,41s] DEBUG: Read 36 bytes from daemon
[+34,41s] DEBUG: Prompt user with 1 message(s)
[+76,56s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+76,56s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+136,59s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+136,59s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+196,57s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+196,57s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+256,55s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+256,55s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[+316,59s] CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
[+316,60s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
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.

(unity-settings-daemon:4351): Gdk-WARNING **: unity-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(nm-applet:4333): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

[+324,20s] WARNING: unity-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

init: indicator-messages main process ended, respawning
init: indicator-bluetooth main process (4338) killed by TERM signal
init: indicator-bluetooth main process ended, respawning
init: indicator-power main process (4341) killed by TERM signal
init: indicator-power main process ended, respawning
init: indicator-datetime main process (4348) killed by TERM signal
init: indicator-datetime main process ended, respawning
init: indicator-sound main process ended, respawning
init: indicator-session main process (4360) killed by TERM signal
init: indicator-session main process ended, respawning
init: indicator-application main process (4378) terminated with status 1
init: indicator-application main process ended, respawning
init: indicator-messages main process ended, respawning
init: indicator-application main process ended, respawning
init: indicator-datetime main process ended, respawning
init: indicator-session main process ended, respawning
init: indicator-messages respawning too fast, stopped
init: indicator-application respawning too fast, stopped
init: indicator-power main process ended, respawning
init: indicator-datetime respawning too fast, stopped
init: indicator-session respawning too fast, stopped
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power main process ended, respawning
init: indicator-power respawning too fast, stopped

Vllt noch wichtig: Ich habe eine ATI Mobility Readon 5650, für welche ich die Treiber von ATI installiert habe.

Vielen Dank im Voraus

Juergen.K

Anmeldungsdatum:
29. Dezember 2009

Beiträge: 14

Hallo allerseits,

gleiches Problem bei mir. Gestern wurden viele "Grafikpakete" (opengl, mesa, dri usw.) upgedated. Compiz schmiert ab, da er Unity nicht starten kann. Im übrigen betrifft dies bei mir eine Kombination aus Intel/NVidia Grafikkarte. Zum Test habe ich einmal den probitären NVidia Treiber durch den nouveau ersetzt und neu gestartet. Dies brachte mich der Lösung des Problems jedoch keinen Schritt weiter. Soweit ich mich erinnern kann, fand u. a. compiz einen Einspringpunkt in der libi965... nicht. Ich muss da allerdings noch mal genau nachsehen, wenn ich mehr Zeit habe.

Gruß Jürgen

P.S. Ich weis, mein Beitrag löst Dein Problem nicht, aber Du bist zumindest nicht allein mit einem zerschossenen System 😉

Juergen.K

Anmeldungsdatum:
29. Dezember 2009

Beiträge: 14

Hi,

so den Fehler bei mir hatte ich heute Nacht noch gefunden. Ansich benutze ich seit Jahren das xorg-edgers ppa und war ansich damit immer gut gefahren. Die Updates vom 31.05.2014 waren jedoch der "letzte Müll". Einsprungpunkte in Libs wurden nicht mehr gefunden usw. Ich habe mich daher entschlossen, in Zukunft auf das ppa zu verzichten.

Zwei beherzte Aufrufe: sudo apt-get install ppa-purge und sudo ppa-purge xorg-edgers brachten dann den gewünschten Fortschritt. Alles von xorg-edgers wurde gelöscht und durch die Originalversionen von Trusty ersetzt. Nach einem Reboot fährt auch die GUI inkl. Unity wieder hoch. Wie war das nochmal? Fremdquellen können das System gefährden 👿

Gruß Jürgen

Lidux

Anmeldungsdatum:
18. April 2007

Beiträge: 16801

Hallo Jam00, Juergen.K,

Ihr müsst nur über ccsm das unity-plugin aktivieren .....

Gruss Lidux

Juergen.K

Anmeldungsdatum:
29. Dezember 2009

Beiträge: 14

Hallo Lidux,

mein System läuft ja wieder. Davon ab ist der compiz und unity Prozeß gnadenlos abgeschmiert, da fehlte u. a. ein Einsprungpunkt in einer libi965... Da war leider nichts mit einfach das Unity Plugin in ccsm aktivieren... Aber trotzdem danke.

Gruß Jürgen

John_Abruzzi

Anmeldungsdatum:
19. Mai 2014

Beiträge: 14

Hallo zusammen;

auch ich habe das selbe Problem! Gestern habe ich ein Update gemacht und nach dem Neustart/Login komme ich auf einen leeren Desktop. Ich sehe zwar den Hintergrund, jedoch keine Leiste oder Unity 😬

Hat jemand eine Idee?

Kann es an dem Grafiktreiber liegen? Verwende Intel HD4000 diese sollen ja funktionieren.

John

Jam00

(Themenstarter)

Anmeldungsdatum:
22. Oktober 2010

Beiträge: 83

Ich konnte das Problem bei mir inzwischen lösen. Ich habe meine Grafiktreiber deinstalliert, ubuntu-desktop & unity neu installiert, dpkg-reconfigure für beide aufgerufen und weiterhin Unity mit unity-tweak-tools reseted und dann meine Grafiktreiber wieder installiert.

lelle

Anmeldungsdatum:
19. Oktober 2007

Beiträge: 21

hallo!

hier genau das selbe problem. unity laedt nicht mehr seit, ich nehme mal an, einem update. kurioserweise funktioniert alles wenn ich mich ueber den gastzugang einlogge. auch neuinstallation (nicht ersetzen wegen der daten auf dem laptop) brachte keine besserung. leider gehen meine faehigkeiten bezueglich dessen ueber ein "nach anleitung aus dem internet vorgehen" nicht aus. was fuer ein mist! das problem scheint ja wirklich verbreitet zu sein :/

Lidux

Anmeldungsdatum:
18. April 2007

Beiträge: 16801

Hallo lelle,

Im Anmeldefester gibst du dein BN / PW ein. Rechtsklick auf dem Desktop und Terminal wählen. Dort ccsm eingeben und danach das "unity plugin" aktivieren. Rechner neu starten.

PS: Falls ccsm nicht installiert ist im Terminal mit:

sudo apt-get install ccsm

Gruss Lidux

Jam00

(Themenstarter)

Anmeldungsdatum:
22. Oktober 2010

Beiträge: 83

Achja das mit dem Plugin hatte ich vergessen, dass habe ich auch Probiert hat aber auch nicht direkt geholfen. Erst nach der Prozedur wie oben beschrieben

lelle

Anmeldungsdatum:
19. Oktober 2007

Beiträge: 21

Hallo!

Ich kann auf dem leeren desktoo leider kein terminal starten. Auch nicht mit strg alt t Wenn ich mich mit den f tasten ohne grafische oberflaeche anmelde und ccsm installieren moechte dann sagt er mir: e: paket ccsm kann nicht gefunden werden :/

Jam00

(Themenstarter)

Anmeldungsdatum:
22. Oktober 2010

Beiträge: 83

lelle

Anmeldungsdatum:
19. Oktober 2007

Beiträge: 21

Das hab ich schon durch. Bringt leider nichts :/

Bibi19

Anmeldungsdatum:
27. August 2012

Beiträge: 9

lelle schrieb:

Das hab ich schon durch. Bringt leider nichts :/

Ich hab genau das gleiche Problem, wie von Dir beschrieben und hänge mich hier mal mit ran. Ich hab inzwischen sogar alles (14.04) neu installiert (mit Formatieren des Laufwerks außer /home), weil ich sowieso 'aufräumen' wollte: Kein Erfolg. Alles bleibt nach Eingabe des Passworts beim Desktop hängen und dann geht nichts mehr. ☹

Jam00

(Themenstarter)

Anmeldungsdatum:
22. Oktober 2010

Beiträge: 83

Bei mir geht es nun auch schon wieder nichtmehr, nachdem ich erneut Updates eingespielt habe

unity --replace
stop: Unknown job: unity-panel-service
start: Unknown job: unity-panel-service
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
compiz (core) - Info: Loading plugin: ccp
compiz (core) - Info: Starting plugin: ccp
compizconfig - Info: Backend     : gsettings
compizconfig - Info: Integration : true
compizconfig - Info: Profile     : unity
compiz (core) - Info: Loading plugin: composite
compiz (core) - Info: Starting plugin: composite
compiz (core) - Info: Loading plugin: opengl
libGL error: failed to load driver: swrast
compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow).
compiz (core) - Info: Starting plugin: opengl
libGL error: failed to load driver: swrast
compiz (core) - Info: Loading plugin: compiztoolbox
compiz (core) - Info: Starting plugin: compiztoolbox
compiz (core) - Info: Loading plugin: decor
compiz (core) - Info: Starting plugin: decor
compiz (core) - Info: Loading plugin: vpswitch
compiz (core) - Info: Starting plugin: vpswitch
compiz (core) - Info: Loading plugin: snap
compiz (core) - Info: Starting plugin: snap
compiz (core) - Info: Loading plugin: mousepoll
compiz (core) - Info: Starting plugin: mousepoll
compiz (core) - Info: Loading plugin: resize
compiz (core) - Info: Starting plugin: resize
compiz (core) - Info: Loading plugin: place
compiz (core) - Info: Starting plugin: place
compiz (core) - Info: Loading plugin: move
compiz (core) - Info: Starting plugin: move
compiz (core) - Info: Loading plugin: wall
compiz (core) - Info: Starting plugin: wall
compiz (core) - Info: Loading plugin: grid
compiz (core) - Info: Starting plugin: grid
compiz (core) - Info: Loading plugin: regex
compiz (core) - Info: Starting plugin: regex
compiz (core) - Info: Loading plugin: imgpng
compiz (core) - Info: Starting plugin: imgpng
compiz (core) - Info: Loading plugin: session
compiz (core) - Info: Starting plugin: session
compiz (core) - Info: Loading plugin: gnomecompat
compiz (core) - Info: Starting plugin: gnomecompat
compiz (core) - Info: Loading plugin: animation
compiz (core) - Info: Starting plugin: animation
compiz (core) - Info: Loading plugin: fade
compiz (core) - Info: Starting plugin: fade
compiz (core) - Info: Loading plugin: unitymtgrabhandles
compiz (core) - Info: Starting plugin: unitymtgrabhandles
compiz (core) - Info: Loading plugin: workarounds
compiz (core) - Info: Starting plugin: workarounds
compiz (core) - Info: Loading plugin: scale
compiz (core) - Info: Starting plugin: scale
compiz (core) - Info: Loading plugin: expo
compiz (core) - Info: Starting plugin: expo
compiz (core) - Info: Loading plugin: ezoom
compiz (core) - Info: Starting plugin: ezoom
compiz (core) - Info: Loading plugin: unityshell
compiz (core) - Info: Starting plugin: unityshell
WARN  2014-06-07 16:29:15 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it...
ERROR 2014-06-07 16:29:15 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory
compiz (unityshell) - Error: GL_ARB_vertex_buffer_object not supported

ERROR 2014-06-07 16:29:15 unity.shell.compiz unityshell.cpp:3850 Impossible to delete the unity locked stamp file
compiz (core) - Error: Plugin initScreen failed: unityshell
compiz (core) - Error: Failed to start plugin: unityshell
compiz (core) - Info: Unloading plugin: unityshell
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0xa0000b
  Serial number of failed request:  9810
  Current serial number in output stream:  9818
Antworten |