I recently upgraded to Ubuntu 13.10 Alpha 1. In addition, I am only able to get a proper working environment in GNOME Flashback ( No effects ) session . I all the others ( Unity aka Ubuntu , GNOME Classic , GNOME Flashback ) desktop environments I am unable to work as I don't find/access anything ( no panels ) other than the files/folders that are present in my desktop folder. In Unity session I am even unable to type anything in the terminal ( I use the shortcut ctrl+Alt+t for it ). Please help.
Output of command " lspci | grep -i graphic " is as follows :-
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-panel 1:3.6.2-0ubuntu11
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Sat Jul 6 13:23:19 2013
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges:
InstallationDate: Installed on 2013-03-15 (113 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: gnome-panel
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_IN
SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-panel
StacktraceTop:
raise () from /lib/i386-linux-gnu/libc.so.6
abort () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-panel crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to saucy on 2013-07-03 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1193651, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.