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",

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

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

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

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 disable

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

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

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,

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

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

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 >

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. >

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

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.

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

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

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.

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

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

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

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 po...@debian.org (21/01/2011): reassign 610743 xserver-xorg-video-intel thanks (might be xserver-xorg-core instead.) Following your blog

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

/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]