Re: systemd: systemctl does not re-create display-manager.service symlink
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2020-02-01 at 03:21 +0100, Michael Biebl wrote: > They should also add a > > [Install] > Alias=display-manager.service > > section > > to their service file. Which will make sure that if you run > "systemctl enable foo.service", display-manager.service will point at > the desired display manager. Hi Michael, I tried that, but it seems that it has the side effect of making lightdm restart when upgrading, which is not really a good idea when you're actually in a X session. Any idea how to prevent that? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl425xsACgkQ3rYcyPpX RFvAMwf/Tk4n/O+Do2BtvKCyGlURo4xlofmHtZNlBISDVV+dxAN5jNxwcnjf2D3t T+65JIJ6sDHWg1DjWSu0Ug6Y0KF3ei3ka7M4di50iMwtn2ULglHg0Z3Prjuyq4bH CH4JfLXfCIsa62XPSn1tSbUW4KAj+SO1j7CGBhVUf7eixF0anMLP1QC/z+W52z78 CAa4Tf2ODrUip9n4iad10W+pHMD9x8uEIrTAF8Grgro916xcAcyyI9c6BDYRKIAS Hxj9ZrDen3n5EjN1gXEzFt3hX8o+X6NRoMNRWNCZNGJSo+4s/Y41vwD0a2x1KmUj mJaXI6l+30ipwGPsWfN0nVBNePA/2Q== =3gP4 -END PGP SIGNATURE-
Re: Bug#929834: Buster/XFCE unlock screen is blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: affects -1 xserver-xorg-core On Sat, 2019-06-22 at 17:34 -0400, John Franklin wrote: > I've been suffering from this bug in a clean Buster system, too. A > solution noted in another bug tracker is to explicitly tell X.org to > use the intel driver. Apparently, it uses the fbdev driver by default. > (Sorry, I don't have a reference to other bug handy.) Hi John, it uses the modesetting DDX driver by default, not fbdev, but it's good to know that changing to the intel DDX workarounds the issue. Regards - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl0Rzk4ACgkQ3rYcyPpX RFsKGggAgv9hw7Cen7bEiCpPU87DniXPvJ+5NsszICoQXal7YBet/RMBpyYSoujo 7G32lLpazDO1s+f8TGReCx/JopjLsZgLVxtL6tOCBLFFBzfRTG8HnoQpwJrITwWU pPbp3e+shd5I6yKPqdv+ZoBG8Eq58poPgrzJbJXLRN3vMAafChl0C+b/N4NYUBuJ HIaz1qkKuoU3ZDtnMdNrIbsfHr/baO9B1Dht5/0TO3WHgd5UIRIuOqNgi4LnJxVF QOQJEYtJSWSZdJGVBGhP9/qxAPI69j/NgEYL1L4ITYb5YrDbPNJUbxBBw3G3nG2Z 4cbF9eOmWAqn4iD8EfoWA4p/i3fuCQ== =XzOA -END PGP SIGNATURE-
Bug#846222: [Pkg-xfce-devel] Bug#846222: x11-common: Please provide a default xsession in /usr/share/xsessions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2019-01-04 at 12:33 -0300, Maximiliano Curia wrote: > I can only speak for the sddm's Xsession which is a wrapper arround Debian's > /etc/X11/Xsession, I think if there are improvement to be made, they should go to /etc/X11/Xsession in order to benefit everyone. But: > what it does is to try to set the corresponding shell > environment by loading the user profile files. Shell environment is enviroment for the shell, not for other stuff. Especially, .profile is for bash, not for graphical applications. > The sourced profiles take care of things like adding /usr/games to the PATH, > which was loudly asked by our users when the wrapper wasn't present. If people are missing environment variables on their session, the right way to do it is to add them to .xsessionrc. See also environment.d(5) for more global ways. Also, for LightDM, we updated the code so the default PATH matches Debian expectations: https://sources.debian.org/src/lightdm/1.26.0-3/debian/patches/01_set-default-path.patch/ Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwvh6gACgkQ3rYcyPpX RFvjeAf9ENgBnGeVtG7VftFZf97in7z/C0KhwDvtSplTLknozG7liQUUwD9hwL93 bciWX4+9oexIIx10t8KiZyhUeUT9PhV2xsNp689MEEyg6mZY795aZ7zfjMPsEQJz /yYYra8yvsrdtfe0NgIl//H/NWUrgddvE8ogYi0scZ1fSaUAvKAr78dmPwPBNNQw p9UMgoymv2mIs2n9G0SZmV+UV96a4xYJ9PV+CtAFkv4Zl3V+qXgT3058lXiD/Wqc dybOsZ1Zw2q1/i0qZw9SScxTmF7tYRD51hDypuaz0ZwbtCmRJUzIZykkWvhHdcYA 7XMGOWcaozm0PAjaQ5QWfXeDMy/F3g== =PRpx -END PGP SIGNATURE-
Bug#901789: mesa: white screen when running Xfwm4 with compositing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=107117 For what it's worth, Olivier Fourdan reported that bug upstream and investigated it, and it's been supposedly fixed there. There's a patch (https://patchwork.freedesktop.org/patch/241077/) which has been committed to mesa developpment tree ( https://gitlab.freedesktop.org/mesa/mesa/commit/03a61b977e1f6adb64658aa059ce53e766ff9ad9 ). Could this commit be backported to Debian? Thanks! - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAltrAHQACgkQ3rYcyPpX RFtPlQf+Obcd9iDQaqFDW+kOC8STFmHV5ZQ4NeRG2gMPB62LafoZ7ZWnzWm4ppba B/Redi6Nx0sYMBne+9FTGfmATh/6So41USYPubANS0wEiyGqjt+6zkAdTqKtS/5b IrldNVOufDQ05EfB1NNEAh6YEvHYF5pomKjnVJ1t3lVyqWHd2TB2A8pKYmBRywwj gymniRQgsYxh4N10tXTlkHUyoZwE2/yAUByHoklyVI47z5lfOJuKHYbVwg4Tz4j1 FsR1cpVGXdsGS7x3/x6hO/DHYScYBqbLpCAU2c7lNvjYMNl4t3WohI7o1IRtkVpH u+CATkFoxuLvvqJQYnR8W0bKfmdueA== =bGgf -END PGP SIGNATURE-
Bug#901789: mesa: white screen when running Xfwm4 with compositing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2018-06-19 at 20:30 +0200, Yves-Alexis Perez wrote: > > Yves-Alexis, which xfwm4 version do you use ? > > Indeed that's a good point, I'm also using xfwm4 4.13 from experimental. I've uploaded xfwm4 4.13.0-2 which disables GL support through libepoxy (and mesa), so the problems is workarounded, but it'd be nice if mesa could be fixed. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlsykfEACgkQ3rYcyPpX RFtnegf/WATo1xT7B1I4GnOpVFwGm7KSMxoTj3QX36s5dWPAVvPBcsK+M3c8GbSy FLUkagGozPo5EqfXkviS39UJLMLAeO1eSsqrY6fOEY5IVSuFcvceD5FPYu7ughGZ 0291GvDWSTxr5+I/P4k2Mw7boPOWu6XBf4vsK/rTkJ/KsUAY+4DwdoIwG3kexIke VqTJDrkMXT86W3sqXJYgUi7AsuoxJrE+uagdnWF8nx1cRn5jTwbUewGuRsp41pHK RgIyp/F/BP9m9Q+pktT1fpwQKTHCZznEdMwm57Z/kDWUVFHy0RMgwrowP4bC4Mz6 nNr48yzYmseUSUYeJtoDU48YoXhsXA== =gLwi -END PGP SIGNATURE-
Bug#901789: mesa: white screen when running Xfwm4 with compositing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2018-06-19 at 16:26 +0200, Pascal Dormeau wrote: > On Mon, 18 Jun 2018 14:06:10 +0200 Yves-Alexis Perez > > since the upgrade from 18.0.5-1 to 18.1.1-1 of the various mesa > > packages, xfwm4 with compositing enabling only display a white screen. > > The cursor is shown on top, but no window appears. When restarting > > xfwm4 I can briefly see the windows, then the white screen. > > > > Disabling compositing in xfwm4 workarounds the problem but then you > > lose all compositing-related features. > > Hello, > > Not sure it helps, but I observe the same here (xfwm4 with compositing + > mesa 18.1.1-1 fail, and a white screen is displayed) but only with > xfwm4 in experimental (4.13.0-1). > Unstable version (4.12.4-1) is perfectly fine with mesa 18.1.1-1 (intel > graphics HD4000, CPU generation is Ivy Bridge, and modesetting driver > is used). > > Problem still exists with mesa 18.1.2-1. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlsqxG0ACgkQ3rYcyPpX RFtV7QgAwpQDHxq3G7C6hmKTbRV1ZONPBTh99CLScbJkwi/plDSS5btkE0e9o83s L7IS98knulJzuo/AVPBa6W0f4sKhlXxewyTqDURv7VKo/avLTbmrnFZa2tNlqv6C /j4cV4x1LS7rPSKErD/7l7j0xFMmAAvFHLEtyNc+WoF4f3Z3lxiJ97xB8tp+RvXV 2H+b/JsVYEYe6RUqktujNl1xF5QzqQAJdjyDGCxKecVvYFmBXj7qEmKyyWzFtPku WCENflTjlg+xkU3tF/+0p5Q9zh7RPDQ+hmcTvdCOoFyzcs6nxW05+18Vq7zkDUMr JoGuhW8O1S+YhwRWLIT47ZZUB87hGA== =S803 -END PGP SIGNATURE-
Bug#901789: mesa: white screen when running Xfwm4 with compositing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2018-06-19 at 16:26 +0200, Pascal Dormeau wrote: > Not sure it helps, but I observe the same here (xfwm4 with compositing + > mesa 18.1.1-1 fail, and a white screen is displayed) but only with > xfwm4 in experimental (4.13.0-1). > Unstable version (4.12.4-1) is perfectly fine with mesa 18.1.1-1 (intel > graphics HD4000, CPU generation is Ivy Bridge, and modesetting driver > is used). > > Yves-Alexis, which xfwm4 version do you use ? Indeed that's a good point, I'm also using xfwm4 4.13 from experimental. - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlspS8cACgkQ3rYcyPpX RFsLywgAptdKK3e9MSeaTpraqXbYVQuZdzmpHYkY+2tivBf1PBeHte3VFyg6967+ C2CJ51rGHRPnKUTY2bpHKxRl0M939FqGUqNNToNxMCvxpjCtMV9u+1Qm8ZDhHnW4 FYMGKxrTDCPojOBjlh5rQiod33cLS2YbaHbAF1VMi0GzW+JQwJMRCFVmfoCCb2nB ZSdu2QDHeY+NHLatM37Wp3POCU+WBBZ2SSTm5taqCsaeAf4U/lmSlVm1NKST7ywi 138MmiNCViVfyhNogyH/K8HRFJRbBjv6tQtoS2XCXqe7/1YFu2s3fZD4ioMtLDfX PP9pqrg7hZyNiwy3avBietPEuM2q/Q== =+OJ9 -END PGP SIGNATURE-
Bug#901789: mesa: white screen when running Xfwm4 with compositing
Source: mesa Version: 18.1.1-1 Severity: important Hi, since the upgrade from 18.0.5-1 to 18.1.1-1 of the various mesa packages, xfwm4 with compositing enabling only display a white screen. The cursor is shown on top, but no window appears. When restarting xfwm4 I can briefly see the windows, then the white screen. Disabling compositing in xfwm4 workarounds the problem but then you lose all compositing-related features. The platform is a ThinkPad X250 with Intel graphics (HD Graphics 5500 I thinks, CPU generation is Broadwell) If you need more information, please ask. Regards, -- Yves-Alexis -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#854594: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed
On Sat, 2017-03-04 at 19:18 +0100, Yves-Alexis Perez wrote: > I'll > try to reproduce using a gstreamer pipeline in case that helps narrowing the > problem. Calling gst-play-1.0 works fine. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#854594: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed
On Sat, 2017-03-04 at 17:53 +0100, Julien Cristau wrote: > Is it multi-threaded? Does XInitThreads get called before any other X > function? It's a GTK (3) application so I assume multi-threaded yes. I've searched for XInitThreads in sources.debian.net but it doesn't seem to be called at all in gthumb or GTK3. There are gstreamer references though so I'll try to reproduce using a gstreamer pipeline in case that helps narrowing the problem. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#854594: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed
Package: libx11-xcb1 Version: 2:1.6.4-3 Severity: normal Hi, gthumb crashes consistenly for me when trying to play a mp4 video (from my Android smartphone). Console outputs points to libx11-xcb, with: [xcb] Unknown request in queue while dequeuing [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. gthumb: ../../src/xcb_io.c:165: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed. The graphic adapter is i915 (Broadwell) and libva is installed, in case it matters. Maybe the bug actually lies in gthumb (or gtk), so please reassign if needed. If you need more information, please ask. Regards, -- Yves-Alexis -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#846222: [Pkg-xfce-devel] Bug#846222: x11-common: Please provide a default xsession in /usr/share/xsessions
On Tue, 2016-11-29 at 11:52 +0100, Maximiliano Curia wrote: > Hi, > > Thanks to the #845948 report against sddm, we noticed that the "Default > Xsession" xsession desktop file is being provided by the lightdm display > manager (in the /usr/share/xsessions/lightdm-xsession.desktop file). And > since: > > - This xsession file is useful for other display managers, such as sddm, that > uses the /usr/share/xsessions/*.desktop to allow the users to choose their > preferred sessions. > > - This ends up calling /etc/X11/Xsession default which is the only way to use > the user's ~/.xsession file > > - The script that processes the "default" parameter > (/etc/X11/Xsession.d/20x11-common_process-args) as a special case is > provided by the x11-common package. > > I believe, it would be better to this file in the x11-common package (renamed > as > /usr/share/xsessions/user-xsession.desktop or > /usr/share/xsessions/default-xsession.desktop). If other DM have the same behavior as LightDM, I guess it's a good idea indeed, although I'm wondering if it can have side effects. In any case, keep me in the loop so I can remove the file from LightDM when needed :) Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#818244: Request to close
On ven., 2016-04-08 at 13:10 -0700, Erik Haller wrote: > I ran the gmonitor program. Attached are two files. It looks like you found > something. > > FYI: I changed my graphics card yesterday. From a radeaon X1300 to an > nvidia GT 610. The nvidia has to ports and I no longer use the Y cable. > They're also appearing under xrandr as DVI-2|3. The new card does not > appear to affect your test. So there's definitely something which changed with the xserver-xorg update, but the changelog really doesn't show anything related. It might be worth comparing Xorg.0.log too. Are you perfectly sure nothing else changed between the two snapshots? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#818244: Request to close
On jeu., 2016-04-07 at 00:58 -0700, Erik Haller wrote:
> All I can say is that xfce4 was using monitorDVI-0 and then switched to
> monitor0. I had to move my settings from monitorDVI-0 to monitor0.
I've crafted the attach gtk/gdk program which indeed returns no monitor name
here. Can you try it on both xorg version and report back?
Regards,
--
Yves-Alexis
#include
#include
#include
/* build with
* gcc -W gmonitor.c -o gmonitor $(pkg-config --cflags --libs gdk-2.0)
* */
int main(int argc, char* argv[]) {
gdk_init(&argc, &argv);
GdkScreen *screen = gdk_screen_get_default();
for (int i = 0; i < gdk_screen_get_n_monitors(screen); ++i) {
gchar *name = gdk_screen_get_monitor_plug_name(screen, i);
printf("monitor %d name: %s\n", i, name);
}
return 0;
}
signature.asc
Description: This is a digitally signed message part
Bug#818244: Request to close
On mer., 2016-04-06 at 21:33 -0700, Erik Haller wrote: > I compiled monitor.c and ran the following command: > > cat <(monitor) <(xrandr) <(dpkg-query -l xserver-xorg) > > > I have one radeon X1300 card with a Y cable going to two monitors. > > Attached to this email are the two output files. So the names returned by RandR are indeed identical. That doesn't make much sense to me here, maybe there's something I missed (maybe at the GTK+ layer or something, I'm unsure). Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#818244: Request to close
On mer., 2016-04-06 at 13:13 +0200, Yves-Alexis Perez wrote:
> On mer., 2016-04-06 at 04:04 -0700, Erik Haller wrote:
> >
> > I have never seen xrandr use monitor0|1. I am running lightdm.
> That just means xfdesktop4 didn't get a monitor name. It gets a name
> from gdk_screen_get_monitor_plug_name() [1,2] which in turns gets it from
> X11
> [3] using XRRGetCrtcInfo(). So my guess is that this behavior changed after
> the xorg update.
>
Actually the name comes from XRRGetOutputInfo(), not XRRGetCrtcInfo() but the
point still stands.
Can you check with the attached program and report back the monitor names with
both xorg versions?
Regards,
--
Yves-Alexis
#include
#include
#include
#include
/* build with gcc -W monitor.c -o monitor -lXrandr -lX11 */
int main(void) {
Display *display = XOpenDisplay(getenv("DISPLAY"));
Window window = DefaultRootWindow(display);
XRRScreenResources *resources = XRRGetScreenResources(display, window);
for (int i = 0; i < resources->ncrtc; ++i) {
XRROutputInfo *output = XRRGetOutputInfo (display, resources, resources->outputs[i]);
printf("monitor %d name: %s\n", i, output->name);
XRRFreeOutputInfo(output);
}
XRRFreeScreenResources(resources);
return 0;
}
signature.asc
Description: This is a digitally signed message part
Bug#818244: Request to close
On mer., 2016-04-06 at 04:04 -0700, Erik Haller wrote: > I have never seen xrandr use monitor0|1. I am running lightdm. That just means xfdesktop4 didn't get a monitor name. It gets a name from gdk_screen_get_monitor_plug_name() [1,2] which in turns gets it from X11 [3] using XRRGetCrtcInfo(). So my guess is that this behavior changed after the xorg update. [1] https://developer.gnome.org/gdk2/stable/GdkScreen.html#gdk-screen-get-moni tor-plug-name [2] https://sources.debian.net/src/gtk%2B2.0/2.24.29-1/gdk/x11/gdkscreen-x11.c /?hl=445#L445 [3] https://sources.debian.net/src/gtk%2B2.0/2.24.29-1/gdk/x11/gdkscreen-x11.c /?hl=796#L796 -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#818244: Request to close
On Tue, 5 Apr 2016 20:33:12 -0700 Erik Haller wrote: > This bug is caused by xfce4. I removed the config files under ~/.config and > the desktop images appeared and the dimming went away. The dimming was > probably caused by a lack of a desktop image on the second monitor. > > The missing desktop images was caused by a change in the > /home//.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml. > Before the upgrade, xfce4 was using the monitorDVI-0 and monitorDVI-1 > sections. After the xserver-xorg package upgraded, xfce4 started using the > monitor0 and monitor1 sections. These sections did not use my desktop > background images. For some reason, xfce4 is working differently after the > xserver-xorg upgrade. > > The xrandr shows two monitors DVI-0/DVI-1 before and after the upgraded. I > do not understand why xfce4 switched from monitorDVI-0|1 to monitor0|1. Well, actually as far as I can tell Xfce didn't switch, Xorg did, but that puzzles me. Xfce (xfwm4) relies on the output named provided by the RandR extension, so if they were modified by the upgrade, then obviously the previous configuration doesn't apply and you'll have to redo it. I'm puzzled by the fact you indicate xrandr doesn't show a name change. It might be worth diffing both Xorg.0.log, because quite obviously Xfce4 (xfdesktop4 actually) saw different names. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#815135: Same issue here
Hi, it seems that I have the same kind of issue here, on my ThinkPad X250 (broadwell). The problem started happening recently, I think when 2:2.99.917+git20160307-1 was installed. This doesn't happen at first, but only when my lock screen engage, and I get redirected to the login screen. I'm running Xfce + LightDM + light-locker, and I can reproduce at will with dm-tool switch-to-greeter. A vt-switch to console is not enough to reproduce though. Once it has happened, the mouse pointer/cursor has disappeared, but I can get it back with xset dpms force off + pressing a key to light up the screen (I guess it manage some kind of reset of the graphic engine). Also, it seems to happen with AccelMethod "sna" (the default) and "glamor" (if that actually exists), but not "uxa". Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#782505: Also, was the libxrender update really built in 2013?
On mar., 2015-04-14 at 14:32 -0400, Anthony DeRobertis wrote: > The changelog entry, at least for i386, gives 14 May *2013* as the date. > Weird a security update got delayed that long, but also concerning is > that the libx11 changelog gives 11 Apr *2015*. > > If those dates are correct, then it'd appear that xrender was /not/ > built against the fixed libx11, meaning it doesn't really include the > CVE-2013-7439 fix. If you take a torough look, the changelog entry date is *the exact same* as the previous changelog entry. It does look weird, but it's the same on other binNMus. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#632030: [Pkg-xfce-devel] Question about weird mouse pointer thing (Bug #632030)
On mar., 2011-07-12 at 09:34 +0200, Andreas Neudecker wrote: > Hello XFCE maintainers. > > A short while ago I filed bug #632030 for libxcursor1 assuming it was a > problem with selection of the correct icons. > > Michel Dänzer arrived at the conclusion that the problem might rather be > related to xfwm4 or maybe GTK. He suggested asking you about it. > > Interestingly, the problem goes away when I run > > xfwm4 --replace & > > What is your opinion? Is it an xfwm thingy? > My guess is that the xressources aren't loaded correctly before xfwm4 is started. As Xressources are only used for program started *after* they are loaded, the fact that restarting xfwm4 fixes the issue means they are loaded too late. Can you check in gdm3 that the session you are using is “Xfce Session” and not default X session or something like that (no idea how it's called in gdm3). Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#610743: libchamplain-0.4-0: makes X segfaults
reassign 610743 libgl1-mesa-dri found 610743 7.8.1-1 thanks On sam., 2011-01-22 at 01:04 +0100, Cyril Brulebois wrote: > Hi, > > Emilio Pozuelo Monfort (21/01/2011): > > reassign 610743 xserver-xorg-video-intel > > thanks > > (might be xserver-xorg-core instead.) Following your blog post, I tried to upgrade libdrm to experimental: ii libdrm-intel1 2.4.23-1 Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-nouveau1 2.4.22-2 Userspace interface to nouveau-specific kernel DRM services -- runtime ii libdrm-radeon1 2.4.22-2 Userspace interface to radeon-specific kernel DRM services -- runtime ii libdrm2 2.4.23-1 Userspace interface to kernel DRM services -- runtime but it still crashes. I've tried on a Squeeze box and it doesn't crash (ouf). > > > X crashing is an X bug. > > > > Please attach Xorg.0.log after the crash. Bonus points if you also > > provide a gdb backtrace. > > Yeah, that'll get us the backtrace() output, which isn't exactly > helpful: The backtrace() is: Backtrace: [ 39745.132] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4aa9c8] [ 39745.132] 1: /usr/bin/X (0x40+0x61bd9) [0x461bd9] [ 39745.132] 2: /lib/libpthread.so.0 (0x384e2dd1000+0xef60) [0x384e2ddff60] [ 39745.132] 3: /usr/lib/dri/i965_dri.so (0x384df1d3000+0x28878) [0x384df1fb878] [ 39745.132] 4: /usr/lib/xorg/modules/extensions/libdri2.so (0x384dfd89000+0x23a2) [0x384dfd8b3a2] [ 39745.132] 5: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2SwapBuffers+0x321) [0x384dfd8c3d1] [ 39745.132] 6: /usr/lib/xorg/modules/extensions/libdri2.so (0x384dfd89000+0x4409) [0x384dfd8d409] [ 39745.132] 7: /usr/bin/X (0x40+0x487a9) [0x4487a9] [ 39745.132] 8: /usr/bin/X (0x40+0x2573b) [0x42573b] [ 39745.133] 9: /lib/libc.so.6 (__libc_start_main+0xfd) [0x384e1b46c4d] [ 39745.133] 10: /usr/bin/X (0x40+0x252c9) [0x4252c9] [ 39745.133] Segmentation fault at address 0x18159 > http://pkg-xorg.alioth.debian.org/howtos/use-gdb.html gdb session is attached. Looking at the backtrace I saw I was missing debugging symbols for libgl1-mesa-dri so I tried to install them. The packages were at version 7.8.2-1 (which looks like an old experimental version) so I had to upgrade it before installing the corresponding gdb package. After upgraded to 7.9+repack-2 the segfault is gone. I'm reassigning first and will -done it on a second mail since I'm not sure in which order it'll be processed. > > > > > If you need more info, please ask. > > As mentioned on IRC: > /usr/share/bug/xorg/script 3>/tmp/script.log Attached (though it's useless now I guess). Regards and thanks for your help :) -- Yves-Alexis /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Oct 25 2007 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1918112 Jan 9 03:33 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 201 Jan 18 2010 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section "Device" Driver "intel" Identifier "intel" Option "FramebufferCompression" "on" Option "XvMC" "on" EndSection Section "Monitor" Identifier "LVDS1" DisplaySize 285 214 EndSection Kernel version (/proc/version): Linux version 2.6.32-5-grsec-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Jan 6 21:35:01 CET 2011 Xorg X server log files on system: -rw-r--r-- 1 root root 24950 Nov 14 17:57 /var/log/Xorg.20.log -rw-r--r-- 1 root root 24490 Jan 22 11:28 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: [ 39869.819] X.Org X Server 1.9.3.901 (1.9.4 RC 1) Release Date: 2011-01-07 [ 39869.819] X Protocol Version 11, Revision 0 [ 39869.819] Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian [ 39869.819] Current Operating System: Linux hidalgo 2.6.32-5-grsec-amd64 #1 SMP Thu Jan 6 21:35:01 CET 2011 x86_64 [ 39869.819] Kernel command line: initrd=/initrd.img-2.6.32-5-grsec-amd64 root=/dev/mapper/hidalgo-root ro quiet splash intel_iommu=on BOOT_IMAGE=/vmlinuz-2.6.32-5-grsec-amd64 [ 39869.819] Build Date: 09 January 2011 02:16:34AM [ 39869.819] xorg-server 2:1.9.3.901-1 (Cyril Brulebois ) [ 39869.819] Current version of pixman: 0.18.2 [ 39869.819] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 39869.819] Markers: (--) probed, (**) from config file, (==) default setting, (++) from comman
Bug#604816: hid_apple module parameter
Something else which is worth a try is the output of: cat /sys/module/hid_apple/parameters/iso_layout and try toggling it (it should be 1 by default, try to set it to 0), restart and report back. Do the key work fine on console and not in X or nowhere? Finally, does a: setxkbmap -option apple:goodmap from X changes anything? Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Re: Bug#604676: linux-2.6: include fix for aluminium powerbooks keyboards
On mar., 2010-11-23 at 14:26 +0100, Yves-Alexis Perez wrote: > The commit seems to be 54a6593d65e638ad7e1e8cc986159d76054dab4b and is not > included in Squeeze kernel. I've opened a bug against xkb-data (#604671) to > revert the fix until the Debian kernel includes the patch but it'd be nice > to include it for Squeeze (though I could understand it's not a priority). > I've tried to rebuild the Squeeze kernel with the patch above (many thanks for debian/bin/test-patches, it's really convenient, by the way), and it doesn't really seem to fix the problem. I can set the iso_layout parameter but it doesn't change anything, and more, it seems to prevent the xkb-data fix to work from inside X (running setxkbmap -option apple:badmap doesn't change anything, I have to put it into /etc/default/keyboard). So it seems safe to not include it for now in Squeeze kernel, I'll open a bug upstream and report back when I have more news. The xkb-data fix alone seems to work fine for now. Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#604671: xkb-data: apple:badmap option doesn't work anymore, breaking @#/<> on powerbook/ibook usb keyboard
On mar., 2010-11-23 at 13:50 +0100, Yves-Alexis Perez wrote: > Package: xkb-data > Version: 1.8-1 > Severity: normal > > Hey, > > as noted on irc, the apple:badmap option was dropped from xkeyboard-config, > supposingly because a fix had been commited into the kernel (which would be > the correct place). Except that in 2.6.32 squeeze kernel, the fix is not > present which means on my (french) powerbook 5,6 with usb keyboard, typing > the key marked <> produces @# and the key marked @# produces <>. > > Some pointers: > > freedesktop.org bug: http://bugs.freedesktop.org/show_bug.cgi?id=9095 > fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=476057 > upstream commit: > http://cgit.freedesktop.org/xkeyboard-config/commit/?id=222afd3220e9c920bef41bc2e95886c5d4414d5b > > Reverting the fix until the kernel is fixed might be a good idea for > Squeeze. As stated on irc, the proposed fix, just reverting the commit, does work fine. Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#604676: linux-2.6: include fix for aluminium powerbooks keyboards
Package: linux-2.6 Version: 2.6.32-27 Severity: wishlist Hey, I recently booted my powerbook and fully upgraded to Squeeze. I noted that the (quite old) proble, of the inverted @#/<> was back in X (while it works fine on console). There was an xkb option supposed to fix that (apple:badmap), but it has been dropped from xkeyboard-configuration because a correct had been committed to the kernel. The commit seems to be 54a6593d65e638ad7e1e8cc986159d76054dab4b and is not included in Squeeze kernel. I've opened a bug against xkb-data (#604671) to revert the fix until the Debian kernel includes the patch but it'd be nice to include it for Squeeze (though I could understand it's not a priority). Thanks in advance, -- Yves-Alexis -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-27) (m...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sat Oct 30 23:26:42 UTC 2010 ** Command line: root=/dev/hda2 ro vga=0x317 quiet ** Not tainted ** Kernel log: [ 10.163771] udev[221]: starting version 164 [ 11.547930] cfg80211: Using static regulatory domain info [ 11.547936] cfg80211: Regulatory domain: US [ 11.547939] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 11.547945] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 11.547949] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.547954] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.547959] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.547964] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 11.547969] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 11.548690] cfg80211: Calling CRDA for country: US [ 11.590197] usb 2-1: USB disconnect, address 2 [ 11.593324] usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -108 [ 11.706290] input: appletouch as /devices/pci0001:10/0001:10:1a.0/usb2/2-2/2-2:1.1/input/input6 [ 11.706596] usbcore: registered new interface driver appletouch [ 11.956042] usb 2-1: new full speed USB device using ohci_hcd and address 4 [ 12.229645] yenta_cardbus 0001:10:13.0: CardBus bridge found [:] [ 12.229667] yenta_cardbus 0001:10:13.0: Enabling burst memory read transactions [ 12.229673] yenta_cardbus 0001:10:13.0: Using CSCINT to route CSC interrupts to PCI [ 12.229678] yenta_cardbus 0001:10:13.0: Routing CardBus interrupts to PCI [ 12.229685] yenta_cardbus 0001:10:13.0: TI: mfunc 0x1002, devctl 0x60 [ 12.238089] usb 2-1: New USB device found, idVendor=05ac, idProduct=8205 [ 12.238097] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 12.238291] usb 2-1: configuration #1 chosen from 1 choice [ 12.332083] yenta_cardbus 0001:10:13.0: ISA IRQ mask 0x, PCI irq 53 [ 12.332091] yenta_cardbus 0001:10:13.0: Socket status: 3007 [ 12.332106] yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge I/O window: 0x0 - 0x7f [ 12.332113] yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge Memory window: 0xf300 - 0xf3ff [ 12.332119] yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge Memory window: 0x8000 - 0xafff [ 12.445727] irq: irq 57 on host /p...@f200/mac...@17/interrupt-control...@4 mapped to virtual irq 57 [ 12.445768] irq: irq 58 on host /p...@f200/mac...@17/interrupt-control...@4 mapped to virtual irq 58 [ 12.458366] ams: Found I2C based motion sensor [ 12.632406] Bluetooth: Core ver 2.15 [ 12.632526] NET: Registered protocol family 31 [ 12.632529] Bluetooth: HCI device and connection manager initialized [ 12.632535] Bluetooth: HCI socket layer initialized [ 12.768597] b43-phy0: Broadcom 4306 WLAN found (core revision 5) [ 12.771691] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 12.772241] usbcore: registered new interface driver btusb [ 12.927820] phy0: Selected rate control algorithm 'minstrel' [ 12.928861] Registered led device: b43-phy0::tx [ 12.928886] Registered led device: b43-phy0::rx [ 12.928910] Registered led device: b43-phy0::radio [ 12.929040] Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] [ 12.955513] irq: irq 30 on host /p...@f200/mac...@17/interrupt-control...@4 mapped to virtual irq 30 [ 12.955548] irq: irq 1 on host /p...@f200/mac...@17/interrupt-control...@4 mapped to virtual irq 21 [ 12.955565] irq: irq 2 on host /p...@f200/mac...@17/interrupt-control...@4 mapped to virtual irq 27 [ 13.026357] snd-aoa-fabric-layout: Using PMF GPIOs [ 13.057945] snd-aoa-codec-tas: found tas3004 [ 13.058683] snd-aoa-fabric-layout: can use this codec [ 13.123328] irq: irq 61 on host /p...@f200/mac...@17/interrupt-control...@4 mapped to virtual irq 61 [ 13.123365] snd-aoa-codec-tas: tas found, addr 0x35 on /p...@f200/mac...@17/i...@18000/i2c-...@0/co...@6a [ 15.383250] Adding 42k swap on /dev/hda4. Priority:-1 ext
Bug#604671: xkb-data: apple:badmap option doesn't work anymore, breaking @#/<> on powerbook/ibook usb keyboard
Package: xkb-data Version: 1.8-1 Severity: normal Hey, as noted on irc, the apple:badmap option was dropped from xkeyboard-config, supposingly because a fix had been commited into the kernel (which would be the correct place). Except that in 2.6.32 squeeze kernel, the fix is not present which means on my (french) powerbook 5,6 with usb keyboard, typing the key marked <> produces @# and the key marked @# produces <>. Some pointers: freedesktop.org bug: http://bugs.freedesktop.org/show_bug.cgi?id=9095 fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=476057 upstream commit: http://cgit.freedesktop.org/xkeyboard-config/commit/?id=222afd3220e9c920bef41bc2e95886c5d4414d5b Reverting the fix until the kernel is fixed might be a good idea for Squeeze. Cheers, -- Yves-Alexis -- System Information: Debian Release: squeeze/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.32-5-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101123125031.3943.73630.report...@vixen
Bug#495888: numlock activated at X startup on powerbook G4 too
On dim., 2009-11-15 at 11:25 -0500, Barry Schatz wrote: > Hello, > > The bug you reported has not been active in over a year. If the bug > still > exists, please say so. If not, can you tell me how/when it was fixed? I barely boot the powerbook under Linux nowadays, but I just did and it seems the numlock is not activated. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#516544: libdrm-dev header conflicts with linux-libc-dev
Package: libdrm-dev Version: 2.4.4+git+20090205+8b88036-1 Severity: serious Justification: undeclared file conflict Hey, trying to install linux-libc-dev 2.6.28-1 along with libdrm-dev 2.4.4+git+20090205+8b88036-1 leads to dpkg complaining: Preparing to replace linux-libc-dev 2.6.26-13 (using .../linux-libc-dev_2.6.28-1_amd64.deb) ... Unpacking replacement linux-libc-dev ... dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.28-1_amd64.deb (--unpack): trying to overwrite `/usr/include/drm/i915_drm.h', which is also in package libdrm-dev Errors were encountered while processing: /var/cache/apt/archives/linux-libc-dev_2.6.28-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) There was an open bug against linux-libc-dev asking for a Replaces: for previous drm versions, which is indeed present. But headers are present in libdrm-dev built from drm-snapshot. Cheers, -- Yves-Alexis -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-rc5+thinkpad-00190-g5f0cd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libdrm-dev depends on: ii libdrm-inte 2.4.4+git+20090205+8b88036-1 Userspace interface to Intel-speci ii libdrm-nouv 2.4.4+git+20090205+8b88036-1 Userspace interface to Nouveau-spe ii libdrm2 2.4.4+git+20090205+8b88036-1 Userspace interface to kernel rend libdrm-dev recommends no packages. libdrm-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509030: xfce4-terminal: Window decoration are not drawn even when enabled
severity 509030 normal reassign 509030 xserver-xorg-video-neomagic thanks On lun, 2008-12-29 at 18:15 +1100, Mark Purcell wrote: > On Friday 19 December 2008 02:37:40 john.lindg...@tds.net wrote: > This RC bug seems to of been brought to ground with two workarounds > logged in the report. > > Given the work todate, what is the proposed conclusion for this bug > for lenny? > 1. Downgrade to normal/ important - leave open as a record of the > issue, and/ or > 2. Upgrade neomagic package to force NoAccel/ XLIB_SKIP_ARGB_VISUALS > and close bug? I would say both, but upgrading neomagic might not be a good idea. Documenting the second workaround in README.Debian in neomagic package would be a good idea too. And I could do the same in xfce4-terminal package. Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#509035: drm-snapshot: update drm snapshot?
On mer, 2008-12-17 at 19:47 +0100, Yves-Alexis Perez wrote: > Package: drm-snapshot > Severity: wishlist > > Hey, > > as requested on #debian-x it'd be nice to have an updated snapshot for > drm, as recent, KMS enabled xorg intel driver needs at least 2.4.2. As libdrm 2.4.3 is now, the snapshot could be replaced by it :) Cheers and thanks, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#509030: [Pkg-xfce-devel] Bug#509030: xfce4-terminal: Window decoration are not drawn even when enabled
On jeu, 2008-12-18 at 07:24 +0100, Yves-Alexis Perez wrote: > reassign 509030 xserver-xorg-video-neomagic > thanks > On mer, 2008-12-17 at 21:25 -0600, john.lindg...@tds.net wrote: > > > > I just tried the VESA driver, and Terminal works correctly with that. > > Based on that, I'm guessing it's either a problem with the NeoMagic > > driver or with my laptop. More likely my laptop. > > Thanks for analysing it. I'll reassign to the neomagic driver, but it's > still weird why it happens on upgrading xfce4-terminal. Also, could you try to: export XLIB_SKIP_ARGB_VISUALS=1 before running xfce4-terminal? -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509035: drm-snapshot: update drm snapshot?
Package: drm-snapshot Severity: wishlist Hey, as requested on #debian-x it'd be nice to have an updated snapshot for drm, as recent, KMS enabled xorg intel driver needs at least 2.4.2. Thanks for your time! Cheers, -- Yves-Alexis -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-rc8+for-airlied-00315-g813d036 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#504739: severity of 504739 is minor
# Automatically generated email from bts, devscripts version 2.10.13~bpo40+1 # As an Xorg user, I agree with Julien severity 504739 minor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495888: numlock activated at X startup on powerbook G4 too
On Mon, Nov 03, 2008 at 09:31:19PM +0900, Charles Plessy wrote: > Yes, it is a IBM-SK-8845, which happens to have a problem with numlock. But > apart from this I really love it. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502161 Ok, so that means the code sure lies in ppc xorg code, or something like that, independantly of the keyboard. (btw, is this keyboard usb or ps/2?) Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#448467: xserver-xorg-video-intel: Thinkpad brightness keys don't work
On dim, 2008-11-02 at 19:48 +0100, Marcus Better wrote: > The brightness keys now work correctly for me even when selecting > "kernel" mode. I'm running kernel 2.6.27, xserver-xorg-video-intel > 2:2.3.2-2+lenny5, xserver-xorg-core 2:1.4.2-7. Perhaps this bug can be > closed. Do you use gnome-power-manager? Using native kernel stuff, one needs 2.6.28 which includes opregion support. Not sure about the requirements for xserver-xorg-video-intel. Sometimes it doesn't work after xset puts the display to sleep and I have to switch back to console and get back to X to make them work. Cheers, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Re: [Pkg-xfce-devel] Bug#490013: Bug#490013: xfce4-xkb-plugin: Not starting when layout 'ro' with variant 'std' is used
On Wed, Jul 09, 2008 at 01:06:54PM +0300, Igor Stirbu wrote: > > This one sure doesn't look good. I'm not an xkb expert but it maybe it > > manages to confuse the plugin. What was the result before xkeybord > > upgrade? > > I would gladly show if I could get the older version of the package. Is > there a way to do that? Maybe try in testing or in snapshot.debian.net > > I guess there are two bugs. I don't think the symname is correct when > > using ro,us. But it shouldn't confuse the plugin like this. > > Should we contact the xkb-data team? yeah, it'd be a good idea. xkb-data maintainers, could you look at #490013 and tell us what you think? Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#448467: news about Thinkpad brightness keys situation
On lun, 2008-05-05 at 09:37 -0700, Jesse Barnes wrote: > This is an X server & driver problem. I fixed it recently, so if you build > the Intel X driver against new server bits (or just wait until 1.5), > xbacklight should fetch the current value. Ok, I'll stay tuned on this and report back with X 1.5 > > > That's even without trying brightness keys. > > > > Pressing brightness keys generates here acpi events video LCD0 87/86 (with > > some delay, but I guess this one is a kernel problem). Nobody seems to > > catch it, nor hal, nor powersaved, nor X driver. > > I think in some kernel versions it'll send a keyboard event that you can make > a desktop applet catch? In 2.6.25 there's a brightness_switch_enable for video module, which can be used to tell kernel not to mess with the brightness, and just warn userspace. When this is set, I can run gnome-power-manager to manage the brightness, and it correctly catch brightness keys, so it works. What I'd like is to manage this in the kernel, but it's not really related to this bug, so I'll check on that later, when it's fixed. Cheers, and thanks for your time. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#448467: news about Thinkpad brightness keys situation
Hi, I wanted to ask if there was any progress on the understanding of the situation? I have a Thinkpad T61 (8897 with intel G965), running Linux 2.6.25 (vanilla+thinkpad-acpi 0.19-20080321, but I can test with debian 2.6.25) and xserver-xorg-video-intel 2.3.0-1 (experimental). Brightness keys sure don't work out of the box (nor in console nor in Xorg). acpid, powersaved and hald are running. I can stop them for testing if needed. The driver by default uses the BACKLIGHT_CONTROL "kernel". xbacklight works fine. I have a /sys/class/backlight/acpi_video0 and 1. acpi_video0 does nothing, but using acpi_video1 and echo'ing 0-15 to brightness works. But in that case, xbacklight is lost. xbacklight =100 # brightness is at full level cat /sys/class/backlight/acpi_video1/actual_brightness 15 # acpi_video1 agree echo 0 > /sys/class/backlight/acpi_video1/brightness # brightness is at minimum level (but is not off, while it has worked at one # time) cat /sys/class/backlight/acpi_video1/actual_brightness 0 # acpi_video1 agree xbacklight 100 # xbacklight disagree. That's even without trying brightness keys. Pressing brightness keys generates here acpi events video LCD0 87/86 (with some delay, but I guess this one is a kernel problem). Nobody seems to catch it, nor hal, nor powersaved, nor X driver. I don't know what's the role of everybody involved, from the enduser pov, something is wrong. If you need more information, please ask, I'd be glad to provide stuff. Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411639: add a file to allow .xsessionrc to be sourced at login
Would it be ok to put this file /etc/X11/Xsession.d so user can have a .xsessionrc in her homedir? -- Yves-Alexis #Source user defined xsessionrc (locales and other environment variables) USERXSESSIONRC=$HOME/.xsessionrc if [ -r "$USERXSESSIONRC" ]; then . "$USERXSESSIONRC" fi
Bug#318076: xcomposite.pc in wrong location
I can confirm this bug, i guess xcomposite.pc should be in /usr/lib/pkgconfig/ and not /usr/X11R6/lib/pkgconfig At the moment pkg-config doesnt find xcomposite.pc so configure script (for xfwm package) doesnt find it. Exporting PKG_CONFIG_PATH is a workaround (which should work even in debian/rules file for xfwm4 package) but it's only a workaround. Would it be possible to move this file ? Regards, -- Yves-Alexis Perez -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
