Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

making KDE WM read my .xprofile

300 views
Skip to first unread message

Sivaram Neelakantan

unread,
Feb 17, 2015, 1:40:05 PM2/17/15
to

For some reason that I haven't figured out yet, my screen estate is
not used fully by Debian and I had some black bands around the edges
of the WM. Reading around, I found a combination of gtf and xrandr
with a rather painful way of discovering that my screen is 1366 x 652
in size.

xrandr --newmode "1360x652_60.00" 71.28 1360 1416 1560 1760 652 653 656 675 -HSync +Vsync
xrandr --addmode Virtual1 1360x652_60.00
xrandr -s 1360x652_60.00

I plug this into a .xprofile and chmod +x it and reboot, my screen
doesn't reset. if I manually execute .xprofile, the screen gets
changed to what I want. Where do I start looking to fix this such
that it gets set upon login into kdm? There is a .xsession-errors
file but that didn't seem to have anything interesting.

I used a live cd KDE install that is now upgraded to Jessie and so I
boot into KDE desktop upon login.

Appreciate some pointers to debug this.

sivaram
--


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87d258m...@gmail.com

Brian

unread,
Feb 17, 2015, 2:20:06 PM2/17/15
to
On Wed 18 Feb 2015 at 00:05:16 +0530, Sivaram Neelakantan wrote:

>
> For some reason that I haven't figured out yet, my screen estate is
> not used fully by Debian and I had some black bands around the edges
> of the WM. Reading around, I found a combination of gtf and xrandr
> with a rather painful way of discovering that my screen is 1366 x 652
> in size.
>
> xrandr --newmode "1360x652_60.00" 71.28 1360 1416 1560 1760 652 653 656 675 -HSync +Vsync
> xrandr --addmode Virtual1 1360x652_60.00
> xrandr -s 1360x652_60.00
>
> I plug this into a .xprofile and chmod +x it and reboot, my screen
> doesn't reset. if I manually execute .xprofile, the screen gets
> changed to what I want. Where do I start looking to fix this such
> that it gets set upon login into kdm? There is a .xsession-errors
> file but that didn't seem to have anything interesting.
>
> I used a live cd KDE install that is now upgraded to Jessie and so I
> boot into KDE desktop upon login.
>
> Appreciate some pointers to debug this.

What leads you to believe a .xprofile has any significance on Debian?


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/1702201519034...@desktop.copernicus.demon.co.uk

Sivaram Neelakantan

unread,
Feb 17, 2015, 9:30:05 PM2/17/15
to
On Tue, Feb 17 2015,Brian wrote:

> On Wed 18 Feb 2015 at 00:05:16 +0530, Sivaram Neelakantan wrote:

[snipped 22 lines]

>
> What leads you to believe a .xprofile has any significance on Debian?
>

ouch! You mean, I can't trust some random page on google? ;)

Well, that's what I did; the first part of finding out the screen real
estate and setting the output worked, so I thought the rest of the
bits would also be true; where to make the changes permanent.


sivaram
--


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/878ufwl...@gmail.com

Curt

unread,
Feb 18, 2015, 3:40:05 AM2/18/15
to
On 2015-02-18, Sivaram Neelakantan <nsivar...@gmail.com> wrote:
>
> ouch! You mean, I can't trust some random page on google? ;)
>
> Well, that's what I did; the first part of finding out the screen real
> estate and setting the output worked, so I thought the rest of the
> bits would also be true; where to make the changes permanent.
>

Have you considered creating an xorg.conf file and putting your
modelines in the Monitor section? (My searches are leading me
to believe that this is one method of achieving your goal).

https://wiki.debian.org/XStrikeForce/HowToRandR12

Or is this off base or just avoiding the fundamental question of what file is
sourced by what when and not overriden by another file subsequently (or
something), which must be learned before xorg.conf is eventually
obsoleted out of existence.

It's great to be modular but it can get complicated.


--

"The world is full of shipping clerks who have read the Harvard Classics."

— Charles Bukowski


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/slrnme8jco...@einstein.electron.org

Brian

unread,
Feb 18, 2015, 5:00:03 AM2/18/15
to
On Wed 18 Feb 2015 at 07:54:53 +0530, Sivaram Neelakantan wrote:

> On Tue, Feb 17 2015,Brian wrote:
>
> > On Wed 18 Feb 2015 at 00:05:16 +0530, Sivaram Neelakantan wrote:
>
> [snipped 22 lines]
>
> >
> > What leads you to believe a .xprofile has any significance on Debian?
> >
>
> ouch! You mean, I can't trust some random page on google? ;)

You could trust

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438866

A search with "xprofile debian" has it in the first few results.

> Well, that's what I did; the first part of finding out the screen real
> estate and setting the output worked, so I thought the rest of the
> bits would also be true; where to make the changes permanent.

Try ~/.xsessionrc.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/1802201509471...@desktop.copernicus.demon.co.uk

Sivaram Neelakantan

unread,
Feb 18, 2015, 8:40:04 PM2/18/15
to
On Wed, Feb 18 2015,Brian wrote:


[snipped 24 lines]

> Try ~/.xsessionrc.


Thanks, that worked.


sivaram
--


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/8761aya...@gmail.com
0 new messages