Mouse doesn't reach left edge of screen (Solved)

[SMG]

Yes! The command fixes the problem! Wow!!

Wow! is right. Glad something finally works.

However: Adding this command line to the file ~/.profile did not cause the command to be executed upon reboot.

Can you think of some way to cause this command to be executed automatically for each boot?

It should have. Please post the contents of that file. Maybe there is a typo there which another pair of eyeballs might notice.

[gemk65]

Below is the contents of my file /home/kenneth/.profile.

Reminder: I am trying to tell my computer to automatically execute the command
xrandr --output HDMI-3 --transform 1,0,-1,0,1,0,0,0,1
each time the computer boots, but for some reason it is not happening.

The command itself works perfectly, but only when performed manually (in Terminal) on a per-session basis.

Maybe I need to add some punctuation marks somewhere?

Code: Select all

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
	. "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

xrandr --output HDMI-3 --transform 1,0,-1,0,1,0,0,0,1

[SMG]

The command itself works perfectly, but only when performed manually (in Terminal) on a per-session basis.

Maybe I need to add some punctuation marks somewhere?

I have no idea what that is not working. If it works in the command line, it should work there as well.

If it needed punctuation then it would have thrown an error message about syntax not being correct.

The only other alternative of which I know is to make a script as described in this post and set the proper permissions as described. Your script would only consist of the two lines.

Code: Select all

#! /bin/bash
xrandr --output HDMI-3 --transform 1,0,-1,0,1,0,0,0,1

[gemk65]

From the instructions I couldn't figure out where to store the new script file, but I noticed that the Mint Cinnamon GUI offers a simple solution:

1. In System Settings (Cinnamon Control Center), click Startup Applications.
2. Click the Add (+) button.
3. Choose Custom Command.
4. Type in the fields Name, Command, and Comment.
5. Click Add.

Now with each new boot, the command is executed.

This post is Solved.

Thank you again, SMG. The key was your finding and posting Bobby Lawrence's comments on Ubuntu One's linked bug report. Kudos to you for going the extra mile and browsing through these comments. It didn't occur to me to do that, and I don't know how you found the pertinent comment among all of the comments.

[SMG]

From the instructions I couldn't figure out where to store the new script file, but I noticed that the Mint Cinnamon GUI offers a simple solution:

1. In System Settings (Cinnamon Control Center), click Startup Applications.
2. Click the Add (+) button.
3. Choose Custom Command.
4. Type in the fields Name, Command, and Comment.
5. Click Add.

Now with each new boot, the command is executed.

This post is Solved.

Thanks for posting those steps. It may be helpful for others.

Thank you again, SMG. The key was your finding and posting Bobby Lawrence's comments on Ubuntu One's linked bug report. Kudos to you for going the extra mile and browsing through these comments. It didn't occur to me to do that, and I don't know how you found the pertinent comment among all of the comments.

You're welcome. I read a LOT of bug reports and know workarounds people have tried are often listed the comments.

[gemk65]

As a followup to this post, I am posting below an informative comment that I received from Daniel van Vugt of Canonical, who forwarded my bug report to the proper channels.

Daniel said:

This issue is unusual in that it's the only case of an Intel hardware fault going unfixed (or not worked around properly by Intel) that I know of... Although I don't know if Intel has made another attempt at it in newer kernel versions.

[SMG]

As a followup to this post, I am posting below an informative comment that I received from Daniel van Vugt of Canonical, who forwarded my bug report to the proper channels.

He did post 13 hours ago in the linked bug reports with a suggested workaround and a link to the bug report (at very bottom).

You have a workaround that is working for you. I would think just periodically checking as new kernel series are released to see if you still need the workaround is probably the easiest solution.