Your message dated Sun, 20 Oct 2013 17:02:48 +0200 with message-id <[email protected]> and subject line Re: Bug#698313: After exiting the game I get dumped to 640x480 screen has caused the Debian Bug report #698313, regarding After exiting the game I get dumped to 640x480 screen to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 698313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698313 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: freedink Version: 1.08.20120427-2.1 Severity: normal Dear Maintainer, I was trying to run freedink and the moment I exited and got dumped to a 640x480 screen. The following is the output on the console :- $ freedink X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 129 (XFree86-VidModeExtension) Minor opcode of failed request: 10 (XF86VidModeSwitchToMode) Value in failed request: 0x5000003 Serial number of failed request: 254 Current serial number in output stream: 256 These are all the valid resolutions on my display :- $ sudo xrandr [sudo] password for shirish: Screen 0: minimum 320 x 200, current 1600 x 900, maximum 4096 x 4096 VGA1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 443mm x 249mm 1600x900 60.0*+ 1400x1050 60.0 1280x1024 75.0 60.0 1440x900 59.9 1280x800 59.8 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (10, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freedink depends on: ii freedink-dfarc 3.10-1.1 ii freedink-engine 1.08.20120427-2.1 -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17
--- End Message ---
--- Begin Message ---Hi, On Sat, Jan 19, 2013 at 11:18:23AM +0100, Bas Wijnen wrote: > On 19-01-13 11:13, Sylvain wrote: > > Hi, > > > > I don't remember having this bug (that is, except when developing > > FreeDink and getting a segfault ;)). > > > > Is FreeDink segfaulting? > > > > Is this specific to FreeDink, or is this related to libSDL? > > For me, it only happens when it crashes on exit. Not returning to the > old resolution is an SDL problem, IMO. However, the crash itself > probably isn't. > > Unfortunately it seems to be hard to reproduce. I recall I saw it all > the time when playing some dmod, but I don't remember which one, sorry. Since we can't reproduce the bug and do not have any other report, I'll close the bug. Feel free to reopen it if that happens again. -- Sylvain
--- End Message ---
