Bug#1004285: [DAViCal-devel] Bug#1004285: fixed in davical 1.1.11-1
Dear Florian, On 18/10/2022 13:01, Florian Schlichting wrote: On Mon, Oct 10, 2022 at 12:46:57PM +0200, Benno Overeinder wrote: Unfortunately the problem persists after updating to davical 1.1.11-1. I see the same messages in the Apache2 error.log as previously reported. looking at your error log from February, I think the crucial part is Fri Feb 18 21:14:58.430957 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: BUG: :DAViCal Fatal Error: [0A000] SQLSTATE[0A000]: Feature not supported: 7 ERROR: set-returning functions are not allowed in CASE... This sounds like https://gitlab.com/davical-project/davical/-/issues/171 The important bit is to make sure that update-davical-database is run from the new package, and that it has replaced the expand_memberships function to not contain a CASE statement any more. Thanks for your email. I updated to php8.1 again and ran the update-davical-database script, and then restarted apache2. At first I saw the same errors, but after rebooting the server, DAViCal worked perfectly as before. Maybe some sticky state in one of the components (postgresql?). Thanks again for your support and maintaining the davical package. Cheers, -- Benno
Bug#1004285: fixed in davical 1.1.11-1
Thank you for your message. Unfortunately the problem persists after updating to davical 1.1.11-1. I see the same messages in the Apache2 error.log as previously reported. I am available to debug and test, as long as I can install packages or other necessary software. -- Benno -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages davical depends on: ii libawl-php0.63-1 ii libdbd-pg-perl3.16.0-1 ii libyaml-perl 1.30-1 ii perl 5.34.0-5 ii php 2:8.1+92 ii php-pgsql 2:8.1+92 ii php-xml 2:8.1+92 ii php8.1 [php] 8.1.7-1 ii php8.1-cli [php-cli] 8.1.7-1+b1 ii php8.1-pgsql [php-pgsql] 8.1.7-1+b1 ii php8.1-xml [php-xml] 8.1.7-1+b1 ii postgresql-client-14 [postgresql-client] 14.5-2 Versions of packages davical recommends: ii php-curl2:8.1+92 ii php8.1-curl [php-curl] 8.1.7-1+b1 ii postgresql 14+243 Versions of packages davical suggests: pn php-ldap | php5-ldap On 04/10/2022 14:34, Debian FTP Masters wrote: Source: davical Source-Version: 1.1.11-1 Done: Florian Schlichting We believe that the bug you reported is fixed in the latest version of davical, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting (supplier of updated davical package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) Format: 1.8 Date: Tue, 04 Oct 2022 13:56:36 +0200 Source: davical Architecture: source Version: 1.1.11-1 Distribution: unstable Urgency: medium Maintainer: Davical Development Team Changed-By: Florian Schlichting Closes: 1004285 1004393 Changes: davical (1.1.11-1) unstable; urgency=medium . * New upstream release(closes: #1004285, #1004393) * Depend on AWL 0.63 * Update copyright years * Declare compliance with Debian Policy 4.6.1 Checksums-Sha1: c549089a0cae8700da529349ea73a11dc5f092b8 2084 davical_1.1.11-1.dsc 06d8180a1c4daa86dcc970e11a3dc594a73968b0 1371432 davical_1.1.11.orig.tar.xz 5b74408b65427baf04a16555b558db3849f5e2eb 13016 davical_1.1.11-1.debian.tar.xz 8a18eba5624bccd5a912e0a9e015caa237c90c3b 7048 davical_1.1.11-1_amd64.buildinfo Checksums-Sha256: e3dee1c549f3a6c4536f8255779dd969ccd227c19f35d17d44f04dd33e675e11 2084 davical_1.1.11-1.dsc 75a6d821d51f9755f41181680466d0352679231b422519d9b4c12d1f52994f51 1371432 davical_1.1.11.orig.tar.xz bf3740bed8b239fb8a4a8f47bde1badd66172d0f199dc4c06b00f57afa08021e 13016 davical_1.1.11-1.debian.tar.xz 2d987e61478d734e8d7b31be27e396452dad9f27edbad7dc80f64f7ed51c4331 7048 davical_1.1.11-1_amd64.buildinfo Files: 8c95ce83fc74592be2f1ef24fc2fbeb8 2084 web optional davical_1.1.11-1.dsc e86053532dcfe8d06f11a9f46c7e66d5 1371432 web optional davical_1.1.11.orig.tar.xz b7a276491c71eeed2a6ea975e5bf3343 13016 web optional davical_1.1.11-1.debian.tar.xz 758834b092283fd179a9de739209e5f8 7048 web optional davical_1.1.11-1_amd64.buildinfo
Bug#1004285: [DAViCal-devel] Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"
Hi Florian, Thank you for your email. I haven't tested it with the git versions of AWL and DAViCal yet, but here is more are more lines from the apache log file. After upgrading (again) to php8, the following lines are in the apache2 error.log. I hope the formatting stays okay. I changed the IP address and username for the caldav.php references to the calendars. Hope this helps. If I have a bit more time, I can try the github version of AWL and DAViCal. [Fri Feb 18 21:13:27.917136 2022] [mpm_prefork:notice] [pid 47871] AH00163: Apache/2.4.52 (Debian) OpenSSL/1.1.1m configured -- resuming normal operations [Fri Feb 18 21:13:27.917271 2022] [core:notice] [pid 47871] AH00094: Command line: '/usr/sbin/apache2' [Fri Feb 18 21:14:15.536261 2022] [mpm_prefork:notice] [pid 47871] AH00170: caught SIGWINCH, shutting down gracefully [Fri Feb 18 21:14:15.642859 2022] [mpm_prefork:notice] [pid 49687] AH00163: Apache/2.4.52 (Debian) OpenSSL/1.1.1m configured -- resuming normal operations [Fri Feb 18 21:14:15.642922 2022] [core:notice] [pid 49687] AH00094: Command line: '/usr/sbin/apache2' [Fri Feb 18 21:14:58.422246 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: ***: ERROR:XML parsing error: Unknown (202) at line 4, column 26 [Fri Feb 18 21:14:58.422288 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: ***: ERROR:Error occurred in:\n\n /caldav.php/username/work/\n /caldav.php/username/home/\n\n [Fri Feb 18 21:14:58.422294 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: ***: ERROR:XML namespace error but tags extracted, trying to continue [Fri Feb 18 21:14:58.430957 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: BUG: :DAViCal Fatal Error: [0A000] SQLSTATE[0A000]: Feature not supported: 7 ERROR: set-returning functions are not allowed in CASE\nLINE 4: ... expanded.g_id FROM (SELECT CASE WHEN $2 > 0 THEN expand_mem...\n ^\nHINT: You might be able to move the set-returning function into a LATERAL FROM item.\nQUERY: \n SELECT group_id FROM group_member WHERE member_id = $1\n UNION\n SELECT expanded.g_id FROM (SELECT CASE WHEN $2 > 0 THEN expand_memberships( group_id, $2 - 1) END AS g_id\n FROM group_member WHERE member_id = $1) AS expanded\n WHERE expanded.g_id IS NOT NULL;\n\nCONTEXT: SQL function "expand_memberships" during startup\nSQL statement "SELECT bit_or(subquery.privileges)FROM\n(\n SELECT privileges FROM grants WHERE by_principal=in_grantor AND by_collection IS NULL\n AND (to_principal=in_accessor OR to_principal IN (SELECT expand_memberships(in_accessor,in_depth)))\nUNION\n SELECT 32::BIT(24) AS privileges FROM expand_memberships(in_accessor,in_depth) WHERE expand_memberships = in_grantor\n) AS subquery"\nPL/pgSQL function pprivs(bigint,bigint,integer) line 14 at SQL statement at /usr/share/awl/inc/AwlDatabase.php:94 [Fri Feb 18 21:14:58.430975 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] = Stack Trace === [Fri Feb 18 21:14:58.430999 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: :Response status 500 for PROPFIND /caldav.php/username/ [Fri Feb 18 21:14:58.431005 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: :* Response Header [Fri Feb 18 21:14:58.431009 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: headers:-->Server: 1.1 [Fri Feb 18 21:14:58.431013 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: headers:-->DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule [Fri Feb 18 21:14:58.431017 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: headers:-->DAV: extended-mkcol, bind, addressbook, calendar-auto-schedule, calendar-proxy [Fri Feb 18 21:14:58.431020 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: headers:-->X-DAViCal-Version: DAViCal/1.1.10; DB/1.3.3 [Fri Feb 18 21:14:58.431024 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: headers:-->Content-type: text/plain; charset="utf-8" [Fri Feb 18 21:14:58.431027 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: : Response [Fri Feb 18 21:14:58.431064 2022] [php:notice] [pid 49689] [client 192.168.1.1:64517] davical: LOG: response:-->DAViCal Fatal Error [Fri Feb 18 21:14:58.725790 2022] [php:notice] [pid 49690] [client 192.168.1.1:64518] davical: ***: ERROR:XML parsing error: Unknown (202) at line 4, column 26 [Fri Feb 18 21:14:58.725814 2022] [php:notice] [pid 49690] [client 192.168.1.1:64518] davical: ***: ERROR:Error occurred in:\n\n /caldav.php/username/work/\n /caldav.php/username/home/\n\n [Fri Feb 18 21:14:58.725820 2022] [php:notice] [pid
Bug#1004385: wireplumber: VLC freezes 20+ seconds before starting
Hi Dylan, On 2/10/22 09:51, Dylan Aïssi wrote: Wireplumber 0.4.8 with a fix for this issue in now available in sid. Could you check if your issue is solved? I updated wireplumber and libwireplumber from sid, and it all works as expected. The issue has been solved with the update. Thanks! -- Benno
Bug#1004385: wireplumber: VLC freezes 20+ seconds before starting
Package: wireplumber
Version: 0.4.7-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: be...@overeinder.net
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After a recent upgrade of wireplumber, vlc freezes for about 20-30
seconds after launch before playing anything. After some searching I
found this issue has been reported on other forums that after upgrading
from 0.4.5 to 0.4.7 the vlc application will freeze for 20-30 seconds
before playing anything.
Here are the URLs to the reported issue:
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/63
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/178
Here a member of the forum reported the following:
I git bisected this problem down to wireplumber commit 6adccbe3
("policy-node: always use the default linkable if default nodes module
is loaded"). Reverting that commit requires first reverting bee9827a
and 23fc4d21. With all 3 reverted, I no longer have any delays when
running VLC.
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wireplumber depends on:
ii init-system-helpers 1.61
ii libc6 2.33-3
ii libglib2.0-0 2.70.2-1
ii libpipewire-0.3-0 0.3.43-2
ii libwireplumber-0.4-0 0.4.7-1
ii pipewire 0.3.43-2
Versions of packages wireplumber recommends:
ii pipewire-pulse 0.3.43-2
wireplumber suggests no packages.
-- no debconf information
Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"
Some additional information. On 24/01/2022 11:58, Benno Overeinder wrote: * What exactly did you do (or not do) that was effective (or ineffective)? I have looked at the apache2 log files and checked the /etc/php and /etc/davical directories if there were any references to php7 instead of php/php8. The apache2 log file reported [Mon Jan 24 11:29:29.678647 2022] [php:notice] [pid 684] [client /IPv6 address/] davical: LOG: response:-->DAViCal Fatal Error The macOS Calendar application warned with the error message: “500” to operation CalDAVAccountRefreshQueueableOperation
Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"
Package: davical Version: 1.1.10-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: be...@overeinder.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am using debian testing. After upgrade to php8 (with all dependencies), my calendar applications/clients on laptop and mobile were unable to contact the davical server. I have also logged into the davical (apache2) server via web browser, and there the user administration web pages seem to work as before. * What exactly did you do (or not do) that was effective (or ineffective)? I have looked at the apache2 log files and checked the /etc/php and /etc/davical directories if there were any references to php7 instead of php/php8. The apache2 log file reported [Mon Jan 24 11:29:29.678647 2022] [php:notice] [pid 684] [client /IPv6 address/] davical: LOG: response:-->DAViCal Fatal Error * What was the outcome of this action? There were no hints or clues for me to further investigate what might be going on. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages davical depends on: ii libawl-php0.62-1 ii libdbd-pg-perl3.15.0-2 ii libyaml-perl 1.30-1 ii perl 5.32.1-6 ii php 2:8.1+92 ii php-pgsql 2:8.1+92 ii php-xml 2:8.1+92 ii php8.1 [php] 8.1.1-4 ii php8.1-cli [php-cli] 8.1.1-4 ii php8.1-pgsql [php-pgsql] 8.1.1-4 ii php8.1-xml [php-xml] 8.1.1-4 ii postgresql-client-14 [postgresql-client] 14.1-5 Versions of packages davical recommends: ii php-curl2:8.1+92 ii php8.1-curl [php-curl] 8.1.1-4 ii postgresql 14+237 Versions of packages davical suggests: pn php-ldap | php5-ldap -- no debconf information
Bug#973052: (unbound unaccountably crashes inside libevent (Assertion nread >= 0 failed in evmap_io_del_))
On Tue, 27 Oct 2020 14:01:13 -0400 Daniel Kahn Gillmor wrote: > I've pushed the patch in #973052 to a new branch named bug-973052 in the > https://salsa.debian.org/dns-team/unbound repo (on top of > branches/1.9.0-2_deb10). > > Hopefully one of the other DNS folks will review it and merge it if it > looks reasonable. Not sure whether we should release a new version with > just this fix, but it might be worth proposing it. Attached is a combined patch of two commits to fix the bug: https://github.com/NLnetLabs/unbound/commit/348cbab016f824a336b65d0091310fe5cd58e762 https://github.com/NLnetLabs/unbound/commit/2b47ca080eb91e209fb86cd1dc90a6aff32e2a1f 5 April 2019: Wouter - Fix to reinit event structure for accepted TCP (and TLS) sockets. 8 April 2019: Wouter - Fix to use event_assign with libevent for thread-safety. And these four for spoolbuf fixes would be nice to have too (not included in the patch): https://github.com/NLnetLabs/unbound/commit/0b77c9d6763686264d44dfd926c8cb4f2f03a43a https://github.com/NLnetLabs/unbound/commit/6067ce6d2b82ce2e80055e578fdfd7ba3e67c523 https://github.com/NLnetLabs/unbound/commit/af6c5dea43fc63452d49b2339e607365b6652987 https://github.com/NLnetLabs/unbound/commit/a08fe8ca609b651c8d8c8379780aad508d492421 Best, — Benno -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/ p1_and_2.diff Description: Binary data
Bug#636303: usbfs: process ... (usb) did not claim interface 1 before use
Some problem here. Debian testing with cups 1.5.0-5 (in the meantime). Use USB to parallel port converter (ATEN UC-1284B) for my old HP LaserJet 2100 printer. Worked before, until the last couple of months with the various CUPS updates. Best, -- Benno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630556: (no subject)
Same problem here with 1.4.7-1 The log file shows messages: usb 3-2: usbfs: process 5042 (usb) did not claim interface 1 before use The printer is a HP LaserJet 2100 connected with a USB-to-parallel port converter. Worked before with cups without problems. Downgrading to 1.4.6-11 did not work for me. Only one job can be printed... Similar to bug report #632630. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#461966: icedove: Confirmation
I experience the same symptom on my system.
As a temporary workaround, you can change the GUI font size by creating
file (also create directory chrome):
.mozilla-thunderbird/.default/chrome/userChrome.css
Instert the following lines in the file:
/* Global UI font */
* {
font-size: 11pt !important;
}
See also /etc/iceweasel/profile/chrome/userChrome-example.css
Next, display font (monosize) is too small. Change message display font:
Edit > Preferences > Display > Formatting > Fonts: monospace size 14
(from 12, which is also default value for iceweasel, but all fonts are
scaled down).
Regards,
-- Benno
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360954: Info received (Denyhosts ignores the allowed-hosts is still in 2.5-2 (testing))
Please ignore previous message. After upgrading, it seemed that two instances of denyhosts were running. After restarting via /etc/init.d/denyhosts restart, only one instance reloaded the config files. The older instance probably still blocked the host which was also in the allowed-hosts file. Excuses for the confusion. -- Benno Overeinder -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360954: Denyhosts ignores the allowed-hosts is still in 2.5-2 (testing)
I still suffer from the bug that denyhosts does ignore the allowed-hosts file. It sends one email indicating that the hostname should not appear in the /etc/hosts.deny file, but after removing the entry and login attempt with a single password mistype, the entry of the host is added again. A normal report message is sent that the host is added (so no indication that it is conflicting with allowed-hosts). -- Benno Overeinder -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352801: xserver-xorg crash with mga driver and glx module
Package: xserver-xorg Version: 6.9.0.dfsg.1-4 Severity: important Hi, After upgrading xserver-xorg from 6.8.2 to 6.9.0, the X server crashes during startup. The graphics card is a Matrox MGA 550. The kernel is the linux kernel as distributed by Debian testing: $ uname -a Linux friendship 2.4.27-2-k7 #1 Wed Nov 30 22:12:04 JST 2005 i686 GNU/Linux The problem of the X server crash seems specific to loading or not loading the glx module. If I comment out "Load glx", the X server starts without problems, of course without any 3D acceleration. With "Load glx" in the xorg.conf file, the X server crashes, leaving my screen blank (black) for all virtual terminals. So not only VT7 is blank, but the graphics card remains in an anomolous state such that all virtual terminals VT1 - VT6 are blank. However, I can type "reboot" in VT1 (if I am logged on the first virtual terminal). A remote log in on the machine shows that no X server or any other X windows program (gdm, gnome, ...) runs. The X server exits with the message: XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. The Xlog.0.log file attached to this report (by reportbug) does not show the error messages generated by the X server _with_ "Load glx" option. I have included the diff of the Xlog.0.log (as included) with the Xlog.0.log.old with the messages of X server crash. The diff with the Xlog.0.log file is: $diff /var/log/Xorg.0.log diff /var/log/Xorg.0.log.old ... 212a213,224 > (II) LoadModule: "glx" > (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so > (II) Module glx: vendor="X.Org Foundation" > compiled for 6.9.0, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 > (II) Loading sub module "GLcore" > (II) LoadModule: "GLcore" > (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.so > (II) Module GLcore: vendor="X.Org Foundation" > compiled for 6.9.0, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 > (II) Loading extension GLX 377c389 < (II) MGA(0): VBE DDC Monitor info: 0x826ce00 --- > (II) MGA(0): VBE DDC Monitor info: 0x8245bc8 596c608 < (++) MGA(0): DPI set to (96, 96) --- > (++) MGA(0): DPI set to (100, 100) 651,726c663,749 < (II) MGA(0): Using 2252 lines for offscreen memory. < (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) < Screen to screen bit blits < Solid filled rectangles < Solid filled trapezoids < 8x8 mono pattern filled rectangles < 8x8 mono pattern filled trapezoids < Indirect CPU to Screen color expansion < Screen to Screen color expansion < Solid Lines < Dashed Lines < Scanline Image Writes < Offscreen Pixmaps < Setting up tile and stipple cache: < 32 128x128 slots < 14 256x256 slots < 5 512x512 slots < (==) MGA(0): Backing store disabled < (==) MGA(0): Silken mouse enabled < (**) Option "dpms" < (**) MGA(0): DPMS enabled < (II) MGA(0): Using overlay video < (WW) MGA(0): Direct rendering disabled < (==) RandR enabled < (II) Initializing built-in extension MIT-SHM < (II) Initializing built-in extension XInputExtension < (II) Initializing built-in extension XTEST < (II) Initializing built-in extension XKEYBOARD < (II) Initializing built-in extension LBX < (II) Initializing built-in extension XC-APPGROUP < (II) Initializing built-in extension SECURITY < (II) Initializing built-in extension XINERAMA < (II) Initializing built-in extension XFIXES < (II) Initializing built-in extension XFree86-Bigfont < (II) Initializing built-in extension RENDER < (II) Initializing built-in extension RANDR < (II) Initializing built-in extension COMPOSITE < (II) Initializing built-in extension DAMAGE < (II) Initializing built-in extension XEVIE < (**) Generic Keyboard: Core Keyboard < (**) Option "Protocol" "standard" < (**) Generic Keyboard: Protocol: standard < (**) Option "AutoRepeat" "500 30" < (**) Option "XkbRules" "xfree86" < (**) Generic Keyboard: XkbRules: "xfree86" < (**) Option "XkbModel" "pc104" < (**) Generic Keyboard: XkbModel: "pc104" < (**) Option "XkbLayout" "us" < (**) Generic Keyboard: XkbLayout: "us" < (**) Option "CustomKeycodes" "off" < (**) Generic Keyboard: CustomKeycodes disabled < (**) Option "Protocol" "ImPS/2" < (**) Configured Mouse: Device: "/dev/input/mice" < (**) Configured Mouse: Protocol: "ImPS/2" < (**) Option "CorePointer" < (**) Configured Mouse: Core Pointer < (**) Option "Device" "/dev/input/mice" < (**) Option "Emulate3Buttons" "true" < (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 < (**) Option "ZAxisMapping" "4 5" < (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 < (**) Configured Mouse: Buttons: 9 < (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE) < (II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD) < (II) Configured Mouse: ps2EnableDataReportin
