Strange occurrence in /var/log/messages
[Please preserve the CC] Apologies for the duplication , I forgot to include a subject in the previous message. At the bottom of /var/log/messages I see Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com";] restart Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com";] restart (Some wraparound may have occurred in the above) The same pair of messages is repeated. First time I notice such a thing. In /var/log/kern.log I see at the bottom Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Once again a duplication. Is there any legitimate reason this might have happened or is it a kernel bug ? Neither file has anything else I haven't seen before. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikSv=eu3jtpnxzqpq9obfpkwed...@mail.gmail.com
[no subject]
[Please preserve the CC] At the bottom of /var/log/messages I see Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com";] restart Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Jul 1 07:35:01 home rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2103" x-info="http://www.rsyslog.com";] restart (Some wraparound may have occurred in the above) The same pair of messages is repeated. First time I notice such a thing. In /var/log/kern.log I see at the bottom Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Jul 1 07:35:01 home kernel: imklog 3.18.6, log source = /proc/kmsg started. Once again a duplication. Is there any legitimate reason this might have happened or is it a kernel bug ? Neither file has anything else I haven't seen before. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTim9ftEhFguf3Evy=+bhnkydhpc...@mail.gmail.com
My X environment has become "magnified" [SOLVED]
I don't seem able to reply to my previous thread titled My X environment has become "magnified" < http://groups.google.com/group/linux.debian.user/browse_thread/thread/3b64dae082545c18 > so this is just to say that doing xrandr --rate 60 solved the problem. Thanks to Andrew Sackville-West. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=if9unxdje79v5x0btum8qqj9q-1dffv9pf...@mail.gmail.com
My X environment has become "magnified"
Hi folks. I downloaded some new levels for the arcade game supertux. I tried supertux -d . on the directory where I had downloaded the levels but presumably I used the option incorrectly because the programme exited immediately. The problem is that my X environment is now "magnified". By this I mean that everything looks much larger and all the windows very much exceed the boundaries of my monitor. When I say everything I really mean everything , for example the fonts on every application I have open. Basically it's as if every pixel goes through a magnifying glass before appearing on the screen. Most applications don't seem aware that anything is different , for example if I do tput cols inside the terminal emulator I get the same value as before. I tried typing supertux hoping it would fix it. The programme works correctly but when I exit it things remain magnified. Some programmes which enter directly into fullscreen mode , like njam , display correctly but when they terminate things remain magnified. I'm sure that killing the X server would fix it but I have several applications running which I would prefer not to terminate so I'm looking for a solution which will not terminate my desktop session. Preferably also something which will work from the command line since most windows are so large that most of their content goes off the screen. I'm typing this on console. Apart from the magnification , everything else works correctly. Files ~/.xsession-errors and /var/log/Xorg.0.log don't seem to have anything relevant but both are quite large so I only looked at the last 3 screenfulls. I tried pressing Alt+Ctrl+ and it changes things a bit but does not return them to normal. Pressing the keys several times eventually results into a black screen and the monitor says "signal out of range" so I have to press Alt+Ctrl+ to get picture again. I'm running Debian lenny with the ratpoison window manager. Any ideas ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=ttdg4ce3ae0cpdcfc8jetfg96kswkczwb3...@mail.gmail.com
