I have been lurking around for a couple of years, and wanted to attend a
meeting, but in a long series of unfortunate timings, I was never able
to attend. This past year, I moved out of the area, so it would be even
more difficult to attend now.

I am far from an expert myself, but I think I can contribute a bit here.
In the past when I have had an issue with the display, it has been
either the gnome settings or xorg settings. Without knowing what exactly
is causing your issue (could be settings or a bug), I would look at
reseting the defaults, and making changes from there. If this sounds too
daunting of a task, maybe others will have some better advice.

Taken from:
http://library.gnome.org/admin/system-admin-guide/stable/sessions-3.html.en

--------------------------------------------------------------
The following table lists the files that contain default session
information:
File    Description
/usr/share/gnome/default.session        Default session file. Default session
details are stored in this file.
$HOME/.gnome2/session   User session file. When a user modifies the
session, the details are stored in this file.

To set default session details for all users, modify the default session
file.

To restore the default session settings for a user, delete the session
file from the home directory of the user. If no user session file is
present, the default settings in /usr/share/gnome/default.session are
used.

To save the current session as the default session, users can run the
gnome-session-save command. 
--------------------------------------------------------------

Your mileage may vary depending on what gnome version you have
installed, so you may have to search the Internet depending on your
specific version.

This should help reset the default session, however personally, I would
copy the files to another location prior to deletion in case this is not
the issue, and you want to restore them.

You could backup the file via command line with something like this:

cp /usr/share/gnome/default.session 
/home/Sharkdance/Backup/usr/share/gnome/default.session


If you reset the defaults, and it resolves your issue, then great. If
not you may want to set a basic xorg.conf file in place in case it is an
issue related to those settings.

Someone kindly posted a how to for installing Debian on a Toshiba
Satellite L305

http://personal.bgsu.edu/~inathan/Toshiba_Satellite_L305/

The person also posted a basic xorg.conf file located at:

http://personal.bgsu.edu/~inathan/Toshiba_Satellite_L305/xorg.conf

>From the command line you should be able to save the file on that laptop
provided you have Internet access with:

wget http://personal.bgsu.edu/~inathan/Toshiba_Satellite_L305/xorg.conf

now backup your current xorg.conf file:

cp /etc/X11/xorg.conf /etc/X11/xorg.bkp

now copy the xorg.conf file you downloaded:

cp xorg.conf /etc/X11/xorg.conf

reboot.

If that resolved your issue, then great. If not you may want to lean on
the advice the experts from this LUG may provide you with, or do some
more research for your specific issue. 

Further reading:

http://wiki.debian.org/Xorg
http://www.debian.org/Bugs/

I hope this helps, good luck.



On Sat, 2012-02-18 at 06:19 -0500, W. David Coleman wrote:
> Greetings all.
> Been a member of Jaxlug for years. Been to several meetings although 
> none of them recently. And rarely post on the mailing list although I do 
> always read it.
> 
> Anyway, been using Linux at home for years (mostly Debian) and even set 
> the wife up on Debian as well. (She loves it)
> Were not all technical and Linux savvy as most are on this list so I 
> will do my best to describe the issue and accept advice accordingly.
> We use Linux mostly for E mail, web browsing, and music/video 
> entertainment in a graphical environment. (Gnome)
> I am familiar with some of the most basic command line functions but far 
> from advanced.
> 
> I have recently acquired a Toshiba laptop that came with Windows Vista 
> (ugg) and dual booted it with Debian 6.03
> Laptop Specs: Toshiba Satellite L305
> 2GHz Pentium dual core
> 3 Gigs RAM
> 64 bit OS both Windows and Linux (Graphical Gnome standard desktop with 
> no special servers running)
> 
> Outline of Issue: After successfully installing Debian 6.03 (squeeze?) 
> and using it for several days with zero issues I began customizing the 
> graphical desktop and playing around with multiple Gnome panels to suit 
> my browsing and media habits.
> One panel on the bottom and another panel set to automatically hide when 
> not in use.
> All was fine until I began changing the physical size of the second 
> panel. I chose minimum size for that panel and adjusted the width to 
> about half.
> I had no issues with these adjustments until I later rebooted. When I 
> did reboot I could log in just fine but the graphical environment would 
> hang up while trying to load the Gnome panel. The background would load 
> but the Gnome panel would only load to a plain white bar with no icons 
> and stop there with the curser showing the little waiting clock.  No 
> interaction with the desktop what so ever beyond that. Not even 
> Ctrl+Alt+Back Space or Ctrl+Alt+Del
> It just hangs there forever.
> 
> When I reboot I am at least able to log into a rescue shell as root but 
> dont know what file to edit to try and fix the graphical problem in my 
> normal user log on profile.
> 
> Im sure this is an easy fix for most of you. Trying to explain it to a 
> semi-noob like me might be more of a challenge lol.
> 
> I thank you in advance for any help resolving my issue and helping me 
> get back to enjoying Debian on my laptop.
> 
> David
> A.K.A. Sharkdance
> 
> 
> ---------------------------------------------------------------------
> Archive      http://marc.info/?l=jaxlug-list&r=1&w=2
> RSS Feed     http://www.mail-archive.com/[email protected]/maillist.xml
> Unsubscribe  [email protected]
> 



---------------------------------------------------------------------
Archive      http://marc.info/?l=jaxlug-list&r=1&w=2
RSS Feed     http://www.mail-archive.com/[email protected]/maillist.xml
Unsubscribe  [email protected]

Reply via email to