Ubuntu
dosbox package

Mouse frozen in lower right corner in edgy version of dosbox

Bug #74719 reported by James Baum
2
Affects Status Importance Assigned to Milestone
dosbox (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After "upgrading" from dapper to edgy where dosbox with The Settlers worked just fine the mouse freezes in the lower right corner og the dosbox window.

I start the game with

dosbox ~/c/SETT.EXE

When graphics load the mouse cursor immediately travels (of its own volition) to the lower right hand corner of the dosbox screen.

Manually installing the dapper version with
dpkg -i dosbox_0.63-2.1_i386.deb
gave the same problems.

I use a USB-mouse which works everywhere else

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in dosbox:
status: New → Incomplete
Revision history for this message
Peter Veenstra (spiru) wrote :

Do you happen to have a dual monitor setup ?
or happen to run unclutter ?

Revision history for this message
James Baum (james-baum) wrote :

Yes, this was with a laptop with 1024x768 on the built-in monitor and 1600x1200 on an external LCD.
X setup done by manually editing xorg.conf (impossible to get right with Kubuntu tools)

(Don't know what unclutter is, I probably don't run it unless it's installed by default.)

Revision history for this message
Peter Veenstra (spiru) wrote :

there is in the dosbox forum a thread on this.
The problem appears to be in the X configuration of the screen names.
http://vogons.zetafleet.com/viewtopic.php?t=16730
check the last post of Moe.

Something to do with that you have to specify both leftof and rightof
Could you see if that would fix your problem as well ?

Brian Murray (brian-murray)
Changed in dosbox:
importance: Undecided → Low
Revision history for this message
Pablo Castellano (pablocastellano) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in dosbox:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.