Bug#1064396: libinput: install udev files into /usr
Source: libinput Version: 1.25.0-1 Severity: normal Tags: patch trixie sid User: helm...@debian.org Usertags: dep17m2 We want to finalize the /usr-merge via DEP17 by moving all files to /usr. libinput installs files into /lib; these should be moved into the respective canonical locations in /usr/. Please find a patch attached. It has been build-tested. This should not be backported to bookworm. If you intend to backport, please use dh_movetousr instead or defer the placement of the unit files to udev.pc. If your package will change for the t64 transition or otherwise rename/split/move its binaries (packages) during trixie, please then upload to experimental and get in touch with the UsrMerge driver, please see the wiki [1]. Michael [1] https://wiki.debian.org/UsrMerge diff -Nru libinput-1.25.0/debian/changelog libinput-1.25.0/debian/changelog --- libinput-1.25.0/debian/changelog2024-02-05 13:20:23.0 +0100 +++ libinput-1.25.0/debian/changelog2024-02-21 14:23:22.0 +0100 @@ -1,3 +1,10 @@ +libinput (1.25.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install udev rules and helpers into /usr. (Closes: #-1) + + -- Michael Biebl Wed, 21 Feb 2024 14:23:22 +0100 + libinput (1.25.0-1) unstable; urgency=medium * New upstream release. diff -Nru libinput-1.25.0/debian/libinput10-udeb.install libinput-1.25.0/debian/libinput10-udeb.install --- libinput-1.25.0/debian/libinput10-udeb.install 2024-01-24 16:25:22.0 +0100 +++ libinput-1.25.0/debian/libinput10-udeb.install 2024-02-21 14:23:22.0 +0100 @@ -1,3 +1,3 @@ -lib/udev +usr/lib/udev usr/lib/*/libinput.so.10* usr/share/libinput diff -Nru libinput-1.25.0/debian/libinput-bin.install libinput-1.25.0/debian/libinput-bin.install --- libinput-1.25.0/debian/libinput-bin.install 2024-01-24 16:25:22.0 +0100 +++ libinput-1.25.0/debian/libinput-bin.install 2024-02-21 14:23:22.0 +0100 @@ -1,2 +1,2 @@ -lib/udev +usr/lib/udev usr/share/libinput diff -Nru libinput-1.25.0/debian/rules libinput-1.25.0/debian/rules --- libinput-1.25.0/debian/rules2024-01-24 16:25:22.0 +0100 +++ libinput-1.25.0/debian/rules2024-02-21 14:23:22.0 +0100 @@ -7,12 +7,12 @@ override_dh_auto_configure: dh_auto_configure -B build-deb -- \ -Ddocumentation=false \ - -Dudev-dir=/lib/udev + -Dudev-dir=/usr/lib/udev ifeq ($(with_udeb),yes) dh_auto_configure -B build-udeb -- \ -Ddocumentation=false \ - -Dudev-dir=/lib/udev \ + -Dudev-dir=/usr/lib/udev \ -Dlibwacom=false endif
Bug#950981: touchpad stopped working reliably
Am 10.02.20 um 07:15 schrieb Timo Aaltonen: > On 9.2.2020 11.20, Michael Biebl wrote: >> On Sun, 09 Feb 2020 09:17:49 +0100 Michael Biebl >> wrote: >> >>> Device: SynPS/2 Synaptics TouchPad >>> Kernel: /dev/input/event5 >>> Group: 8 >>> Seat: seat0, default >>> Size: 74x43mm >>> Capabilities: pointer gesture >>> Tap-to-click: disabled >>> Tap-and-drag: enabled >>> Tap drag lock: disabled >>> Left-handed: disabled >>> Nat.scrolling: disabled >>> Middle emulation: disabled >>> Calibration: n/a >>> Scroll methods: *two-finger edge >>> Click methods: *button-areas clickfinger >>> Disable-w-typing: enabled >>> Accel profiles: none >>> Rotation: n/a >> >> I re-installed 1.15.1 and here's the same output >> >> Device: SynPS/2 Synaptics TouchPad >> Kernel: /dev/input/event5 >> Group: 8 >> Seat: seat0, default >> Size: 53x24mm >> Capabilities: pointer gesture >> Tap-to-click: disabled >> Tap-and-drag: enabled >> Tap drag lock: disabled >> Left-handed: disabled >> Nat.scrolling: disabled >> Middle emulation: disabled >> Calibration: n/a >> Scroll methods: *two-finger edge >> Click methods: *button-areas clickfinger >> Disable-w-typing: enabled >> Accel profiles: none >> Rotation: n/a >> >> Notice how the size is much smaller. >> I suspect what happens is, that when I swipe into the outer areas >> libinput simply ignores those events due to the wrong dimensions. >> >> 74x43mm appears like the correct size, 53x24mm is way too small >> > > alright, needs to be reported upstream: > > https://gitlab.freedesktop.org/libinput/libinput/issues Can you give me some hints which information I should include in the upstream bug report?
Bug#950981: Info received (touchpad stopped working reliably)
touchpad speed is also way off with 1.15.1 (it's much slower then before) signature.asc Description: OpenPGP digital signature
Bug#950981: touchpad stopped working reliably
On Sun, 09 Feb 2020 09:17:49 +0100 Michael Biebl wrote: > Device: SynPS/2 Synaptics TouchPad > Kernel: /dev/input/event5 > Group:8 > Seat: seat0, default > Size: 74x43mm > Capabilities: pointer gesture > Tap-to-click: disabled > Tap-and-drag: enabled > Tap drag lock:disabled > Left-handed: disabled > Nat.scrolling:disabled > Middle emulation: disabled > Calibration: n/a > Scroll methods: *two-finger edge > Click methods:*button-areas clickfinger > Disable-w-typing: enabled > Accel profiles: none > Rotation: n/a I re-installed 1.15.1 and here's the same output Device: SynPS/2 Synaptics TouchPad Kernel: /dev/input/event5 Group:8 Seat: seat0, default Size: 53x24mm Capabilities: pointer gesture Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock:disabled Left-handed: disabled Nat.scrolling:disabled Middle emulation: disabled Calibration: n/a Scroll methods: *two-finger edge Click methods:*button-areas clickfinger Disable-w-typing: enabled Accel profiles: none Rotation: n/a Notice how the size is much smaller. I suspect what happens is, that when I swipe into the outer areas libinput simply ignores those events due to the wrong dimensions. 74x43mm appears like the correct size, 53x24mm is way too small signature.asc Description: OpenPGP digital signature
Bug#950981: touchpad stopped working reliably
Package: libinput10 Version: 1.15.1-1 Severity: important Hi Timo, I encounter a very nasty regression with the latest update of libinput. The touchpad in my X220 no longer works reliably. When I swipe over the touchpad area, sometimes the cursor simply stops moving. This happens sporadically. Downgrading to 1.14.3-1 fixes the issue immediately. libinput list-devices output (removed a few unrelated entries) Device: SynPS/2 Synaptics TouchPad Kernel: /dev/input/event5 Group:8 Seat: seat0, default Size: 74x43mm Capabilities: pointer gesture Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock:disabled Left-handed: disabled Nat.scrolling:disabled Middle emulation: disabled Calibration: n/a Scroll methods: *two-finger edge Click methods:*button-areas clickfinger Disable-w-typing: enabled Accel profiles: none Rotation: n/a Device: TPPS/2 IBM TrackPoint Kernel: /dev/input/event6 Group:9 Seat: seat0, default Capabilities: pointer Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: disabled Nat.scrolling:disabled Middle emulation: disabled Calibration: n/a Scroll methods: *button Click methods:none Disable-w-typing: n/a Accel profiles: flat *adaptive Rotation: n/a Device: ThinkPad Extra Buttons Kernel: /dev/input/event7 Group:10 Seat: seat0, default Capabilities: keyboard switch Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a (This output from libinput 1.14.3) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libinput10 depends on: ii libc6 2.29-10 ii libevdev2 1.8.0+dfsg-2 hi libinput-bin 1.14.3-1 ii libmtdev1 1.1.5-1.1 ii libudev1 244.2-1 ii libwacom2 1.1-2 libinput10 recommends no packages. libinput10 suggests no packages. -- no debconf information
Re: systemd: systemctl does not re-create display-manager.service symlink
Am 02.02.20 um 16:13 schrieb Yves-Alexis Perez: > 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? Can you show me the (complete) postinst code? signature.asc Description: OpenPGP digital signature
Re: systemd: systemctl does not re-create display-manager.service symlink
Control: retitle -1 Improve handling of display-manager.service symlink Control: clone -1 -2 -3 -4 -5 -6 -7 Control: reassign -1 gdm3 Control: reassign -2 lightdm Control: reassign -3 sddm Control: reassign -4 lxdm Control: reassign -5 xdm Control: reassign -6 slim Control: reassign -7 wdm On Thu, 09 Oct 2014 17:55:18 +0300 Andrei POPESCU wrote: > Package: systemd > Version: 215-5+b1 > Severity: normal > > Hi, > > # systemctl disable lightdm > Synchronizing state for lightdm.service with sysvinit using update-rc.d... > Executing /usr/sbin/update-rc.d lightdm defaults > Executing /usr/sbin/update-rc.d lightdm disable > insserv: warning: current start runlevel(s) (empty) of script `lightdm' > overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script > `lightdm' overrides LSB defaults (0 1 6). > Removed symlink /etc/systemd/system/display-manager.service. > # systemctl enable lightdm > Synchronizing state for lightdm.service with sysvinit using update-rc.d... > Executing /usr/sbin/update-rc.d lightdm defaults > insserv: warning: current start runlevel(s) (empty) of script `lightdm' > overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script > `lightdm' overrides LSB defaults (0 1 6). > Executing /usr/sbin/update-rc.d lightdm enable > The unit files have no [Install] section. They are not meant to be enabled > using systemctl. > Possible reasons for having this kind of units are: > 1) A unit may be statically enabled by being symlinked from another unit's >.wants/ or .requires/ directory. > 2) A unit's purpose may be to act as a helper for some other unit which has >a requirement dependency on it. > 3) A unit may be started when needed via activation (socket, path, timer, >D-Bus, udev, scripted systemctl call, ...). > > > I have to run 'dpkg-reconfigure lightdm' to have lightdm's postinst > recreate the display-manager.service symlink, which is not obvious. I think, the proper solution is, that gdm, lightdm etc drop this bit from their service file (in case they have added this previously) ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ]' This is not longer necessary, as all relevant x-display-managers ship a .service file nowadays. 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. Cloning, reassigning this bug report. Regards, Michael signature.asc Description: OpenPGP digital signature
Bug#798097: Restarting logind kills Xserver
Hi Julien Am 31.03.19 um 11:23 schrieb Julien Cristau: > On Thu, Mar 21, 2019 at 17:59:26 +0100, Michael Biebl wrote: > >> Julien, in case you are busy, I could offer to NMU. >> WDYT? >> > No objection. (Just git cherry-pick -x the upstream change and add a > changelog entry with the explanation.) I just rebuilt the xserver package with this patch applied and tested it again. Seems like something has regressed in the mean time. Now restarting logind still kill the (X) session, this time it looks like gnome-shell is crashing directly. Back then with stretch, this worked fine. So this needs further investigation and possibly additional changes in Xorg and/or gnome-shell. As it's not ready for buster, there is no point in applying this patch either, so I guess it's best to postpone this. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#798097: Restarting logind kills Xserver
On Thu, 21 Mar 2019 17:59:26 +0100 Michael Biebl wrote: > Hi Julien > > On Thu, 5 Oct 2017 09:39:11 +0200 Julien Cristau > wrote: > > On Sun, Aug 27, 2017 at 13:16:48 +0200, Michael Biebl wrote: > > > > > On Sun, 11 Oct 2015 16:22:24 +0200 Michael Biebl wrote: > > > > > > > We dropped the logind restart in systemd_226-4 for now and the > > > > xserver-xorg-core package gained a Breaks against older systemd > > > > versions. > > > > > > > > This is not a real fix yet, but it should be sufficient to not be RC. > > > > > > > > Thus downgrading to important. We still should change both logind and > > > > Xorg so logind can be restarted safely without wreaking havoc. > > > > > > Upstream logind/systemd has been fixed so it can be restarted safely > > > now, see https://github.com/systemd/systemd/pull/5600 > > > > > > This change is in systemd v234. > > > I suggest that we ship a patch that reverts [1] and xserver-xorg bumps > > > the breaks against systemd to << 234. > > > > > I don't want to ship a debian-specific patch for this. Is there a way > > for Xorg to detect logind has that bug fix? > > > > This patch was merged upstream. See > https://gitlab.freedesktop.org/xorg/xserver/merge_requests/150 > > Would be great if this patch could be applied for buster. This would > mean I could add the logind to systemd's postinst in buster+1. > If we don't get this Xorg fix into buster, we'd have to wait another > full release cycle. > > Julien, in case you are busy, I could offer to NMU. > WDYT? Bringing Timo and Andreas into the loop here as well. Would welcome your thoughts on how to proceed here. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#798097: Restarting logind kills Xserver
Hi Julien On Thu, 5 Oct 2017 09:39:11 +0200 Julien Cristau wrote: > On Sun, Aug 27, 2017 at 13:16:48 +0200, Michael Biebl wrote: > > > On Sun, 11 Oct 2015 16:22:24 +0200 Michael Biebl wrote: > > > > > We dropped the logind restart in systemd_226-4 for now and the > > > xserver-xorg-core package gained a Breaks against older systemd versions. > > > > > > This is not a real fix yet, but it should be sufficient to not be RC. > > > > > > Thus downgrading to important. We still should change both logind and > > > Xorg so logind can be restarted safely without wreaking havoc. > > > > Upstream logind/systemd has been fixed so it can be restarted safely > > now, see https://github.com/systemd/systemd/pull/5600 > > > > This change is in systemd v234. > > I suggest that we ship a patch that reverts [1] and xserver-xorg bumps > > the breaks against systemd to << 234. > > > I don't want to ship a debian-specific patch for this. Is there a way > for Xorg to detect logind has that bug fix? > This patch was merged upstream. See https://gitlab.freedesktop.org/xorg/xserver/merge_requests/150 Would be great if this patch could be applied for buster. This would mean I could add the logind to systemd's postinst in buster+1. If we don't get this Xorg fix into buster, we'd have to wait another full release cycle. Julien, in case you are busy, I could offer to NMU. WDYT? Regards, Michael
Bug#914238: libgl1-mesa-dri: browser stays white when opening a website (i965, Intel HD Graphics 520)
Hi Jochen On Tue, 20 Nov 2018 21:21:05 +0100 Jochen Sprickerhof wrote: > Package: libgl1-mesa-dri > Version: 18.2.5-1 > Severity: normal > > Hi, > > the latest version libgl1-mesa-dri (18.2.5-1) break epiphany-browser and > surf for me. > > Steps to reproduce: > > $ epiphany-browser kde.org > $ surf kde.org > > Both only produce a white page when the site is loaded. Some other site > (like debian.org) do work, however. It works again when downgrading this > package to 18.1.9-1. > > I can also make it work by only downgrading i965_dri.so to the old > version. Might be another duplicate of #914267 which is an issue in gcc-8 miscompiling mesa. You could try my patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914267#20 which switches to gcc-7. or use the pre-compiled binary packages from https://people.debian.org/~biebl/mesa/ This worked for me. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#914267: mesa: [regression] with Mesa 18.2.5-2 the charackter model in Tomb Raider is no longer rendered.
Control: severity -1 serious Hi mesa maintainers, after further contemplating about this, I think this bug is ugly enough and hard to diagnose for our users, that the package should not enter testing in this state. I'm thus raising the severity to RC which will prevent testing migration and also make the bug more visible to users. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: mesa: [regression] with Mesa 18.2.5-2 the charackter model in Tomb Raider is no longer rendered.
Control: reassign -1 src:mesa 18.2.5-2 Control: severity -1 important Control: clone -1 -2 Control: reassign -2 gcc-8 8.2.0-9 Control: retitle -2 gcc-8 miscompiles mesa Control: forwarded -2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 Control: tags -2 + patch Control: affects -2 src:mesa On Thu, 22 Nov 2018 02:32:35 +0100 GSR wrote:> Package: mesa > Version: 18.2.5-2 > Followup-For: Bug #914267 > > That looks like missing shaders. I hit a similar thing with mpv (just > blue window, sound but no video) after upgrading 18.2.5-1 => 18.2.5-2, > luckly showing some output that later helped with searches. > > ---8<--- > [vo/gpu/opengl] fragment shader compile log (status=0): > [vo/gpu/opengl] 0:36(27): error: invalid input layout qualifier used > [vo/gpu/opengl] > [vo/gpu/opengl] shader link log (status=0): error: linking with uncompiled/unspecialized shader > --->8--- > > Bug 914303 could be the same too, garbled or single color output could > mean shaders not working because they failed to compile. Looking up > the error text, I found the culprit could be gcc, creating faulty > mesa binaries. https://bugs.freedesktop.org/show_bug.cgi?id=108646 > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 I ran into a similar issue. I use vmware and hosts using 3D acceleration no longer start successfully. On stdout I get the error message NOT_IMPLEMENTED bora/mks/renderers/gl/GLShader.c:1887 I can confirm the findings of GSR that this appears to be a gcc-8 regression. Rebuilding src:mesa with gcc-7 fixed those issues for me. Might be a good idea to (temporarily) switch to gcc-7 depending on how long it takes until this fix is applied in gcc-8. The attached patch worked for me. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff -u mesa-18.2.5/debian/changelog mesa-18.2.5/debian/changelog --- mesa-18.2.5/debian/changelog +++ mesa-18.2.5/debian/changelog @@ -1,3 +1,11 @@ +mesa (18.2.5-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Force compilation against gcc-7, gcc-8 miscompiles mesa +See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 + + -- Michael Biebl Thu, 22 Nov 2018 03:32:38 +0100 + mesa (18.2.5-2) unstable; urgency=medium * Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev diff -u mesa-18.2.5/debian/control mesa-18.2.5/debian/control --- mesa-18.2.5/debian/control +++ mesa-18.2.5/debian/control @@ -6,6 +6,9 @@ Standards-Version: 4.1.4 Build-Depends: debhelper (>= 11), + gcc-7, + g++-7, + cpp-7, quilt (>= 0.63-8.2~), pkg-config, libdrm-dev (>= 2.4.92) [!hurd-any], diff -u mesa-18.2.5/debian/rules mesa-18.2.5/debian/rules --- mesa-18.2.5/debian/rules +++ mesa-18.2.5/debian/rules @@ -10,6 +10,9 @@ DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) +export CC = gcc-7 +export CXX = g++-7 + ifeq (,$(filter $(DEB_HOST_ARCH), armhf sh3 sh4)) buildflags = \ $(shell DEB_CFLAGS_MAINT_APPEND=-Wall DEB_CXXFLAGS_MAINT_APPEND=-Wall dpkg-buildflags --export=configure) signature.asc Description: OpenPGP digital signature
Bug#900095: FTBFS against xserver-xorg-core 1.20.0
Source: xserver-xorg-video-vmware Version: 13.2.1-1 Severity: serious The recent update of xserver-xorg-core to 1.20.0 makes the package FTBFS as can be seen by the latest binNMU https://buildd.debian.org/status/package.php?p=xserver-xorg-video-vmware make[3]: Entering directory '/<>/build/saa' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../saa -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libsaa_la-saa.lo `test -f 'saa.c' || echo '../../saa/'`saa.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../saa -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c ../../saa/saa.c -fPIC -DPIC -o .libs/libsaa_la-saa.o ../../saa/saa.c: In function 'saa_validate_gc': ../../saa/saa.c:399:31: error: implicit declaration of function 'fbGetRotatedPixmap'; did you mean 'fbGetScreenPixmap'? [-Werror=implicit-function-declaration] PixmapPtr pRotatedTile = fbGetRotatedPixmap(pGC); ^~ fbGetScreenPixmap ../../saa/saa.c:399:31: warning: nested extern declaration of 'fbGetRotatedPixmap' [-Wnested-externs] ../../saa/saa.c:399:31: warning: initialization makes pointer from integer without a cast [-Wint-conversion] In file included from ../../saa/saa.c:37:0: ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:424:5: note: in expansion of macro 'saa_swap' saa_swap(sgc, pGC, funcs); ^~~~ ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:426:5: note: in expansion of macro 'saa_swap' saa_swap(sgc, pGC, funcs); ^~~~ ../../saa/saa.c: In function 'saa_destroy_gc': ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:444:5: note: in expansion of macro 'saa_swap' saa_swap(sgc, pGC, funcs); ^~~~ ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:446:5: note: in expansion of macro 'saa_swap' saa_swap(sgc, pGC, funcs); ^~~~ ../../saa/saa.c: In function 'saa_change_gc': ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:454:5: note: in expansion of macro 'saa_swap' saa_swap(sgc, pGC, funcs); ^~~~ ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:456:5: note: in expansion of macro 'saa_swap' saa_swap(sgc, pGC, funcs); ^~~~ ../../saa/saa.c: In function 'saa_copy_gc': ../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] (priv)->saved_##mem = (real)->mem; \ ^ ../../saa/saa.c:464:5: note: in
Re: Bug#885318: systemd kills X or freezes it when logging out from last opened tty
Control: reassign -1 xserver-xorg-core Control: forcemerge 810660 -1 Am 29.12.2017 um 09:30 schrieb Awtul: > Changingif [ "$SHLVL" = 1 ] in .bash_logout to if [ "$SHLVL" = 2 ] > > solves my problem; now X doesn't crash and I can switch between my openbox > session (on tty1) > and other tty's (logged in or not) just fine. According to https://bugs.freedesktop.org/show_bug.cgi?id=93164, this can also be triggered via chvt, so I'm reassigning this to xserver-xorg-core and merging with the existing bug report to have all information in one place. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#846222: [Pkg-xfce-devel] Bug#846222: x11-common: Please provide a default xsession in /usr/share/xsessions
Another issue I noticed: gdm3 uses /etc/gdm3/Xsession sddm uses /etc/sddm/Xsession lightdm uses /etc/X11/Xsession to start this special default session. I wonder if there would be potential for unification (i.e. all affected display managers using the Xsession script from x11-common) or does someone know why it could be beneficial to keep separate Xsession scripts per display manager? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#846222: [Pkg-xfce-devel] Bug#846222: x11-common: Please provide a default xsession in /usr/share/xsessions
Am 06.11.2017 um 00:32 schrieb Michael Biebl: > On Tue, 29 Nov 2016 12:07:26 +0100 Yves-Alexis Perez <cor...@debian.org> >> 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. [..] > I would prefer though, if that xsession.desktop file is *not* provided > by x11-common, as some desktop environments might actually choose not > wanting to have such an entry in the display manager menu, and > x11-common is not really uninstallable. > So a separate binary package seems like the most flexible approach to me. > > lightdm's /usr/share/xsessions/lightdm-xsession.desktop file might be a > good basis for such a package. Another reason why it might be a good idea to ship that as a package separate from x11-common is, that as you mentioned, not all display manager might support that ExecStart=default feature. Only those that do could decide to add a Recommend or Depends on that new xsession-default package. If there is some agreement on this, I could prepare a patch for src:xorg which adds such a new xsession-default package. I think src:xorg would be the right source package for building such a package. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#846222: [Pkg-xfce-devel] Bug#846222: x11-common: Please provide a default xsession in /usr/share/xsessions
Hi On Tue, 29 Nov 2016 12:07:26 +0100 Yves-Alexis Perezwrote: > On Tue, 2016-11-29 at 11:52 +0100, Maximiliano Curia wrote: > > 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 :) Fwiw, we just discussed today to drop /usr/share/gdm/BuiltInSessions/default.desktop from gdm3 as well (which starts Xsession). It would be nice if such a xsession.desktop file would be provided by a common package, which invididual desktop environments can depend on, if they want. This would have the benefit, that we would have no duplication in all the different display manager. I would prefer though, if that xsession.desktop file is *not* provided by x11-common, as some desktop environments might actually choose not wanting to have such an entry in the display manager menu, and x11-common is not really uninstallable. So a separate binary package seems like the most flexible approach to me. lightdm's /usr/share/xsessions/lightdm-xsession.desktop file might be a good basis for such a package. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#798097: Restarting logind kills Xserver
On Sun, 11 Oct 2015 16:22:24 +0200 Michael Biebl <bi...@debian.org> wrote: > We dropped the logind restart in systemd_226-4 for now and the > xserver-xorg-core package gained a Breaks against older systemd versions. > > This is not a real fix yet, but it should be sufficient to not be RC. > > Thus downgrading to important. We still should change both logind and > Xorg so logind can be restarted safely without wreaking havoc. Upstream logind/systemd has been fixed so it can be restarted safely now, see https://github.com/systemd/systemd/pull/5600 This change is in systemd v234. I suggest that we ship a patch that reverts [1] and xserver-xorg bumps the breaks against systemd to << 234. [1] http://cgit.freedesktop.org/xorg/xserver/commit/?id=dc48bd653c7e1013e2d69e3f59ae3cbc0c893473 signature.asc Description: OpenPGP digital signature
Bug#867991: should provide xorg-driver-video
Package: xserver-xorg-core Version: 2:1.19.3-2 Severity: normal Tags: patch I use the modesetting driver provided by xserver-xorg-core for my Intel hardware. Yet xserver-xorg insist on pulling in other video drivers due to Depends: xserver-xorg-video-all | xorg-driver-video xserver-xorg-core should have a Provides: xserver-xorg-video so unneeded drivers can be uninstalled -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.166 ii libaudit1 1:2.7.7-1+b1 ii libbsd0 0.8.5-1 ii libc6 2.24-12 ii libdbus-1-3 1.10.20-1 ii libdrm2 2.4.81-2 ii libegl1-mesa 17.1.4-1 ii libepoxy0 1.3.1-3 ii libgbm1 17.1.4-1 ii libgcrypt20 1.7.8-2 ii libgl1-mesa-glx [libgl1] 17.1.4-1 ii libpciaccess0 0.13.4-1+b2 ii libpixman-1-0 0.34.0-1 ii libselinux1 2.6-3+b2 ii libsystemd0 233-10 ii libudev1 233-10 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.1-3 ii libxshmfence1 1.2-1+b2 ii udev 233-10 ii xserver-common2:1.19.3-2 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 17.1.4-1 ii libpam-systemd 233-10 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information diff --git a/debian/control b/debian/control index ccbefd65f..5f8203a5f 100644 --- a/debian/control +++ b/debian/control @@ -134,6 +134,7 @@ Provides: ${videoabi}, ${inputabi}, xserver-xorg-video-modesetting, + xorg-driver-video, Description: Xorg X server - core server The Xorg X server is an X server for several architectures and operating systems, which is derived from the XFree86 4.x series of X servers.
Bug#861683: Install xserver-xorg-legacy by default for stretch
Am 10.05.2017 um 07:32 schrieb Moritz Muehlenhoff: > On Tue, May 02, 2017 at 07:39:37PM +0200, Michael Biebl wrote: >> Same is true for users of startx. They need the suid wrapper provided by >> xserver-xorg-legacy in such a case. such a case == a non-KMS driver being in use. > That's not true. I use the text mode console nearly all the time and only > start X as needed via startx, that works fine without the setuid wrapper. What driver do you use? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#861683: Package: installation-reports GNOME is not Working
On Mon, 1 May 2017 00:28:59 -0500 Gerardo Floreswrote: > Package:installation-reports > Boot method: (Virtual box) > > Image version: > RC3 > Date: Abril 29 20717 > Machine: Virtual BOX DELL Presicion and Lenovo X230 > Processor: Xeon / icore 7 > Memory: En la virtual 2G / Virtual 2GB > Partitions: Basicos en una sola partición LVM > > Output of lspci -knn (o lspci -nn): «lspci -nn»)> > > Base System Installation Checklist: si dicha fase funcionó, «E» si presentó algún fallo y déjela en blanco si > no intentó o no usó esta opción.> > [O] = OK, [E] = Error (descríbalo a continuación), [ ] = didn't try it > > Initial boot: [E] <¿Funcionó el arranque inicial?> > Detect network card:[O] <¿Se configuró el hardware de red?> > Configure network: [O] <¿Se configuró la red?> > Detect CD: [O] <¿Se detectó la unidad de CD?> > Load installer modules: [O] <¿Se cargaron los módulos del instalador?> > Detect hard drives: [O] <¿Se detectaron los discos duros?> > Partition hard drives: [O] <¿Se particionó el disco duro?> > Install base system:[O] <¿Se instaló el sistema base?> > Clock/timezone setup: [O] <¿Se configuró bien la zona horaria?> > User/password setup:[O] <¿Se configuró correctamente el usuario?> > Install tasks: [O] <¿Se instalaron bien las tareas?> > Install boot loader:[O] <¿Se instaló el gestor de arranque?> > Overall install:[E] <¿Reinició correctamente?> > > Comments/Problems: > > Hi, I am writing because you have tried to install Debian 9 for a month, on > two different computers with virtual box. And I can not put Gnome. In the > installation on a computer I get a red screen. So I just put the base system > without graphical environment and then try to install the gnome, the next > reboot will not boot. On any of the other desktops no problem is installed. > Then > I continued testing on different computers and different configurations > and continued with the problem I was not allowed to install gnome on > reboot after the computer does not boot. And in any desktop without problem > and also with only text I have problem only happens with gnome. > Sorry for my english, in fact I'm using google translator. I hope it helps > them to have a shiny Debian, as always. And while happy with my Jessie it > works phenomenally :) Most likely a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861683 seeing that you installed this system using Virtualbox -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#861683: Install xserver-xorg-legacy by default for stretch
Source: xorg Version: 1:7.7+18 Severity: serious With virtualbox-dkms gone for stretch, trying to install GNOME inside Virtualbox will lead to gdm failing to start, as it tries to run Xorg as unprivileged user. This requires a KMS compatible driver though. Same is true for users of startx. They need the suid wrapper provided by xserver-xorg-legacy in such a case. Not having the Xorg.wrap suid wrapper is a worthwile goal, but I guess we are not quite there yet, as there are still to many popular cases where it's needed. I would thus like to see xserver-xorg-legacy added as a Recommends to one of the xorg packages. This means it would be installed on upgrades and new installations but users with a KMS compatible driver can uninstall it. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg depends on: ii x11-xkb-utils7.7+3+b1 ii xkb-data 2.19-1 ii xserver-xorg-core2:1.19.3-1 ii xserver-xorg-input-all 1:7.7+18 ii xserver-xorg-input-evdev [xorg-driver-input] 1:2.10.5-1 ii xserver-xorg-input-libinput [xorg-driver-input] 0.23.0-2 ii xserver-xorg-input-wacom [xorg-driver-input] 0.34.0-1 ii xserver-xorg-video-all 1:7.7+18 ii xserver-xorg-video-amdgpu [xorg-driver-video]1.2.0-1+b1 ii xserver-xorg-video-ati [xorg-driver-video] 1:7.8.0-1+b1 ii xserver-xorg-video-fbdev [xorg-driver-video] 1:0.4.4-1+b5 ii xserver-xorg-video-nouveau [xorg-driver-video] 1:1.0.13-3 ii xserver-xorg-video-radeon [xorg-driver-video]1:7.8.0-1+b1 ii xserver-xorg-video-vesa [xorg-driver-video] 1:2.3.4-1+b2 ii xserver-xorg-video-vmware [xorg-driver-video]1:13.2.1-1+b1 Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 13.0.6-1+b2 -- no debconf information
Re: Bug#858114: gdm3: Impossible to login for users created after system installation
Am 22.03.2017 um 03:56 schrieb Michel Dänzer: > Hmm, looks like the upcoming version 1.3.0-1 of > xserver-xorg-video-amdgpu might help, or the upcoming version 1:7.9.0-1 > of xserver-xorg-video-radeon. Michel, do you have any preference which package which should reassign this bug report to? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#858114: gdm3: Impossible to login for users created after system installation
Am 18.03.2017 um 14:57 schrieb franx.ricci: > Package: gdm3 > Version: 3.22.1-2 > Severity: normal > > Dear Maintainer, > > I have a new ASUS laptop and i just installed Debian stretch , removing > completely Windows 10. > > I creates three more users for this machine, with gnome users manager, but > nobody of them can do a correct login to his desktop. > > If i check the xorg log file of user that failes login i found these lines at > the end: > > ''' > [ 158.567] (II) RADEON(G0): [DRI2] VDPAU driver: radeonsi > [ 158.567] (EE) RADEON(G0): failed to initialise surface manager > [ 158.567] (EE) RADEON(G0): radeon_setup_kernel_mem failed > [ 158.567] (EE) > Fatal server error: > [ 158.567] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 > [ 158.567] (EE) > [ 158.567] (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > [ 158.567] (EE) Please also check the log file at > "/home/francesca/.local/share/xorg/Xorg.0.log" for additional information. > [ 158.567] (EE) > [ 158.578] (EE) Server terminated with error (1). Closing log file. > ''' > That looks like a driver/mesa or Xorg problem. Which version of xserver-xorg-core and libgl1-mesa-dri do you have installed. I'm not quite sure which driver you use, i.e. xserver-xorg-video-amdgpu or xserver-xorg-video-radeon. Maybe the X maintainers can chime in here. What kind of hardware do you have? Maybe this hardware needs firmware which is not installed. On a cursory glance this doesn't look like a gdm problem per se. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#845398: x11-common: Can't configure
Package: x11-common Version: 1:7.7+17 Followup-For: Bug #845398 Attached is a log file of running x11-common.postinst with set -x -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages x11-common depends on: ii lsb-base 9.20161101 x11-common recommends no packages. x11-common suggests no packages. -- Configuration Files: /etc/X11/Xsession.d/20x11-common_process-args changed [not included] -- debconf information: x11-common/xwrapper/allowed_users: Console Users Only x11-common/xwrapper/actual_allowed_users: console Setting up x11-common (1:7.7+17) ... + '[' -f /usr/share/debconf/confmodule ']' + . /usr/share/debconf/confmodule ++ '[' '!' '' ']' ++ PERL_DL_NONLAZY=1 ++ export PERL_DL_NONLAZY ++ '[' '' ']' ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/x11-common.postinst configure 1:7.7+16 + '[' -f /usr/share/debconf/confmodule ']' + . /usr/share/debconf/confmodule ++ '[' '!' 1 ']' ++ '[' -z '' ']' ++ exec ++ '[' '' ']' ++ exec ++ DEBCONF_REDIR=1 ++ export DEBCONF_REDIR + db_purge x11-common/xwrapper/allowed_users + _db_cmd 'PURGE x11-common/xwrapper/allowed_users' + _db_internal_IFS=' ' + IFS=' ' + printf '%s\n' 'PURGE x11-common/xwrapper/allowed_users' + IFS=' ' + IFS=' ' + read -r _db_internal_line + RET='20 Incorrect number of arguments' + case ${_db_internal_line%%[ ]*} in + return 20 dpkg: error processing package x11-common (--configure): subprocess installed post-installation script returned error exit status 20 dpkg: dependency problems prevent configuration of xserver-common: xserver-common depends on x11-common; however: Package x11-common is not configured yet. dpkg: error processing package xserver-common (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of xvfb: xvfb depends on xserver-common (>= 2:1.19.0-1); however: Package xserver-common is not configured yet. dpkg: error processing package xvfb (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of xfonts-utils: xfonts-utils depends on x11-common; however: Package x11-common is not configured yet. dpkg: error processing package xfonts-utils (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of xserver-xephyr: xserver-xephyr depends on xserver-common (>= 2:1.19.0-1); however: Package xserver-common is not configured yet. dpkg: error processing package xserver-xephyr (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of xwayland: xwayland depends on xserver-common (>= 2:1.19.0-1); however: Package xserver-common is not configured yet. dpkg: error processing package xwayland (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of xorg: xorg depends on xfonts-utils; however: Package xfonts-utils is not configured yet. dpkg: error processing package xorg (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: x11-common xserver-common xvfb xfonts-utils xserver-xephyr xwayland xorg
Re: Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'
Am 15.11.2016 um 14:03 schrieb Andreas Boll: > On Mon, Nov 14, 2016 at 06:47:00PM +0100, Michael Biebl wrote: >> Am 13.11.2016 um 19:43 schrieb Michael Biebl: >>> Am 13.11.2016 um 18:37 schrieb Sven Joachim: >>>> The toolchain has also changed quite a bit in the past four weeks, with >>>> gcc having pie enabled by default and binutils at a bleeding edge >>>> snapshot. Maybe one of those has triggered the build failure. >>> >>> That might well be it. Currently mutter still builds fine in stretch. >>> The new binutils should migrate to testing soon. >>> I can then retry the build on a mips porter machine with >>> 2.27.51.20161108-1 >> >> binutils 2.27.51.20161108-1 just migrated to stretch. mutter still >> builds fine in stretch with this version. So I'd say we can cross off >> binutils from the list of suspects. > > As Sven already mentioned these symbols are still available otherwise > Mesa would FTBFS as we strictly check those symbols in the build with > > override_dh_makeshlibs: > dh_makeshlibs -a -- -c4 > > Furthermore I've manually checked libegl1-mesa_12.0.4-2_mips.deb [1] > with nm that those symbols are still exported. > > Mesa could be still affected by a broken binutils. To cross out > binutils or other toolchain bugs we would need to rebuild Mesa > 12.0.3-3 (= version in testing) with the current toolchain and build > mutter against this rebuild of Mesa. > Michael, could you check this on a mips porter machine? > Unfortunately I can't install arbitrary versions on the porter boxes. All I get is either a sid or a stretch chroot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'
Am 13.11.2016 um 19:43 schrieb Michael Biebl: > Am 13.11.2016 um 18:37 schrieb Sven Joachim: >> The toolchain has also changed quite a bit in the past four weeks, with >> gcc having pie enabled by default and binutils at a bleeding edge >> snapshot. Maybe one of those has triggered the build failure. > > That might well be it. Currently mutter still builds fine in stretch. > The new binutils should migrate to testing soon. > I can then retry the build on a mips porter machine with > 2.27.51.20161108-1 binutils 2.27.51.20161108-1 just migrated to stretch. mutter still builds fine in stretch with this version. So I'd say we can cross off binutils from the list of suspects. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'
Am 13.11.2016 um 18:37 schrieb Sven Joachim: > The toolchain has also changed quite a bit in the past four weeks, with > gcc having pie enabled by default and binutils at a bleeding edge > snapshot. Maybe one of those has triggered the build failure. That might well be it. Currently mutter still builds fine in stretch. The new binutils should migrate to testing soon. I can then retry the build on a mips porter machine with 2.27.51.20161108-1 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#844227: Acknowledgement (FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString')
Looking at the git log for mutter, I don't find any changes between 3.22.1 and 3.22.2 which look like it could be the cause for this build failure. So I suspect it's a change in mesa. 3.22.1-2 (from 2016-10-15) successfully built against mesa 12.0.3-1 3.22.2-1 failed to build [1] against 12.0.4-2 @mesa maintainers: any ideas? [1] https://buildd.debian.org/status/fetch.php?pkg=mutter=mips=3.22.2-1=1479018257 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'
Source: mutter Version: 3.22.2-1 Severity: serious The latest build of mutter failed on mips, mipsel and mips64el with ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString' ./.libs/libmutter-cogl.so: undefined reference to `eglTerminate' collect2: error: ld returned 1 exit status This looks like a recent regression in either mutter or mesa, mutter 3.22.1 built fine on those architectures. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Re: Bug#827335: evince: assertion failed: (wayland_display->cursor_theme_name)
Am 11.10.2016 um 22:53 schrieb Jason Crain: > On Tue, Oct 11, 2016 at 09:44:48PM +0200, Michael Biebl wrote: >> Am 11.10.2016 um 19:52 schrieb Diane Trout: >>> --- debian/evince/etc/apparmor.d/usr.bin.evince 2016-10-10 >>> 23:32:09.826405495 -0700 >>> +++ /etc/apparmor.d/usr.bin.evince 2016-10-11 10:45:06.401131452 >>> -0700 >>> @@ -65,8 +65,9 @@ >>>owner @{HOME}/** rw, >>>owner /media/** rw, >>>owner @{HOME}/.local/share/gvfs-metadata/** l, >>>owner /{,var/}run/user/*/gvfs-metadata/** l, >>> + owner /{,var/}run/user/*/weston-shared-* rw, >> >> Does anyone know why this rule includes /var/run/user? >> We are talking about XDG_RUNTIME_DIR here, which is /run/user/ and I >> never saw it referenced as /var/run/user > > I don't know. If I delete every occurance of {,var/} from the file it > still works. It could be left over cruft from this release goal, to > transition from /var/run to /run: > https://wiki.debian.org/ReleaseGoals/RunDirectory I've tried running evince under GNOME/Wayland and I don't have a /run/user/*/weston-shared-* directory Since I know nothing about apparmor, I'd prefer having input from the apparmor and wayland maintainers first, if the proposed patch is sensible. I don't like to simply guess. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#821760: Please pull in xserver-xorg-input-libinput
Package: xserver-xorg-input-all Version: 1:7.7+14 Severity: normal Hi, GNOME 3.20 has dropped support for non-libinput mouse configurations [1] So any configuration changes you make in gnome-control-center won't have any effect unless xserver-xorg-input-libinput is installed, e.g. my tap-to-click touchpad settings had no effect otherwise [2] We quickly discussed this issue on #debian-gnome IRC where I suggested that we let one of the GNOME packages pull in xserver-xorg-input-libinput. pochu mentioned that doing this via xserver-xorg-input-all might be nicer. What's the state of xserver-xorg-input-libinput, Timo? Do you consider it ready for the masses and do we want to have it installed (and enabled) by default? Regards, Michael [1] https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=66c211ff24bec6a938d6a6a0dd8730f4689ef383 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821354 -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-input-all depends on: ii xserver-xorg-input-evdev 1:2.10.1-1+b1 ii xserver-xorg-input-synaptics 1.8.3-1+b1 ii xserver-xorg-input-vmmouse1:13.1.0-1+b1 Versions of packages xserver-xorg-input-all recommends: ii xserver-xorg-input-wacom 0.30.0-1+b1 xserver-xorg-input-all suggests no packages. -- no debconf information
Re: Bug#814365: Xorg.0.log in question
Control: severity -1 normal Control: reassign -1 xserver-xorg-core Am 10.02.2016 um 22:09 schrieb Send Me: > [ 4033.331] (II) UnloadModule: "evdev" > [ 4033.331] (II) systemd-logind: releasing fd for 13:78 > [ 4033.331] (EE) systemd-logind: failed to release device: Connection is > closed > [ 4033.331] (II) evdev: Power Button: Close > keeps on happening, until > [ 4033.331] (II) systemd-logind: releasing fd for 13:67 > [ 4033.331] (EE) systemd-logind: failed to release device: Connection is > closed > [ 4033.397] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error > [ 4033.397] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error > [ 4033.397] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error > [ 4033.397] (EE) systemd-logind: ReleaseControl failed: Connection is closed > [ 4033.397] (II) Server terminated successfully (0). Closing log file. > I think that this is the source of the problems. Looks like an X server issue to me. Thus reassigning. Please followup up with the exact version of xserver-xorg-core and the driver (version) you are using. Steps how to reproduce this issue will be helpful for the X maintainers as well. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bug#803184: override: libpam-systemd:admin/standard
Am 27.10.2015 um 21:54 schrieb Cyril Brulebois: > Michael Biebl <bi...@debian.org> (2015-10-27): >> I've CCed debian-b...@lists.debian.org, debian-x@lists.debian.org and >> pkg-systemd-maintain...@lists.alioth.debian.org . Please CC them on >> replies. >> >> I especially would like to see an ACK from KiBi/debian-boot before the >> prio is bumped. > > Thanks for the ping. I don't see why that would be an issue on the > installer side, but maybe wait a few days to see if someone else has an > objection? Since no-one objected so far, it would be great if the priority of libpam-systemd would be bumped now. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#803254: xserver-xorg-core: Compile Xorg against libsystemd-daemon-dev, to enable socket activation support.
On Wed, 28 Oct 2015 13:03:08 +0100 Jeremiejigwrote: > Package: xserver-xorg-core > Version: 2:1.16.4-1+aptbuild5 > Severity: wishlist > > Dear Maintainer, > > I hope to see Xorg compiled with libsystemd to have systemd socket > activation support. > I checked the package xserver-xorg-core_1.17.2-3_amd64.deb (stretch) > with `grep sd_listen usr/lib/Xorg`, and got a negative match > `ldd usr/lib/Xorg` show that it isn't compiled with libsystemd > > My version of xserver-xorg is compiled with the flag > (--with-systemd-daemon) to see if which package was required for the > build (libsystemd-daemon-dev) libsystem-daemon-dev was a transitional compat package and it is now gone in unstable/testing. xserver-xorg-core's configure.ac should be updated to check for libsystemd instead (or in addition to the old name). It would probably make sense to get that fixed upstream first. Jeremiejig, could you forward this issue please? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#803184: override: libpam-systemd:admin/standard
Package: ftp.debian.org Severity: normal Hi, I'd like to see the priority of libpam-systemd bumped from optional to standard. The recent changes in xserver-xorg make it possible to run X without root privileges [1], which is awesome! This requires a proper logind session though, for which libpam-systemd needs to be installed (and enabled). While xserver-xorg-core added a Recommends on libpam-systemd, not everyone has Recommends enable. X is also not the only reason, why one want libpam-systemd installed. E.g. for SSH logins you also want proper logind sessions. The only environment where you don't want/need libpam-systemd is on a buildd or very specialised, minimal systems. I think prio:standard would fit that quite well. We also already have dbus (a dependency of libpam-systemd) already in prio:standard, libpam-rutime is prio:required. So no additional dependencies would be necessary. I've CCed debian-b...@lists.debian.org, debian-x@lists.debian.org and pkg-systemd-maintain...@lists.alioth.debian.org . Please CC them on replies. I especially would like to see an ACK from KiBi/debian-boot before the prio is bumped. Cheers, Michael [1] https://packages.qa.debian.org/x/xorg-server/news/20150821T010032Z.html [2] https://packages.qa.debian.org/x/xorg-server/news/20151027T170547Z.html
Re: Bug#803184: override: libpam-systemd:admin/standard
Am 27.10.2015 um 21:54 schrieb Cyril Brulebois: > Michael Biebl <bi...@debian.org> (2015-10-27): >> I especially would like to see an ACK from KiBi/debian-boot before the >> prio is bumped. > > Thanks for the ping. I don't see why that would be an issue on the > installer side, but maybe wait a few days to see if someone else has an > objection? Yeah, no hurry. No problem with waiting a week or two. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#798097: Restarting logind kills Xserver
Control: severity -1 important On Sat, 05 Sep 2015 17:40:32 +0200 Michael Biebl <bi...@debian.org> wrote: > Package: xserver-xorg-core > Version: 2:1.17.2-2 > Severity: serious > > I installed gdm3 from experimental which brought xserver-xorg-core from > experimental along with it. > This version has support for logind enabled, which apparently is > required to run gdm successfully. > > There is one particular issue though: Atm, we do restart systemd-logind > on upgrades in systemd.postinst. This kills your running X session > though, due to [1]. > > I'm not yet sure, how to address this, i.e. if we can revert this Xorg > patch and find a solution in X or stop restarting systemd-logind as part > of the upgrade process. > > I've decided to make this bug RC, since we need to fix that one way or > another. We dropped the logind restart in systemd_226-4 for now and the xserver-xorg-core package gained a Breaks against older systemd versions. This is not a real fix yet, but it should be sufficient to not be RC. Thus downgrading to important. We still should change both logind and Xorg so logind can be restarted safely without wreaking havoc. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#798097: Restarting logind kills Xserver
I filed this bug against systemd in the mean time: https://github.com/systemd/systemd/issues/1163 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#798097: Restarting logind kills Xserver
Package: xserver-xorg-core Version: 2:1.17.2-2 Severity: serious I installed gdm3 from experimental which brought xserver-xorg-core from experimental along with it. This version has support for logind enabled, which apparently is required to run gdm successfully. There is one particular issue though: Atm, we do restart systemd-logind on upgrades in systemd.postinst. This kills your running X session though, due to [1]. I'm not yet sure, how to address this, i.e. if we can revert this Xorg patch and find a solution in X or stop restarting systemd-logind as part of the upgrade process. I've decided to make this bug RC, since we need to fix that one way or another. Reading [1] again, I remember that systemd now has a facility to pass FDs, which is used to restart journald safely. Maybe Xorg upstream needs to be poked again. Michael [1] http://cgit.freedesktop.org/xorg/xserver/commit/?id=dc48bd653c7e1013e2d69e3f59ae3cbc0c893473 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.132 ii libaudit1 1:2.4.4-1 ii libc6 2.19-19 ii libdbus-1-3 1.10.0-1 ii libdrm2 2.4.64-1 ii libegl1-mesa 10.6.5-1 ii libepoxy0 1.3.1-1 ii libgbm1 10.6.5-1 ii libgcrypt20 1.6.3-2 ii libgl1-mesa-glx [libgl1] 10.6.5-1 ii libpciaccess0 0.13.4-1 ii libpixman-1-0 0.32.6-3 ii libselinux1 2.3-2+b1 ii libudev1 225-2~local0 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxfont1 1:1.5.1-1 ii libxshmfence1 1.2-1 ii udev 225-2~local0 ii xserver-common2:1.17.2-2 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 10.6.5-1 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information
Bug#797661: Fails to upgrade, file conflict with x11-common
Package: xserver-xorg-core Version: 2:1.17.2-2 Severity: serious The xserver-xorg-core package fails to upgrade due to a file conflict with x11-common: Unpacking xserver-xorg-core (2:1.17.2-2) over (2:1.17.2-1.1) ... dpkg: error processing archive /var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man5/Xwrapper.config.5.gz', which is also in package x11-common 1:7.7+9 Errors were encountered while processing: /var/cache/apt/archives/xserver-xorg-core_2%3a1.17.2-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.132 ii libaudit1 1:2.4.4-1 ii libc6 2.19-19 ii libdrm2 2.4.64-1 ii libegl1-mesa 10.6.4-1 ii libepoxy0 1.2-1 ii libgbm1 10.6.4-1 ii libgcrypt20 1.6.3-2 ii libgl1-mesa-glx [libgl1] 10.6.4-1 ii libpciaccess0 0.13.4-1 ii libpixman-1-0 0.32.6-3 ii libselinux1 2.3-2+b1 ii libudev1 225-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxfont1 1:1.5.1-1 ii libxshmfence1 1.2-1 ii udev 225-1 iu xserver-common2:1.17.2-2 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 10.6.4-1 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information
Bug#779754: [HEADS-UP] libsystemd transition
Hi On Mon, 13 Jul 2015 16:30:11 +0200 Michael Biebl bi...@debian.org wrote: Control: severity -1 important Hi, this is a heads-up that we plan to drop the libsystemd-* compat libraries in about two months. At that point, your package will FTBFS and this bug will be raised to serious. This is another friendly reminder that the compat libraries will be dropped in 2 weeks. Would be great if you can prepare an upload. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#759005: xdm: Missing xdm.service, can't use with systemd
Control: severity -1 important Hi! On Fri, 21 Nov 2014 16:02:15 +0100 Alessandro Ghedini gh...@debian.org wrote: Control: tags -1 patch On sab, ago 23, 2014 at 09:30:24 +0200, Sven Joachim wrote: On 2014-08-23 19:52 +0200, Kan-Ru Chen (é³ä¾å¦) wrote: Package: xdm Version: 1:1.1.11-1 Severity: important The xdm upstream ships a xdm.service file however it is not include in the xdm debian package. It would probably make sense to ship it, but care must be taken not to enable the service unless xdm is the default display manager. I wrote a patch that makes the display-manager.service systemd thing work with xdm (see attached patch). The patch does: 1 Patches the systemd service file to not start unless xdm is the default manager (as per /etc/X11/default-display-manager). 2 Removes the [Install] section in the systemd service file so that if the user manually enables the service it does nothing (so that it doesn't conflict with the default manager). 3 Creates the /etc/systemd/system/display-manager.service in postinst if xdm is the dfault manager. 4 Installs the systemd service file. Note that 1 and 3 above actually come from the lightdm package (I only removed the part where it reloads dbus, which is not used by xdm). I'm bumping the severity of this bug report back to important. Without a native .service file and xdm setting up the /etc/systemd/system/display-manager.service symlink, a lot of strange thinks can happen, like repeated start attempts of multiple display managers. For jessie we shipped a hack which mitigated a few of those problems, but not under all conditions. This is a Debian specific patch, which we are going to get rid of for Stretch and it will be removed in unstable soonish. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779754: [HEADS-UP] libsystemd transition
Control: severity -1 important Hi, this is a heads-up that we plan to drop the libsystemd-* compat libraries in about two months. At that point, your package will FTBFS and this bug will be raised to serious. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779754: weston: Transition to libsystemd
Control: tags -1 + patch Please find attached a patch which makes use of the new libsystemd library. Since your package already uses dh-autoreconf, no further changes should be necessary. Thanks for considering. Would be great if you can include that in your next upload. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff --git a/debian/control b/debian/control index 4519559..f561495 100644 --- a/debian/control +++ b/debian/control @@ -37,7 +37,7 @@ Build-Depends: libmtdev-dev, libpam0g-dev, libvpx-dev, - libsystemd-login-dev, + libsystemd-dev, libinput-dev (= 0.8.0), Standards-Version: 3.9.6 Homepage: http://wayland.freedesktop.org/ diff --git a/debian/patches/0001-Add-suport-for-new-libsystemd.patch b/debian/patches/0001-Add-suport-for-new-libsystemd.patch new file mode 100644 index 000..23b7762 --- /dev/null +++ b/debian/patches/0001-Add-suport-for-new-libsystemd.patch @@ -0,0 +1,28 @@ +From fe00842e1562d78f2811c8dad46125041cccab87 Mon Sep 17 00:00:00 2001 +From: Michael Biebl bi...@debian.org +Date: Thu, 9 Jul 2015 16:18:39 +0200 +Subject: [PATCH] Add suport for new libsystemd + +In systemd v209, the various libraries were merged into a single +libsystemd library. When checking for systemd 209, use the new library +name instead of the deprecated libsystemd-login. +--- + configure.ac | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/configure.ac b/configure.ac +index 2c55e1b..034f4a5 100644 +--- a/configure.ac b/configure.ac +@@ -349,7 +349,7 @@ AS_IF([test x$have_systemd_login = xyes], + [AC_DEFINE([HAVE_SYSTEMD_LOGIN], [1], [Have systemd-login])]) + AM_CONDITIONAL(HAVE_SYSTEMD_LOGIN, test x$have_systemd_login = xyes) + +-PKG_CHECK_MODULES(SYSTEMD_LOGIN_209, [libsystemd-login = 209], ++PKG_CHECK_MODULES(SYSTEMD_LOGIN_209, [libsystemd = 209], + [have_systemd_login_209=yes], [have_systemd_login_209=no]) + AS_IF([test x$have_systemd_login_209 = xyes], + [AC_DEFINE([HAVE_SYSTEMD_LOGIN_209], [1], [Have systemd-login = 209])]) +-- +2.1.4 + diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..844880f --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +0001-Add-suport-for-new-libsystemd.patch signature.asc Description: OpenPGP digital signature
Bug#750567: startx does not propagate the logind session
On Wed, Jun 11, 2014 at 03:01:01AM -0700, Ben Longbons wrote: rant IMO it should be considered the responsibility of logind maintainers to fix this bug, regardless of in what package, but apparently they consider it everyone else's problem to fix their breakage. I weep for systemd, because I love its architecture, but its community of blame-shifting is unbearable. How am I supposed to explain to people why I use linux, when I suddenly can't get wifi to work and they call it not a bug? /rant This issue is known and patches have been provided by the systemd maintainers See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747882 It's unfortunate that those haven't been applied yet to the xinit patches but there is not a lot that the systemd maintainers can do about that. Regards, Michael -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140711212658.ga17...@pluto.milchstrasse.xx
Bug#747882: systemd-logind not tracking startx sessions
On Mon, May 26, 2014 at 08:39:51AM +0200, Julien Cristau wrote: On Sun, May 25, 2014 at 18:54:40 +0200, Laurent Bigonville wrote: Hi, Apparently this has been fixed with different patches in Arch linux and upstream. I tested both and the Arch linux way seems to work (logind session marked as active), while backporting the upstream patches in the debian version doesn't seems to work. If the upstream changes don't work please take it upstream... Aside from the fact that those changes aren't in any upstream release yet and the debian xinit package being one upstream release behind, please also consider that debian/local/xserverrc is already debian specific. So adjusting xserverrc to properly work within Debian seems reasonable to me. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140527185150.ga9...@pluto.milchstrasse.xx
Bug#747882: systemd-logind not tracking startx sessions
On Sun, May 25, 2014 at 06:54:40PM +0200, Laurent Bigonville wrote: Hi, Apparently this has been fixed with different patches in Arch linux and upstream. I tested both and the Arch linux way seems to work (logind session marked as active), while backporting the upstream patches in the debian version doesn't seems to work. Arch linux patches can be found at: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/xorg-xinitid=f9f5de58df03aae6c8a8c8231a83327d19b943a1 https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/xorg-xinitid=645e47d624d43e4ec84060476ea7356fb5fd01ab Upstream patches: http://cgit.freedesktop.org/xorg/app/xinit/commit/startx.cpp?id=44915d6953076849b69a017f6fc8234b0f254362 http://cgit.freedesktop.org/xorg/app/xinit/commit/startx.cpp?id=1b23094a8606bf383ec6c7803a9cd300b1bb96a7 Any idea in which direction we should go? The arch patch looks pretty simple and clean to me. It has the additional benefit of only changing the vt if a logind session is registered, i.e. the XDG_VTNR env var is only set if logind is active. Michael -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140525172323.ga5...@pluto.milchstrasse.xx
Re: [Pkg-utopia-maintainers] Bug#747882: policykit-1: breaks xfce4-power-manager
Am 14.05.2014 15:05, schrieb Zhao Difei: I am using startx, is this sympton caused by systemd incompatibility? Sorry for didn't notice the systemd transition. On Wed, May 14, 2014 at 8:57 PM, Zhao Difei dif...@gmail.com wrote: Hi, Here's the output: ~$ loginctl SESSIONUID USER SEAT 1 1000 alphaseat0 ~$ loginctl show-session 1 Id=1 Timestamp=Wed 2014-05-14 20:50:52 CST TimestampMonotonic=57570110 DefaultControlGroup=systemd:/user/1000.user/1.session VTNr=1 TTY=/dev/tty1 Remote=no Service=login Leader=614 Audit=1 Type=tty Class=user Active=no Since you don't have an active session (according to logind), the resulting behaviour is expected. This is indeed a startx issue, since usually the display manager (lightdm, gdm) takes care of registering a logind session. IIRC if you want to use startx, you need to make sure pam_systemd is enabled for the console login and you need to teach startx to inherit the tty from the console login, i.e. if you logged in on tty1, X needs to start on tty1 (and not on tty7, which it usually does). See [0]. There this issue was re-assigned to xinit. I've CCed the X maintainers for their input. Are you ok if we re-assign this bug to xinit? Cheers, Michael [0] https://bugzilla.redhat.com/show_bug.cgi?id=806491 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#653327: x11-common: Quoting in 20x11-common_process-args breaks starting gnome-session with arguments.
severity 653327 important thanks Since this now also affects the new GNOME Classic mode in GNOME 3.8, I'm raising the severity to important. I'll add a wrapper script as workaround for now, but it would be nice to see this fixed properly in Xsession. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#653327: x11-common: Quoting in 20x11-common_process-args breaks starting gnome-session with arguments.
Am 11.10.2013 18:50, schrieb Michael Biebl: severity 653327 important thanks Since this now also affects the new GNOME Classic mode in GNOME 3.8, I'm raising the severity to important. I'll add a wrapper script as workaround for now, but it would be nice to see this fixed properly in Xsession. Since Julien asked me for further explanation of this problem, here we go: gnome-session can run different type of sessions which you can specify via the --session foo switch That is e.g. used in /usr/share/xsessions/gnome-classic.desktop as Exec=gnome-session --session classic That is passed on by the login manager (in my case gdm3) to /etc/X11/Xsession as gnome-session --session classic /etc/X11/Xsession.d/20x11-common_process-args fails to process that additional command line arguments, specifically STARTUP_FULL_PATH=$(/usr/bin/which $1 || true) $1 contains gnome-session --session classic, so which fails and doesn't return /usr/bin/gnome-session. One needs to strip the additional parameter, which the expression ${1%% *} does. Patch is from Didier Roche, see attachment. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? From 3036d68b3fdd702243f69672fbc824a99bc22193 Mon Sep 17 00:00:00 2001 From: Didier Roche didro...@ubuntu.com Date: Fri, 11 Oct 2013 22:52:39 +0200 Subject: [PATCH] Add support for session command containing args Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/512235 Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653327 --- debian/local/Xsession.d/20x11-common_process-args | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/local/Xsession.d/20x11-common_process-args b/debian/local/Xsession.d/20x11-common_process-args index 93e4653..149d1d2 100644 --- a/debian/local/Xsession.d/20x11-common_process-args +++ b/debian/local/Xsession.d/20x11-common_process-args @@ -45,7 +45,7 @@ case $# in ;; *) # Specific program was requested. -STARTUP_FULL_PATH=$(/usr/bin/which $1 || true) +STARTUP_FULL_PATH=$(/usr/bin/which ${1%% *} || true) if [ -n $STARTUP_FULL_PATH ] [ -e $STARTUP_FULL_PATH ]; then if [ -x $STARTUP_FULL_PATH ]; then STARTUP=$1 -- 1.8.4.rc3 signature.asc Description: OpenPGP digital signature
Bug#701372: xorg-server: ftbfs with GCC-4.8
On Sat, Feb 23, 2013 at 11:22:17AM +, Matthias Klose wrote: Package: src:xorg-server Version: 2:1.12.4-4 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. ../../dix/window.c:887:5: error: implicit declaration of function 'DeleteWindowFromAnySelections' [-Werror=implicit-function-declaration] I've uploaded and NMU based on Gerardo's patch. debdiff is attached, plus patches which can be applied via git am. Regards, Michael diff -u xorg-server-1.12.4/debian/changelog xorg-server-1.12.4/debian/changelog --- xorg-server-1.12.4/debian/changelog +++ xorg-server-1.12.4/debian/changelog @@ -1,3 +1,12 @@ +xorg-server (2:1.12.4-6.1) unstable; urgency=low + + * Non-maintainer upload. + * 10_Include-missing-selection-h.diff: Fix FTBFS with GCC 4.8. Include +selection.h in dix/window.c for the missing DeleteWindowFromAnySelections +function prototype. Patch by Gerardo Malazdrewicz (closes: #701372) + + -- Michael Biebl bi...@debian.org Thu, 25 Jul 2013 19:45:29 +0200 + xorg-server (2:1.12.4-6) unstable; urgency=low * Touch: Fix duplicate TouchBegin selection with virtual devices diff -u xorg-server-1.12.4/debian/patches/series xorg-server-1.12.4/debian/patches/series --- xorg-server-1.12.4/debian/patches/series +++ xorg-server-1.12.4/debian/patches/series @@ -12,0 +13 @@ +10_Include-missing-selection-h.diff only in patch2: unchanged: --- xorg-server-1.12.4.orig/debian/patches/10_Include-missing-selection-h.diff +++ xorg-server-1.12.4/debian/patches/10_Include-missing-selection-h.diff @@ -0,0 +1,20 @@ +Description: Fix build failure with GCC 4.8 + This patches fixes the following build failure: + + ../../dix/window.c:887:5: error: implicit declaration of function 'DeleteWindowFromAnySelections' [-Werror=implicit-function-declaration] + + by including selection.h, where the function is prototyped. + +Author: Gerardo Malazdrewicz gera...@malazdrewicz.com.ar +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701372 +--- xorg-server-1.12.4/dix/window.c2012-05-17 14:09:02.0 -0300 xorg-server-1.12.4.good/dix/window.c 2013-04-18 11:53:06.787521781 -0300 +@@ -131,6 +131,8 @@ + #include xace.h + #include exevents.h + ++#include selection.h ++ + #include X11/Xatom.h /* must come after server includes */ + + /** From ece1ad591b9e4022edd2766441adc35f845f3ac4 Mon Sep 17 00:00:00 2001 From: Michael Biebl bi...@debian.org Date: Thu, 25 Jul 2013 19:44:21 +0200 Subject: [PATCH 1/2] Fix build failure with GCC 4.8 This patches fixes the following build failure: ../../dix/window.c:887:5: error: implicit declaration of function 'DeleteWindowFromAnySelections' [-Werror=implicit-function-declaration] by including selection.h, where the function is prototyped. --- debian/patches/10_Include-missing-selection-h.diff | 20 debian/patches/series | 1 + 2 files changed, 21 insertions(+) create mode 100644 debian/patches/10_Include-missing-selection-h.diff diff --git a/debian/patches/10_Include-missing-selection-h.diff b/debian/patches/10_Include-missing-selection-h.diff new file mode 100644 index 000..873b14e --- /dev/null +++ b/debian/patches/10_Include-missing-selection-h.diff @@ -0,0 +1,20 @@ +Description: Fix build failure with GCC 4.8 + This patches fixes the following build failure: + + ../../dix/window.c:887:5: error: implicit declaration of function 'DeleteWindowFromAnySelections' [-Werror=implicit-function-declaration] + + by including selection.h, where the function is prototyped. + +Author: Gerardo Malazdrewicz gera...@malazdrewicz.com.ar +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701372 +--- xorg-server-1.12.4/dix/window.c 2012-05-17 14:09:02.0 -0300 xorg-server-1.12.4.good/dix/window.c 2013-04-18 11:53:06.787521781 -0300 +@@ -131,6 +131,8 @@ + #include xace.h + #include exevents.h + ++#include selection.h ++ + #include X11/Xatom.h /* must come after server includes */ + + /** diff --git a/debian/patches/series b/debian/patches/series index c89edaf..e05122f 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -10,3 +10,4 @@ 07_Revert-kinput-allocate-enough-space-for-null-charact.diff 08_xfree86_fix_ia64_inx_outx.diff 09_EXA-Track-source-mask-pixmaps-more-explicitly-for-Co.diff +10_Include-missing-selection-h.diff -- 1.8.3.2 From 7f78d952a19f48d8834944797fc6c9aa6a63c1a1 Mon Sep 17 00:00:00 2001 From: Michael Biebl bi...@debian.org Date: Thu, 25 Jul 2013 19:45:59 +0200 Subject: [PATCH 2/2] Update changelong and upload to unstable --- debian/changelog | 9 + 1 file changed, 9 insertions(+) diff --git a/debian/changelog b/debian/changelog index
Bug#710196: Uses deprecated HAL on non-Linux
Source: xorg-server Version: 2:1.12.4-6 Severity: serious User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: halectomy Hi, HAL has been deprecated and dead upstream for many years now so I'm going to request its removal from Debian [1]. Your package builds with HAL support on non-Linux plattforms. Please disable HAL support on those plattforms and if applicable, port it to native interfaces provided on those architectures. Regards, Michael [1] http://wiki.debian.org/HALRemoval -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130529002933.7547.11268.report...@pluto.milchstrasse.xx
Bug#710197: Uses deprecate HAL on non-Linux
Source: xorg Version: 1:7.7+3 Severity: serious User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: halectomy Hi, HAL has been deprecated and dead upstream for many years now so I'm going to request its removal from Debian [1]. Your package has a dependency on hal on non-Linux plattforms. Please remove that dependency for those plattforms and if applicable replace with something suitable on those architectures. Regards, Michael [1] http://wiki.debian.org/HALRemoval -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg depends on: ii libc6 2.17-3 ii x11-xkb-utils 7.7~1 ii xkb-data2.5.1-3 ii xserver-xorg-core 2:1.12.4-6 ii xserver-xorg-input-all 1:7.7+3 ii xserver-xorg-input-evdev [xorg-driver-input]1:2.7.0-1+b1 ii xserver-xorg-input-mouse [xorg-driver-input]1:1.7.2-3 ii xserver-xorg-input-vmmouse [xorg-driver-input] 1:12.9.0-1 ii xserver-xorg-input-wacom [xorg-driver-input]0.15.0+20120515-2 ii xserver-xorg-video-intel [xorg-driver-video]2:2.19.0-6 ii xserver-xorg-video-vesa [xorg-driver-video] 1:2.3.1-1+b1 Versions of packages xserver-xorg recommends: ii libgl1-mesa-dri 8.0.5-6 -- 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/20130529003151.7652.26655.report...@pluto.milchstrasse.xx
Bug#656685: xkb-data: new version breaks F10 key
I've NMUed xkeyboard-config with Julien and KiBi's permission. Debdiff is attached. Upload of a fixed gtk+3.0 is forthcoming. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff -u xkeyboard-config-2.5.1/debian/changelog xkeyboard-config-2.5.1/debian/changelog --- xkeyboard-config-2.5.1/debian/changelog +++ xkeyboard-config-2.5.1/debian/changelog @@ -1,3 +1,11 @@ +xkeyboard-config (2.5.1-2.1) unstable; urgency=low + + * Non-maintainer upload. + * Preserve Shift modifier so GTK3 apps can properly differentiate between +F10 and Shift+F10 (Closes: #656685). + + -- Michael Biebl bi...@debian.org Fri, 21 Sep 2012 18:12:52 +0200 + xkeyboard-config (2.5.1-2) unstable; urgency=low [ Ansgar Burchardt ] diff -u xkeyboard-config-2.5.1/debian/patches/series xkeyboard-config-2.5.1/debian/patches/series --- xkeyboard-config-2.5.1/debian/patches/series +++ xkeyboard-config-2.5.1/debian/patches/series @@ -2,0 +3 @@ +preserve-shift.diff only in patch2: unchanged: --- xkeyboard-config-2.5.1.orig/debian/patches/preserve-shift.diff +++ xkeyboard-config-2.5.1/debian/patches/preserve-shift.diff @@ -0,0 +1,37 @@ +From a4f62448819764f6f27ebcb86115734d0d57ea8d Mon Sep 17 00:00:00 2001 +From: Sergey V. Udaltsov s...@gnome.org +Date: Sun, 02 Sep 2012 07:57:52 + +Subject: Fixed Shift-F10 behaviour + +Preserving shift is essential for many applications +https://bugs.freedesktop.org/show_bug.cgi?id=45008 +--- +diff --git a/types/pc b/types/pc +index 01a5634..daebe74 100644 +--- a/types/pc b/types/pc +@@ -59,17 +59,19 @@ partial default xkb_types default { + }; + + type CTRL+ALT { +- modifiers = Control+Alt+Shift+LevelThree; ++modifiers = Control+Alt+Shift+LevelThree; + map[None] = Level1; + map[Shift] = Level2; + map[LevelThree] = Level3; + map[Shift+LevelThree] = Level4; +- map[Control+Alt] = Level5; ++map[Control+Alt] = Level5; ++preserve[Shift] = Shift; ++preserve[Shift+LevelThree] = Shift; + level_name[Level1] = Base; + level_name[Level2] = Shift; + level_name[Level3] = Alt Base; + level_name[Level4] = Shift Alt; +- level_name[Level5] = Ctrl+Alt; ++level_name[Level5] = Ctrl+Alt; + }; + +// Local eight level +-- +cgit v0.9.0.2-2-gbebe signature.asc Description: OpenPGP digital signature
Bug#656685: xkb-data: new version breaks F10 key
To fix this issue we apparently need both a fix in xkb-data and gtk+3.0. So I've unmerged the bug reports again and reassigned this one for xkb-data. The patch for xkb-data is available at http://cgit.freedesktop.org/xkeyboard-config/commit/?id=a4f62448819764f6f27ebcb86115734d0d57ea8d -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#656685: xkb-data: new version breaks F10 key
On 03.09.2012 23:26, Michael Biebl wrote: To fix this issue we apparently need both a fix in xkb-data and gtk+3.0. So I've unmerged the bug reports again and reassigned this one for xkb-data. The patch for xkb-data is available at http://cgit.freedesktop.org/xkeyboard-config/commit/?id=a4f62448819764f6f27ebcb86115734d0d57ea8d I can confirm that [1] for xkb-data and [2] for gtk+3.0 fix the issue. [1] http://cgit.freedesktop.org/xkeyboard-config/commit/?id=a4f62448819764f6f27ebcb86115734d0d57ea8d [2] http://bugzilla-attachments.gnome.org/attachment.cgi?id=223188 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#675022: Frequent lockups when using icedove (thunderbird)
Package: xserver-xorg-video-intel Version: 2:2.19.0-1 Severity: grave Since upgrading xserver-xorg-video-intel from 2:2.18.0-2 to 2:2.19.0-1 I get frequent lookups of X. So far this always happened when opening a large email folder in icedove(thunderbird). At this point the desktop is completely frozen and the system no longer reacts on keyboard input. I can still move the mouse, but X no longer reacts on clicks. This both happened in a composited DE (gnome-shell) and a non-composited DE (gnome-fallback/metacity). Downgrading to 2:2.18.0-2 reliably fixes the problem for me. My system is a X220 sandy bridge laptop, i.e a HD 3000 integrated graphics card. When the lockup happens I get a Xorg backtrace in Xorg.0.log (attached) As this particular error happened several times a day and I had to hard-reset my laptop, I'm filing with RC severity. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Nov 11 2011 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044664 May 20 10:59 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-2-amd64 (Debian 3.2.18-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon May 21 17:45:41 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 42647 May 20 23:56 /var/log/Xorg.1.log -rw-r--r-- 1 root root 56472 May 29 12:04 /var/log/Xorg.0.log udev information: - P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME=Power Button E: PHYS=LNXPWRBN/button/input0 E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: UDEV_LOG=3 E: USEC_INITIALIZED=12086995 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4 N: input/event4 E: BACKSPACE=guess E: DEVNAME=/dev/input/event4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4 E: DMI_VENDOR=LENOVO E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=68 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=12292596 E: XKBLAYOUT=de E: XKBMODEL=pc105 E: XKBVARIANT=nodeadkeys P: /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXVIDEO_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: KEY=3e000b 0 0 0 E: MODALIAS=input:b0019vp0006e-e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw E: NAME=Video Bus E: PHYS=LNXVIDEO/video/input0 E: PRODUCT=19/0/6/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: UDEV_LOG=3 E: USEC_INITIALIZED=14014544 P: /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11/event11 N: input/event11 E: BACKSPACE=guess E: DEVNAME=/dev/input/event11 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11/event11 E: DMI_VENDOR=LENOVO E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: MAJOR=13 E: MINOR=75 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=14017133 E: XKBLAYOUT=de E: XKBMODEL=pc105 E: XKBVARIANT=nodeadkeys P: /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 E: EV=21 E: ID_FOR_SEAT=input-acpi-PNP0C0D_00 E: ID_INPUT=1 E: ID_PATH=acpi-PNP0C0D:00 E: ID_PATH_TAG=acpi-PNP0C0D_00 E: MODALIAS=input:b0019vp0005e-e0,5,kramlsfw0, E: NAME=Lid Switch E: PHYS=PNP0C0D/button/input0 E: PRODUCT=19/0/5/0 E: PROP=0 E: SUBSYSTEM=input E: SW=1 E: TAGS=:seat: E: UDEV_LOG=3 E: USEC_INITIALIZED=12084770 P: /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2/event2 N: input/event2 E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2/event2 E: ID_INPUT=1 E: ID_PATH=acpi-PNP0C0D:00 E: ID_PATH_TAG=acpi-PNP0C0D_00 E: MAJOR=13 E: MINOR=66 E: SUBSYSTEM=input E: UDEV_LOG=3 E: USEC_INITIALIZED=12087029 P: /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 E: DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 E: EV=3 E: ID_FOR_SEAT=input-acpi-PNP0C0E_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-PNP0C0E:00 E: ID_PATH_TAG=acpi-PNP0C0E_00 E: KEY=4000 0 0 E:
Bug#675022: Acknowledgement (Frequent lockups when using icedove (thunderbird))
I can confirm that the proposed fix to disable FBC worked for me. Since i915.i915_enable_fbc=0, the GPU hangs didn't occur again. I'm wondering if xserver-xorg-video-intel should ship a modprobe file accordingly or if it is feasible to backport the fixes in 3.4 that were briefly mentioned in the upstream bug report. [1] https://bugs.freedesktop.org/show_bug.cgi?id=50455#c9 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#648022: Uses deprecated libgnome-window-settings which is scheduled to be removed
Hi Sean, On 27.01.2012 06:38, Michael Biebl wrote: Sean, any objections to apply this patch? If you are no longer interested in compiz / lack time I could offer to upload an NMU. I went ahead and uploaded an NMU to DELAYED/10. Just let me know if you are not ok with the proposed patch and I'll cancel the NMU. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#648022: Uses deprecated libgnome-window-settings which is scheduled to be removed
tags + 648022 thanks Seeing that compiz-gnome ships a g-c-c 2.x plugin which isn't useful anymore with gnome-control-center 3.x and a desktop file in /usr/share/gnome/wm-properties which ttbomk isn't used either anymore, I think the most straightforward way is to just drop compiz-gnome and the related build-deps. See the attached debdiff. Sean, any objections to apply this patch? If you are no longer interested in compiz / lack time I could offer to upload an NMU. In any case, feedback or any kind of reaction would be appreciated. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff -u compiz-0.8.4/debian/compiz-core.install compiz-0.8.4/debian/compiz-core.install --- compiz-0.8.4/debian/compiz-core.install +++ compiz-0.8.4/debian/compiz-core.install @@ -4 +3,0 @@ -usr/share/applications/compiz.desktop diff -u compiz-0.8.4/debian/rules compiz-0.8.4/debian/rules --- compiz-0.8.4/debian/rules +++ compiz-0.8.4/debian/rules @@ -41,6 +41,7 @@ confflags += --disable-static \ --disable-fuse \ --disable-kde \ + --disable-gnome \ --enable-kde4 \ --enable-librsvg \ --enable-gconf diff -u compiz-0.8.4/debian/control compiz-0.8.4/debian/control --- compiz-0.8.4/debian/control +++ compiz-0.8.4/debian/control @@ -8,9 +8,8 @@ kdebase-workspace-dev, libcairo2-dev, libdbus-glib-1-dev, libgconf2-dev, - libgl1-mesa-dev (= 6.5.1) | libgl-dev, libglib2.0-dev, libgnome-desktop-dev, - libgnomeui-dev, - libgnome-window-settings-dev, libgtk2.0-dev, libice-dev (= 1:1.0.1), + libgl1-mesa-dev (= 6.5.1) | libgl-dev, libglib2.0-dev, + libgtk2.0-dev, libice-dev (= 1:1.0.1), libmetacity-dev, libpango1.0-dev, libpng12-dev | libpng-dev, librsvg2-dev, libsm-dev (= 1:1.0.1), libtool, libwnck-dev, libxcomposite-dev (= 1:0.3-2), libxdamage-dev (=1:1.0.3), libxfixes-dev (= 1:4.0.1), libxinerama-dev, @@ -27,7 +26,7 @@ Package: compiz Architecture: all -Depends: compiz-core (= ${source:Version}), compiz-plugins (= ${source:Version}), compiz-gtk (= ${source:Version}), compiz-gnome (= ${source:Version}), libcompizconfig0, ${misc:Depends} +Depends: compiz-core (= ${source:Version}), compiz-plugins (= ${source:Version}), compiz-gtk (= ${source:Version}), libcompizconfig0, ${misc:Depends} Suggests: compizconfig-settings-manager Description: OpenGL window and compositing manager Compiz brings to life a variety of visual effects that make the Linux desktop @@ -93,17 +92,6 @@ This package contains a window decorator that uses KDE to provide a look and feel similar to that of the default KDE window manager. -Package: compiz-gnome -Architecture: any -Depends: compiz-gtk (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} -Description: OpenGL window and compositing manager - GNOME window decorator - Compiz brings to life a variety of visual effects that make the Linux desktop - easier to use, more powerful and intuitive, and more accessible for users - with special needs. - . - This package contains files needed to integrate compiz with the GNOME desktop - environment. - Package: compiz-plugins Architecture: any Depends: compiz-core (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} diff -u compiz-0.8.4/debian/changelog compiz-0.8.4/debian/changelog --- compiz-0.8.4/debian/changelog +++ compiz-0.8.4/debian/changelog @@ -1,3 +1,11 @@ +compiz (0.8.4-5.1) unstable; urgency=low + + * Non-maintainer upload. + * Disable GNOME integration as it uses deprecated interfaces which don't +work anymore and drop the compiz-gnome package. (Closes: #648022) + + -- Michael Biebl bi...@debian.org Fri, 27 Jan 2012 06:00:59 +0100 + compiz (0.8.4-5) unstable; urgency=low [ Sean Finney ] reverted: --- compiz-0.8.4/debian/compiz-gnome.install +++ compiz-0.8.4.orig/debian/compiz-gnome.install @@ -1,2 +0,0 @@ -usr/lib/window-manager-settings/libcompiz.so usr/lib/libgnome-window-settings1 -usr/share/gnome/wm-properties/compiz-wm.desktop reverted: --- compiz-0.8.4/debian/compiz-gnome.docs +++ compiz-0.8.4.orig/debian/compiz-gnome.docs @@ -1,4 +0,0 @@ -AUTHORS -NEWS -README -TODO signature.asc Description: OpenPGP digital signature
Bug#656682: minor graphical glitches since the latest upgrade
Package: libpixman-1-0 Version: 0.24.2-1 Severity: normal Hi, since the upgrade from 0.24.0 → 0.24.2 I notice minor graphical glitches in gtk2 apps. See the attached screenshot (from icedove). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpixman-1-0 depends on: ii libc6 2.13-24 ii multiarch-support 2.13-24 libpixman-1-0 recommends no packages. libpixman-1-0 suggests no packages. -- no debconf information attachment: before.pngattachment: after.png
Bug#656682: minor graphical glitches since the latest upgrade
On 20.01.2012 23:08, Cyril Brulebois wrote: Michael Biebl bi...@debian.org (20/01/2012): Some commits which might be reverted (one after the other): ee500cb2b1abf04ba40a8abfe358f6211d6078d1 Reverting this commit fixes the glitches. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#648022: Uses deprecated libgnome-window-settings which is scheduled to be removed
Any news/comments? We would really like to move on with removing the old control-center package. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#648022: Uses deprecated libgnome-window-settings which is scheduled to be removed
Source: compiz Version: 0.8.4-5 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs Hi, compiz uses libgnome-window-settings This library is built by control-center 2.x, which is scheduled to be removed soon (it has been replaced by gnome-control-center 3.x). The usage of gnome-window-settings seems to be optional and can be turned off via --disable-gnome, so /usr/lib/libgnome-window-settings1/libcompiz.so (shipped by compiz-gnome) would no longer be built. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/2008115823.3070.97023.report...@pluto.milchstrasse.xx
Bug#648022: Acknowledgement (Uses deprecated libgnome-window-settings which is scheduled to be removed)
Posting the short conversation from irc, so it is not lost: mbiebl do you know what the gnome support in compiz 0.8.x does? mbiebl it uses libgnome-window-settings, which is scheduled to be removed mbiebl and I'm wondering what to do about that seanius was it for cheating / cloning the keybindings maybe? my memory here is a bit vague seanius er, no, that's the libgnomecompat plugin seanius mbiebl: taking a brief look in ./gtk/gnome it looks like it's for registering the wm/decorator with gnome mbiebl seanius: so it shows up in gnome-control-center? seanius mbiebl: and it looks like it also hooks into config changes, so probably includes some kind of support for keeping gconf settings etc in sync seanius i don't actually have a system i can test on atm seanius just looking int he sources seanius mbiebl: yeah, and control-center stuff too mbiebl given that g-c-c 3 no longer uses libgnome-window-settings, I'm wondering if this gnome support is still functional mbiebl i.e. if we'd actually lose functionality by using --disable-gnome -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#554114: compize build failures due to missing libraries
tags 554114 + patch tags 639681 + patch thanks The attached patch fixes all build failures due to missing libraries. It compiles both with binutils and binutils-gold. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? diff -u compiz-0.8.4/debian/changelog compiz-0.8.4/debian/changelog --- compiz-0.8.4/debian/changelog +++ compiz-0.8.4/debian/changelog @@ -1,3 +1,10 @@ +compiz (0.8.4-4.1) unstable; urgency=low + + * Non-maintainer upload. + * Link against all necessary libraries. + + -- Michael Biebl bi...@debian.org Tue, 25 Oct 2011 12:08:38 +0200 + compiz (0.8.4-4) unstable; urgency=low * Drop libdbus-qt-1-dev from Build-Depends, as kindly requested by diff -u compiz-0.8.4/debian/patches/series compiz-0.8.4/debian/patches/series --- compiz-0.8.4/debian/patches/series +++ compiz-0.8.4/debian/patches/series @@ -24,0 +25 @@ +070_link_needed_libs.patch only in patch2: unchanged: --- compiz-0.8.4.orig/debian/patches/070_link_needed_libs.patch +++ compiz-0.8.4/debian/patches/070_link_needed_libs.patch @@ -0,0 +1,58 @@ +Index: compiz-0.8.4/configure.ac +=== +--- compiz-0.8.4.orig/configure.ac 2011-10-25 11:57:51.847926095 +0200 compiz-0.8.4/configure.ac 2011-10-25 12:07:34.612599752 +0200 +@@ -126,6 +126,8 @@ + xcursor\ + ice \ + sm \ ++ x11 \ ++ xext \ + libxml-2.0 \ + libxslt\ + libstartup-notification-1.0 = 0.7 +@@ -133,6 +135,8 @@ + PKG_CHECK_MODULES(COMPIZ, $COMPIZ_REQUIRES) + AC_SUBST(COMPIZ_REQUIRES) + ++AC_SEARCH_LIBS(dlopen, dl) ++ + DECORATION_REQUIRES=xrender + + PKG_CHECK_MODULES(DECORATION, $DECORATION_REQUIRES) +@@ -300,6 +304,7 @@ + if test x$use_gtk = xyes; then + PKG_CHECK_MODULES(GTK_WINDOW_DECORATOR, + xrender = 0.8.4 \ ++ xcursor \ + gtk+-2.0 = 2.8.0 \ + libwnck-1.0 \ + pangocairo, +@@ -514,11 +519,11 @@ + + if test -d $kde4libs; then + PKG_CHECK_MODULES(KDE4_WINDOW_DECORATOR, +- dbus-1 xdamage xcomposite QtCore = 4.5.0 QtGui QtDBus, ++ dbus-1 xdamage xcomposite x11 xext QtCore = 4.5.0 QtGui QtDBus, + [use_kde4=yes], [use_kde4=no]) + + KDE4_CFLAGS=-I$kde4incs +-KDE4_LIBS=-L$kde4libs -lkdecore -lkdecorations -lplasma ++KDE4_LIBS=-L$kde4libs -lkdecore -lkdecorations -lkdeui -lplasma + + QT4_MOC=`pkg-config QtGui --variable=moc_location` + QDBUSXML2CPP=`pkg-config QtGui --variable=exec_prefix`/bin/qdbusxml2cpp +Index: compiz-0.8.4/gtk/window-decorator/Makefile.am +=== +--- compiz-0.8.4.orig/gtk/window-decorator/Makefile.am 2009-10-14 04:34:41.0 +0200 compiz-0.8.4/gtk/window-decorator/Makefile.am 2011-10-25 12:04:58.614560913 +0200 +@@ -11,7 +11,8 @@ + @GTK_WINDOW_DECORATOR_LIBS@ \ + @GCONF_LIBS@ \ + @DBUS_GLIB_LIBS@ \ +- $(metacitylibs) ++ $(metacitylibs) \ ++ -lm + + gtk_window_decorator_SOURCES = \ + gtk-window-decorator.c signature.asc Description: OpenPGP digital signature
Bug#604967: Xprint: Please disable hal support
Hi! Am 20.04.2011 03:10, schrieb Drew Parsons: On Tue, 2011-04-19 at 11:30 +0200, Michael Biebl wrote: Am 19.04.2011 11:21, schrieb Michael Biebl: That said, should we just reassign this bug report to ftp.debian.org and ask for removal, now that squeeze is out? No, don't reassign it that way. I'm just back from holidays and am preparing to send the removal notifications out shortly. It's just that a whole heap of work matters turned up during the week I was gone which I should deal with first :) I've seen that you discussed this issue on debian-devel a while ago. What's the outcome of this decision resp. what's your plan now going forward? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#624398: [Pkg-utopia-maintainers] Bug#624398: xserver-xorg: postinst script wants to invoke-rc.d hal on GNU/kFreeBSD, but there is no more /etc/init.d/hal
Am 01.05.2011 15:34, schrieb Julien Cristau: On Thu, Apr 28, 2011 at 09:39:14 +0200, Michael Biebl wrote: The last step (triggering a hald start via D-Bus activation). It was initially added for applications which used a buggy approach to check if hald was running and disabled themselves otherwise, i.e. they didn't trigger a D-Bus activation request. All affected packages I know of have been fixed. Does this mean for example that if X is running, and I kill hal, it will be restarted automatically so it can tell the already running X server about possible new input devices? That should be possible. But then, that depends on how Xorg is setting up and using the Hal D-Bus interface, e.g. if it uses dbus_bus_start_service_by_name() or a Ping() to auto-start hal. I don't know the Xorg code, so I can't tell. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#624398: [Pkg-utopia-maintainers] Bug#624398: xserver-xorg: postinst script wants to invoke-rc.d hal on GNU/kFreeBSD, but there is no more /etc/init.d/hal
Am 01.05.2011 15:58, schrieb Julien Cristau: On Sun, May 1, 2011 at 15:53:17 +0200, Michael Biebl wrote: Am 01.05.2011 15:34, schrieb Julien Cristau: Does this mean for example that if X is running, and I kill hal, it will be restarted automatically so it can tell the already running X server about possible new input devices? That should be possible. But then, that depends on how Xorg is setting up and using the Hal D-Bus interface, e.g. if it uses dbus_bus_start_service_by_name() or a Ping() to auto-start hal. I don't know the Xorg code, so I can't tell. http://cgit.freedesktop.org/xorg/xserver/tree/config/hal.c Xorg seems to use libhal_ctx_init() in connect_and_register() and we ship http://patch-tracker.debian.org/patch/series/view/hal/0.5.14-5/02_libhal_dont_check_running.patch So it *should* work. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#624398: [Pkg-utopia-maintainers] Bug#624398: xserver-xorg: postinst script wants to invoke-rc.d hal on GNU/kFreeBSD, but there is no more /etc/init.d/hal
Am 28.04.2011 09:10, schrieb Julien Cristau: On Thu, Apr 28, 2011 at 03:01:32 -0400, Daniel Kahn Gillmor wrote: Package: xserver-xorg Version: 1:7.6+6 Severity: normal trying to install xserver-xorg on this kFreeBSD system failed in the postinst script (attached) when trying to invoke-rc.d hal restart. I was able to push through without hal by prefixing that line of /var/lib/dpkg/info/xserver-xorg.postinst with a : But i'm not sure what the right thing to do is to really resolve the issue. /usr/share/doc/hal/changelog.Debian.gz notes that the hal maintainer removed the init script several months ago. Any thoughts on what the right thing to do is? The right thing to do is making Xorg stop using hal on !linux. Bring the init script back, or give us another way to restart hal if it's running. The hal init script will not be re-introduced. If you want to see how hal handles (re)starting hald on upgrades, check the postinst script, I basically does get_pid() { [ -n $1 ] || return 0 dbus-send --system --dest=org.freedesktop.DBus --print-reply \ /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID \ string:$1 2/dev/null | awk '/uint32/ {print $2}' } # restart hald if it was running before pid=$(get_pid org.freedesktop.Hal) if [ -n $pid ]; then kill $pid 2/dev/null || true lshal /dev/null || true # will trigger through D-Bus activation fi The last step (triggering a hald start via D-Bus activation). It was initially added for applications which used a buggy approach to check if hald was running and disabled themselves otherwise, i.e. they didn't trigger a D-Bus activation request. All affected packages I know of have been fixed. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#624398: [Pkg-utopia-maintainers] Bug#624398: xserver-xorg: postinst script wants to invoke-rc.d hal on GNU/kFreeBSD, but there is no more /etc/init.d/hal
Am 28.04.2011 09:39, schrieb Michael Biebl: lshal /dev/null || true # will trigger through D-Bus activation fi The last step (triggering a hald start via D-Bus activation). ^ is probably no longer necessary today. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#604967: closed by Drew Parsons dpars...@debian.org (reply to dpars...@debian.org) (#604967: Xprint: Please disable hal support)
Am 19.04.2011 11:21, schrieb Michael Biebl: Am 08.02.2011 01:15, schrieb Debian Bug Tracking System: This is an automatic notification regarding your Bug report which was filed against the xprint package: #604967: Please disable hal support It has been closed by Drew Parsons dpars...@debian.org (reply to dpars...@debian.org). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Drew Parsons dpars...@debian.org (reply to dpars...@debian.org) by replying to this email. This bug has not been fixed. Please don't close it, as long as xprint is either updated to no longer use hal or removed from the archive completely. I'm reopening the bug report so I can track the progress of the hal removal. Just wanted to add: I packages are removed from the archive, the associated bug reports are automatically closed, so there is no need to do that prematurely. That said, should we just reassign this bug report to ftp.debian.org and ask for removal, now that squeeze is out? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#605750: Please remove hal from LSB init header
Am 03.12.2010 13:24, schrieb Michael Biebl: On 03.12.2010 10:54, Julien Cristau wrote: On Fri, Dec 3, 2010 at 03:05:14 +0100, Michael Biebl wrote: Package: xdm given that Xorg no longer uses hal for input hotplugging, the Should-Start/Should-Stop: hal in xdm's LSB init header no longer makes sense and should be removed. Xorg uses hal on kfreebsd. The hal version in experimental (0.5.14-4), which will be uploaded to sid after the squeeze release, will use D-Bus activation, to start hal on demand. So even on kfreebsd it should be safe to remove it then. FWIW, the D-Bus activated HAL version is in unstable/wheezy now. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#605750: Please remove hal from LSB init header
On 03.12.2010 10:54, Julien Cristau wrote: On Fri, Dec 3, 2010 at 03:05:14 +0100, Michael Biebl wrote: Package: xdm Version: 1:1.1.10-3 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: halectomy Hi, given that Xorg no longer uses hal for input hotplugging, the Should-Start/Should-Stop: hal in xdm's LSB init header no longer makes sense and should be removed. Xorg uses hal on kfreebsd. The hal version in experimental (0.5.14-4), which will be uploaded to sid after the squeeze release, will use D-Bus activation, to start hal on demand. So even on kfreebsd it should be safe to remove it then. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#604967: Please disable hal support
Package: xprint Version: 1.6.0-4 Severity: normal Tags: patch User: pkg-utopia-maintain...@lists.alioth.debian.org Hi, as we want to get rid of hal eventually, please disable hal support in xprint (or remove the package altogether). In case you decide for the former, a patch is attached. Cheers, Michael -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/control b/debian/control index 8cdbc2a..24a67b5 100644 --- a/debian/control +++ b/debian/control @@ -48,8 +48,6 @@ Build-Depends: libpixman-1-dev (= 0.13.2), libpciaccess-dev, libgcrypt-dev, - libdbus-1-dev [!hurd-i386], - libhal-dev [!hurd-i386], libselinux1-dev (= 2.0.80) [alpha amd64 arm armeb armel avr32 hppa i386 ia64 lpia m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc], libaudit-dev [alpha amd64 arm armeb armel avr32 hppa i386 ia64 lpia m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc], x11proto-xf86dri-dev, diff --git a/debian/rules b/debian/rules index 9ec70b9..7745d57 100755 --- a/debian/rules +++ b/debian/rules @@ -42,10 +42,8 @@ endif ifeq ($(DEB_HOST_ARCH), hurd-i386) dri = --disable-dri --disable-dri2 - config_hal = --disable-config-hal else dri = --enable-dri --enable-dri2 - config_hal = --enable-config-hal endif INSTALL=/usr/bin/install @@ -97,7 +95,7 @@ confflags += \ --disable-xf86bigfont \ --enable-dpms \ --disable-config-dbus \ - $(config_hal) \ + --disable-config-hal \ --enable-xfree86-utils \ --disable-xorg \ --disable-dmx \
Bug#581788: Please drop bogus b-dep on libdbus-qt-1-dev
Package: compiz Version: 0.8.4-3 Severity: important Hi, I'd like to get rid of dbus-qt3 as it is basically unmaintained and dead upstream. As it seems, compiz still has a b-dep on libdbus-qt-1-dev though. But compiz no longer builds the kde(3) window decorator (--disable-kde), so this b-dep should be removed. Please consider uploading compiz with this fix soonish so we can progress wit the removal of dbus-qt3. Thanks, Michael -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages compiz depends on: ii compiz-core 0.8.4-3+b1 OpenGL window and compositing mana ii compiz-gnome 0.8.4-3+b1 OpenGL window and compositing mana ii compiz-gtk0.8.4-3+b1 OpenGL window and compositing mana ii compiz-plugins0.8.4-3+b1 OpenGL window and compositing mana compiz recommends no packages. Versions of packages compiz suggests: ii compizconfig-settings-manager 0.8.4-2Compizconfig Settings Manager -- 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/20100515211209.12011.18266.report...@localhost.localdomain
Bug#556159: Bug#575881: Dbus generates an empty hex string in /var/lib/dbus/machine-id
On 30.03.2010 18:47, José Luis Castellón Sosa wrote: What kind of file system do you use? Can you be certain that it is not a hardware issue (faulty memory, hard drive etc.)? Can you reliably reproduce this problem? Can you also reproduce it with 1.2.24-1 from unstable? Thanks, Michael Filesystem is ext4. I'm certain it is not a hardware issue because I've tried it in 2 different PC's and the same problem happened in both. Could you describe in detail, how you installed your system (net-install, live-cd, gnome task during installation, etc) Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#531659: [Pkg-utopia-maintainers] Bug#531659: hal-info: Audio keys in MSI Wind don't work
reassign 531659 xorg thanks Stefan Monnier wrote: Package: hal-info Version: 20090309-1 Severity: normal [ I'm not sure how audio keys are supposed to work, so maybe this is not the right place to report it, but here it goes. ] When I hit the Fn-F7, Fn-F8, Fn-F9 keys (resp. volume-down, volume-up, mute) on my MSI Wind, nothing seems to happen. I don't get any setkeycodes errors in dmesg, and instead get unmapped keycoeds in X: xev tells me the three keys generate the X keycodes 174, 176, and 160 (respectively). Following some hints found at http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html, I tried to add a file /etc/hal/fdi/information/foo.fdi: ?xml version=1.0 encoding=ISO-8859-1? !-- -*- SGML -*- -- deviceinfo version=0.2 device !-- These are raw scancodes produced by the atkbd driver -- match key=@input.originating_device:info.linux.driver string=atkbd match key=/org/freedesktop/Hal/devices/computer:system.hardware.vendor prefix=MICRO-STAR match key=/org/freedesktop/Hal/devices/computer:system.hardware.product contains_outof=U-100 append key=input.keymap.data type=strlist00a0:mute/append append key=input.keymap.data type=strlist00ae:volumedown/append append key=input.keymap.data type=strlist00b0:volumeup/append append key=info.capabilities type=strlistinput.keymap/append /match /match /match /device /deviceinfo but it didn't seem to make any difference (tho it does appear in lshal, so the match statements seem to work right). I'd love to dig deeper, but as mentioned earlier I have no idea how such keys are *supposed* to work, so I'd be happy to be directed to some info explaining how such keys are supposed to be configured. Hi Stefan, first of all, hal no longer does any keymap remapping (it's done by udev nowadays), so this bug no longer belongs to hal-info. Second, if you already get X keycodes, then it is no hal/udev issue either afaik. Not entirely sure, which package to correctly reassign, so I'm using the general xorg package. Hopefully a more knowledgeable X maintainer can help you and if necessary reassign to a more correct package. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#515214: Xorg / HAL
Hi, just a few thoughts from a HAL co-maintainer: As no software is bug free (and HAL or D-Bus are certainly no exception), or a sysadmin has deliberatly decided to disable the D-Bus or HAL service from starting during boot, I think the Xorg server needs a safe/basic fallback anyway, if D-Bus or HAL is down and not accessible. One recent example is [1] or [2]. Leaving the user with no keyboard or mouse in such a case is imho not a sane behaviour. I guess it should just assume AutoAddDevices false in such a case and use the settings from xorg.conf (or if they are not set, use a basic us keyboard layout and mouse) If Xorg has such a fallback behaviour, demoting hal to recommends should be certainly possible and you wouldn't even have to bail out in postinst if AutoAddDevices has not been explictly set. Cheers, Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527860 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527872 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#515214: Xorg / HAL
Julien Cristau wrote: On Thu, May 14, 2009 at 17:42:16 +0200, Michael Biebl wrote: I guess it should just assume AutoAddDevices false in such a case and use the settings from xorg.conf (or if they are not set, use a basic us keyboard layout and mouse) How can I make a distinction between hal won't be started and hal takes a while to start? I guess you can't. But do you want to wait (possibly indefinitly) for hal to show up, leaving the user without a usable keyboard/mouse? Is your concern, that during bootup, hal takes to long to start and is not yet available when X starts? Wouldn't something like a 10sec timeout within Xorg help here? Assuming NoAutoAddDevices if hal isn't there when we start up means getting duplicated events whenever it shows up. I thought, if NoAutoAddDevices is used, that Xorg ignores devices reported via hal? Or maybe I'm just misunderstanding what you mean with duplicated events. (also, xorg.conf devices are currently set up before the hal stuff, so it's not clear -to me anyway- how to make this work without changing the dix/ddx interface) Can't comment on that. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: [Pkg-utopia-maintainers] restarting hal in xserver-xorg postinst?
Julien Cristau wrote: Hi, Hi when installing the new xserver-xorg, people seem to run into the following problem: since hal isn't restarted, it doesn't pick up the callout installed by xserver-xorg to set input.xkb.*, so if people restart X without rebooting they end up with a us keymap. So I'm wondering if it'd be ok to run 'invoke-rc.d hal restart' in xserver-xorg.postinst on upgrade (and probably initial install), or if there's a better way to fix this? The hal package already has an dpkg file trigger for /usr/share/hal/fdi. That means, hal will automatically be restarted, when the fdi file of xserver-xorg is updated / freshly installed. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#513545: xserver-xorg-input-synaptics: tapping and scrolling broken, speed too high
Package: xserver-xorg-input-synaptics Version: 0.99.3-3.1 Severity: important Hi, after upgrading to the latest packages from experimental, my synaptics touchpad is severly hampered: 1.) vertical scrolling no longer works 2.) tapping no longer work 3.) speed is too high (makes it hard to maneuver) I pulled some patches from the ubuntu package, and no everything is working again. The patches are: 103_enable_cornertapping.patch 104_always_enable_tapping.patch 105_always_enable_multifinger_click.patch 106_always_enable_vert_edge_scroll.patch 107_reduce_cursor_speed.patch (I'm not sure if all of them are needed). FWIW, I ran xinput list props without the patches (attached as props.debian) and with the ubuntu patches applied (attached as props.ubuntu). Cheers, Michael -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.27.13 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-input-synaptics depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libx11-6 2:1.1.5-2 X11 client-side library ii libxi62:1.2.0-1 X11 Input extension library ii xserver-xorg-core 2:1.5.99.901-2 Xorg X server - core server xserver-xorg-input-synaptics recommends no packages. Versions of packages xserver-xorg-input-synaptics suggests: pn gsynaptics | ksynaptics | qsy none (no description available) -- no debconf information Device 'SynPS/2 Synaptics TouchPad': Device Enabled (132): 1 Synaptics Edges (264): 1632, 5312, 1575, 4281 Synaptics Finger (265): 24, 29, 255 Synaptics Tap Time (266): 180 Synaptics Tap Move (267): 221 Synaptics Tap Durations (268): 180, 180, 100 Synaptics Tap FastTap (269):0 Synaptics Middle Button Timeout (270): 75 Synaptics Two-Finger Pressure (271):280 Synaptics Scrolling Distance (272): 100, 100 Synaptics Edge Scrolling (273): 0, 0, 0 Synaptics Two-Finger Scrolling (274): 1, 0 Synaptics Edge Motion Pressure (275): 29, 159 Synaptics Edge Motion Speed (276): 1, 401 Synaptics Edge Motion Always (277): 0 Synaptics Button Scrolling (278): 1, 1 Synaptics Button Scrolling Repeat (279):1, 1 Synaptics Button Scrolling Time (280): 100 Synaptics Off (281):0 Synaptics Guestmouse Off (282): 0 Synaptics Locked Drags (283): 0 Synaptics Locked Drags Timeout (284): 5000 Synaptics Tap Action (285): 0, 0, 0, 0, 0, 0, 0 Synaptics Click Action (286): 1, 1, 1 Synaptics Circular Scrolling (287): 0 Synaptics Circular Scrolling Trigger (288): 0 Synaptics Circular Pad (289): 0 Synaptics Palm Detection (290): 0 Synaptics Palm Dimensions (291):10, 199 Synaptics Pressure Motion (292):29, 159 Synaptics Grab Event Device (293): 1 Device 'SynPS/2 Synaptics TouchPad': Device Enabled (132): 1 Synaptics Edges (264): 1632, 5312, 1575, 4281 Synaptics Finger (265): 24, 29, 255 Synaptics Tap Time (266): 180 Synaptics Tap Move (267): 221 Synaptics Tap Durations (268): 180, 180, 100 Synaptics Tap FastTap (269):0 Synaptics Middle Button Timeout (270): 75 Synaptics Two-Finger Pressure (271):280 Synaptics Scrolling Distance (272): 100, 100 Synaptics Edge Scrolling (273): 1, 0, 0 Synaptics Two-Finger Scrolling (274): 1, 0 Synaptics Edge Motion Pressure (275): 29, 159 Synaptics Edge Motion Speed (276): 1, 401 Synaptics Edge Motion Always (277): 0 Synaptics Button Scrolling (278): 1, 1 Synaptics Button Scrolling Repeat (279):1, 1 Synaptics Button Scrolling Time (280): 100 Synaptics Off (281):0 Synaptics Guestmouse Off (282): 0 Synaptics Locked Drags (283): 0 Synaptics Locked Drags Timeout (284): 5000 Synaptics Tap Action (285): 2, 3, 0, 0, 1, 2, 3 Synaptics Click Action (286): 1, 2, 3 Synaptics Circular Scrolling (287): 0 Synaptics Circular Scrolling Trigger (288): 0 Synaptics
Bug#513545: xserver-xorg-input-synaptics: tapping and scrolling broken, speed too high
Brice Goglin schrieb: Michael Biebl wrote: Brice Goglin schrieb: Please send your log and config as well. xorg.conf is basically empty. Which synaptics driver did you have before the upgrade ? The one from Lenny ? Yes. But even with xserver-xorg from unstable, my xorg.conf did not have any special configuration regarding the synaptics touchpad. Fwiw I attached my current xorg.conf and also my old xorg.conf (when still using xorg from unstable). -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? # (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the manual page. # (Type man at the shell prompt.) # # This file is automatically updated on package upgrades *only* # if it has not been modified since the last upgrade of the # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh Section Device Identifier ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] Driver radeon BusID PCI:1:0:0 Option XAANoOffscreenPixmaps true Option AGPMode 4 EndSection Section Monitor Identifier Configured Monitor Option DPMS EndSection Section Screen Identifier Default Screen Monitor Configured Monitor # DefaultDepth24 SubSection Display Virtual 2960 1050 # Modes 1680x1050 EndSubSection EndSection xorg.conf.old Description: application/trash signature.asc Description: OpenPGP digital signature
Re: [Pkg-utopia-maintainers] Bug#506644: gnome-power-manager: Brightness applet does not change brightness
Josselin Mouette wrote: Le vendredi 05 décembre 2008 à 09:40 +0900, Charles Plessy a écrit : Le Thu, Dec 04, 2008 at 05:54:35PM +0100, Josselin Mouette a écrit : Does it work when you set the brightness with xbacklight? It doesn’t work anymore on my system, and I’m pretty sure it used to. The bug could lie in the X server somehow. Good point, xbacklight does not work on my system either, that's very bad news :( Yes, the same goes for me. X Utopia people: do you know what it means when neither g-p-m (through HAL) nor xbacklight (through XRandR) work to change the backlight of a display? Is it a problem in the kernel? Thanks for your insight, I can't control my backlight either (never could). Afaik it's because this function is hard wired and not controllable by software on my laptop. But if you say, that it worked for you before, than this is something different. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#497612: Acknowledgement (regression: artefacts when watching videos (xv))
FWIW I did a quick git bisect, and this is the commit that causes the regression: 15536739b0e68e25dbd89d5d517680d855077fab Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#452627: Acknowledgement (xinit: Please add ConsoleKit support)
reassign 452627 consolekit thanks I'm reassigning the bug to consolekit. I'll basically take the same approach as Ubuntu and provide a Xsession script within the consolekit package. So no patching of xinit is necessary. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#469142: xserver-xorg-video-mach64: Conflicting files with xserver-xorg-video-ati
Package: xserver-xorg-video-mach64 Version: 1:6.8.1~git20080301.d855d208 Severity: serious Justification: upgrade fails Hi, the upgrade of xserver-xorg-video-ati to the version in experimental failed, as xserver-xorg-video-mach64 has conflicting files with the old xserver-xorg-video-ati package. The problem very likely is a typo in the Replaces line in debian/control: s/xserver-xorg-driver-ati/xserver-xorg-video-ati/ The same is true for xserver-xorg-video-r128. Cheers, Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24.3 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-video-mach64 depends on: ii libc6 2.7-9 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.4.1~git20080131-1 Xorg X server - core server xserver-xorg-video-mach64 recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459507: Acknowledgement (xserver-xorg: Remove obsole init script on package upgrade)
And don't forget to clean up any existing symlinks! Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#459507: xserver-xorg: Remove obsole init script on package upgrade
Package: xserver-xorg Version: 1:7.3+9 Severity: normal Hi, it seems that the (obsolete) init script /etc/init.d/xserver-xorg is not removed on package upgrades. A way to correctly handle this conffile upgrade is described here: http://wiki.debian.org/DpkgConffileHandling Cheers, Michael -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2006-11-15 01:08 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1672764 2007-12-22 01:43 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 01) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1011 2008-01-04 03:39 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the manual page. # (Type man at the shell prompt.) # # This file is automatically updated on package upgrades *only* # if it has not been modified since the last upgrade of the # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh Section Device Identifier ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] Driver radeon BusID PCI:1:0:0 Option XAANoOffscreenPixmaps Option AGPMode 4 EndSection Section Monitor Identifier Configured Monitor Option DPMS EndSection Section Screen Identifier Default Screen Monitor Configured Monitor DefaultDepth24 SubSection Display Virtual 2960 1050 Modes 1680x1050 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 43595 2007-12-11 17:56 /var/log/Xorg.20.log -rw-r--r-- 1 root root 37976 2007-12-19 07:34 /var/log/Xorg.1.log -rw-r--r-- 1 root root 47732 2008-01-07 00:39 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20071212-2) Current Operating System: Linux pluto 2.6.23.12 #1 Wed Dec 19 06:44:03 CET 2007 i686 Build Date: 22 December 2007 01:30:34AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jan 6 23:29:17 2008 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (==) |--Input Device default pointer (==) |--Input Device default keyboard (==) The core pointer device wasn't specified explicitly in the layout. Using the default mouse configuration. (==) The core keyboard device wasn't specified explicitly in the layout. Using the default keyboard configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81d85a0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.4.0, module version = 1.0.0
Bug#452627: xinit: Please add ConsoleKit support
Package: xinit Version: 1.0.7-1 Severity: wishlist Tags: patch Hi, the attached patch adds support for ConsoleKit. It's taken from upstream BTS: https://bugs.freedesktop.org/show_bug.cgi?id=12378 It can be enabled with the --with-consolekit configure switch (a autoreconf run is required). You can find more info about what CK is at http://www.freedesktop.org/wiki/Software/ConsoleKit The pkg-utopia group plans to upload a CK enabled hal to unstable in the near future. This requires that login managers or xinit correctly registers new sessions within CK. gdm and kdm already have support for CK. Cheers, Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.8 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xinit depends on: ii cpp 4:4.2.1-6 The GNU C preprocessor (cpp) ii libc6 2.6.1-6GNU C Library: Shared libraries ii libx11-6 2:1.0.3-7 X11 client-side library ii x11-common1:7.3+6X Window System (X.Org) infrastruc xinit recommends no packages. -- no debconf information diff --git a/Makefile.am b/Makefile.am index babc2f3..9b912a3 100644 --- a/Makefile.am +++ b/Makefile.am @@ -24,8 +24,8 @@ XINITDIR = $(libdir)/X11/xinit bin_PROGRAMS = xinit bin_SCRIPTS = startx -xinit_CFLAGS = $(XINIT_CFLAGS) -DXINITDIR=\$(XINITDIR)\ -DBINDIR=\$(bindir)\ -xinit_LDADD = $(XINIT_LIBS) +xinit_CFLAGS = $(XINIT_CFLAGS) $(CK_CFLAGS) -DXINITDIR=\$(XINITDIR)\ -DBINDIR=\$(bindir)\ +xinit_LDADD = $(XINIT_LIBS) $(CK_LIBS) xinit_SOURCES =\ xinit.c diff --git a/configure.ac b/configure.ac index 1aee1d2..5775db3 100644 --- a/configure.ac +++ b/configure.ac @@ -47,6 +47,7 @@ DEFAULT_XMODMAP=xmodmap DEFAULT_TWM=twm DEFAULT_XCLOCK=xclock DEFAULT_XTERM=xterm +DEFAULT_CK=yes # You always want to specify the full path to the X server DEFAULT_XSERVER=${bindir}/X DEFAULT_XAUTH=xauth @@ -104,6 +105,20 @@ esac AC_SUBST(XINIT_CFLAGS) AC_SUBST(XINIT_LIBS) +# Check for ConsoleKit +AC_ARG_WITH(consolekit, +AS_HELP_STRING([--with-consolekit], [Use ConsoleKit in xinit]), + [CK=$withval], + [CK=$DEFAULT_CK]) +if test x$CK != xno ; then + PKG_CHECK_MODULES(CK, ck-connector, + have_conkit=yes, + [have_conkit=no; echo no]) + if test x$have_conkit = xyes ; then + AC_DEFINE(USE_CONKIT, 1, [Define if you have ConsoleKit]) + fi +fi + AC_PATH_PROGS(MCOOKIE, [mcookie], [$MCOOKIE], [$PATH:/bin:/usr/bin:/usr/lib:/usr/libexec:/usr/local/bin]) if test x$MCOOKIE != x ; then diff --git a/startx.cpp b/startx.cpp index 42421ef..998c7f8 100644 --- a/startx.cpp +++ b/startx.cpp @@ -222,6 +222,12 @@ EOF fi done +if [ x$display != x ]; then +export DISPLAY=$display +else +export DISPLAY=:0 +fi + #if defined(__SCO__) || defined(__UNIXWARE__) if [ $REMOTE_SERVER = TRUE ]; then exec SHELL_CMD ${client} diff --git a/xinit.c b/xinit.c index 46dee54..c2c4527 100644 --- a/xinit.c +++ b/xinit.c @@ -39,6 +39,12 @@ in this Software without prior written authorization from The Open Group. #include ctype.h #include stdint.h +#ifdef USE_CONKIT +#include ck-connector.h +#include X11/Xatom.h +static CkConnector *ckc = NULL; +#endif /* USE_CONKIT */ + #ifdef X_POSIX_C_SOURCE #define _POSIX_C_SOURCE X_POSIX_C_SOURCE #include signal.h @@ -521,6 +527,39 @@ processTimeout(int timeout, char *string) return( serverpid != pidfound ); } + +#ifdef USE_CONKIT +static void +register_new_session_with_console_kit (void) +{ + static char conkitbuf[256]; + DBusError error; + + ckc = ck_connector_new (); + if (ckc == NULL) { + Error (Cannot register with ConsoleKit: OOM creating CkConnector\n); + goto out; + } + + dbus_error_init (error); + if (!ck_connector_open_session (ckc, error)) { + Error (Cannot register with ConsoleKit: %s: %s\n, error.name, error.message); + goto out; + } + + /* If we managed to register with ConsoleKit, put the +* environment variable XDG_SESSION_COOKIE=cookie as second +* element in newenviron. See set_environment() where we +* earlier have made sure there is room... +*/ + conkitbuf[sizeof (conkitbuf) - 1] = '\0'; + snprintf (conkitbuf, sizeof (conkitbuf) - 1, XDG_SESSION_COOKIE=%s, ck_connector_get_cookie (ckc)); + newenviron[1] = conkitbuf; +out: + ; +} +#endif /* USE_CONKIT */ + static int startServer(char *server[]) { @@ -631,6 +670,12 @@ startServer(char *server[]) break; } +#ifdef USE_CONKIT + if (serverpid != -1 ) { + register_new_session_with_console_kit (); + } +#endif /*
Bug#448815: compiz: (cube) - Warn: Failed to load slide: freedesktop
Michel Dänzer schrieb: On Thu, 2007-11-01 at 07:55 +0100, Michael Biebl wrote: /usr/bin/compiz.real (cube) - Warn: Failed to load slide: freedesktop And the top of the cube is empty, there is no freedesktop.org logo. Make sure the png plugin is loaded (before the cube plugin). Shouldn't that be the default then? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448815: compiz: (cube) - Warn: Failed to load slide: freedesktop
Package: compiz Version: 1:0.6.2-0~emiscabpo+3~debian1 Severity: normal When running compiz --replace, I get Checking for Xgl: not present. xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log Detected PCI ID for VGA: 01:00.0 0300: 1002:4c66 (rev 01) (prog-if 00 [VGA]) Checking for texture_from_pixmap: not present. Trying again with indirect rendering: Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. Checking for nVidia: not present. Checking for FBConfig: present. Checking for Xgl: not present. Starting gtk-window-decorator /usr/bin/compiz.real (cube) - Warn: Failed to load slide: freedesktop And the top of the cube is empty, there is no freedesktop.org logo. Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages compiz depends on: ii compiz-cor 1:0.6.2-0~emiscabpo+3~debian1 OpenGL window and compositing mana ii compiz-gno 1:0.6.2-0~emiscabpo+3~debian1 OpenGL window and compositing mana ii compiz-kde 1:0.6.2-0~emiscabpo+3~debian1 OpenGL window and compositing mana ii compiz-plu 1:0.6.2-0~emiscabpo+3~debian1 OpenGL window and compositing mana compiz recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442316: [Pkg-utopia-maintainers] Bug#442316: Xorg hotplugging problems [WAS: Re: Bug#442316: xserver-xorg-input-evdev: evdev from experimental messes up my keyboard layout]
David Nusinow schrieb: On Wed, Oct 24, 2007 at 01:53:40PM +0300, Daniel Stone wrote: On Tue, Oct 23, 2007 at 08:17:10PM -0400, ext David Nusinow wrote: On Tue, Oct 23, 2007 at 10:02:35PM +0300, Daniel Stone wrote: On Tue, Oct 23, 2007 at 08:02:31PM +0200, ext Michael Biebl wrote: Whenever xorg input hotplugging kicks in, the evdev driver is used. The kbd keyboard settings from xorg.conf are ignored and the en_US keyboard layout is used. Yes, this should probably be fixed up, I guess. But the long-term fix is to provide an FDI file in /etc that specifies the keyboard layout. My feeling is the other way around, provided that the X server is the only user of this field. People already know how to edit xorg.conf, and they expect it. Telling them to edit a relatively obscure file among many other fdi's is more painful. There's also userspace tools that exist to help with generating a xorg.conf, but nothing friendly to deal with fdi's. As I've said before, the X server isn't the only user of the field. :) Ubuntu were trying to move to cxkb a year or so ago, and the only thing that stopped them in the end was how huge the XKB codebase was, which I'm fixing (very slowly) upstream. So yeah, if having this in HAL lets us finaly unify console and X keymaps ... Ok, I missed that somehow. So it should probably be hal that generates this and not the xserver? The problem with hal generating the fdi file, would be that it could get out of sync, whenever you run dpkg-reconfigure xserver-xorg. We would also have to duplicate a lot of logic from xserver-xorgs postinst in hal. Generating the fdi file from within xserver-xorg seems to be more straightforward to me. If you are going to remove the input device section (generation) completely from xserver-xorgs postinst and rely completely on hal for that, then I agree hal should be the one and only place where to configure the keyboard/input. Doing the configuration at two places (xserver-xorg-xorg.conf and hal- fdi) will really cause headaches imho. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#442316: Xorg hotplugging problems [WAS: Re: Bug#442316: xserver-xorg-input-evdev: evdev from experimental messes up my keyboard layout]
Julien Cristau schrieb: On Sat, Sep 15, 2007 at 02:15:52 +0200, Michael Biebl wrote: Package: xserver-xorg-input-evdev Version: 1:1.2.0~git20070819-2 Severity: important As you can see from the xorg.conf, I set up a German keyboard layout. After installing evdev from experimental I lost my German keyboard layout (I guess its english, y is z e.g.). Also, my special keys like alt+f1 dont work anymore. Hrm. I'm not sure why evdev is even loaded. Did you enable input hotplug via hal? You were right, Julien. It was because of hal (specifically the file /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi) that the evdev driver was enabled. Whenever xorg input hotplugging kicks in, the evdev driver is used. The kbd keyboard settings from xorg.conf are ignored and the en_US keyboard layout is used. Unfortunately, the evdev driver seems to lack functionality, e.g. my multimedia keys don't work anymore, also, very important, STRG+ALT+F1 is non-functional (maybe this is just a misconfiguration, I don't know. At least the default configuration seems to lack this functionality). It gets even worse, if you try to apply a pc105 keyboard layout over evdev (which can happen if you use GNOMEs/KDEs keyboard selector). Then you not only have missing keys but also some keys are mis-mapped. E.g. the UP key is mapped to PRINT [1]. This really makes it hard to navigate. Since the latest upgrade of hal to 0.5.10, the above fdi file is shipped by default in hal. So several users have already encountered this problem (debian bug #447666, #447676). The question now is, how we proceed from here. I CCed Daniel Stone, maybe he can give us some input on how to solve this, and how we can get xorg hotplugging work correctly. If I understood Daniel correctly, he proposes to set the keyboard layout (probably based on the values from xorg.conf) via a generated fdi file. I'd like to avoid that, because that would complicate things. Preferably, the X server should use the keyboard layout specified in xorg.conf (for the old kbd driver) even when used in xorg hotplugging mode. For the second part (DEs applying a pc105 keyboard layout over evdev) I can't think of a proper solution right now. All I can say is, that I would prefer, if we don't break working setups. In case we can't fix the above issues in a reasonable time frame, I will consider to remove /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi from hal again, at least temporarily. If you say, that this is soon fixable, I would at least raise the severity of the hal bug #447666 to critical, so users of testing will not be affected by this. Feedback and comments welcome, Michael [1] http://lists.freedesktop.org/archives/xorg/2007-October/029202.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#439254: xserver-xorg-video-ati: Does not enable default resolution
Brice Goglin schrieb: On Thu, Aug 23, 2007 at 06:30:55PM +0200, Michael Biebl wrote: upgraded to the latest radeon driver from exp which is said to support tv-out (which I haven't tested yet). I built the driver against the xorg-server from unstable myself, as I didn't want to upgrade all the other components. My panel size (laptop) is 1680x1050. xrandr shows: Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1600 x 1200 VGA-0 disconnected (normal left inverted right) LVDS connected 1280x768+0+0 (normal left inverted right) 0mm x 0mm 1680x1050 60.7 + 1280x800 60.0 1280x768 60.0* 1024x768 60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right) So 1280x768 is chosen by the xserver, although 1680x1050 is my default. The Xorg.0.log says something about the width of my virtual size being to wide. I don't exactly know, what that means and how I can fix that. I can switch to my preferred solution via xrandr -s 1680x1050, but that doesn't work e.g. for gdm. Maybe you can help me, and tell me if I misconfigured something. Anything new about this bug with latest 1:6.7.193-1 in experimental or upstream git ? Yeah, my main display now uses the correct default resolution. I still need the Virtual Option though, when I use a second monitor. That's a different issue I guess, so imho this bug report can be closed. Rock on, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#442316: xserver-xorg-input-evdev: evdev from experimental messes up my keyboard layout
Julien Cristau schrieb: On Sat, Sep 15, 2007 at 02:15:52 +0200, Michael Biebl wrote: Package: xserver-xorg-input-evdev Version: 1:1.2.0~git20070819-2 Severity: important As you can see from the xorg.conf, I set up a German keyboard layout. After installing evdev from experimental I lost my German keyboard layout (I guess its english, y is z e.g.). Also, my special keys like alt+f1 dont work anymore. Hrm. I'm not sure why evdev is even loaded. Did you enable input hotplug via hal? Not that I know of. I actually don't know how to enable input hotplugging via hal. I didn't explicitly enabled it in my xorg.conf (as you can see) so I guess it's a compiled in default. I purged xserver-xorg-input-evdev for now to get a working keyboard back. I'm not sure if xserver-xorg-input-all should depend on evdev until this is fixed. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#442314: xserver-xorg-input-synaptics: Please provide packages for xserver-xorg-core 1.4
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070517-2 Severity: normal Please provide a package suitable for xserver-xorg-core 1.4 / xserver-xorg 7.3. Thanks, Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23-rc6 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-input-synaptics depends on: ii libc6 2.6.1-4GNU C Library: Shared libraries ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxi62:1.1.3-1 X11 Input extension library ii xserver-xorg-core 2:1.4-1X.Org X server -- core server xserver-xorg-input-synaptics recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390901: Bug#390551: compiz: Flickery after resume
Michel Dänzer wrote: reassign 390901 xserver-xorg-video-ati 1:6.6.3-2 reassign 390551 xserver-xorg-video-ati 1:6.6.3-2 kthxbye On Thu, 2007-06-07 at 02:43 +0200, Michael Biebl wrote: Brice Goglin wrote: Hi, Do you still reproduce these rendering problems in compiz after suspend/resume? Even with latest xserver-xorg-core 1.3, compiz 0.5 and drivers? I'm running an up2date sid system and I unfortunately still experience the problem. #390901 should be fixed in xserver-xorg-video-ati in experimental. I can confirm, that with xserver-xorg-video-ati from experimental I have no more problems after suspend-to-(disk,ram). Great, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature