Bug#891020: Bug#891413: fixed in ppp 2.4.7-2+2
Thanks, this fixed my problem as well. -Chris Dow
Bug#891020: Network Manger
I have the same problem when trying to connect through Network Manager. My connection fails with ppp 2.4.7-2+1, network-manager 1.10.4-1+b1, and network-manager-pptp 1.2.4-5+b1. However, it works with ppp 2.4.7-1+4, network-manager 1.6.2-3, and network-manager-pptp 1.2.4-2 -Chris Dow
Bug#775855: weston: Please enable RDP and screen-share support
Package: weston Version: 1.6.0-2+b1 Severity: wishlist It appears that rdp-backend and the screen-share module are disabled in the Debain package. It would be nice if these were enabled. Thanks -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages weston depends on: ii adduser 3.113+nmu3 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libcolord2 1.2.1-1+b2 ii libdbus-1-3 1.8.12-3 ii libdrm2 2.4.58-2 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libgbm1 10.3.2-1 ii libgles2-mesa [libgles2]10.3.2-1 ii libglib2.0-02.42.1-1 ii libinput5 0.6.0+dfsg-2 ii libjpeg62-turbo 1:1.3.1-11 ii liblcms2-2 2.6-3+b3 ii libmtdev1 1.1.5-1 ii libpam0g1.1.8-3.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libpng12-0 1.2.50-2+b2 ii libsystemd0 215-8 ii libudev1215-8 ii libwayland-client0 1.6.0-2 ii libwayland-cursor0 1.6.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 10.3.2-1 ii libwayland-server0 1.6.0-2 ii libx11-62:1.6.2-3 ii libx11-xcb1 2:1.6.2-3 ii libxcb-composite0 1.10-3+b1 ii libxcb-render0 1.10-3+b1 ii libxcb-shape0 1.10-3+b1 ii libxcb-shm0 1.10-3+b1 ii libxcb-xfixes0 1.10-3+b1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxcursor1 1:1.1.14-1+b1 ii libxkbcommon0 0.4.3-2 Versions of packages weston recommends: ii libgl1-mesa-dri 10.3.2-1 weston suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661943: xserver-xorg-video-radeon: Unable to set native resolution with KMS enabled
I did some more digging in to this and it appears that the reason that I am getting the 'invalid mode' error is that the refresh rate the monitor is receiving is not the refresh rate configured by X or the framebuffer. I noticed that my monitors report what resolution and refresh rate they are receiving. If X or the framebuffer are configured with a refresh rate of 75Hz then the monitor is reporting that it receives a refresh rate of 56Hz (which is at the bottom of the range supported by my monitors). Refresh rates of 70Hz produce an output of 52Hz (which still works but is not supported). I assume that 60Hz is producing an even lower output frequency (hence the 'invalid mode'). If I disable KMS then the reported frequency matches the configured frequency. After realizing this, I am able to get the native resolution to display by cofiguring it with a higher refresh rate. I have no idea why the output frequency doesn't match the configured frequency with KMS. I assume this is a kernel driver bug, unless there is some configuration I am missing. -Chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661943: xserver-xorg-video-radeon: Unable to set native resolution with KMS enabled
Attached is the Xorg.0.log from a boot with only 1 monitor attached. Interestingly, when I boot with only only 1 monitor, I never get to a resolution I can use. It stays on the invalid mode. It doesn't matter which monitor I use. Both produce the same result. The only reason I have been getting a resolution I can use is because I have 2 monitors attached. I think the console is trying to use the native resolution (which produces the "invalid mode" message), since sometimes the screen goes black before the startup messages get to the part about KDM (I assume that is when X starts). I never see the startup messages in a different resolution than what they start with. -Chris D Xorg.0.log.old Description: application/trash
Bug#661943: xserver-xorg-video-radeon: Unable to set native resolution with KMS enabled
Unfortunately, my problem is that I can't change the display modes to the native resolution. Even with one display disabled, I still can't set the native resolution. I get the same "input timing not supported" message every time I have tried. It wouldn't be a problem if the default was not what I wanted but I could change to the correct resolution. Most of my attempts to change the resolution have been been using the KDE display tool (which, as I understand, uses xrandr underneath). However, I've also attempted to use xrandr directly. -Chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org